hex-conventionslisted
Install: claude install-skill wntic/pyhouse
# Hexagonal Conventions — the derivation registry
This is the **derivation layer**: the rules that turn the bare identifiers a change introduces — an
entity name, a protocol name, a command base-name, a datastore kind — into concrete file paths, class
names and package placement. Other skills own what goes *inside* an artifact; this one owns the mapping
between a name and its place in the tree. It produces **no file of its own**.
All paths below are relative to the target package root `src/myapp/`. Worked names use a deliberately
neutral vocabulary — subdomains `foos` and `bars`, entities `Foo` and `Bar` — so nothing here reads as
belonging to one product. Technology tokens (`postgres`, `redis`, `s3`, `jwt`) stay concrete, because the
whole point of the infrastructure rule is that the folder is named after the real technology.
## When to use vs. neighbours
- Turning a bare identifier into a file path or class name → this skill.
- Deciding which repository form a datastore gets, or writing its connection factory → block B.
- Resolving a `<subdomain>:<Name>` reference, or deciding what is shared across contexts → block C.
- Layer boundaries → `hex-architecture`; `__all__`, the re-export contract and import forms → `python-packaging`.
- What goes *inside* the artifact whose name you just derived → the skill that owns it
(`hex-persistence`, `exception-catalog`, `hex-application`). This skill is consulted **alongside**
them, never instead of them — it produces no file of i