Menu
Use when adding a new top-level `launch` command or subcommand — wire it as thin commander code and regenerate the docs the CLI surface drives.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when adding or changing a build, storage, credentials, submit, or compute backend in launch-store — implement one of the five provider interfaces and register it, without touching the pipeline.
Use when finishing or verifying a change to launch-store — run the full typecheck, lint, test, build, and docs gate that must be green before a change is done or a PR merges.
Use when adding teaching text for a concept or step in launch-store — add it to the single glossary source that feeds both `launch explain` and the `--explain` step expansions.
| name | add-a-command |
| description | Use when adding a new top-level `launch` command or subcommand — wire it as thin commander code and regenerate the docs the CLI surface drives. |
launch <command> or subcommanddocs:check failure after changing the CLI surfacesrc/cli/commands/ and register its register*Command in src/cli/program.ts's buildProgram(). Keep domain logic in src/core, not the CLI layer.npm run docs:gen — it introspects buildProgram() and regenerates docs/commands.md, llms.txt, the README stats badges, and the committed .cursor/rules / .claude/skills.npm run docs:check (CI) fails if they drift.*.test.ts beside the new logic, then run the gate.The docs are generated from the live buildProgram() in src/cli/program.ts, so a new command surfaces in the reference automatically once you run docs:gen — never hand-edit the generated files.
See AGENTS.md.