improve-codebase-architecture

Identify architectural friction by surfacing shallow modules and analyzing seams to generate a prioritized list of deepening candidates. This reveals areas where poor locality limits testability, providing concrete rationale for structural improvements across the codebase.

Refactor shallow modules by applying a deepening plan that consolidates seams and increases leverage behind external interfaces. This approach preserves behavior while improving locality, resulting in a codebase that is significantly more testable and AI-navigable.

Align refactoring with architecture decisions by satisfying domain concepts defined in CONTEXT.md and ADR-FORMAT.md. This ensures that proposed structural changes and module deepening opportunities stay coherent with the established project domain language.

Yes, this approach specifically applies to refactoring contexts across large codebases. It focuses on analyzing module depth, seams, and locality to surface deepening opportunities, ensuring structural improvements scale effectively within complex dependency networks.

Deepen modules when architectural friction surfaces through shallow structures that reduce testability and AI-navigability. A prioritized plan helps consolidate these seams, increasing leverage behind the external interface while preserving existing system behavior.

Generate a prioritized refactoring plan by running the Explore flow to identify deepening opportunities in your repository. This surfaces architectural friction and outputs a structured list of candidates with rationale for improving modularity.