fec-storybook-component-doc
Installation
SKILL.md
Storybook component documentation
Purpose
Establish documentation, design system display and isolated state preview environment for UI components; interaction and visual testing only cover component states within the Storybook scene.
Procedure
- Initialize or identify an existing Storybook configuration, inheriting the project framework adapter, stories globs, themes, and build commands.
- Each component's Story covers default state, main variant, size, semantic tone, disabled, loading, error, empty, selected, invalid and key edge states.
- Components that rely on Router, Store, i18n, and ThemeProvider are wrapped with decorators and do not copy the application entry in Story.
- Use MDX to supplement complex components with usage instructions, Props, slots/children, variant matrices, status examples, accessibility requirements and source code display.
- When automation is required, connect interaction tests, addon-a11y, Chromatic or Storybook Test Runner; these capabilities serve component documentation and design system display and do not undertake cross-page business journeys.
- Design system components should record token sources, Tailwind/class variants, dark modes, responsive sizes, and unsupported combinations to avoid consumers guessing at assembly.
Detailed reference
- Load references/story-patterns.md when you need
main.ts,preview.ts, stories, decorators, MDX, interaction tests and visual regression examples.