storybook-stories — Claude Code skill: Storybook stories by convention

What storybook-stories does

The skill handles four jobs on stories: create, update, refactor, troubleshoot. It finds the nearest existing story and extends that one instead of starting fresh. First it works out which Storybook config owns the layer, since primitives and app or domain stories usually sit apart.

Providers get reused, not copied. Global decorators for QueryClient, the router and MSW stay where they are. Metadata is typed CSF with StoryObj<typeof meta>. Controlled props go through args; compound cases go through render, and a render-only story needs no empty args. Show the smallest set of states that explains real behavior — there is no required story count. The tags: ["autodocs"] policy comes from whoever owns that page, so you don't end up with duplicate pages.

Before composing examples the agent checks the shared primitive inventory and uses its public exports, while domain components stay local. references/patterns.md is read only for the composition pattern in play, and its examples are adaptable rather than a scaffold you must follow. Component implementation, token changes, browser E2E tests and other documentation fall outside the skill, so a request about those won't trigger it.