Menu
Answer "why" questions about architectural choices using arkive/architecture.json.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Open the arkive web viewer to browse the project's architecture interactively.
Process queued architecture prompts from the web viewer. Drains the prompt queue by claiming, executing, and acknowledging each prompt.
Maintain the living architecture document as you build. This is the core skill — always active when arkive/architecture.json exists.
Convert an existing project into arkive by analyzing git history or filesystem dates. Builds a phased, history-rich arkive/architecture.json.
Initialize arkive architecture tracking in the current project. Handles MCP registration and skill installation.
Socratic quizzing after architecture updates. Optional — activates when user opts in.
| name | explain-decisions |
| description | Answer "why" questions about architectural choices using arkive/architecture.json. |
| trigger | User asks "why did we choose X?", "why this database?", "why not use Y?", "explain the architecture", or clicks "Why this?" in the web viewer. |
Read architecture data:
architecture://decisions resourcedecisions array from arkive/architecture.jsonFind the relevant decision: Search by topic, decision, or relatedServices matching the user's question.
Explain with this structure:
## {topic}
**Decision:** {decision}
**Why:** {rationale}
**Alternatives considered:**
- **{alternative.name}**: Rejected because {alternative.whyNot}
**Related services:** {relatedServices}
If no matching decision exists:
record_decision to document this choice"arkive/architecture.json"Connect to the bigger picture: After explaining, briefly mention how this decision relates to other architectural choices in the project.