Storybook

Keep stories as accurate, reviewable examples of the public component contract. Read the project's Storybook setup and nearby stories before writing or updating one.

Workflow

1. Locate the component and its affected stories. Treat creating a component or changing its public contract as a Storybook update trigger.
2. Classify the title as Components, Foundations, or Compounds.
3. Define typed meta and stories with autodocs, useful controls, and representative args.
4. Cover each meaningful visual variant and state without inventing unsupported behavior.
5. Update removed or invalid args, controls, union options, and affected stories when props or types change.
6. Run the narrowest available Storybook, type, and lint checks.

Requirements