Skip to main content
prompt GP ChatGPT

Storybook taste — ChatGPT prompt: what it does, how to install

The Storybook taste prompt for ChatGPT sets conventions for writing component stories in Storybook. It covers story structure, component states, interaction checks and sharing changes for review.

CC0-1.0 ★ 178,201 updated 2026-10-24

Open on GitHub

What Storybook taste does

The prompt asks for Component Story Format 3 with typed Meta and StoryObj, and places each story file beside its component. Each component gets a Default story and separate examples for meaningful states such as loading, error and empty content.

It also specifies shared decorators in preview.tsx, MSW handlers for network mocks, and interaction tests using play functions with Testing Library queries. The guidance includes running stories in CI, checking accessibility and capturing visual snapshots for design-system components. In Claude Code, the file path is .claude/commands/prompts.csv.md.

What it helps with

  • write component stories in CSF 3
  • cover loading, error and empty states
  • test component interactions with play
  • mock network requests in stories

Example prompts for the agent

  • Create Storybook stories for this component in CSF 3 with typed Meta and StoryObj.
  • Add stories for loading, error and empty states, using args for props.
  • Set up an MSW mock and a play test for the form submission story.

How to install Storybook taste

How to use

Paste the text at the start of a chat or into project instructions

Questions about Storybook taste

How do I install Storybook taste in Claude Code?

Add .claude/commands/prompts.csv.md to the Claude Code project.

What does Storybook taste do?

It sets conventions for Storybook component stories, including CSF 3 structure, typed definitions, state coverage, mocks and interaction checks.

How does this prompt differ from using storiesOf?

It calls for CSF 3 with typed Meta and StoryObj instead of the legacy storiesOf API.

Source text

prompts.csv · CC0-1.0
# Storybook taste of a frontend developer who builds components in isolation
- Write stories in Component Story Format 3 with a typed `Meta` and `StoryObj`, not the legacy `storiesOf` API. Confidence: 0.95
- Colocate each story file next to its component, as `Button.stories.tsx` beside `Button.tsx`. Confidence: 0.90
- Give every component a `Default` story plus one story per meaningful state: loading, empty, error, disabled and long content. Confidence: 0.90
- Use `args` for props so controls, docs and tests all reuse the same story definitions. Confidence: 0.90
- Keep default `args` realistic, with real-looking names, prices and dates instead of "foo" and "lorem ipsum". Confidence: 0.75
- Put shared providers such as theme, router, i18n and query client in global decorators in `preview.tsx`. Confidence: 0.85
- Mock network requests with MSW handlers per story rather than wiring components to fake service modules. Confidence: 0.85
- Use `play` functions with Testing Library queries to exercise interactions such as opening menus and submitting forms. Confidence: 0.80
- Run stories as tests in CI with the Storybook test runner or Vitest integration so broken stories fail the build. Confidence: 0.85
- Enable the accessibility addon and treat new violations as failures, not as optional warnings. Confidence: 0.85
- Add visual regression snapshots for design-system components, and keep them focused to avoid flaky noise. Confidence: 0.75
- Organize the sidebar by product domain and design-system layer, such as `Foundations/`, `Components/` and `Patterns/`. Confidence: 0.70
- Use autodocs with JSDoc comments on props instead of hand-maintained MDX tables that drift out of date. Confidence: 0.80
- Reserve MDX pages for usage guidelines, do-and-don't examples and design decisions that code cannot express. Confidence: 0.70
- Keep stories free of business logic and data fetching; containers get thin stories with mocked data only when useful. Confidence: 0.80
- Use the viewport and theme toolbar globals to check mobile layouts and dark mode, rather than duplicating stories for each. Confidence: 0.75
- Keep Storybook's builder aligned with the app, using the Vite builder when the app uses Vite, so behavior matches production. Confidence: 0.80
- Publish a static Storybook for every pull request so designers and reviewers can check changes without running code. Confidence: 0.85
- Upgrade Storybook regularly with its automigration tool instead of letting major versions pile up. Confidence: 0.70
- Delete stories for removed components in the same pull request; a stale story is worse than no story. Confidence: 0.75
- Avoid hard-coded story IDs in links and tests; reference stories by their exported names. Confidence: 0.65

© f · CC0-1.0 · f/prompts.chat

Similar prompts

All prompts for Frontend and UI →

From the same set218

The whole set →
Jupyter Notebook taste Jupyter Notebook taste is a ChatGPT prompt for clean, repeatable notebooks. It applies when an analysis is prepared for review or a commit. GP ChatGPT ★ 178,201repo stars Gradle Build taste Gradle Build taste is a ChatGPT prompt that enforces fast JVM builds using Kotlin DSL and the wrapper. GP ChatGPT ★ 178,201repo stars MongoDB taste MongoDB taste is a ChatGPT prompt for MongoDB document design around query patterns, indexes, and schema checks. Claude Code loads it from a command file. GP ChatGPT ★ 178,201repo stars API Key and Credential Rotation Runbook (JSON) The API Key and Credential Rotation Runbook (JSON) is a prompt for ChatGPT, Claude.ai, and Claude Code that builds a secure secret rotation plan. It outputs a structured JSON object with steps. GP ChatGPT ★ 178,201repo stars RAG Pipeline taste RAG Pipeline taste — a prompt for ChatGPT defines engineering standards for building retrieval systems and evaluating generation accuracy. GP ChatGPT ★ 178,201repo stars Makefile taste The Makefile taste ChatGPT prompt sets conventions for project Makefiles. It guides target structure, recipes, and dependencies so make can act as the project’s front door. GP ChatGPT ★ 178,201repo stars API Deprecation and Sunset Plan Builder (YAML) API Deprecation and Sunset Plan Builder (YAML) is a prompt that turns API deprecation details into a structured YAML sunset plan with timelines, communication strategies, and migration steps. GP ChatGPT ★ 178,201repo stars Nginx Config taste The Nginx Config taste ChatGPT prompt sets conventions for Nginx configuration and operations. Use it while configuring virtual hosts, HTTPS, or proxy routes. GP ChatGPT ★ 178,201repo stars

More in the catalog

Project sponsors

Companies that keep this analytics open