Skip to main content
Clementine DS includes a live Storybook sandbox with stories for every component and every interaction state. Every paint you see in the sandbox traces back to a component-tier token — there are no hardcoded values in the stories or the components they render. Live Storybook: clementine-ds-storybook.vercel.app

Run Storybook locally

Clone the repo, install dependencies, and start the dev server:
Storybook starts at http://localhost:6006. Hot reload is on by default.

What the sandbox contains

The sandbox covers all 10 components, each with a story per interaction state.

The contract between specs and stories

Every state listed under interaction_states: in a component spec must have a corresponding Storybook story. This is a hard gate — a component cannot be promoted to AI-Ready status until all stories exist. For Button, the spec declares:
All six states have stories in apps/storybook/stories/Button.stories.tsx. The AI-Ready gate checks this correspondence mechanically.

Example story structure

Stories live in apps/storybook/stories/<Component>.stories.tsx. Here is the structure for Button:
Each named export is one story. Each story corresponds to one row in the component spec’s interaction_states list. Add a state to the spec, add a story to the file.

Promoting a component to AI-Ready

Before you set status: AI-Ready in a component spec, confirm:
  1. Every entry in interaction_states: has a named export in the component’s .stories.tsx file.
  2. The story renders correctly in the live sandbox (run pnpm storybook and check).
  3. checks.states_complete: true in the spec frontmatter.
A component with missing stories fails the ai-ready-gate validation rule.

Auto-deploy

Storybook auto-deploys to clementine-ds-storybook.vercel.app on every push to main after CI passes. You do not need to trigger a manual deploy. Push your branch, merge, and the live sandbox reflects your changes within minutes.