improve-codebase-architecture

Identify shallow modules in a Rust monorepo by detecting interface structures that lack depth, analyzing codebase architecture to surface deepening opportunities where consolidation improves leverage and testability at the interface.

A seam placement issue in codebase architecture occurs when dependency boundaries leak locality, spreading verification across callers. Dependency-aware seam classification categorizes in-process, local-substitutable, remote-but-owned, and true-external dependencies to guide safe refactoring.

Plan refactoring using ports and adapters by driving interface-first exploration with defined modules, seams, and adapters. This produces dependency-aware deepening candidates that consolidate shallow modules into deep, testable ones.

Yes, this approach fixes MCP tool runtime contention and monolithic crate boundaries by analyzing specific codebase areas to present deepening candidates, letting you choose which architectural boundary to drill into and refactor next.

Avoid interface-first deepening when architectural understanding already concentrates effectively across callers. If modules possess sufficient depth and no locality failures or seam leaks exist, deepening candidates will not yield meaningful leverage improvements.

Structure CLI handlers by detecting shallow module patterns and applying dependency-aware seam classification. Consolidate handler logic into deep modules using interface-first exploration to ensure testing requirements remain navigable and verifiable.