메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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 a new top-level `launch` command or subcommand — wire it as thin commander code and regenerate the docs the CLI surface drives.
| name | add-a-glossary-topic |
| description | 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. |
launch explain topicsrc/core/terminal/glossary.ts — the single source for teaching text. It feeds both launch explain and the --explain step expansions; never duplicate the strings elsewhere.src/core/terminal/glossary.test.ts (expect(topics.length).toBe(N)) by the number of topics you added, and add a toContain(...) assertion per new topic.The toBe(N) count is a known merge hotspot: if a concurrent PR also added a topic, the count collides. On rebase, sum both additions rather than taking one side, and keep both topics.
See AGENTS.md.