superspecs: Skill for Claude Code

.skills/storybook/SKILL.md

storybook is a skill for Claude Code, Codex from fokkerone/superspecs. It costs 61 tokens per session (2,047 once invoked), scanned A, original, MIT.

A visual workbench for building and cataloguing frontend components in Storybook, a tool that displays UI components in isolation.

In plain words
What is it for?
It helps create components, add visual examples called stories, and maintain a reusable component catalogue for later design and specification work.
Why use it?
It lets developers design and review components separately from the full application, without adding test-driven development or behavior-driven development steps.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is fokkerone/superspecs's own configuration. It tells Claude Code and Codex how to work on superspecs itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything superspecs configures →

Reuse

Borrowing it

Nothing to install: this file belongs to fokkerone/superspecs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/fokkerone/superspecs/main/.skills/storybook/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/fokkerone/superspecs

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for storybook

README.md
[![agentmods](https://agentmods.dev/badge/skills/fokkerone/superspecs/storybook/github.svg)](https://agentmods.dev/skills/fokkerone/superspecs/storybook)
Your own site
<a href="https://agentmods.dev/skills/fokkerone/superspecs/storybook"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/storybook/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for storybook

Your own site · 80×15
<a href="https://agentmods.dev/skills/fokkerone/superspecs/storybook"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/storybook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,047 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00061 $0.02047
Opus 5 $0.00030 $0.01024
Sonnet 5 $0.00012 $0.00409
Haiku 4.5 $0.00006 $0.00205

Measured 11d ago against content hash f38aa2ec2a29, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

storybook 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 11d 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.

.skills/storybook/SKILL.md · 239 lines

How it starts

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

Skill: storybook

You are a Storybook expert and frontend component craftsman. This skill operates outside the main SuperSpecs lifecycle — it is a visual workbench, not a spec-driven workflow.

The goal: Build, iterate, and document frontend components visually in Storybook. The output is a growing component catalogue that /discuss and /spec can reference to skip design work that's already done.

No tests. No BDD. No RED/GREEN/REFACTOR. Pure visual development.


Inputs

Before starting, read:

  1. superspec/wiki/techstack.md (if it exists) — identify the frontend framework (React, Vue, Svelte, etc.) and styling approach (Tailwind, CSS Modules, styled-components, etc.)
  2. superspec/wiki/ui/component-catalogue.md (if it exists) — existing components to avoid duplication
  3. package.json — confirm Storybook is installed; detect framework version

Steps

1. Detect or set up Storybook

Check if Storybook is installed:

grep -E "storybook|@storybook" package.json

If Storybook is NOT installed:

Ask the user which framework to install for, then show the exact command:

  • React: npx storybook@latest init
  • Vue: npx storybook@latest init
  • Svelte: npx storybook@latest init
  • Next.js: npx storybook@latest init

Say: "Storybook is not installed. Run the command above, then re-run /superspecs:storybook."

Stop here if Storybook is not installed. Do not proceed.

If Storybook IS installed:

Identify:

  • Stories location (.storybook/main.tsstories glob pattern)
  • Component convention (co-located *.stories.tsx or separate stories/ folder)
  • Framework-specific story format (CSF3 preferred)

2. Clarify the component

Ask (one at a time, stop when clear):

  1. Name: What is the component called? (e.g. Button, UserCard, PricingTable)
  2. Purpose: What does it do in one sentence?
  3. Variants: What visual states should exist? (e.g. primary/secondary, sizes, disabled, loading)
  4. Props: What data does it receive? Any obvious required props?
  5. Existing reference? Screenshot, Figma link, or verbal description of the visual target?

Read the full file on GitHub · 239 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. 11d ago First seen · 239 lines · 61 tokens per session scan A f38aa2ec2a29

Subscribe to this mod's changes

storybook is a skill published in the GitHub repository fokkerone/superspecs (4 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 2,047 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 50 tokens

frontend-visual-qa

Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…

daymade/claude-code-skills · 145 tokens

prototype-web

A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.

nexu-io/html-anything · 24 tokens

animation-principles

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.

Owl-Listener/designer-skills · 59 tokens

refactoring-ui

Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…

wondelai/skills · 132 tokens