improve-codebase-architecture

To find architectural friction, analyze module depth, seams, locality, and coupling to identify shallow modules needing deeper interfaces. This surfaces consolidation opportunities and tighter seams to improve testability, domain language clarity, and AI-navigability without re-litigating settled architecture.

A shallow module has an interface nearly as complex as its implementation, requiring bouncing across too many files to understand logic. Deepening these modules improves testability by establishing clearer seams and better locality for both human and automated testing.

Review codebase architecture by reading project glossaries, decisions, and code structure to propose module deepening opportunities. Analyze where coupling leaks across modules to produce a visual architecture review with concrete refactoring candidates and a top recommendation.

Yes, this approach reads project decisions and glossary entries to guide analysis. It proposes refactoring opportunities that respect and build upon settled architecture rather than re-litigating prior design decisions.

Avoid module deepening refactoring when prior architecture decisions have already settled the design constraints. Re-litigating settled architecture defeats the purpose; only surface refactoring candidates where coupling leaks across modules without overriding established project context.