Starwind 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.json as the V3 authority for framework, component destination, registry, Tailwind, and Pro authorization settings.
• Initialize missing Starwind UI with starwind init --framework astro --pro; use starwind setup for 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_KEY in .env.local or a secret manager and out of code, logs, chat, and handoff text.