improve-codebase-architecture

Surface architectural friction by analyzing tightly coupled modules to find deepening opportunities that increase interface leverage and locality, guiding you through a Discovery-Grilling loop to generate concrete refactor candidates.

Seams are adapter locations in a codebase where behavior can be altered without editing in that place. You need them when consolidating tightly coupled modules to improve testability and create AI-navigable code surfaces.

Refactor tightly coupled modules by proposing concrete deepening candidates that increase interface leverage, clarifying seams and test surfaces to align with domain language and maintain architectural consistency.

Yes, you can align refactors with domain language documented in CONTEXT.md and ADR decisions to maintain architectural consistency, ensuring deepening candidates satisfy domain-aligned terminology and evaluation criteria.

Make a codebase AI-navigable during modernization by clarifying seams, adapters, and test surfaces for maintainability, applying the Discovery-Grilling loop to evaluate deepening opportunities across the repository.

Avoid architectural deepening when modules are not tightly coupled or lack defined seam locations, as the process requires identifiable friction points and a high-level refactor plan to successfully increase interface leverage.