What are the best Storybook skills for Claude Code?

Storybook stories are the tests developers skip: every component should ship with them, and agent-written code rarely does. A Storybook skill fixes the defaults, and the catalog's leader is storybook from dalestudy at 808 installs (skills.sh registry).

Key takeaways

• storybook from dalestudy/skills is the most-installed Storybook skill at 808 installs (skills.sh registry, July 2026).
• thebushidocollective's han suite is the deepest coverage: storybook-story-writing (602 installs), component documentation (155), play functions (111), and args/controls (85) as separate, composable skills.
• Interaction testing is covered: storybook-testing (125 installs) turns stories into a test suite.
• Setup has its own skill: storybook-setup (208 installs) for fresh installs and configuration.
• Stories are the documentation layer of a component library; the design systems hub and best skills for frontend design rank the surrounding stack.

Why use a skill for Storybook instead of just prompting?

Because story quality is conventions all the way down, and the agent does not know yours. Unguided, Claude Code produces Storybook 6-era CSF2 syntax, skips args typing, and writes one default story per component. A Storybook skill pins the format (CSF3, typed meta, autodocs), the coverage expectations (variants, edge states, interaction tests), and the naming scheme. The catalog lists a dozen Storybook-specific skills; the top four alone account for over 2,100 installs (skills.sh registry, July 2026). That granularity matters for adoption: a skill that matches your existing conventions gets kept, while a generic one gets uninstalled the first time it rewrites a story file your team already liked.

What is the best Storybook skill overall?

storybook from dalestudy/skills leads at 808 installs (skills.sh registry). It is the generalist option: story structure, CSF3 conventions, and decorator patterns in one skill, which makes it the right first install for a repo that has Storybook but no story discipline.

npx skills add dalestudy/skills

Strong alternatives: storybook-story-writing (602 installs) goes deeper on authoring specifically, and storybook from mindrally (585 installs, 181 GitHub stars) is a close third with its own take on story organization. The wider component-workflow field is ranked at best skills for frontend design.

Which skills cover Storybook testing and play functions?

Two, and they compose. storybook-play-functions (111 installs, skills.sh registry) teaches the play-function pattern: user interactions scripted inside the story so every variant doubles as an integration test. storybook-testing (125 installs, from the 200-star orchestkit repo) wires those stories into a runnable test workflow. Together they push Storybook from a visual catalog into the test layer, which pairs naturally with the picks in best skills for testing and review.

Is there a skill for documenting components?

Yes: storybook-component-documentation (155 installs, skills.sh registry) covers autodocs, MDX pages, and prop documentation, and storybook-args-controls (85 installs) makes generated stories interactive through properly typed args. The han suite's granularity is deliberate: each skill loads only when its topic comes up, so installing all five costs nothing until triggered. Storybook's own docs define the underlying formats.

How do you set Storybook up in a new project?

With storybook-setup (208 installs, skills.sh registry), which handles installation, framework config, and addon selection. Build-tool variants exist too: storybook-rsbuild (104 installs) is the rstack team's first-party path for Rsbuild projects. After setup, the design-side skills in the frontend and design category keep the components themselves worth documenting.

A complete starter stack

• storybook (808 installs): the generalist baseline for story structure and CSF3.
• storybook-story-writing (602 installs): deeper authoring conventions per component variant.
• storybook-testing (125 installs): stories as an executable test suite.
• storybook-setup (208 installs): only for repos starting from zero.

Common pitfalls

• Accepting CSF2 output: unguided agents still generate the old format; a story skill pins CSF3 with typed meta.
• One story per component: the value is in variants and edge states; the authoring skills enforce that coverage.
• Treating stories as decoration: without play functions they document but never verify; add the testing layer early.

Install the baseline skill, add testing when stories exist, and component documentation stops being the chore that never ships.

Common questions