Hi Product Hunt, I’m Branden, the creator of Starwind UI. Starwind started as an Astro component library. As the component set grew, I kept running into the same problem: interaction behavior for focus, forms, overlays, and keyboard controls had to stay consistent even when the component syntax changed. For v3, I rebuilt that foundation around one framework-neutral Runtime. Astro and React now have stable first-party adapters backed by the same DOM behavior, while the styled component source still lands in your project for you to inspect and change. Astro and React are stable today. Vue is the next adapter, and development is already well underway. The free MIT-licensed release includes 55 styled components, 36 lower-level primitives, a stable CLI, and a documented v2 migration path. I also built Starwind Skills and an MCP server so coding agents can use current, framework-aware docs instead of guessing from old examples. I’d value feedback on three parts of the release: • Does the source-owned Astro and React model make sense from the homepage? • Do the interaction details hold up in a project you know well? • Does the CLI or migration guide leave you unsure about any step? You can try it with: npx starwind@latest init Thanks for taking a look. I’ll be here to answer questions and fix launch-blocking issues.

Starwind UI

55 accessible components you own for Astro and React

55 accessible components you own for Astro and React