メニュー
Enters teaching mode to explain a concept, pattern, or decision in the codebase. Invoke when the user wants to understand something rather than build it. Presents the topic in three progressive levels and pauses for confirmation between each.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
System design skill for complex multi-component projects. Produces a system diagram, component breakdown, API contracts, data model, and tech decisions before any code is written. Run /architect before /createplan on anything that spans more than one layer (frontend + backend, multiple services, or a new data model).
Creates a structured implementation plan document. Invoke after /explore Q&A is complete and all ambiguities are resolved. Produces a markdown plan with steps, subtasks, key decisions, and risks.
Curates the owner's reference library at ~/.claude/references/repos.yaml. Each entry is a GitHub repo you find inspiring — patterns to copy, products to study, stacks to learn from. The skill ingests the repo's signal files (README, manifests, schemas, docs) into the local 'refs' ChromaDB collection so /cto and github-scout pull from YOUR curated taste, not generic GitHub search. Idempotent — re-running on an existing entry is safe.
Generates an exhaustive product-facing PRD with screens, features, flows, landing page mock, and visual direction. This is the artifact the operator reviews BEFORE any code is written. Output is both narrative (prd.md) and visual (lightweight HTML wireframes for every screen + landing page). Run after /grill (and /benchmark if competitive) and before /architect. The prd-reviewer agent must PASS before the user is brought in for manual review.
Produces an exhaustive feature matrix for a competitive product category BEFORE any PRD is written. Rows = atomic features, columns = competitors + you, cells = yes/no/partial with evidence. Forces "does product X do feature Y?" instead of prose summaries where features slip through. Run this before /grill, /architect, or any PRD work on a competitive product. Replaces lazy prose teardowns.
YC-style forcing questions before writing any code. Six questions that reframe the product, challenge bad assumptions, and surface the 10-star version. Run this before /architect or /createplan on any new product or major feature. Stops you from building the wrong thing.
| name | learning |
| description | Enters teaching mode to explain a concept, pattern, or decision in the codebase. Invoke when the user wants to understand something rather than build it. Presents the topic in three progressive levels and pauses for confirmation between each. |
| argument-hint | ["concept or topic to explain"] |
Pause development mode. The user wants to understand something — a concept, a pattern, a decision in the code. Teach it well.
If the topic isn't clear from context, ask: "What do you want to understand?"
If the topic is in the codebase, read the relevant code before explaining it. Don't explain an abstraction when you can show the actual implementation.
Present the concept at three levels. Stop after each level and ask: "Does that land? Want me to go deeper?" Don't dump all three at once — let the user pace the conversation.
Cover in 3-5 sentences:
No code yet unless a one-liner makes the concept click instantly.
Cover:
Keep this under ~10 sentences. If you need more, you're going too broad.
Cover:
This level is optional — only go here if the user asks or if the concept genuinely has production-relevant gotchas.
Peer-to-peer, not lecture. You're explaining something to a colleague who's smart but hasn't seen this pattern before. Honest about complexity: "this is genuinely tricky because..." is better than a clean but misleading simplification. If the concept is simple, say so.
