improve-codebase-architecture

To find shallow modules in your codebase, run an architecture scan to surface deepening opportunities. It applies architecture heuristics to identify candidate modules that would benefit from a seam-based refactor and presents them in an HTML report with before/after visuals.

A seam-based refactor introduces an interface boundary to isolate shallow modules, enabling easier testing and navigation. You need one when architectural friction prevents domain-aligned growth and future-proof modifications.

To align your architecture refactor with domain language, apply ADR-informed terms and use a CONTEXT.md glossary. This ensures suggested deepening opportunities match your domain and support deliberate interface-design explorations.

Yes, you can generate an HTML architecture report with before/after visuals for your project. The report communicates depth and seams by presenting shallow modules and targeted deepening opportunities based on domain terms.

No dependencies are required to run this codebase architecture analysis. You can execute the architecture-scan workflow directly on your current project to surface deepening candidates and generate the report without external components.

The best way to guide a grilling loop workflow for interface design is to surface deepening opportunities first, then apply ADR considerations and domain language from a CONTEXT.md glossary. This approach supports deliberate refactors and targeted architecture exploration.