菜单
This skill should be used when the user asks "where is X", "how does X work", "explain X", "show me the architecture", "find component", "what handles X", or references C3 IDs (c3-0, c3-1, adr-*). Requires .c3/ to exist. For changes, route to c3-alter instead.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user asks to "add a component", "change architecture", "refactor X", "implement feature", "fix bug", "create new service", "update diagram", or "remove component". Requires .c3/ to exist. All changes flow through ADR process. For questions, route to c3-query instead.
This skill should be used when the user asks to "adopt C3", "onboard me to architecture", "scaffold C3 docs", "init C3", "audit architecture", "validate C3", or "check C3 docs". Also triggers when no .c3/ directory exists. Routes to c3-query for navigation, c3-alter for changes.
Creates C3 architecture documentation from scratch using staged Socratic discovery. Use when the user asks to "adopt C3", "onboard me to architecture", "scaffold C3 docs", "init C3", "set up architecture docs", or starts C3 documentation for a new project. Implements 3-stage workflow: Inventory → Details → Finalize.
| name | c3-query |
| description | This skill should be used when the user asks "where is X", "how does X work", "explain X", "show me the architecture", "find component", "what handles X", or references C3 IDs (c3-0, c3-1, adr-*). Requires .c3/ to exist. For changes, route to c3-alter instead. |
Navigate C3 docs AND explore corresponding code. Full context = docs + code.
../../references/skill-harness.md - Routing and red flags../../references/layer-navigation.md - How to traverse C3 docsQuery → Clarify Intent → Navigate Layers → Extract References → Explore Code
│
└── Use AskUserQuestion if ambiguous
Ask when:
Skip when:
Follow layer navigation: Context → Container → Component
| Doc Section | Extract For Code |
|---|---|
| Component name | Class/module names |
## References | Direct file paths, symbols |
| Technology | Framework patterns |
| Entry points | Main files, handlers |
If query relates to patterns/conventions:
.c3/refs/ for ref-* matching topicUse extracted references:
src/auth/**/*.ts## References| Type | User Says | Response |
|---|---|---|
| Docs | "where is X", "explain X" | Docs + suggest code exploration |
| Code | "show me code for X" | Full flow through code |
| Deep | "explore X thoroughly" | Docs + Code + Related |
**Layer:** <c3-id> (<name>)
<Architecture from docs>
**Code References:**
- `path/file.ts` - <role>
**Key Insights:**
<Observations from code>
**Related:** <navigation hints>