What problem does it solve? It helps you decide whether components, modules, or services are coupled in a way that makes your system hard to change, and guides split-or-merge decisions with a structured model instead of gut feeling. ## Core Features & Use Cases - Three-Dimensional Coupling Analysis: Classify coupling by integration strength (intrusive, functional, model, contract), distance (code, organizational, runtime), and volatility (via DDD subdomains). - Balance Rule for Design Decisions: Apply the rule that modularity emerges when strength and distance counterbalance each other, and that low volatility can neutralize unbalanced coupling. - Use Case: When reviewing whether to split a service into microservices, use the model to check if high integration strength across a high-distance boundary signals a distributed monolith risk before committing to the split. ## Quick Start Use the balanced-coupling skill to evaluate whether the checkout and billing modules in this codebase are balanced or drifting toward a distributed monolith.
