improve-codebase-architecture

To identify shallow modules during codebase refactoring, you can analyze where complexity fails the deletion test and where seams or adapters are missing. This Skill explores your project context and codebase to present deepening candidates without proposing new interfaces upfront.

A deep module in software architecture provides a clean, minimal interface while hiding substantial implementation complexity. This Skill evaluates your codebase to find tightly-coupled logic that fails this principle and helps convert shallow modules into deep, testable structures.

Improve codebase testability by evaluating seam placement and adapter usage to ensure tests target the interface rather than internal logic. This Skill guides a loop to define candidate changes, dependencies, and how tests should interact with the deepened module.

Yes, architectural friction analysis requires reading existing project documentation like CONTEXT.md and ADR entries. The Skill uses these files to understand your current architecture before exploring the codebase to find deepening opportunities.

You should not use an automated refactoring candidate generator when your project lacks foundational context files like CONTEXT.md or ADRs. The Skill requires this documentation to accurately identify architectural friction and propose deepening candidates.