upgrading-react-native-storybook — Claude Code skill
upgrading-react-native-storybook guides step-by-step upgrades for React Native Storybook across versions 5.3.x through 10.x. It executes exactly one migration hop per run to prevent broken setups.
MIT 334 installs ★ 1,329 updated 2026-10-24
npx skills add storybookjs/react-native --skill upgrading-react-native-storybook -a claude-codeWhat upgrading-react-native-storybook does
The skill inspects project files before editing anything. It reads Storybook dependencies in package.json, checks whether the setup uses .storybook/ or .rnstorybook/, and identifies imports in Metro config. It also detects the package manager and target environment, including Expo, Expo Router, React Native CLI, or Re.Pack.
Upgrades run strictly one step at a time across supported paths between 5.3.x and 10.x. Skipping major versions in a single prompt is blocked by design. When moving from 6.5.x to 7.6.x, it converts remaining storiesOf calls into Component Story Format (CSF). The workflow updates configs, regenerates storybook.requires, and runs available test scripts before reporting the next hop.
What it helps with
- upgrade React Native Storybook safely between adjacent major releases
- convert legacy
storiesOfsyntax into CSF format - regenerate
storybook.requiresafter dependency changes - adjust Metro configuration for newer Storybook packages
Example prompts for the agent
- Check our current Storybook setup and run the next migration step
- Upgrade Storybook from 6.5 to 7.6 and convert remaining storiesOf calls to CSF
- Update Storybook dependencies to the next version and regenerate storybook.requires
How to install upgrading-react-native-storybook
1Skills CLI (Vercel)
npx skills add storybookjs/react-native --skill upgrading-react-native-storybook -a claude-code2Manually: put the files in place
~/.claude/skills/upgrading-react-native-storybook/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/upgrading-react-native-storybook/
1Skills CLI (Vercel)
npx skills add storybookjs/react-native --skill upgrading-react-native-storybook -a codex2Manually: put the files in place
.agents/skills/upgrading-react-native-storybook/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add storybookjs/react-native --skill upgrading-react-native-storybook -a cursor2Manually: put the files in place
.cursor/skills/upgrading-react-native-storybook/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install storybookjs/react-native skills/upgrading-react-native-storybook2Manually: put the files in place
.github/skills/upgrading-react-native-storybook/SKILL.md1Skills CLI (Vercel)
npx skills add storybookjs/react-native --skill upgrading-react-native-storybook -a gemini-cli2Platform CLI
gemini skills install https://github.com/storybookjs/react-native --path skills/upgrading-react-native-storybookManually: put the files in place
.devin/skills/upgrading-react-native-storybook/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add storybookjs/react-native --skill upgrading-react-native-storybook -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about upgrading-react-native-storybook
How to install upgrading-react-native-storybook in Claude Code?
Run npx skills add storybookjs/react-native --skill upgrading-react-native-storybook -a claude-code. The file is saved at ~/.claude/skills/upgrading-react-native-storybook/SKILL.md.
What does upgrading-react-native-storybook do?
It inspects your React Native Storybook dependencies, detects the current version, and performs a single migration step. It adjusts Metro configurations, formats, and generated files.
Can it upgrade directly from version 6 to 9 at once?
No, multi-major jumps in one pass are disallowed. You must run each release step individually, verify the build, and then trigger the next migration.
Source text
SKILL.md · MIT
--- name: upgrading-react-native-storybook 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. --- # React Native Storybook Upgrades Upgrade one supported version step at a time. Do not jump from an older major directly to the latest release in a single pass. ## Rules - Detect the project's package manager first and use it consistently. - Detect the currently installed Storybook version from `package.json`, lockfiles, and config files before editing anything. - Apply exactly one migration step per run. If a project is multiple versions behind, complete the next hop, verify it, and then report the next required hop. - During the `6.5.x -> 7.6.x` step, convert any remaining `storiesOf` stories to CSF instead of preserving compatibility mode. - Preserve the project's existing app structure. Only make the migration changes required for the current step. ## Version Detection Look at these signals together: - `package.json` versions for `@storybook/react-native`, `storybook`, `@storybook/react`, and `@storybook/addon-ondevice-*` - Whether the config folder is `.storybook/` or `.rnstorybook/` - Metro config imports such as `metro/withStorybook`, `metro/withStorybookConfig`, or default-vs-named `withStorybook` - Story format usage: CSF vs `storiesOf` - Generated file names such as `storybook.requires.js` vs `storybook.requires.ts` If the version is ambiguous, stop and clarify the current installed version instead of guessing. ## Migration Selection Use exactly one reference file: 1. `9.x -> 10.x`: [references/from-9-to-10.md](references/from-9-to-10.md) 2. `8.x -> 9.x`: [references/from-8-to-9.md](references/from-8-to-9.md) 3. `7.6.x -> 8.3.x`: [references/from-7-6-to-8-3.md](references/from-7-6-to-8-3.md) 4. `6.5.x -> 7.6.x`: [references/from-6-5-to-7-6.md](references/from-6-5-to-7-6.md) 5. `5.3.x -> 6.5.x`: [references/from-5-3-to-6-5.md](references/from-5-3-to-6-5.md) ## Workflow 1. Confirm the current Storybook version and whether the repo uses Expo, Expo Router, React Native CLI, or Re.Pack. 2. Pick the next migration step only. Never bundle multiple major upgrades together. 3. Apply the dependency, config, and source-file changes from the matching reference. 4. Regenerate `storybook.requires` or restart Metro when that step requires it. 5. Run the smallest useful verification available for the repo, such as the generation script, tests, lint, or the local Storybook app launch path. 6. If the repo still is not on the user's target version, stop with a clear note describing the next required migration step. ## Output Expectations When you finish a migration step, report: - The version hop that was completed - The files and config surfaces that changed - The verification you ran, or what you could not run - The next required migration hop, if the project is still behind
© storybookjs · MIT · storybookjs/react-native