PixelPilot component-storybook.instructions.md

A guide that creates Storybook stories for React or Vue components. Storybook is a tool for displaying UI components in different versions and states, such as loading, disabled, or error.

In plain words
What is it for?
It helps document component variants, test interactions, check accessibility, and create `.stories.tsx` or `.stories.ts` files.
Why use it?
It turns a component's properties and possible states into documented examples, with interaction and accessibility checks.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/dev-lou/pixelpilot/component-storybook
Clone the repo
git clone --depth 1 https://github.com/dev-lou/PixelPilot

Made for: GitHub Copilot.

Per session 3,224 This file is loaded in full into every session.
When invoked 3,224 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.03224 $0.03224
Opus 5 $0.01612 $0.01612
Sonnet 5 $0.00645 $0.00645
Haiku 4.5 $0.00322 $0.00322

Measured 2d ago against content hash 918c77fae08d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

PixelPilot component-storybook.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

vscode/.github/instructions/component-storybook.instructions.md · 456 lines

How it starts

The opening of the file, as written. The whole thing — 456 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Component Storybook 2026

Component file → prop extraction → story generation → interaction tests → a11y checks. Produces stories that document every design system variant and all 9 component states.


PREREQUISITES

# Install Storybook (if not present)
npx storybook@latest init

# Required addons
npm install -D \
  @storybook/addon-a11y \
  @storybook/addon-interactions \
  @storybook/test \
  @storybook/addon-docs \
  chromatic  # optional — visual regression

STEP 1 — ANALYSE THE COMPONENT

Read the component file and extract:

## Component Analysis: {ComponentName}

### Props interface
{extracted TypeScript interface or prop-types}

### Variants (from union types / enums)
{e.g., variant: 'primary' | 'secondary' | 'ghost' | 'danger'}

### States (from the 9-state law)
{which of default/hover/focus/active/loading/disabled/error/success/empty apply}

### Design tokens used
{list of CSS custom property references found in the component}

### Sub-components / composition
{e.g., Button is used inside Form, Card, etc.}

STEP 2 — STORYBOOK CONFIG

// .storybook/main.ts
import type { StorybookConfig } from '@storybook/nextjs';

const config: StorybookConfig = {
  stories: ['../src/**/*.stories.@(ts|tsx)'],
  addons: [
    '@storybook/addon-essentials',
    '@storybook/addon-interactions',
    '@storybook/addon-a11y',
    '@storybook/addon-docs',
  ],
  framework: {
    name: '@storybook/nextjs',
    options: {},
  },
};
export default config;
// .storybook/preview.ts
import type { Preview } from '@storybook/react';
import '../src/tokens.css';   // design tokens — must be first
import '../src/globals.css';

const preview: Preview = {
  parameters: {
    controls: { matchers: { color: /(background|color)$/i, date: /Date$/i } },
    a11y: { config: { rules: [{ id: 'color-contrast', enabled: true }] } },
    backgrounds: {
      default: 'light',
      values: [
        { name: 'light', value: 'var(--bg)' },
        { name: 'dark',  value: '#0A0B0E' },
      ],
    },
  },
  globalTypes: {
    theme: {
      name: 'Theme',
      description: 'Global theme for components',
      defaultValue: 'light',
      toolbar: {
        icon: 'circlehollow',
        items: ['light', 'dark'],
        showName: true,
      },
    },
  },
  decorators: [
    (Story, context) => {
      const theme = context.globals.theme;
      document.documentElement.setAttribute('data-theme', theme);
      return <Story />;
    },
  ],
};
export default preview;

Read the full file on GitHub · 456 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 456 lines · 3,224 tokens per session scan A 918c77fae08d

Subscribe to this mod's changes

PixelPilot component-storybook.instructions.md is an instructions file published in the GitHub repository dev-lou/PixelPilot (2 stars, last pushed 4mo ago), licensed MIT. It adds 3,224 tokens to every session, about $0.0161 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.