couplinglisted
Install: claude install-skill wntic/pyhouse
# Coupling — where boundaries go and what may cross them
Every architecture skill in this set answers "given a boundary, what goes on each side, what is each
part called, and what may import what". This one answers the question *before* that: **where the
boundary goes, how much knowledge may cross it, and how much design effort the components on either
side deserve.** It is architecture-neutral — a hexagonal app, a flat-layered worker and a monorepo
of both get the same answers — and it is loaded *alongside* whichever architecture skill owns the
layout, never instead of it.
The vocabulary below — shared knowledge, distance, volatility, the counterbalance between them — is
**Vlad Khononov's Balanced Coupling model**, set out in *Balancing Coupling in Software Design*
(Addison-Wesley) and at [coupling.dev](https://coupling.dev). The model is his. What follows is this
catalogue's own restatement of it in this set's terms rather than a reproduction of his text, and where
the two differ the book is right. Read it for the full treatment — the continuous form of the balance
rule, the worked cases and the connascence detail all live there and are only gestured at here.
It absorbs the two older models rather than competing with them. Constantine's module coupling
supplies the rungs of the strength ladder — content, common/external/control, stamp and data coupling
are the classic names for intrusive, functional, model and contract. Connascence grades *within* a
rung: its static leve