flat-project-setuplisted
Install: claude install-skill wntic/pyhouse
# Flat Project Setup — dependencies by role, migration bootstrap
What a flat-layered service needs **once**, beyond the toolchain every Python project carries: the
libraries its roles bring, and the migration bootstrap the first revision cannot be written without.
None of it recurs per feature. The project file itself — src layout, ruff, mypy, dependency
declarations — is `python-toolchain`'s; what goes inside `src/myapp/` is `flat-layered`; what a schema
change looks like after the bootstrap is `flat-persistence`.
## When to use vs. neighbours
- Starting a flat service, adding a dependency, or justifying one of this family's floors → block A.
- Laying migrations on a service that has none → block B, once; this skill is one-shot, and
`flat-persistence`'s revisions and `flat-test-integration-setup`'s migration fixture both depend on it
having run.
- The `pyproject.toml` tables, the src layout, the linter and type checker, the sanctioned
suppressions, the line length, and whether any dependency may carry a floor → `python-toolchain`.
- A second store's migration directory beside `migrations/postgres/`, and the tool that applies it →
`flat-persistence`, which owns where every store's history lives.
- The per-change revision that pairs with a table edit, and what a deploy obliges of it →
`flat-persistence`.
- The packages inside `src/myapp/`, the settings class each component owns, and the entry point →
`flat-layered`.
- The pytest configuration block → `python-too