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.
Look up the components of a project with Storybook, with their props and usage examples, to answer questions about them or to reuse them instead of building duplicates. Use when the project's agent instructions (such as AGENTS.md) or the user ask for it. For a UI change, use ui-workflow, which includes the same component lookup.
component-docs looks up a project's UI components to answer questions about their use and find components you can reuse. It checks Storybook for the component list, props—the inputs used to configure components—and usage examples. These findings help you decide whether an existing component meets your needs before creating a similar one.
Use it when joining a project and learning which components are available. It also helps you check which settings to pass to a component, see concrete usage examples, or find something suitable for a screen you are about to build.
Storybook lookup requires version 11.0 or later, including qualifying prereleases and canary builds. If Storybook is missing or older, the skill reads component source files instead. Upgrades require user approval. For work that changes the UI itself, use ui-workflow, which includes the same component lookup.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Prerequisites:
11.0.0-alpha.x) or a canary build (0.0.0-pr-*) also counts. If it is older, invoke the /storybook-upgrade skill only after the user explicitly approves an upgrade; until then, read the components' source files instead.Run every Storybook CLI command from the package where Storybook is installed (in a monorepo often a leaf package such as packages/ui).
If the sandbox blocks network access, request escalated permissions for Storybook CLI commands.
Run npx storybook skills component-docs and follow its output: it lists the commands that show this project's components, props, and usage examples, and when to use them.
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.
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.
Add Storybook to a project that does not have it configured, choosing the installation tag based on the latest stable version. Then use the separate setup skill to configure Storybook for the project.