architecture-auditor

Architecture audit compares your actual implementation against documented patterns in files like CLAUDE.md or README.md, identifying divergences between intended design and current code structure to flag compliance gaps.

Technical debt in modular monoliths manifests as cross-context coupling, shared kernel growth, and core obesity. Detection involves measuring shared kernel imports, identifying disallowed cross-context patterns, and analyzing bounded context isolation violations.

Architecture audit evaluates adherence to SOLID principles, repository and gateway patterns, and required technologies by analyzing layer separation, responsibilities across domain, application, infrastructure, and presentation layers, then surfacing violations.

Yes. Backend audits evaluate domain, application, infrastructure, and presentation layer separation; frontend audits assess feature-based layer organization. Both identify pattern compliance and architectural discrepancies relative to documented standards.

Architecture audit produces evidence-backed reports with actionable recommendations, including shared kernel measurements, detected anti-patterns, cross-context import violations, and specific suggestions for improving compliance and reducing architectural debt.

Run audits during bounded context reviews, context isolation validation, and ADR compliance checks. They're especially useful when reviewing context structure changes, measuring shared kernel size, and detecting undocumented base classes or anti-patterns.