What problem does it solve? Codebases often suffer from hidden coupling problems—tight integration across distant components, distributed monolith risks, and areas where changes are unexpectedly expensive. This Skill systematically reviews a codebase's modularity using the Balanced Coupling model, turning vague architectural discomfort into a concrete, prioritized list of design issues. ## Core Features & Use Cases - Balanced Coupling Analysis: Evaluates every component integration across three dimensions—strength, distance, and volatility—using the formula BALANCE = (STRENGTH XOR DISTANCE) OR NOT VOLATILITY. - Guided Domain Discovery: Reads your docs and code first, then asks targeted one-at-a-time questions about domain classification, team ownership, and pain points to fill gaps that affect the assessment. - Prioritized Review Output: Produces a modularity review in Markdown and HTML that flags only integrations that are both unbalanced and volatile, grounded in specific code observations. - Use Case: You suspect your microservices are actually a distributed monolith. Run this Skill to map integrations, identify intrusive coupling across service boundaries in volatile domains, and get a review explaining which integrations to fix first and why. ## Quick Start Use the modularity-review skill to analyze this codebase for coupling problems and produce a modularity review.
