architecture

Design or audit system boundaries and consequential technical decisions. Triggers on "system design", "架构设计".

SKILL.md

GitHub

Architecture

When to use

  • Design or audit system boundaries and consequential technical decisions.

Not for: spec for behavior; codebase-design for existing module boundaries.

Steps

  1. Extract confirmed behavior, real constraints and operational context; do not invent quality thresholds.

  2. Investigate comparable implementations and current official docs for consequential choices; compare complexity, failure modes and operating costs.

  3. Define components, trust boundaries, ownership, contracts and recovery using the simplest adequate architecture.

  4. Record significant decisions and rejected alternatives; prepare TECH and risk-based human review before dependent implementation.

Output: Suggested paths, subject to human audit: docs/TECH.md; optionally docs/vX.Y/tech.md and docs/design/adr/NNNN-slug.md.

Verify

  • Boundaries and failure paths fit requirements; significant decisions have evidence, trade-offs and review criteria.

References