storybook-stories · oakoss — Claude Code skill: what it does, how to install
Writes Storybook stories and interaction tests in CSF3 format. Handles component examples, Chromatic visual snapshot setup, and accessibility checks.
MIT 124 installs ★ 29 updated 2026-08-17
npx skills add oakoss/agent-skills --skill storybook-stories -a claude-codeWhat storybook-stories does
This skill generates Storybook stories following CSF3 syntax. It applies the args object pattern for individual components and switches to custom render functions for multi-component layouts. Interaction testing runs inside the play function with userEvent actions and Testing Library queries, giving priority to accessible role lookups. It also configures Chromatic parameters for visual regression checks, including snapshot delays and skips.
The skill is limited to isolated UI development and does not handle end-to-end browser automation or API testing. When components render inside portals or run asynchronous animations, querying the standard canvas context directly fails, requiring body-level lookups and waitFor wrappers.
What it helps with
- generate CSF3 component stories with typed args
- write interaction tests using play functions and userEvent
- set up Chromatic snapshot delays and capture rules
- verify accessible names and labels across UI elements
Example prompts for the agent
- Generate a CSF3 story for Button with a play function testing click events
- Add Chromatic parameters to skip visual regression snapshots for Modal
- Refactor interaction test queries from getByTestId to getByRole
How to install storybook-stories
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill storybook-stories -a claude-code2Manually: put the files in place
~/.claude/skills/storybook-stories/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/storybook-stories/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill storybook-stories -a codex2Manually: put the files in place
.agents/skills/storybook-stories/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill storybook-stories -a cursor2Manually: put the files in place
.cursor/skills/storybook-stories/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install oakoss/agent-skills skills/storybook-stories2Manually: put the files in place
.github/skills/storybook-stories/SKILL.md1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill storybook-stories -a gemini-cli2Platform CLI
gemini skills install https://github.com/oakoss/agent-skills --path skills/storybook-storiesManually: put the files in place
.devin/skills/storybook-stories/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill storybook-stories -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 storybook-stories
How to install storybook-stories in Claude Code?
Run npx skills add oakoss/agent-skills --skill storybook-stories -a claude-code. The skill file is placed in ~/.claude/skills/storybook-stories/SKILL.md.
What does the storybook-stories skill do?
It writes CSF3 component stories, creates play function interaction tests with userEvent, and sets up Chromatic visual snapshot rules.
Can storybook-stories be used for end-to-end testing?
No, the skill only handles isolated component development. For end-to-end application journeys or API validation, tools like Playwright, Cypress, or Vitest are required.
Source text
SKILL.md · MIT
---
name: storybook-stories
description: 'Writes and maintains Storybook stories and interaction tests using CSF3 format. Covers component stories, play functions, visual regression testing with Chromatic, and accessibility testing. Use when creating component documentation, writing interaction tests, debugging test failures, configuring visual snapshots, or updating story structure. Use for CSF3, play functions, userEvent, Testing Library queries, Chromatic configuration, autodocs, MDX.'
license: MIT
metadata:
author: oakoss
version: '1.1'
source: https://storybook.js.org/docs
user-invocable: false
---
# Storybook Stories
## Overview
Storybook is a frontend workshop for building UI components in isolation. Stories are written in Component Story Format 3 (CSF3), which uses object syntax with `args` for type-safe component documentation and testing.
**When to use:** Component documentation with live examples, interaction testing with play functions, visual regression testing, accessibility validation, design system maintenance, isolated component development.
**When NOT to use:** End-to-end testing (use Playwright/Cypress), API integration testing (use Vitest/Jest), full application testing (use browser automation), performance testing (use Lighthouse/WebPageTest).
## Quick Reference
| Pattern | API | Key Points |
| ---------------------- | ------------------------------------------------------ | -------------------------------------- |
| Basic story | `export const Default: Story = { args }` | Use args for simple single components |
| Complex story | `export const Example: Story = { render }` | Use render for multi-component layouts |
| Meta configuration | `const meta = { component, args } satisfies Meta` | Define defaults and argTypes |
| Interaction test | `play: async ({ canvas, userEvent, args })` | canvas and userEvent provided directly |
| User interaction | `await userEvent.click(element)` | Always await userEvent methods |
| Query elements | `canvas.getByRole('button')` | Prefer getByRole over other queries |
| Assertions | `await expect(args.onPress).toHaveBeenCalled()` | Use storybook/test assertions |
| beforeEach hook | `beforeEach: async ({ args }) => {}` | Setup mocks before story renders |
| Play composition | `await OtherStory.play?.(context)` | Reuse setup across stories |
| Autodocs | `tags: ['autodocs']` | Enable automatic documentation |
| Controls customization | `argTypes: { variant: { control: 'select' } }` | Configure control panel |
| Decorators | `decorators: [withTheme]` | Add wrappers or context providers |
| Parameters | `parameters: { layout: 'centered' }` | Configure addon behavior per story |
| Chromatic snapshot | `parameters: { chromatic: { delay: 300 } }` | Control visual regression captures |
| Disable snapshot | `parameters: { chromatic: { disableSnapshot: true } }` | Skip story in visual tests |
| A11y testing | `await expect(button).toHaveAccessibleName()` | Validate accessible labels |
## Common Mistakes
| Mistake | Correct Pattern |
| ------------------------------------------ | -------------------------------------------------------- |
| Using args with multi-component layouts | Use render for complex compositions |
| Not awaiting userEvent methods | Always await: `await userEvent.click(button)` |
| Using within(canvasElement) manually | Destructure `canvas` from play context directly |
| Using getByTestId first | Prefer getByRole, getByLabelText, getByText |
| Missing default args at meta level | Add args to meta to prevent placeholder controls |
| Exposing non-serializable props | Disable className, ref, style in argTypes |
| Not composing play functions | Reuse setup with `await BaseStory.play?.(context)` |
| Forgetting to mock callbacks | Use `fn()` for event handlers: `args: { onPress: fn() }` |
| Missing accessible names for icon buttons | Add aria-label or use aria-labelledby |
| Not scoping queries for portal content | Use `within(canvasElement.ownerDocument.body)` |
| Using boolean && for conditional rendering | Use ternary in stories for consistent snapshots |
| Not waiting for animations | Wrap assertions in waitFor for async state |
## Common Fixes
| Problem | Solution |
| -------------------------- | ----------------------------------------------- |
| Controls show placeholders | Add `args` at meta level with default values |
| Serialization error | Disable `className`, `ref`, `style` in argTypes |
| Portal element not found | Search `body` instead of `canvas` |
| Animation timing issues | Wrap assertions in `waitFor` |
| Multiple buttons found | Add `{ name: '...' }` to getByRole |
| A11y test failing | Add `label` prop or `aria-label` |
## Delegation
- **Story structure review**: Use `code-reviewer` skill for CSF3 pattern validation
- **Accessibility audit**: Use `Explore` agent to discover ARIA patterns across stories
- **Visual regression analysis**: Use `Task` agent to investigate Chromatic failures
## References
- [Story writing patterns and CSF3 syntax](references/story-writing.md)
- [Interaction tests with play functions](references/interaction-tests.md)
- [Component documentation and controls](references/component-documentation.md)
- [Visual testing with Chromatic](references/visual-testing.md)
© oakoss · MIT · oakoss/agent-skills
Similar skills
All skills for Frontend and UI →storybook-stories by other authors comes first.