32 skills (repositories by storybookjs) · sorted by popularity
Find reusable UI components in Storybook, create or update stories that show their states, run story tests, and publish a curated review so others can inspect the results of UI changes.
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.
Prepare a CHANGELOG.md entry for a Storybook minor or major release. Collect changes from prereleases, filter out changes already backported to patch releases, select significant highlights, and combine them with the full change list.
Create a draft pull request from the current branch using the project’s template. The skill checks changes, detects the base branch, gathers label choices, and prepares a title, description, and testing details.
Rebuild modified packages in the Storybook monorepo and restart its internal UI after code changes. The workflow provides the running URL and can optionally create a UI review of stories related to the changes.
Measure Storybook startup from launching the process to displaying the first story. Separate server readiness from browser rendering, summarize repeated runs, and compare versions or feature flags to investigate slower startup.
Upgrade an existing Storybook installation to version 11.0 or later using the official upgrade guide. If the latest stable release is below 11.0, the skill uses the 11.0 alpha, a prerelease version.
Update all Storybook packages in a project to a chosen release or canary, an early development build. Use it to test changes in external apps, reproduce bugs, and keep package versions aligned while handling peer dependencies.
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.
Review Storybook's minimum supported browser versions using Plausible documentation traffic data. The skill presents usage evidence and proposed versions for approval, then updates pinned settings and documentation and opens a pull request with the recorded decision.
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.
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.
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.
Turn repeated corrections into automated safeguards, such as code checks, metadata flags, or scripts. This skill helps choose where each lesson belongs and turns recurring mistakes into concrete changes or actionable tasks.
Upgrade an existing Storybook installation to version 11.0 or later using the official upgrade instructions. When the latest stable release is below 11.0, the skill directs the agent to use the 11.0 alpha release.
Set up an existing Storybook installation with a working preview file and stories that display real components. The skill checks prerequisites, then uses Storybook’s setup command and the instructions it provides.
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.
Check a pull request’s title and description against its commits and code changes. Identify missing major changes or outdated claims, propose accurate wording, and apply agreed updates while following the repository’s existing template.
Set up a working preview file and stories, examples showing real components, in an existing Storybook project. Check the installed version first, then follow the setup instructions produced by Storybook’s command.
Create a draft pull request for reviewing Storybook changes. Prepare a title, required labels, and a description using the repository template, including verified manual testing steps that another maintainer can follow.
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.
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.
Create and edit React Native Storybook stories using Component Story Format (CSF). Use when writing .stories.tsx files, adding stories to React Native components, configuring Storybook addons (controls, actions, backgrounds, notes), setting up argTypes, decorators, parameters, or working with portable stories for testing. Applies to any task involving @storybook/react-native story authoring.
The English summary is being prepared. Showing the original description.
Incrementally upgrade React Native Storybook across the supported migration paths. Use when upgrading `@storybook/react-native` projects from 5.3.x to 6.5.x, 6.5.x to 7.6.x, 7.6.x to 8.3.x, 8.x to 9.x, or 9.x to 10.x. Detect the currently installed Storybook version, choose only the next migration step, update dependencies and config, regenerate `storybook.requires`, convert remaining `storiesOf` stories to CSF during the `6.5.x -> 7.6.x` upgrade, and stop after a single version hop instead of jumping multiple major versions at once.
The English summary is being prepared. Showing the original description.