Goal
Design Python backend systems that are clear, operable, and suitable for the chosen runtime.
When to Use
- The backend is Python-first.
- A Python service or app needs structural guidance.
- Framework choice and module layout affect maintainability.
Instructions
- Identify whether the system is an API, worker, CLI, script set, or mixed service.
- Separate domain logic, adapters, entrypoints, and environment handling.
- Pick framework patterns that fit the runtime and team.
- Plan packaging, testing, and operational boundaries.
Constraints
- Do not assume every Python backend is a FastAPI app.
- Keep business logic outside framework glue.
- Make environment assumptions explicit.
Output Format
- architecture summary
- module boundaries
- framework/runtime notes
- testing and ops notes
Examples
- "Design the Python backend architecture for this internal service."
- "How should this mixed API and worker Python project be structured?"