backend-architecture-orchestratorlisted

# Backend Architecture Orchestrator The single entry skill for server-side work. It locates the task on the **layer × concern** map and delegates to one of 8 specialist spokes. The cross-cutting model every backend shares — the dependency-inversion boundary (domain → ports → adapters), the layering contract, the API/transport conventions, and the runtime/tooling matrix — lives in `backend-architecture-core`; read it before drawing a module boundary, designing an endpoint, or wiring an integration. ## Routing map (intent → spoke) **Shape the architecture** - "How should I structure this service?" / boundaries, testability, decoupling → `hexagonal-architecture` *(model in `backend-architecture-core`)* - General server-side patterns — repository/service/controller layers, caching, background jobs, query optimization → `backend-patterns` - Framework-specific structure (NestJS modules, providers, guards, interceptors, DTO validation) → `nestjs-patterns` **Design the API surface** - REST contracts — resource naming, status codes, pagination, filtering, versioning, error shapes, rate limiting → `api-design` - Add an outbound integration / provider that matches the repo's existing pattern → `api-connector-builder` - Expose tools/resources/prompts to an AI assistant (Model Context Protocol) → `mcp-server-patterns` **Ship & remember why** - Deploy, containerize, CI/CD, health checks, rollback, production readiness → `deployment-patterns` - Record an architectural decision (contex