storybookjs/storybook's Claude Code Plugin for Users and Contributors
By Flowy · Updated 2026-08-28
The storybookjs/storybook plugin packages 18 Claude Code skills plus one MCP server, storybook-mcp, taken from the Storybook project's own repository. A handful, including init, storybook-setup, upgrade, and stories, help add, configure, or maintain Storybook in your own project. Most of the rest are the Storybook team's own tooling for managing pull requests and releases on their codebase.
What is the storybookjs/storybook plugin?
storybookjs/storybook is the source repository for Storybook itself, described in its own summary as "the industry standard workshop for building, documenting, and testing UI components in isolation" (90,934 GitHub stars). Flowy indexes 19 components straight out of that repository: 18 skills and a single MCP server, storybook-mcp. None of this is a separate wrapper built around Storybook. It is the automation the Storybook team keeps inside its own codebase, for its own contributors, plus a smaller set that any team adding Storybook to a project can put to use.
Who actually gets value from these skills?
Read the skill names as two audiences before installing anything. One set is written for someone working on their own app: adding Storybook, wiring up a preview, generating stories, or running an upgrade. The other, larger set is written for people who work on the storybookjs/storybook repository itself: cutting releases, moving a pull request through review, and running the project's own QA process. If you do not have that repository checked out and are not contributing to Storybook's own source, the second set will not come up for anything you do.
Which skill adds Storybook to a project that does not have it yet?
init and storybook-init carry the exact same description in the fact pack: use it when adding Storybook to a project that does not have Storybook configured yet. Two names, one job, aimed at a project with no Storybook install at all. Once Storybook exists, upgrade takes over, described as for use when Storybook exists but needs an upgrade. A second skill, storybook-upgrade, has no description of its own in the fact pack, though its name pairs it with the same job.
What handles day to day story and style work?
storybook-setup and setup are also a matched pair, both described as for when Storybook is already installed and someone wants a working preview configuration and stories for real components. That is the skill for turning a bare install into actual coverage of your components.
stories is the broadest skill in the set. Its description says to invoke it first, before creating, editing, or deleting components, stories, styles, CSS, themes, colors, or design tokens, and also for starting or previewing Storybook, or for requests to show, browse, or list components. In practice that makes it the gate for anything that changes how a UI looks, not a narrow story generator.
rebuild-restart-storybook has no description in the fact pack, and neither the pack nor Storybook's public repository page says whether it targets your own project's dev server or the Storybook team's own internal instance. Its name is the only fact available, so treat its exact audience as unconfirmed rather than assume either way.
What are the release and pull request skills for?
minor-release and canary name the storybookjs/storybook project's own release process. open-pr, pr, update-pr-description, handle-pr-comments, and fix-linting-types-on-pr cover stages of a pull request against that repository. github-qa-labels applies QA labels on GitHub issues or pull requests, docs-review reviews documentation changes, and storybook-startup-benchmark measures Storybook's own startup performance. Every one of these carries only a broken internal file reference in place of a description in the fact pack, so this guide is naming the domain each skill points to, not the exact steps it runs. None of them will fire for work on your own codebase, since they are scoped to the storybookjs/storybook repository itself.
What does storybook-mcp do?
The fact pack lists storybook-mcp as an MCP server with no description attached, and Storybook's public repository page does not explain it either. What is confirmed is that it exists as an MCP component inside storybookjs/storybook. What it exposes to an MCP client is not something this guide can state without guessing, so treat its exact behavior as unconfirmed until you have read its own source.
Should I install this plugin?
That depends on which half of it you need. If you are adding Storybook to a project, wiring up a preview and starter stories, or running an upgrade, the small skill set above covers that job, and stories is the one to reach for on any later styling or design token change. If you are not a contributor to the storybookjs/storybook GitHub repository, the release and pull request skills will simply sit unused. Install it from the listing page linked at the top of this guide. Flowy indexes this plugin from its public repository; it does not own, bundle, or host any part of it.
Common questions
- What is the storybookjs/storybook Claude Code plugin?
- It packages 18 skills and one MCP server, `storybook-mcp`, taken directly from the Storybook project's own GitHub repository. A handful of the skills, such as `init` and `stories`, help you add or maintain Storybook in your own project, and most of the rest are the tooling the Storybook team uses to manage its own pull requests and releases.
- Which skill adds Storybook to a project that does not have it yet?
- `init` and `storybook-init` share the exact same description in Flowy's fact pack: use it when adding Storybook to a project that does not have Storybook configured yet. They point to the same job under two names. Once Storybook is installed, `upgrade` or `storybook-upgrade` covers moving to a newer version.
- What does the stories skill do in this plugin?
- `stories` is described as the skill to invoke first, before creating, editing, or deleting components, stories, styles, CSS, themes, colors, or design tokens. It also covers starting or previewing Storybook and requests to show, browse, or list components. It is the broadest of the 18 skills in this plugin, not a narrow story generator.
- Are the storybookjs/storybook skills meant for my own project, or for the Storybook team?
- Both. A small set, including `init`, `storybook-init`, `storybook-setup`, `setup`, `upgrade`, `storybook-upgrade`, and `stories`, is for anyone adding or maintaining Storybook in a project. The rest, such as `minor-release`, `canary`, `open-pr`, `pr`, `handle-pr-comments`, and `github-qa-labels`, are process skills for people contributing to the storybookjs/storybook GitHub repository itself, and will not do anything for your own codebase.
- What does the storybook-mcp server do?
- Flowy's fact pack does not carry a description for `storybook-mcp`, and Storybook's public repository page does not explain it either. It is confirmed to exist as an MCP-type component in the storybookjs/storybook repository, but what it exposes to an MCP client is not documented anywhere Flowy could check, so treat its exact behavior as unconfirmed.