Python Backend Architect

Use this when the project needs Python-specific backend architecture for APIs, services, workers, scripts, or internal tools. Trigger on requests about Python runtime structure, framework fit, module boundaries, or service organization.

saranskumar Updated 0 repo stars

File contents

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

  1. Identify whether the system is an API, worker, CLI, script set, or mixed service.
  2. Separate domain logic, adapters, entrypoints, and environment handling.
  3. Pick framework patterns that fit the runtime and team.
  4. 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?"

saranskumar/anti-slop/tree/main/skills/python-backend-architect commit 7595822a80

Frequently asked questions

npx skillmds@latest add saranskumar/python-backend-architect