improve-codebase-architecture

To identify shallow modules for refactoring, analyze your project's ADRs and architecture documents to find spots where the interface nearly matches the implementation. This surfaces deepening opportunities to turn them into deeply testable units.

A shallow module in software architecture is a component where the interface is nearly identical in complexity to its implementation. Identifying these modules helps surface friction and guides refactoring efforts to create deep, testable units.

To refactor shallow modules and improve testability, review your domain glossaries and ADR constraints to propose deepening actions. Constrain suggestions to existing domain language to ensure the refactored modules are easier to navigate and evolve.

Yes, this architecture analysis reads your project's ADRs, CONTEXT.md, and architecture-related documents to align recommendations with your domain language and constraints. These documents provide the necessary vocabulary for before and after visualisations.

Yes, you can generate an HTML report visualizing architectural friction and deepening opportunities. The report includes before and after visualizations aligned with your domain vocabulary, a recommended top candidate to deepen, and a grid of trade-offs.

The best way to align architectural refactoring with domain language is to constrain suggestions strictly to existing terms found in your CONTEXT.md and LANGUAGE.md files. This approach respects the domain language and avoids proposing new interfaces during the analysis.