Low Coupling

Use this skill to minimize dependency strength and blast radius while keeping boundaries practical and testable.

Intent Router

Need	Load
coupling types, measurement signals, refactoring moves, and review checklist	`references/coupling-guide.md`

Start by locating the change that currently ripples too far.
Identify which form of coupling is dominant: structural, schema, temporal, shared-state, or operational.
Look for seams where policy can depend on abstractions and volatile details can move behind adapters or interfaces.
Constrain the design with explicit dependency rules before attempting large refactors.
Re-measure after each change so cycle count, propagation, or coordination cost trends move in the right direction.