Code Architecture Review

This one's for catching the structural problems that make your codebase progressively harder to change. It reviews architecture through the lens of dependencies and coupling, asking whether modules can be tested in isolation and whether they have single, clear responsibilities. Use it when evaluating PRs with structural changes, planning refactors, or before releases when tech debt has piled up. The philosophy here is pragmatic: good architecture is invisible, bad architecture is a constant tax. It comes with reference files for patterns, known sharp edges, and validation rules, so you're getting specific guidance rather than generic best practices. Honest take: most teams wait too long to do this kind of review, and by then the fixes are 10x more expensive.