balanced-coupling

What problem does it solve?

This Skill eliminates the risk of building software that becomes increasingly difficult and costly to modify over time due to unbalanced coupling between components, which causes unexpected cascading changes and accelerates technical debt accumulation as code generation speeds increase.

Core Features & Use Cases

• Three-Dimensional Coupling Framework: Evaluates coupling across integration strength, distance, and volatility, moving beyond simplistic "loose vs tight" metrics to provide context-aware, actionable assessments.
• Architecture Review Support: Analyzes existing codebases for coupling imbalances, identifies distributed monolith risks, and produces concrete recommendations for improving modularity.
• Modular Design Guidance: Helps design new modular systems from functional requirements, producing module design docs with integration contracts, test specifications, and full coupling assessments aligned with domain-driven design principles.
• Use Case: A team experiencing frequent breaking changes when updating a shared payment processing component can use this Skill to map coupling imbalances, classify component volatility, and restructure boundaries to reduce cascading change risk.

Quick Start

Use the balanced-coupling skill to evaluate the coupling balance of your team's user authentication and notification services and get recommendations for reducing cascading change risk as the system scales.