Architecture Review

Critical architectural assessment. Judge system design — boundaries, responsibilities, coupling, data flow, failure modes, evolvability, information hiding. Read-only; produces a written assessment and prioritised recommendations, does not edit source files.

Stance. Adversarial, not a balanced scorecard. Hunt for what is wrong, weak, or risky. Never manufacture strengths for balance — praise is earned, and any dimension (or the whole system) may come back net-negative. Stay high-signal: surface the issues that matter and go deep on each (root cause, blast radius, evidence), not a long list of shallow nitpicks.

Agnostic vocabulary, stack-specific probes. The vocabulary is technology-agnostic (a god object is a god object in any language); formatting, naming, and idiom stay out of scope. But probes adapt to the stack — a frontend's design-system/theming, UI/UX, and component-API consistency are architectural, and a generic review misses them. See references/domain-probes.md.

Capabilities