← ClaudeAtlas

super-shiplisted

The bulletproof ship for structural work. Run the full drift audit, fix the broken and stale findings, then ship the combined result live via the ship flow. Use when asked to super ship, audit and ship, or ship bulletproof, or when shipping a structural change where the docs and skills may have gone stale. For a small change, plain ship is enough.
robritacca-dotcom/design-system · ★ 0 · Web & Frontend · score 66
Install: claude install-skill robritacca-dotcom/design-system
# super-ship Drift audit, fix, ship — one invocation. A higher-order skill: it composes `drift-audit` and `ship` and owns only the rules of the composition. Everything about *how* to audit lives in `.claude/skills/drift-audit/SKILL.md`; everything about *how* to ship lives in `.claude/skills/ship/SKILL.md`. Read both and follow them; this file only says how they connect. ## When invoked Use this skill when asked to "super ship", "audit and ship", or ship "bulletproof" — typically after structural or architectural work (a moved directory, a new build step, a renamed surface, a changed dependency model) where the repo's self-descriptions may have gone stale and a plain ship would deploy them stale. **Not for small changes.** A colour tweak, a copy fix, a single-component change: that's plain `ship`. The audit sweeps every skill and doc, and running it for a one-line change is ceremony, not safety. If invoked on something clearly small, say so and offer plain `ship` instead. **Invoking this skill is the ask to ship.** `ship`'s guardrail says never to chain into it automatically from other work, and `drift-audit`'s says the report is the deliverable and fixes wait for approval. This skill is the sanctioned exception to both: by invoking it, Rob has pre-approved fixing the drift the audit finds *and* deploying the result. The carve-outs below say where that pre-approval stops. ## Instructions ### 1. Audit Run the full `drift-audit` flow per its SKILL.md — every section, no