菜单
Use when the user says /catalog, "what skills are available", "show me the toolkit", "list my skills/agents/rules", or wants an in-session inventory of claude-config rules, skills, agents, and templates without leaving the session to grep docs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | catalog |
| description | Use when the user says /catalog, "what skills are available", "show me the toolkit", "list my skills/agents/rules", or wants an in-session inventory of claude-config rules, skills, agents, and templates without leaving the session to grep docs. |
| disable-model-invocation | true |
Renders the in-repo claude-config inventory (rules, skills, agents, templates) from docs/catalog.md, grouped by purpose. Purely informational — no side effects.
The model does not auto-invoke this skill. It runs only when the user explicitly types /catalog (or one of its argument forms).
skills — Skills only (pipeline + leader + ops).agents — Agents only.rules — Rules only.leader — Senior eng leader toolkit only (/onboard, /strategy-doc, /swot, /stakeholder-map, /1on1-prep, /present).templates — Templates only (drop-in scaffolds shipped by the repo).ecosystem — Third-party plugins this config plays well with.--mine — List skills present under ~/.claude/skills/ that are NOT documented in the canonical docs/catalog.md. Useful for finding plugin skills (caveman, superpowers, harness) and user-added skills outside the claude-config repo.Arguments are mutually exclusive except --mine, which combines with any group filter.
Resolve the canonical catalog path in this order:
<repo-root>/docs/catalog.md — if the current working directory is inside the claude-config repo.~/repos/claude-config/docs/catalog.md — the user's canonical clone.The catalog file is the single source of truth. Do not re-derive tables from disk scans — render what's documented.
docs/catalog.md uses H2/H3 headers and GitHub-flavored markdown tables. Map argument → section:
| Argument | Section header(s) to render |
|---|---|
| (no args) | All H2/H3 sections in order |
rules | ## Rules (always active) |
skills | ### Pipeline + design-thinking, ### Senior eng leader toolkit, ### Other operational skills |
agents | ## Agents (specialized reviewers) |
leader | ### Senior eng leader toolkit |
templates | ## Templates |
ecosystem | ## Ecosystem (third-party plugins this config plays well with) |
Render the matching tables verbatim. Do not paraphrase rows — the catalog file owns the descriptions.
When --mine is present:
~/.claude/skills/ via ls or Glob.docs/catalog.md (scan rows in the skills tables; strip leading / from slash-command names).~/.claude/skills/* MINUS catalog-documented skills.superpowers:*, caveman:*, harness:*) vs. unprefixed entries (likely user-added).--mine is a diff, not a full inventory. Output explicitly labels what's NOT in the canonical catalog.
docs/catalog.md.leader arg, prepend a one-line context: "Senior eng leader toolkit — 90-day ramp orchestration."--mine with no extras found: "No skills found outside the canonical catalog."~/.claude/skills/ listing — does not query MCP servers or plugin marketplaces.docs/catalog.md./catalog
→ Full inventory (workflow diagram + rules + all skills + agents + templates + ecosystem).
/catalog leader
→ Senior eng leader toolkit table only.
/catalog skills --mine
→ Skills directories present under ~/.claude/skills/ but absent from docs/catalog.md, grouped by plugin prefix.
docs/catalog.md — canonical inventory this skill renders.rules/README.md — rule install contract; rules listed in the catalog are the HARD-GATE set.bin/link-config.fish — installs the symlinks that make catalog entries available at runtime.Use when the user says /org-design <org>, "analyze the org I inherited", "inherited org analysis", "span of control / SPOF / on-call distribution review", or wants a descriptive read of the org structure they just walked into during a senior eng leader ramp. The analyze mode reads a manual org/structure.md + stakeholder memory graph into a 7-section analysis under ~/repos/onboard-<org>/decisions/. The scenario mode projects a reorg (split-team, add-headcount, merge-teams, change-reporting, reduce-headcount), validates it structurally, and gates on explicit user review before writing. reduce-headcount adds a machine layoff-acknowledgment gate (machine-enforced deliberateness; the human confirmation behind the flag is prose-bound, not machine-verified). Do NOT use for codebase architecture (use /architecture-overview).
Use when the user says /risk-register, "add a risk", "review risks", "escalate R-N", "ack R-N", "resolve R-N", or "show my risk register" during a 90-day ramp or any initiative. Tracks org-level technical risks in any initiative workspace. Six actions: add, review, ack, escalate, resolve, list.
Use when the user says /strategy-doc <org>, "draft my 90-day plan", "review the 90-day plan", or "challenge the 90-day plan" during a senior eng leader ramp. Phase 1 supports the 90-day-plan mode only — collates /swot + /stakeholder-map + /architecture-overview + free-form notes/*.md into a 7-section markdown artifact under ~/repos/onboard-<org>/decisions/. Cross-org RFC mode is Phase 2 (separate spec).
Use when the user explicitly invokes /glossary, asks to canonicalize a domain term in ./CONTEXT.md, or wants to record agreed-upon project-specific terminology so future sessions and downstream artifacts (ADRs, SDRs, systems-analysis output) stay consistent. Also invoked by define-the-problem and systems-analysis at end-of-skill via the caller-hook contract to offer canonicalization for terms resolved during planning. Write-only format-owner for per-project ./CONTEXT.md. Lazy-create on first term resolution; never auto-write — user approval gates every entry. Do NOT use for: casual term mentions in conversation, code-level naming questions, architectural primitives (Module, Interface, Adapter, Seam — those belong in LANGUAGE.md owned by architecture-overview), general programming concepts, or decisions about why a term was chosen (those belong in docs/superpowers/decisions/ or an ADR).
Use when the user says /ring-review-tiered, "ring review these PRs", "antagonistic ring on this batch", "review PR #N with the ring", or asks to run adversarial / critic review across one or more pull requests. Calibrates critic count to per-PR risk tier — trivial PRs skip the ring, surgical PRs get one cross-dimension critic, medium PRs get two dimension-targeted critics, large/boundary/security PRs get the full 5-critic ring plus arbiter. Use even when the user names a uniform critic count — surface the tier and let them override. Do NOT use for solo single-PR review where the user explicitly asks for the full ring; that's `pr-review-toolkit:review-pr`.
Use when the user says /swot, "landscape analysis", "SWOT analysis", "strengths and weaknesses", or wants to capture, review, or challenge organizational observations.