What problem does it solve? It answers whether a module is cohesive or secretly two modules, by grading every internal and boundary integration on strength, distance, and volatility instead of relying on gut-feel architecture opinions. ## Core Features & Use Cases - Component and dependency mapping: Inventories components, extracts the public surface, builds the internal dependency graph, and collects co-change evidence from git history. - Balanced Coupling grading: Grades each edge with the Balanced Coupling model (strength, distance, volatility) and flags tight coupling, low cohesion, cycles, hubs, and pass-through layers. - Restructuring proposals: Produces evidence-backed findings with file:line citations, a mermaid component diagram, and a move map with migration order when restructuring is warranted. - Use Case: Ask it to review a Go package that has grown unwieldy; it maps the components, finds an intrusive coupling to a shared store, and proposes a step-by-step split with a blast-radius estimate. ## Quick Start Ask the assistant to review the structure of the module at a given path, for example by saying: review the module structure of ./internal/billing.
