Tools· Design & Creative

    Starwind UI

    Open source Astro component library that copies roughly 40 groups and about 193 individual .astro files into the project as owned, freely customizable source code via CLI, without requiring a React runtime, complemented by skills and an MCP server for AI-assisted workflows.

    designingexecutableOpen Source

    Description

    Strengths

    Ownership instead of package dependency
    Components land in the project as owned source code, so styling, functionality, and behavior can be fully customized.
    Broad component coverage
    Roughly 40 component groups with about 193 individual Astro files cover the common interactive UI building blocks, from dialogs to tabs to a color picker.
    Accessibility built in
    The components are keyboard navigable and designed to be screen reader friendly.
    No React requirement
    The stable base works purely with Astro components and vanilla JavaScript, without pulling a React runtime into the project.
    CLI-driven installation
    A dedicated command line interface adds only the components actually needed, along with their dependencies.

    Assessment

    AI features

    • Machine-readable documentation Every documentation page is also available as Markdown, complemented by a generated JSON manifest that AI tools can read directly.
    • Installable agent skills Publicly available Starwind Skills teach compatible AI assistants how to use the CLI, how to compose components instead of copying raw HTML, and how to distinguish free blocks from premium blocks that require Pro access.
    • MCP server A dedicated MCP server connects Starwind UI to Model Context Protocol-capable assistants and complements the skills with direct tool access during a session.

    Suitable for

    • Astro projects that need interactive controls such as dialogs, tabs, dropdowns, or form controls without a React island
    • Teams that want to keep components as owned, freely customizable source code in the project instead of a closed package dependency
    • AI-assisted development workflows that should access current component documentation directly through skills or MCP
    • Less suitable for Less suitable for finished marketing page sections such as hero areas or pricing tables; the Starwind Pro extension or a dedicated block library is the better starting point there.

    Limitations and notes

    • React support still in beta The Astro core is stable; the cross-framework runtime adapter for React is, according to the project documentation, currently in the beta channel.
    • Copy multi-part components as a unit Components such as the dropdown consist of several files that belong together; partial manual copying leads to missing dependencies.
    • Initialization required before first use Without the one-time init step, adding individual components through the CLI fails.
    • Starwind Pro is a separate offering The more than 200 ready-made marketing blocks are a separate offering with free and premium blocks that require Pro access, and are not part of the free base library.
    • No finished page sections Anyone looking for complete marketing sections rather than individual controls will not find a counterpart in the free library.

    Quick start

    1. Create a new Astro project or use an existing one.
    2. Run `npx starwind@latest init` once through the command line and confirm the base configuration.
    3. Add individual components such as dialog, tabs, or select with `npx starwind@latest add <component>`.
    4. Open the generated source code in the project folder and adjust styling or behavior directly as needed.
    5. For multi-part components, check that all associated files were fully adopted.

    Tips

    • Always run the init step before adding the first component, otherwise the CLI fails.
    • For marketing page sections rather than individual controls, consider a dedicated block library or the Starwind Pro extension.
    • Always adopt multi-part components in full; the component folder is the unit.
    • For AI-assisted workflows, wire in the published skills or the MCP server instead of only consulting the documentation manually.

    Access

    Last reviewed: · Pricing, plans and features are a snapshot in time. Check the provider's own page before deciding.

    In the workshop this becomes your method.

    Whoever sees this process run once wants the agent behind it next. We build that in the workshop From Process to Agent.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call