← ClaudeAtlas

flat-project-setuplisted

Use when laying a flat-layered service down once — which runtime and development libraries each of its roles brings, with the version floors this family's templates rely on, and the relational migration bootstrap (`alembic init -t async` under `migrations/postgres/`, then the generated environment changed to read the connection string at its own composition root and see every table, the revision template changed to the house annotation forms, and a baseline only over a schema that already exists). The src layout, ruff and mypy, the line length and the dependency-floor discipline every Python project shares are `python-toolchain`'s. Never per feature — each later schema revision is `flat-persistence`'s, and the package layout inside `src/` is `flat-layered`'s. A hexagonal project's setup is `hex-project-setup`, in the `pyhouse-hex` plugin. - Also when asked to start a new worker, pipeline or ETL service, which libraries it needs, to add a dependency or justify one of this family's version floors, or to add mig
wntic/pyhouse · ★ 3 · AI & Automation · score 76
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