القائمة
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.