91k stars · MIT · v10.6.0 (2026-09-02)
Every component rendered on its own, in every state, including the states you never remember to open.
▶Repo detailsthe review · specs · pros & cons · install
What it is
A workshop that renders each interface component on its own, outside the running app, in all of its variants. It builds to a static website you can open, host or send to somebody.
Why it matters
The characteristic failure of a solo-built product is not the happy path — it is the empty state, the error state and the state where a Russian label is forty percent longer than the English one and breaks the row. You never see those, because you only ever open the screen with your own good data in it. Storybook makes looking at them deliberate rather than accidental. There is a second, marketing-shaped payoff: the built output is a living style guide, which is the thing you point a freelancer or a future collaborator at instead of writing an explanation. Honest warning — this is overhead, and it pays only if you actually write the stories.
- Forces the empty, error and overflow states into view before a user finds them.
- The static build doubles as documentation of how the product is meant to look.
- Pairs naturally with shadcn/ui (#1) — one story per component you copy in.
- Genuine overhead: every component needs a story file written and then kept current.
- A third build toolchain beside Astro and the app itself.
- The common outcome is a Storybook that goes stale within a month and then misleads.
There is a second, marketing-shaped payoff: the built output is a living style guide, which is the thing you point a freelancer or a future collaborator at instead of writing an explanation.
npx storybook@latest init
