storybook-development
Installation
SKILL.md
Storybook development
Each story renders one production component. A page or section can compose many children internally. The app and
Storybook import that same page or section. When starting from a design before the route exists, implement the component
in production source first and preview it from a colocated *.stories.tsx file. The route can then import it directly.
| When working on | Read |
|---|---|
| Translating a design, covering a route, or choosing what to render in isolation | Pages, sections, and controls |
| Supplying routing, providers, app styling, network data, or clean state | Preview environment and data |
| Stressing a design, selecting scenarios, or configuring visual coverage | Scenarios and visual modes |
Use react-components for component boundaries, hooks, state ownership, and source
layout. Use test-quality when deciding what a play function should exercise or assert. Use
MSW for request handler APIs. Match the project's installed Storybook framework, CSF format,
decorators, and visual runner.