hex-architecturelisted
Install: claude install-skill wntic/pyhouse
# Hexagonal Architecture — the layer contract
Which layer a thing belongs to, and what it is allowed to reach. This skill owns boundaries only: the
mechanics of packaging a module and spelling an import are `python-packaging`, and they are the same here
as in any other project. What goes *inside* a module belongs to whichever skill owns that artifact.
## When to use vs. neighbours
- Whether this style is the right one at all, or the service belongs in the flat-layered family →
`architecture-choice`, which owns the hex-vs-flat decision in full and is universal, so it is
available whichever family plugins are installed.
- The family is settled the other way — a worker, crawler, pipeline or integration service grouped by
technical role, with no ports until a second real implementation → `flat-layered`, in the
`pyhouse-flat` plugin. Nothing in this skill applies there.
- Where a boundary goes at all — split vs merge, whether an integration needs a contract, how much
structure a component deserves → `coupling`, loaded alongside this skill; it owns the boundary
reasoning, this skill owns the layer layout.
- Deciding where a module belongs, or whether an import may cross a boundary → this skill.
- Moving code between layers, or restructuring a layer package's public surface → this skill for where
it lands; `python-packaging` for how the module and its re-exports are spelled.
- Editing the body of an existing module, once its layer is settled → that artifact's skill