← ClaudeAtlas

clean-architecture-pythonlisted

Use when laying out a Python service packaged with pyproject.toml (FastAPI or another web framework), or adding a feature, endpoint, use case, aggregate or repository to one — which package a module belongs in, which package may import which, and how an endpoint reaches a use case. Not for configuration, dependency or tooling changes.
SebastienDegodez/skraft-plugin · ★ 14 · AI & Automation · score 70
Install: claude install-skill SebastienDegodez/skraft-plugin
# Clean Architecture — Python The layer rules are those of `architecture-patterns`. This skill maps them onto Python packages. ## One package per layer | Package | Holds | May import | |---|---|---| | `<context>.domain` | aggregates, value objects, domain events | the standard library only | | `<context>.application` | use cases and the `Protocol`s they call | `<context>.domain` | | `<context>.infrastructure` | implementations of those `Protocol`s (SQLAlchemy, HTTP clients, files) | `<context>.application`, `<context>.domain` | | `<context>.api` | routes, the app factory, the wiring of every class | all three | - Lay out `src/<context>/` with one sub-package per layer, in a single `pyproject.toml`. A new feature goes into the existing layer packages, never into a new top-level package. - FastAPI, Pydantic, SQLAlchemy and HTTP clients are imported only in `infrastructure` and `api`. Domain and application use `dataclasses` and `typing`. - ORM models and their mapping live in `infrastructure`; never make a domain class an ORM or Pydantic model. - Tests live in the two test packages `clean-architecture-testing` defines, never inside `src/`. ## Use cases - A use case is a class named after the action (`BorrowBook`) with one public method. The route calls it directly: no `Protocol` or ABC in front of it, no `*Service` implementation. - A command method returns `None`; the caller creates the new id and passes it in. A query returns a frozen `*ViewModel` dataclass defined in `