The Balanced Coupling model for software design. Use when: designing modular architectures, evaluating coupling between components, reviewing code modularity, deciding whether to split or merge modules/services, assessing integration patterns, classifying coupling as balanced or unbalanced, applying DDD strategic and tactical patterns, reasoning about cohesion vs coupling trade-offs, identifying distributed monolith risks, or explaining why a system is hard to change. Provides the three-dimensional framework (integration strength, distance, volatility) and the balance rule for making coupling decisions.
$npx -y skills add vladikk/modularity --skill balanced-couplingInstalls into the current project.
Run `npx skills use "https://github.com/vladikk/modularity" --skill "vladikk/modularity/balanced-coupling"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/vladikk/modularity" that are relevant to the current task. Run `npx skills add "https://github.com/vladikk/modularity"` and select the relevant skills, then follow their instructions.