- 📁 assets/
- 📁 references/
- 📁 scripts/
- 📄 SKILL.md
Guide for implementing the Architect-First development philosophy - perfect architecture, pragmatic execution, quality guaranteed by tests. Use this skill when starting new features, refactoring systems, or when architectural decisions are needed. Enforces non-negotiables like complete design/documentation before code, zero coupling, and validation by multiple perspectives before structural decisions.
- 📁 data/
- 📁 scripts/
- 📄 PROMPT.md
- 📄 SKILL.md
strategic planning, career & business decisions. Use when user says "decide",
Manages Architecture Decision Records (ADR) for tracking important architectural decisions
Triage new issues and PRs on awesome-list repos by applying curation criteria distilled from past decisions.
Reconstruct high-level past events (decisions, commitments, timelines) from /chronicle chapters. Use for longer-term recall beyond what <context_summary> paragraphs cover — arc of past discussions, decisions made, what happened last week(s).
Combines uctx (decisions), ubus (messaging), and uinit (initialization).
functions/types/files, planning refactors, or needing context about past decisions.
You MUST use this skill when the user wants to discuss, analyze, or explore ideas before making decisions. Triggers on: \"讨论一下\", \"我想聊聊\", \"帮我分析\", \"我们来探讨\", \"let's discuss\", \"I want to talk about\", or any request for in-depth conversation about architecture, design choices, or technical decisions. Usage: (1) Explicit - use slash command to select this skill; (2) Implicit - automatically triggered by keywords above. Provides structured discussion facilitation with decision precipitation.