improve-codebase-architecture

To refactor shallow modules into deep modules, you analyze code dependencies and domain language to restructure interfaces. This process enhances codebase architecture by hiding complexity behind deeper modules, which improves overall testability and maintainability.

Identifying shallow modules involves analyzing your code structure against architectural principles to find interfaces that do not hide sufficient complexity. This Skill reviews your codebase, highlights these problematic interfaces, and recommends refactoring suggestions to deepen them.

Improving code testability after major updates requires converting shallow modules into deep modules to better encapsulate domain logic. This Skill assesses your updated codebase structure, analyzes dependencies, and proposes interface designs that yield higher testability.

Yes, you can use architectural decision records (ADRs) to guide codebase refactoring. This Skill integrates existing ADRs to inform its analysis, ensuring that the recommended module depth and interface refactoring suggestions align with your project's recorded architectural decisions.

Yes, the code structure analysis outputs an HTML report visualizing refactoring scenarios. This comprehensive report compares before-and-after states of deepened modules, presents parallel interface design suggestions, and recommends a starting point for your refactoring effort.

You should avoid deep module refactoring when your codebase lacks clear domain language or suffers from unresolved circular dependencies. If the architectural analysis cannot isolate problematic interfaces, forcing module depth may increase coupling rather than improve maintainability.