Add Storybook to a project that has no existing setup. Check the stable release to choose the installation tag, use the appropriate package manager, and hand off project-specific configuration to the separate /storybook-setup skill.
Use when adding Storybook to a project that does not have Storybook configured yet.
Review the instructions the agent will receive before you install.
If Storybook is already installed (a storybook dependency in package.json, or a .storybook/ directory), do not install it again: switch to /storybook-setup.
npm view create-storybook version. If it is below 11.0, run npm create storybook@next inside your project's root directory to get the 11.0 alpha; otherwise run npm create storybook@latest. Use the matching package-manager command with the same tag when appropriate, such as pnpm create storybook@next./storybook-setup skill to help the user set up project-specific Storybook configuration, such as the .storybook/preview.ts file.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Find a trial Storybook package for a specific branch, or trigger its publication when needed. Check release progress and obtain the package reference or commands for creating or upgrading a project with that build.
Look up a project's existing UI components in Storybook, including their props, or configuration inputs, and usage examples. Use the findings to answer questions and identify components to reuse before building duplicates.
Review, improve, rewrite, or draft Storybook documentation in /docs. Assess each page’s purpose, audience, structure, and examples, then make suitable edits or provide a content plan, with formatting checks after changes.
Check out a GitHub pull request, fix linting and TypeScript errors, and commit and push the changes. The workflow supports forked pull requests and repeats type checks to verify fixes while keeping changes focused on these errors.
Organize GitHub issues and pull requests found during quality assurance testing. Apply release tracking labels, classify bugs by four severity levels, and label multiple findings while keeping documentation issues and feature requests outside the severity scheme.
Work through unresolved GitHub pull request reviews one at a time. The skill explains each comment, proposes a fix, asks how to proceed, and handles chosen edits, replies, commits, and thread resolution.