Skill Launch Cheatsheet
ShipGlows skills are not all simple free-text commands. Some arguments
describe the work, some switch modes, and some select a structured
target. Start with shipglows <instruction> when you
want routing handled, then use direct master or owner skills when you
already know the lane.
The Short Version
shipglows <instruction> when you are not choosing manually.The router answers pure questions directly or hands the main thread to the selected skill. Direct master skills still matter when you already know the exact lifecycle you want handled. It asks one numbered decision question when no context-safe route is available.
Why It Matters
The point is not to memorize syntax. The point is to recognize when a skill exposes distinct workflows behind one command name.
Runtime Families
Public categories make the catalog easier to browse. Runtime families explain how ShipGlows routes work: lifecycle owners carry work, source skills expose future chantiers, proof skills validate behavior, and helpers keep orientation clean without owning closure. Routing should preserve quality and proof first; shortest path is not the default objective.
Carry a work item across several gates.
Examples: shipglows, sf-build, sf-maintain, sf-deploy, sf-design, sf-content, sf-customer
Frame local-first user data becoming account-backed cloud data.
Examples: sf-local-cloud-sync
Expose risk or drift that may need a chantier.
Examples: sf-audit*, sf-deps, sf-perf, sf-platform-parity
Diagnose failures, prove behavior, or validate deployment truth.
Examples: sf-bug, sf-fix, sf-test, sf-browser, sf-auth-debug, sf-prod, sf-check, sf-migrate
Keep public content, docs, scaffolding, changelogs, skill maintenance, and git/GitHub hygiene coherent.
Examples: sf-content repurpose, sf-docs, sf-redact, sf-enrich, sf-changelog, sf-scaffold, sf-init, sf-github-hygiene
Clarify information, prioritize, summarize, route, or preserve context.
Examples: 009-sg-marketing, sf-research, sf-veille, sf-backlog, sf-priorities, sf-review, sf-tasks, sf-context, sf-model, sf-help, sf-status, sf-resume, sf-explore, name
Primary And Master Skills
shipglows <instruction> Recommended non-technical first command when you want ShipGlows to choose the route. sf-build <story, bug, or goal> Direct entrypoint for non-trivial product, code, docs, or site work. sf-maintain [mode] Recurring project upkeep across bugs, docs, dependencies, checks, audits, fixes, and ship routing. sf-deploy [target or mode] Release confidence after implementation when checks, push, deployment truth, browser proof, and verification must stay connected. sf-bug [BUG-ID, summary, or mode] Bug-loop lifecycle execution from observed failure to dossier, fix, retest, verification, and ship risk. sf-content [goal, source, file, or mode] Content management across strategy, repurposing, drafting, enrichment, audits, docs, validation, and ship routing. 009-sg-marketing <mode> <target> Use when the unmet need is market evidence, GTM readiness, copy clarity, or persuasion—not a broader content lifecycle. sf-design <design question or goal> Design lifecycle across UI/UX, tokens, playgrounds, component and accessibility audits, implementation, browser proof, and ship routing. sf-customer <feature, flow, or audit target> End-user experience review for UX/UI clarity, friction, trust, first-success paths, setup sequencing, recoverable states, docs impact, and proof routing. sf-local-cloud-sync <project, feature, or data domains> Local-to-cloud data sync contract for local data promotion, account association, merge policy, sync UX, and security. sf-product-entitlements <project or feature> Product access and entitlement contract for premium gates, provider events, support access flows, and backend authorization. Supporting Skills
sf-spec -> sf-ready -> sf-start -> sf-verify -> sf-end Use the manual lifecycle when you want explicit control over each gate instead of the sf-build master flow. sf-ship [mode] Use after work is already ready locally. Modes include skip-check, end la tache/end/fin/close task, and all-dirty/ship-all/tout-dirty. sf-browser / sf-auth-debug / sf-test / sf-prod Choose by proof type: non-auth browser evidence, auth/session diagnosis, checklist-first manual QA, or live deployment truth. sf-check / sf-docs / sf-audit* / sf-deps / sf-migrate Use focused owner skills when you need one lane: checks, docs, audit, dependency posture, or framework migration. sf-github-hygiene [mode] Use when the problem is git/GitHub hygiene: sync drift, stale branches, PR drift, or Dependabot backlog triage. sf-platform-parity <project, feature, or spec> Use when platform claims, implementations, or QA proof may drift across web, mobile, desktop, or native surfaces. sf-status / sf-help / sf-model / sf-resume Use support skills for orientation, command choice, model routing, and clean context transfer. Documented Mode Switches
If a skill is not listed here, treat its argument as a target or task description unless the skill file says otherwise.
shipglows The primary non-technical router for answering questions, executing deterministic micro-edits directly, or handing substantive work to the right ShipGlows skill.
<instruction>
sg-bug A professional bug loop executor that reads bug state and continues through the right ShipGlows owner skills when safe.
no argument / BUG-ID / --retest BUG-ID / --ship BUG-ID
sg-build The master user-facing lifecycle orchestrator for carrying a story, bug, or goal through ShipGlows's spec, readiness, implementation, verification, onboarding consideration, documentation, closure, and shipping gates.
<story, bug, or goal> / agents / no-agents / report=agent / handoff / verbose / full-report
sg-platform-parity Audits platform parity, separates legitimate platform adaptations from implementation debt, and routes missing work to the right ShipGlows skill.
<project | feature | spec path> / platforms=<list> / report=agent / handoff / verbose / full-report
sg-ship A shipping skill for moving finished work through the final commit-and-push path and recording the shipping result when a chantier spec is in scope.
no special argument / skip-check / end la tache / end / fin / close task / all-dirty / ship-all / tout-dirty
sg-audit-translate A translation audit and controlled i18n sync skill for completeness, tone consistency, cross-language coherence, and missing localized entries.
no special argument / file path or scope / global / sync / apply / sync [path] / apply [path]
sg-content A master content lifecycle skill for routing strategy, repurposing, drafting, enrichment, audits, public-content governance, validation, and ship readiness through the right owner skills.
capture-full-conversation / clean-transcript <path> / plan / strategy / repurpose <source> / draft / article / blog / guide / enrich / audit / marketing / seo / apply / publish / ship
sg-github-hygiene A git/GitHub hygiene skill for sync drift, stale branches, PR drift, and Dependabot backlog triage with bounded safe fixes.
audit / branches / dependabot / fix
sg-tasks A task-management skill for updating `TASKS.md`, reflecting progress, and capturing the next sensible steps.
sessions <project-or-cwd> / sessions rename <status>
sg-design The single public design entrypoint for system creation, playgrounds, UI/token/component/accessibility audits, implementation, proof, verification, and shipping.
system [scope] / audit <ui|tokens|components|a11y> [scope] / playground [route-path] / redesign [scope] / migration [scope]
sg-deploy A release orchestration skill for moving work through technical checks, bounded shipping, deployment readiness, post-deploy evidence, final verification, and optional changelog routing.
no argument / skip-check / --preview / --prod / no-changelog
sg-customer A customer-experience skill for UX/UI clarity, friction, trust, first-success paths, onboarding, setup sequencing, recoverable states, docs coherence, and proof routing.
audit [scope] / flow [feature-or-flow] / onboarding [feature-or-flow] / recovery [feature-or-state]
sg-maintain A master maintenance lifecycle skill for reviewing project health, creating or continuing specs when needed, delegating remediation, verifying results, and routing ship or deploy.
no argument / full / quick / security / deps / docs / audits / no-ship / global
sg-local-cloud-sync A data-sync skill for local data promotion, cloud hydration, merge/conflict policy, sync UX states, sensitive-data exclusions, and proof routing.
project or feature / audit / Flutter / secrets / sensitive data / sync overlay / SocialGlowz
sg-conversation-audit A focused audit lane that reads canonical conversation evidence, classifies repeatable failure patterns, and routes recommended owners.
latest / path <file-or-dir> / export shipglows / report=agent
A specific word acts as a switch. The skill recognizes it and enters a specialized workflow instead of treating it as ordinary task text.
The argument has a recognizable shape. The skill parses that shape and derives a target from it, such as a package and a version.
If no special keyword or input pattern matches, the argument is usually treated as the actual work description or content focus.
Example: sf-docs
The documentation skill is a clear example. Certain arguments are not content scopes. They are direct mode switches.
sf-docs metadataThis switches to the frontmatter and metadata workflow. The skill reads migration doctrine, classifies files, and validates the result against the metadata rules.
sf-docs migrate-frontmatterThis is another explicit trigger for the same family of metadata work. It does not mean “write docs about frontmatter.” It means “run the frontmatter migration workflow.”
sf-docs readmeHere the argument acts more like a target surface. The skill is now being steered toward a documentation area rather than a dedicated metadata mode.
Example: sf-migrate
The migration skill does not only react to keywords. It also reacts to how the argument is structured.
sf-migrate astro@5A structured target. The skill interprets this as “migrate Astro to version 5” and builds the upgrade workflow around that exact goal.
sf-migrate astroA package target without version. The skill treats it as a request to resolve the latest version first, then confirm the path.
sf-migrateNo argument means discovery mode. The skill looks for possible upgrades and asks which migration you actually want to run.
How To Read A Skill
argument-hintThis tells you whether the skill expects a free-form task, a target surface, a package pattern, or a small set of known trigger words.
If the file contains lines such as “If $ARGUMENTS is ...”, you are looking at an explicit routing layer rather than a loose prompt.
Two skills can both accept one argument and still interpret it in completely different ways. The contract lives in the skill file.
Shell Shortcuts
ch
Expands to clear; tmux clear-history. It clears the
current shell screen and the current tmux pane scrollback.
Next Step
Start with the mode rules, not with your intuition. That is the fastest way to understand what the skill will actually do once execution starts.