# Storybook Stories > Create, update, refactor, or troubleshoot Storybook stories using project conventions. Excludes component implementation, token changes, E2E browser tests, and other documentation. - Skill: `compozy/storybook-stories` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add compozy/storybook-stories` - Raw SKILL.md: https://api.skillmd.com/api/skills/compozy/storybook-stories/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend, Coding & Dev Tools - Author: compozy (https://skillmd.com/u/compozy) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/compozy/storybook-stories --- # Storybook Stories Extend the nearest existing story using the Storybook instance and naming conventions for its layer. In Compozy, primitive stories belong to `packages/ui/.storybook`; web systems, including route stories, use `web/.storybook`. Reuse global QueryClient/router/MSW decorators instead of duplicating providers. - Inspect the shared primitive inventory before composing examples. In Compozy, use `packages/ui/src/index.ts` and imports from `@compozy/ui`; domain components remain local. Follow the actual token source, `DESIGN.md`, and surface instructions. - Use typed CSF metadata and `StoryObj`. Choose layout/decorators for the component's real surface; centered layout is useful for some controls, not full routes. - Show the smallest set of supported states that explains meaningful behavior. No minimum or maximum story count, exhaustive prop matrix, or per-export JSDoc requirement. - Use `args` for controlled props and `render` for compound composition. A render-only story does not need empty `args`. Add descriptions when they explain behavior, constraints, or usage that the canvas cannot show. - Keep examples interactive, accessible, and realistic. Use the actual component API, not assumed variants copied from a template. - Do not enable `tags: ["autodocs"]` in this workflow; keep documentation intentional and avoid duplicate generated pages. - Run the owning Storybook/build or visual check for the changed behavior. Reuse existing evidence; stories do not automatically require new unit or end-to-end suites. Read `references/patterns.md` only for the story composition pattern being used. Examples are adaptable, not a required scaffold.