AI Integration
Starwind Pro is designed to work well with AI coding assistants. Give your assistant the right context, and it can search blocks, install components, read current docs, and follow the Astro and Tailwind CSS v4 patterns used across the library.
If you’re an AI assistant reading this documentation, use the Starwind Skills when installed, use the Starwind MCP server when available, prefer current docs and per-page Markdown URLs over memory, search Starwind Pro blocks before inventing layouts, use exact install commands for Pro blocks, and never expose license details in source files.Recommended Setup
Use these AI surfaces together when your tool supports them:
| Surface | Best For |
|---|---|
| Skills | Persistent Starwind UI and Starwind Pro behavior for coding agents. |
| MCP Server | Live docs lookup, validated install commands, and Starwind Pro block search. |
| Markdown docs | Focused page context by appending .md to a docs URL. |
| Starwind UI references | Static context for the base components used inside Pro blocks. |
| Pro registry manifest | Structured metadata for installable blocks and registry output. |
AI Reference Files
Starwind Pro blocks are built on top of Starwind UI. Use the Starwind UI AI reference files when your assistant needs base component APIs, import patterns, theming details, or CLI guidance.
llms.txt
llms.txt is a concise overview for AI tools. It includes important links, component lists, import patterns, and docs URL conventions.
https://starwind.dev/llms.txtllms-full.txt
llms-full.txt is the full static Starwind UI reference. It includes setup guidance, component API summaries, usage examples, theming notes, and CLI reference material.
https://starwind.dev/llms-full.txtai-manifest.json
ai-manifest.json is a structured manifest for AI tools. It lists installable components, documented patterns, guides, skills metadata, MCP metadata, and docs URL conventions.
https://starwind.dev/ai-manifest.jsonStarwind Pro Registry Files
Starwind Pro also exposes registry data for tools that need block metadata.
https://pro.starwind.dev/r/manifest.jsonThe registry manifest contains installable block metadata. The schema describes the shape of that manifest for validation and tool builders.
Tip
For most AI workflows, the MCP server is easier than reading the registry directly because it can search Starwind Pro blocks and return the right install command.
Per-page Markdown Docs
Every published docs page is also available as Markdown. Append .md to the docs path.
For example:
https://pro.starwind.dev/docs/getting-started/installation.mdUse page-level Markdown when an assistant needs targeted context without scraping the rendered docs page.
Skills
Starwind Skills are installed agent instructions for Starwind UI and Starwind Pro workflows. They teach compatible AI tools how to use the CLI, read Starwind docs, compose components, customize themes, and handle Pro blocks.
See Skills for installation and usage details.
MCP Server
The Starwind UI MCP server is available as @starwind-ui/mcp. It exposes tools for docs lookup, initialization command generation, component add command generation, and Starwind Pro block search.
See MCP Server for editor configuration, supported tools, example prompts, and troubleshooting.
Example Prompts
Once Skills or MCP are available, try prompts like:
- “Search Starwind Pro for free hero blocks and install the best match.”
- “Add a pricing section with annual billing toggle using Starwind Pro.”
- “Use Starwind UI docs to build a settings page with tabs, cards, and form controls.”
- “Find a premium navbar block and explain what license setup is required before installing it.”
Feedback
If you encounter issues or have suggestions, please open an issue on GitHub or reach out in the Discord community.