architecture-choicelisted
Install: claude install-skill wntic/pyhouse
# Architecture Choice — hexagonal, flat-layered, or neither
Which of the catalogue's two service-architecture families a service belongs to, settled before any
code exists. This skill decides and hands off: the layer contract, the package layout and every
artifact template belong to the family skill it routes to, and the question *where a boundary goes at
all* belongs to `coupling`. Both families assume the codebase chooses its own layout; where something
else already fixes it, this skill names the shape as uncovered instead of routing.
It is a universal skill, so it **names** the two family skills without requiring either. Everything
needed to reach a recommendation and state its reason is here; the family skills carry the how. See
`## Reading this with neither family installed`.
## When to use vs. neighbours
- A new service, no code yet, and the family is not settled → this skill.
- The family is settled as hexagonal — the four layers, dependency direction, ports, adapters, the
composition root → `hex-architecture`, in the `pyhouse-hex` plugin.
- The family is settled as flat-layered — packages named for technical roles, no ports until a second
implementation → `flat-layered`, in the `pyhouse-flat` plugin.
- Where a boundary goes at all — split or merge, contract or shared knowledge, how much design effort
a component deserves → `coupling`. It loads alongside this skill and supplies the volatility
judgement the cost question below runs on.
- Whether one particul