// Design or review a layered backend architecture (routes, controllers, services, repositories) for HTTP APIs and microservices.
| name | design-layered-backend-architecture |
| description | Design or review a layered backend architecture (routes, controllers, services, repositories) for HTTP APIs and microservices. |
| category | backend/architecture |
| ssot_path | .ai/skills/backend/architecture/design-layered-backend-architecture |
Canonical source: .ai/skills/backend/architecture/design-layered-backend-architecture/
Open .ai/skills/backend/architecture/design-layered-backend-architecture/SKILL.md and any supporting files referenced there (for example reference.md, examples.md, scripts/, templates/).
Note: The frontmatter above is identical to the canonical source except for
ssot_pathandcategorywhich are added for navigation. After opening the source file, skip re-reading the description to avoid redundant token usage.
Evidence-driven debugging loop with mandatory instrumentation + fix approvals, run_id-tagged logs, default 3-pass verification for flaky issues, and guaranteed cleanup of debug-only instrumentation.
Apply cross-cutting backend service patterns across routing, services, repositories, validation, configuration, errors, and tests.
Manage backend configuration safely with typed, validated settings and clear separation between defaults and secrets.
Apply safe and maintainable backend database patterns (transactions, pagination, soft deletes, query optimization, data consistency).
Build backend service and repository layers to isolate business logic from persistence and improve testability.
Handle async/await and error propagation in backend services with consistent error types, wrappers, and response mapping.
