Skills

# Skills

Starwind Skills give AI assistants project-aware guidance for Starwind UI. When installed, compatible
agents know how to find docs, use the Starwind CLI, compose components, customize themes, and work
with Starwind Pro blocks using the right conventions for Astro and Tailwind CSS v4.

The public skills live in [starwind-ui/skills](https://github.com/starwind-ui/skills).

For example, you can ask your AI assistant to:

- "Add a searchable select to this Astro form."
- "Use Starwind UI to build a settings page with tabs and cards."
- "Adapt these shadcn-style theme tokens to Starwind UI."
- "Find a free Starwind Pro pricing block for this landing page."

## Install

```bash
npx skills@latest add starwind-ui/skills
```

This installs the current public Starwind skills from GitHub. Learn more about skills at
[skills.sh](https://skills.sh).

## What's Included

### Starwind UI

The `starwind-ui` skill applies when an agent is working with Starwind UI components, Astro projects,
Tailwind CSS v4, `starwind.config.json`, theme tokens, dark mode, shadcn-style theme migration, or
component requests such as Combobox.

It guides agents to:

- Prefer `npx starwind@latest init`, `npx starwind@latest add`, and other documented Starwind CLI
commands.
- Read current Starwind docs through docs URLs, Markdown pages, `llms-full.txt`, the CLI, or MCP when
available.
- Compose existing Starwind components instead of injecting raw copied HTML.

### Starwind Pro

The `starwind-pro` skill applies when an agent is discovering, installing, or adapting Starwind Pro
blocks.

It guides agents to:

- Distinguish free blocks from premium blocks that require Starwind Pro access.
- Use the exact block install command returned by the docs, CLI, or MCP.
- Respect Pro setup requirements before installing Pro blocks.
- Avoid exposing license details in source files.

## How It Works

1. The skill activates when an agent is working in a Starwind UI or Starwind Pro context.
2. The agent reads the local project shape, including `package.json`, Astro config, Starwind config,
installed components, theme CSS, and import aliases.
3. The agent uses current Starwind context from docs, Markdown pages, `llms-full.txt`, the CLI, or the
MCP server before generating code.
4. The agent follows Starwind-specific composition rules, such as using `class` and `for` in Astro,
composing loading buttons with `Spinner`, and using `SelectSearch` for searchable selects.

## Skills And MCP

Skills and MCP solve different parts of the workflow:

| Surface | Use it for |
| --- | --- |
| Skills | Persistent agent behavior, Starwind-specific rules, and project editing guidance. |
| MCP Server | Live tool calls for docs lookup, component commands, project context, customization docs, and Pro block discovery. |
| Markdown docs | Focused page-level context by appending `.md` to the docs path. |
| `llms-full.txt` | Full static docs context when an agent cannot call MCP tools. |

Use both Skills and [MCP](/docs/getting-started/mcp/) when your agent supports them. Skills teach the
agent how to behave; MCP gives it current Starwind data and actions.