Storybook Setup — Claude Launch

Use this skill when Storybook is configured but Claude needs a .claude/launch.json entry to start the dev server (for example when repair instructions mention missing launch config).

Workflow

1. Inspect the project's Storybook scripts and preferred package manager.
2. Inspect any existing .claude/launch.json.
3. Add or repair a Storybook launch entry that runs the existing Storybook script from the Storybook invocation directory.
4. Keep other launch entries intact.
5. Verify the launch entry by using the Claude launcher or by inspecting the saved launch config.

Use the project's existing Storybook script instead of inventing a new command whenever possible.

NEVER start Storybook with a Bash command or background task — not npm run storybook, not storybook dev, not run_in_background, not a detached process. "Start the preview" always means invoking the Claude launcher on the .claude/launch.json Storybook entry. A backgrounded dev server is not a launcher-managed preview and will not satisfy the story workflow.

Claude Launch Config Details

• autoPort must be set to true to avoid port conflicts.
• Storybook command must pass a --port flag set to the launcher-provided port env var, using the appropriate interpolation syntax for the target shell/launcher (for example, --port $PORT in a POSIX shell or --port %PORT% on Windows), so Storybook starts on the expected port.
• Storybook command must use the --ci flag to skip prompts and ensure it can run in a non-interactive environment.

If this skill is invoked when creating stories

If this skill is invoked as part of the story creation flow, start the preview immediately after repairing the launch config — by launching the .claude/launch.json Storybook entry through the Claude launcher — so the user can continue with story creation without manually starting Storybook.