About starwind-pro
starwind-pro is a skill for using Starwind UI v3 Pro blocks in Astro projects. It guides developers through searching, installing, and adapting blocks while accounting for project configuration, access requirements, and accessibility.
Key features
- 01Inspect Astro and Starwind configuration
- 02Search blocks by intent, category, or plan
- 03Install blocks with the specified command
- 04Adapt layout, motion, themes, and accessibility
- 05Check premium block access requirements
Use cases
- 01Choose a suitable block for an Astro page
- 02Configure Pro in an existing Starwind project
- 03Add a block to a route and replace demo content
- 04Check builds and page behavior after installation
MCP support
It can search blocks through the MCP starwind_search tool or the CLI command starwind search --json. The returned install command is used to add a block.
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/starwind-proin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
blocks.mdsetup.mdagents/openai.ymlDetails
From the project READMEStarwind Pro
Starwind Pro builds on Starwind UI v3. Its public blocks remain Astro components installed into the application and customized locally.
Rules
- Confirm an Astro target before selecting a Pro block.
- Treat
starwind.config.jsonas the V3 authority for framework, component destination, registry, Tailwind, and Pro authorization settings. - Initialize missing Starwind UI with
starwind init --framework astro --pro; usestarwind setupfor an existing project. - Search current MCP, CLI, or Pro metadata before naming a block.
- Use the exact returned install command; retain declared component dependencies.
- Preserve the block's responsive layout, container queries, motion and reduced-motion behavior, accessibility, and light/dark theme contract while replacing demo content.
- Distinguish free from premium blocks. Premium blocks require access; availability is metadata.
- Keep
STARWIND_LICENSE_KEYin.env.localor a secret manager and out of code, logs, chat, and handoff text.
Context
Before recommending or installing a block, inspect:
package.json, lockfiles,astro.config.*, and the route/layout being changed.starwind.config.json, configured component directory, installed records, and local exports.- The active Starwind CSS file from config and existing theme conventions.
.gitignorewhen setup may create or update.env.local.
A legacy components.json can contain old Pro registry settings; current setup can import them, but
starwind.config.json wins if the two differ.
Find, Install, Adapt
- For a new project, initialize with
starwind init --framework astro --pro; for an initialized Starwind project, runstarwind setuponce when Pro configuration is missing. - Search by intent/category/plan through current MCP
starwind_searchorstarwind search <query> --json. - Select a result whose plan and dependencies fit the project.
- Run its exact install command from the project root.
- Read every added block and component file.
- Wire it into the intended Astro route using local aliases.
- Replace placeholder content, links, data, and imagery while preserving responsive, container query, animation, accessibility, and theme behavior.
- Run relevant format, typecheck, build, and page/browser checks.
The block task is complete when its source and dependencies are installed in configured locations, placeholder content is resolved, imports build, and access requirements are accurately reported.