How do I install the Sb Ship skill?

Run npx skillmds@latest add strongeron/sb-ship in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sb Ship safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sb Ship?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sb Ship free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Sb Ship?

strongeron (@strongeron) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sb Ship by strongeron — Agent Skill

Name: Sb Ship
Author: strongeron

Sb Ship

Graduate ONE Explore experiment to a production component — preserve the experiment (cp, never git mv), pick new-vs-update, close the decision loop. Use for 'ship this', 'promote this experiment', 'graduate to production'.

strongeron d5dcca2 7 files · 53.3 KB Updated Sep 17, 2026

File contents

sb-ship — graduate, preserving history

Event-triggered when an Explore iteration meets the graduation gate. The one rule that matters: preserve the experiment — cp, never git mv. The Explore story stays as design history; git mv here is the destructive bug propagate-workflow.md exists to prevent. Load references/propagate-workflow.md before any Ship action — it's the only reference this skill needs; Do NOT load the sb-wrappers/sb-audit refs (lifecycle, galleries, composition) for a Ship.

Decide the path (ask yourself)

Did the Explore define its own component file, or iterate on an existing one? → Path A vs Path B.
Path B: evolve in place (B1) or keep V1 in _legacy/ (B2)? B2 only when V1 still has live callsites needing a migration window.
Did the import path change? If yes → ast-grep callsites. If not → skip it.
Other tagged stories that should flip? (a Compare decision:pending → decision:chosen + winner.)

Execute

Path A — NEW component. cp the component explore→components, write a fresh production stories file to the recorded storiesLocation (.storybook/audit/status.md; the rule lives in CONTEXT.md §STORIES LOCATION — never scatter) — don't cp the Explore stories (production has different concerns: autodocs, no decision metadata), validate, then ast-grep callsites only if a path changed.
Path B — UPDATE existing. Apply the Explore's diffs into the production component + stories in place; ast-grep only if the import path changed.
Both — close the loop IN PLACE (no git mv): tags: ['explore','decision:chosen','archived','!autodocs','!test'] + parameters.decision = { status, winner, date, shippedTo }. Confirm with find-stories-by-tag.sh decision:chosen.

Gate + next

Run the bundled scripts/validate-stories.sh on the new production story (in the bundle: ${CLAUDE_PLUGIN_ROOT}/scripts/validate-stories.sh, or ${CLAUDE_PLUGIN_ROOT}/scripts/). Confirm the flip with scripts/find-stories-by-tag.sh decision:chosen. Append the decision to the ledger (templates/design-decisions.md); the graduated experiment stays put.

Re-enter the usage flow. A graduated component is new to src/ — it isn't in the rendered JSONs yet, so its Docs "Real usage" band and storyCoverage are blank. Trigger the one-command usage refresh (refresh-usage.sh, owned by sb-audit/sb-inventory) so the new component enters component-usage.json / project-inventory.json; a Storybook rebuild then shows its real usage. Then /sb-hub.

---name: sb-shipdescription: Graduate ONE Explore experiment to a production component — preserve the experiment (cp, never git mv), pick new-vs-update, close the decision loop. Use for 'ship this', 'promote this experiment', 'graduate to production'.license: MIT---# sb-ship — graduate, preserving historyEvent-triggered when an Explore iteration meets the graduation gate. **The one rule that matters:preserve the experiment — `cp`, never `git mv`.** The Explore story stays as design history;`git mv` here is the destructive bug `propagate-workflow.md` exists to prevent. **Load`references/propagate-workflow.md` before any Ship action** — it's the *only* referencethis skill needs; **Do NOT load** the sb-wrappers/sb-audit refs (lifecycle, galleries, composition) fora Ship.## Decide the path (ask yourself)- **Did the Explore define its own component file, or iterate on an existing one?** → Path A vs Path B.- **Path B: evolve in place (B1) or keep V1 in `_legacy/` (B2)?** B2 only when V1 still has live callsites needing a migration window.- **Did the import path change?** If yes → `ast-grep` callsites. If not → skip it.- **Other tagged stories that should flip?** (a Compare `decision:pending` → `decision:chosen` + winner.)## Execute- **Path A — NEW component.** `cp` the component explore→components, write a *fresh* production stories file **to the recorded `storiesLocation`** (`.storybook/audit/status.md`; the rule lives in `CONTEXT.md` §STORIES LOCATION — never scatter) — don't `cp` the Explore stories (production has different concerns: autodocs, no decision metadata), validate, then `ast-grep` callsites only if a path changed.- **Path B — UPDATE existing.** Apply the Explore's diffs into the production component + stories in place; `ast-grep` only if the import path changed.- **Both — close the loop IN PLACE** (no `git mv`): `tags: ['explore','decision:chosen','archived','!autodocs','!test']` + `parameters.decision = { status, winner, date, shippedTo }`. Confirm with `find-stories-by-tag.sh decision:chosen`.## Gate + nextRun the bundled `scripts/validate-stories.sh` on the new production story (in the bundle:`${CLAUDE_PLUGIN_ROOT}/scripts/validate-stories.sh`, or`${CLAUDE_PLUGIN_ROOT}/scripts/`). Confirm the flip with `scripts/find-stories-by-tag.shdecision:chosen`. Append the decision to the ledger (`templates/design-decisions.md`); the graduated experiment stays put.**Re-enter the usage flow.** A graduated component is new to `src/` — it isn't in the rendered JSONsyet, so its Docs "Real usage" band and `storyCoverage` are blank. Trigger the one-command usage refresh(`refresh-usage.sh`, owned by `sb-audit`/`sb-inventory`) so the new component enters `component-usage.json`/ `project-inventory.json`; a Storybook rebuild then shows its real usage. Then `/sb-hub`.

Frequently asked questions