architecture

Run the skill in review mode with an optional path to score the codebase across nine dimensions including modularity, layering, and dependency direction. It gathers structural metrics like circular dependencies, fan-in/fan-out, and temporal coupling before producing a weighted health score with evidence.

Use ADR mode to document a technical decision such as a framework or data store choice. The skill checks existing ADRs for conflicts, evaluates at least two options across complexity, cost, scalability, and lock-in, then saves a structured record to docs/adr/.

The review collects dependency cycles via madge, duplication via jscpd, complexity via radon, cross-module fan-in and fan-out, instability indices, module sizes, and temporal coupling from git history. These metrics provide evidence for the nine dimension scores.

Yes, design mode follows a six-step framework covering requirements, high-level design, deep dives into data models and APIs, scale and reliability planning, rollout and migration strategy, and explicit trade-offs. The output is a design document saved to docs/design/.

Per-file code quality, test quality, business logic correctness, and general security vulnerabilities are excluded and handled by other dedicated audit skills. Architectural security such as auth boundaries and input validation placement remains in scope.