Storybook
Overview
Storybook is a UI component workshop for developing, documenting, and testing components in isolation. It supports React, Vue, Svelte, and Angular with Component Story Format (CSF), interactive controls, accessibility auditing, and visual regression testing through Chromatic integration.
Instructions
- When writing stories, use Component Story Format (CSF) with a default export for component metadata and named exports for each variant (Primary, Secondary, Loading, Error, Disabled).
- When making stories interactive, use
args for all dynamic props to enable the Controls panel, and add play functions with @storybook/test for automated interaction testing.
- When adding documentation, use autodocs tag for automatic generation from stories, or MDX files for combining prose with live component examples using doc blocks like
<Canvas>, <Controls>, and <ArgTypes>.
- When testing accessibility, enable
@storybook/addon-a11y which runs axe-core audits on every story automatically.
- When setting up visual regression, integrate Chromatic or Percy for screenshot comparison across PRs, and run
@storybook/test-runner in CI to execute all play functions.
- When configuring globally, set shared decorators (ThemeProvider, RouterProvider) and parameters in
.storybook/preview.ts to apply to all stories.
- When organizing, use sidebar hierarchy with
title: "Components/Forms/Input" and keep stories co-located with components (Button.tsx + Button.stories.tsx).
Examples
Example 1: Build a component library with stories
User request: "Set up Storybook for our React component library with all variants"
Actions:
- Initialize Storybook with
npx storybook@latest init for the React Vite framework
- Write stories for each component with args for variant, size, disabled, and loading states
- Add play functions for interactive components (buttons, forms, modals)
- Configure autodocs for automatic documentation generation
Output: A browsable component catalog with interactive controls and auto-generated docs.
Example 2: Add visual regression testing to CI
User request: "Set up visual testing for our Storybook components in CI"
Actions:
- Install
@storybook/test-runner and configure CI pipeline
- Add
@storybook/addon-a11y for accessibility checks
- Integrate Chromatic for visual regression screenshots on each PR
- Configure the test-runner to execute all play functions in headless Playwright
Output: A CI pipeline that catches visual regressions, accessibility issues, and broken interactions.
Guidelines
- Write at least one story per component variant: default, loading, error, disabled, and empty states.
- Use
args for all dynamic props to enable the Controls panel and story composition.
- Keep stories next to components:
Button.tsx + Button.stories.tsx in the same directory.
- Add play functions for interactive components: buttons, forms, modals, and dropdowns.
- Use decorators for shared context (ThemeProvider, RouterProvider) at the preview level.
- Document design decisions in MDX: when to use each variant, dos and don'ts.
- Run
storybook test-runner in CI to catch broken interactions before merge.
1---2name: storybook3description: Assists with developing, documenting, and testing UI components in isolation using Storybook. Use when writing component stories, setting up visual regression testing, configuring addons, or generating component documentation. Trigger words: storybook, stories, csf, component story format, visual testing, chromatic, storybook addons.4license: Apache-2.05---67# Storybook89## Overview1011Storybook is a UI component workshop for developing, documenting, and testing components in isolation. It supports React, Vue, Svelte, and Angular with Component Story Format (CSF), interactive controls, accessibility auditing, and visual regression testing through Chromatic integration.1213## Instructions1415- When writing stories, use Component Story Format (CSF) with a default export for component metadata and named exports for each variant (Primary, Secondary, Loading, Error, Disabled).16- When making stories interactive, use `args` for all dynamic props to enable the Controls panel, and add `play` functions with `@storybook/test` for automated interaction testing.17- When adding documentation, use autodocs tag for automatic generation from stories, or MDX files for combining prose with live component examples using doc blocks like `<Canvas>`, `<Controls>`, and `<ArgTypes>`.18- When testing accessibility, enable `@storybook/addon-a11y` which runs axe-core audits on every story automatically.19- When setting up visual regression, integrate Chromatic or Percy for screenshot comparison across PRs, and run `@storybook/test-runner` in CI to execute all play functions.20- When configuring globally, set shared decorators (ThemeProvider, RouterProvider) and parameters in `.storybook/preview.ts` to apply to all stories.21- When organizing, use sidebar hierarchy with `title: "Components/Forms/Input"` and keep stories co-located with components (`Button.tsx` + `Button.stories.tsx`).2223## Examples2425### Example 1: Build a component library with stories2627**User request:** "Set up Storybook for our React component library with all variants"2829**Actions:**301. Initialize Storybook with `npx storybook@latest init` for the React Vite framework312. Write stories for each component with args for variant, size, disabled, and loading states323. Add play functions for interactive components (buttons, forms, modals)334. Configure autodocs for automatic documentation generation3435**Output:** A browsable component catalog with interactive controls and auto-generated docs.3637### Example 2: Add visual regression testing to CI3839**User request:** "Set up visual testing for our Storybook components in CI"4041**Actions:**421. Install `@storybook/test-runner` and configure CI pipeline432. Add `@storybook/addon-a11y` for accessibility checks443. Integrate Chromatic for visual regression screenshots on each PR454. Configure the test-runner to execute all play functions in headless Playwright4647**Output:** A CI pipeline that catches visual regressions, accessibility issues, and broken interactions.4849## Guidelines5051- Write at least one story per component variant: default, loading, error, disabled, and empty states.52- Use `args` for all dynamic props to enable the Controls panel and story composition.53- Keep stories next to components: `Button.tsx` + `Button.stories.tsx` in the same directory.54- Add play functions for interactive components: buttons, forms, modals, and dropdowns.55- Use decorators for shared context (ThemeProvider, RouterProvider) at the preview level.56- Document design decisions in MDX: when to use each variant, dos and don'ts.57- Run `storybook test-runner` in CI to catch broken interactions before merge.
eliferjunior