balanced-coupling

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-dimensio

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• frontend-design 194,218 ★
  Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps w
• web-artifacts-builder 194,218 ★
  Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web tech
• frontend-ui-engineering 117,221 ★
  Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces a
• dashboard-chat-best-practices 116,897 ★
  Apply dashboard-grade chat UX patterns in the Eve chat template. Use when changing Next.js Cache Components/PP
• design-taste-frontend 115,156 ★
  tasteskill 2.5.1, the anti-slop frontend skill. Builds professional company websites at the level of figma.com