flat-entrypointlisted
Install: claude install-skill wntic/pyhouse
# Flat-Layered Entrypoint — loop vs schedule vs stream vs HTTP vs durable
Covers the **process-definition** and **framework-wrapper** roles of one `flat-layered` service, whatever
this service calls those packages. The shapes differ only in *what triggers a run*; the work itself is
always the same functions, so switching later is a wrapper change, not a rewrite.
The invariant that makes that true: **the work a trigger performs is a plain async function in a module
named for that work, taking every dependency as an argument and importing no framework**, and named by
`naming` for what it does. Everything in this skill is a wrapper around one of those.
Every template below is one distribution: `myapp` is this service's own root package (`flat-layered`), and
nothing here assumes a sibling distribution or a repository above it.
## When to use vs. neighbours
- The architecture family is not settled yet — this may not be a flat-layered service at all →
`architecture-choice` decides hexagonal versus flat first; everything here assumes flat.
- The service's own settings and logging modules, its client and payload packages → not this skill, use
`flat-layered`, which owns the role kinds and the import contract between them.
- The tables, the write path and the repository class the work calls → `flat-persistence`.
- Several distributions sharing one repository — the member split, the container profiles, the root task
runner → `python-workspace`. One distribution on its own nee