improve-codebase-architecture

Architectural friction is identified by analyzing your codebase to find shallow modules and tightly-coupled clusters. This skill evaluates module depth and dependency strategy to surface friction and propose boundary interfaces for refactoring.

The best way to refactor shallow modules is to deepen them by consolidating tight couplings and defining clear boundaries. This skill guides a structured modernization workflow to improve testability and AI-navigability across module clusters.

To draft an RFC for a codebase refactor, initiate an exploratory analysis to identify modules ripe for deepening. This skill generates RFC-style design notes and migration artifacts to guide your proposed architecture improvements.

Yes, you can use this approach to consolidate tightly-coupled modules by applying the module deepening framework. It evaluates dependency strategy and testing impact to surface opportunities for reducing friction across your codebase clusters.

You need to evaluate module depth when your codebase suffers from poor testability and tight couplings. Evaluating depth helps transition a codebase from exploratory analysis to guided design by surfacing shallow modules ripe for deepening.