FastAPI Best Architecture

Official documentation: https://fastapi-practices.github.io/fastapi_best_architecture_docs/

Use this skill to follow fba architecture and plugin conventions. Load the required baseline below, then only the additional references needed for the task.

Required Coding Baseline

For every backend Python implementation, fix, refactor, or code review, read references/coding-style.md and references/naming.md before working on code. These rules apply to ordinary development as well as explicit style requests; the user does not need to repeat them. Apply them to maintained application and plugin code, including runtime modules, utilities, and relevant tests, while preserving framework-required contracts.

For cross-layer features, directory changes, or SDK integrations, also read references/development.md before choosing module boundaries, then load the layer-specific references.

Keep the requested scope: a comprehensive plugin review covers all maintained modules in that plugin and affected tests, not only API/Service/CRUD files. An ordinary feature or fix does not authorize unrelated repository-wide cleanup. For documentation-only work, load the relevant documentation reference without the Python baseline.

Before completion, apply the review checks in references/coding-style.md. Ruff passing alone does not verify function design, test-driven helper extraction, or layer boundaries.

Core Architecture

Project adopts a layered backend architecture centered on API, Service, and CRUD, with Schema and Model as explicit data contracts: