improve-codebase-architecture

To identify architectural friction, analyze the codebase structure to detect shallow modules, tight coupling, and lack of testability. This process pinpoints areas where deepening opportunities can improve module interfaces and reduce internal complexity.

The best way to refactor modules for testability and AI navigation is to analyze interface depth and internal complexity. This identifies deepening opportunities that enhance locality and leverage, making the codebase more navigable for both humans and AI agents.

You find deepening opportunities by analyzing the codebase architecture for shallow modules and tight coupling. The skill provides refactoring candidates based on interface depth and internal complexity, encouraging a design conversation to decide on the best improvements.

Analyzing a codebase for refactoring candidates requires a working knowledge of the codebase's structure and usage patterns. Without this prerequisite knowledge, accurately recommending refactoring based on interface depth and internal complexity is difficult.

You should not rely solely on automated architectural refactoring recommendations when you lack a working knowledge of the codebase's structure. The tool provides candidates for guided design conversation rather than executing changes blindly without understanding usage patterns.