By strongeron
Work WITH Storybook on React+Vite apps: audit a vibe-coded codebase for real-vs-slop components, capture flows/app-maps, write CSF3 stories, and ship — as focused skills, not one monolith.
Scaffold a Storybook-only wrapper — ABCanvas, StateGrid, AppFlowGraph, ProjectInventory, and more. Use for 'compare two designs', 'every state on one canvas', 'the full flow', 'track this decision', or 'scaffold wrappers'.
Periodic Storybook audit — naming-drift survey, archived/decision-board review, lifecycle tagging, usage refresh. Use for 'audit my Storybook', 'find drift', 'show pending decisions', or a periodic catalog health check.
Iterate on a new or redesigned component in a sandboxed Explore story outside src/components/ (+ Figma), checked against a graduation gate. Use for 'prototype this', 'try a v2', 'explore from Figma', or net-new UI not ready to ship.
The Figma↔Storybook bridge, both directions, via the native Figma MCP. design→code: map foundation tokens (color/spacing/type) from Figma variables with design↔code parity + drift, and deliver approved Figma components (extract → build → embed), authoring stories via sb-stories' rules. code→design: build Code Connect mappings from components + stories + token parity + usage so Figma Dev Mode shows the real code. Use for 'sync my Figma tokens', 'map Figma variables to my design system', 'deliver this approved Figma design', 'check design↔code token parity', 'connect my components to Figma / code connect'. NOT for prototyping/iterating an undecided design (that's sb-explore).
Write a CSF3 story for ONE React component, covering only its materially-different states (no Cartesian), with a factory when 3+ stories share a shape. Use for 'write a story for X', 'document this component', 'add a Storybook story'.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Storybook toolkit for React + Vite apps — driven by your AI coding agent.
Work with Storybook on a real codebase: audit what components are actually there (real vs. AI slop),
map the app's flows and user roles, write conformant CSF3 stories for only the states that matter, and
ship — across Claude Code, Codex, and Cursor. Everything lands under .storybook/, so src/ stays
clean and the whole audit is one removable folder.
11 focused skills over a shared foundation, orchestrated by a hub — not one monolithic prompt.
A live Storybook these skills generated end-to-end on a real, vibe-coded React + Vite app — every view is their output, not a mockup. The cover below is one of them:
Open the live demo — real skill output on a real codebase, panel by panel.
Each section is one skill's output:
Works on any agent that supports the Agent Skills standard.
Any agent (skills.sh) — all 11 skills (the whole bundle):
npx skills add strongeron/storybook-workbench # installs ALL 11 skills
npx skills add strongeron/storybook-workbench --all # same, fully non-interactive (all skills + all agents, -y) — for CI
Just one skill (each ships self-contained — its own scripts, references, wrappers, and the layout decorator):
npx skills add strongeron/storybook-workbench --list # see the 11 skills
npx skills add strongeron/storybook-workbench -s sb-wrappers # install only this one
npx skills use strongeron/storybook-workbench@sb-wrappers # try it without installing
Pipeline note: the renderer skills show data another skill produces — e.g.
sb-wrappers'ProjectInventoryreadsproject-inventory.jsonfromsb-inventory,DesignSystemHealthreadssb-health's output. Installed alone they work and render an empty state until that JSON exists; add the producer skill (or supply the JSON) for live data. The pure composition wrappers (StateGrid/ABCanvas/StateMatrix/StorySet) have no cross-skill dependency.
Claude Code (plugin marketplace) — the whole bundle:
claude plugin marketplace add strongeron/storybook-workbench
claude plugin install storybook-workbench@storybook-workbench
Codex: install project-scoped (drop --global — the skills CLI doesn't support global install for
Codex), run from your project root:
npx skills add strongeron/storybook-workbench --agent codex --yes
Cursor: skills are project-scoped (Cursor has no global skills dir) — run from your project root, then reload the window:
npx skills add strongeron/storybook-workbench --agent cursor --yes
# then: Cmd/Ctrl+Shift+P → "Developer: Reload Window"
After reload the skills appear in Cursor's / menu under Skills — invoke one by name
(/sb-hub, /sb-setup, /sb-inventory, …), or just ask in plain language and the matching skill
triggers by description.
Then restart your agent session so it registers the skills.
Skills install as a snapshot, so to pull the latest — new skills (like sb-figma), fixes, wrapper
updates — re-run the add command. It re-fetches and overwrites in place:
npx skills add strongeron/storybook-workbench --all # update every installed skill to latest
npx skills add strongeron/storybook-workbench -s sb-figma # update just one skill
Restart your agent session afterward so it re-registers the updated skills.
npx claudepluginhub strongeron/storybook-workbench --plugin storybook-workbenchBuild, preview, and test UI components with Storybook.
Create and edit React Native Storybook stories using Component Story Format (CSF). Includes controls reference, addon configuration, and portable story patterns.
React, React Flow, React Router, shadcn/ui, Tailwind v4, Vitest, and Zustand code review. Pairs with beagle-core for full workflow.
AI-first engineering workflow with BDD living documentation. Lean PRD writing, Gherkin generation, and wireframe mockups for Product and Engineer roles.
Create a React component using the Container/Presentation pattern in src/components by asking for the component name and type (ui or features), then scaffold files that follow this repository's TypeScript, Storybook, and SCSS conventions. Use when the user explicitly asks for a…
Premium design patterns, UX research skills, and user journey mapping for modern web applications.