Terminal
Terminal/Skill
Guides UI changes and story writing in Storybook 11 or later projects, keeping stories in sync with components.
By Storybook
Works with
npx skills add storybookjs/storybook --skill storiesPrerequisites:
/storybook-init skill to set up Storybook, but only if the user explicitly invoked this skill and approves a Storybook installation.11.0.0-alpha.x) or a canary build (0.0.0-pr-*) also counts. Treat a request to set up or install Storybook as approval to perform any required Storybook upgrade. For other requests, invoke the /storybook-upgrade skill only after the user explicitly approves an upgrade.Run the Storybook dev server and every Storybook CLI command from the same working directory: the package where Storybook is installed (in a monorepo often a leaf package such as packages/ui).
If the sandbox blocks network access or ports, request escalated permissions for Storybook CLI commands; otherwise the dev server can fail in confusing ways (for example, it finds no free port to bind to).
For docs, props, or usage questions, use npx storybook tools docs list followed by npx storybook tools docs show --id <id> before inspecting source files. Fall back to source inspection only when the documentation commands are unavailable or return no relevant documentation.
Run npx storybook skills stories and read the output in its entirety to get the mandatory, ordered workflow for working on UI changes, writing stories, and keeping stories in sync with every frontend component you create, modify, or delete. This workflow explains how to write stories, preview stories, and display a curated Storybook review.
Some commands require a running Storybook dev server:
http://localhost:6006) instead of starting a second one. Otherwise start one in the background, using the project's preferred package manager and existing package.json Storybook script (e.g. npm run storybook) instead of inventing a new command whenever possible. Wait until the URL responds before running commands that need it.