Sb explore

Skill strongeron/storybook-workbench/skills/sb-explore

AI agent skill bundle for Storybook on React + Vite — audit real-vs-slop components, capture flows, write CSF3 stories, ship. Claude Code / Codex / Cursor.

Install

npx -y skills add strongeron/storybook-workbench --skill sb-explore

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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 file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, as published. Nobody here has run it

sb-explore — sandboxed iteration (Build mode: Explore)

The component is new or being redesigned. It lives outside src/components/ so production code can't depend on it. Load references/labs-workflow.md before scaffolding. If the user pasted a Figma URL, ALSO load references/figma-to-storybook.md. Do NOT load composition-patterns.md (that's Compare → sb-wrappers).

Naming: Explore is the canonical term used throughout this skill (titles, disk paths, tags). references/labs-workflow.md predates the rename and says Labs / src/stories/labs/ — read it as the same track (Explore = Labs). Author with Explore; treat Labs only as a legacy alias you may meet in an existing repo.

Before scaffolding (ask yourself)

Iterating on a shipping component, or net-new? Determines Path A vs Path B at Ship time.
Figma URL pasted? If yes — set parameters.design = { type: 'figma', url } immediately and iterate against the frame (see figma-to-storybook.md).
API stable enough to graduate? See the 4 criteria in labs-workflow.md. If not — stay in Explore.

Scaffold

Disk path — honor the recorded storiesLocation (.storybook/audit/status.md): when stories are isolated (the audit/client default), scaffold the experiment under .storybook/explore/<topic>/ — don't scatter into a src/ you don't own. Only use src/explore/<topic>/ when the user opted into co-located for a project they own. Vite excludes either from the production bundle.
Title — Explore/<topic>/<name> — last in storySort.order, bottom of sidebar.
Tags — ['explore', '!autodocs', '!test']. Optional: 'motion', 'figma-sync', 'v2-preview'.

Graduation gate (Explore → Component)

Four criteria in labs-workflow.md: stable API · ≥3 callsites planned · designer-reviewed · tokens not magic numbers. When all met → trigger sb-ship (it preserves the experiment, never git mv). Until then, keep iterating here.

Iterate; when the gate is met, hand off to sb-ship. Append progress to .storybook/audit/status.md so an interrupted session resumes cleanly (CONTEXT.md resume protocol).