AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendmedium PriorityID: storybook-v8-csf3

Storybook 8 Component Story Format (CSF3) Standard

Modern component-driven development with Storybook 8 and CSF3. Replaces deprecated CSF2 template factories (Template.bind({})) with declarative Meta/StoryObj typing, play functions for interaction tests, and autodocs.

Prohibited Anti-Pattern: AI outputs deprecated CSF2 Template.bind({}) or legacy storiesOf syntax that fails TypeScript checking in Storybook 8.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Storybook 8 Component Story Format (CSF3) Standard - Modern component-driven development with Storybook 8 and CSF3. Replaces deprecated CSF2 template factories (Template.bind({})) with declarative Meta/StoryObj typing, play functions for interaction tests, and autodocs.
globs: **/*.stories.tsx, **/*.stories.ts
alwaysApply: false
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/storybook-v8-csf3"
---

# Storybook 8 Component Story Format (CSF3) Standard

> **Severity**: MEDIUM | **Category**: frontend
> **Anti-Pattern Warning**: AI outputs deprecated CSF2 Template.bind({}) or legacy storiesOf syntax that fails TypeScript checking in Storybook 8.

## System Constraints
You are a design system engineer. In Storybook 8, never use CSF2 Template.bind({}) patterns or storiesOf. Always write CSF3 declarative story objects typed with Meta<typeof Component> and StoryObj<typeof meta>.

## Strict Guidelines
- Export default metadata using `satisfies Meta<typeof Component>` for strict argument type checking.
- Define individual stories as plain objects of type `StoryObj<typeof meta>`; do not create `const Template = ...` functions.
- Use Storybook play functions with `@storybook/test` (canvas, userEvent, expect) for automated visual interaction tests.
- Enable autodocs in the default export meta object to generate automatic API documentation.

## Bad vs Good Implementations
### Storybook 8 CSF3 Declaration vs Deprecated CSF2 Template.bind({})

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: CSF2 Template.bind({}) requires tedious boilerplate, lacks type inference for story-specific overrides, and is legacy in v8.
```tsx
// ANTI-PATTERN: Deprecated Storybook CSF2 pattern (obsolete since v7/v8)
import { ComponentMeta, ComponentStory } from "@storybook/react";
import { Button } from "./Button";

export default {
  title: "Components/Button",
  component: Button,
} as ComponentMeta<typeof Button>;

const Template: ComponentStory<typeof Button> = (args) => <Button {...args} />;

export const Primary = Template.bind({});
Primary.args = {
  label: "Click Me",
  variant: "primary",
};
```

#### Production Standard (Correct)
> **Standard**: CSF3 stories are plain, type-checked JavaScript objects that support story composition and automated doc generation.
```tsx
// PRODUCTION STANDARD: Declarative Storybook 8 CSF3 with StoryObj
import type { Meta, StoryObj } from "@storybook/react";
import { Button } from "./Button";

const meta = {
  title: "Components/Button",
  component: Button,
  parameters: {
    layout: "centered",
  },
  tags: ["autodocs"],
  argTypes: {
    variant: {
      control: "select",
      options: ["primary", "secondary", "destructive"],
    },
  },
} satisfies Meta<typeof Button>;

export default meta;
type Story = StoryObj<typeof meta>;

export const Primary: Story = {
  args: {
    label: "Confirm Action",
    variant: "primary",
  },
};

export const Destructive: Story = {
  args: {
    label: "Delete Project",
    variant: "destructive",
  },
};
```

### Interactive Story Testing with play Function

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Manual clicking in Storybook is required to verify stateful behavior.
```tsx
// ANTI-PATTERN: No automated user interaction assertion in story
export const ClickCounter: Story = {
  args: { initialCount: 0 },
};
```

#### Production Standard (Correct)
> **Standard**: Play functions execute interaction tests headlessly during CI via test-runner.
```tsx
// PRODUCTION STANDARD: Play function verifying component interaction
import { within, userEvent, expect } from "@storybook/test";

export const ClickCounter: Story = {
  play: async ({ canvasElement }) => {
    const canvas = within(canvasElement);
    const button = canvas.getByRole("button", { name: /increment/i });
    await userEvent.click(button);
    await expect(canvas.getByText("Count: 1")).toBeInTheDocument();
  },
};
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Storybook Component Inspector
Inspect storybook component hierarchy and visual regression states.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Storybook CSF3 Story Scaffolder
Generate Storybook 8 CSF3 stories with argTypes and interaction play tests.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Storybook 8 Component Story Format (CSF3) Standard

Storybook 8 Component Story Format (CSF3) Standard defines an industrial-grade behavioral standard for frontend engineering. Modern component-driven development with Storybook 8 and CSF3. Replaces deprecated CSF2 template factories (Template.bind({})) with declarative Meta/StoryObj typing, play functions for interaction tests, and autodocs. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: AI outputs deprecated CSF2 Template.bind({}) or legacy storiesOf syntax that fails TypeScript checking in Storybook 8. Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftAI outputs deprecated CSF2 Template.bind({}) or legacy storiesOf syntax that fails TypeScript checking in Storybook 8.High
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Export default metadata using `satisfies Meta<typeof Component>` for strict argument type checking.

Export default metadata using `satisfies Meta<typeof Component>` for strict argument type checking.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Define individual stories as plain objects of type `StoryObj<typeof meta>`

Define individual stories as plain objects of type `StoryObj<typeof meta>`; do not create `const Template = ...` functions.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Use Storybook play functions with `@storybook/test` (canvas, userEvent, expect) for automated visual interaction tests.

Use Storybook play functions with `@storybook/test` (canvas, userEvent, expect) for automated visual interaction tests.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Enable autodocs in the default export meta object to generate automatic API documentation.

Enable autodocs in the default export meta object to generate automatic API documentation.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Storybook 8 Component Story Format (CSF3) Standard critical for AI coding assistants?

Modern component-driven development with Storybook 8 and CSF3. Replaces deprecated CSF2 template factories (Template.bind({})) with declarative Meta/StoryObj typing, play functions for interaction tests, and autodocs. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (AI outputs deprecated CSF2 Template.bind({}) or legacy storiesOf syntax that fails TypeScript checking in Storybook 8.) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Storybook