add-backend-architecturelisted

# Backend Architecture Consultant <!-- uses: - mention: add-architecture-discovery - mention: add-backend-development - mention: add-frontend-architecture - mention: add-project-scaffolding - skill: add-backend-architecture/references/clean-architecture.md - skill: add-backend-architecture/references/combined-strategy.md - skill: add-backend-architecture/references/universal-rules.md - skill: add-backend-architecture/references/vertical-slice.md --> Guide architectural decisions for backend projects. Language and framework agnostic. Choose between Vertical Slice, Clean Architecture, Simple Modular, or a Combined strategy based on project context. **Use for:** Choosing architecture patterns, organizing features, structuring folders, deciding boundaries, avoiding over-engineering. ## When NOT to Use - **Code implementation** — use `add-backend-development` instead - **Project scaffolding / file generation** — use `add-project-scaffolding` instead - **Discovering existing architecture** — use `add-architecture-discovery` instead - **Frontend structure decisions** — use `add-frontend-architecture` instead --- ## Core Philosophy The right architecture is the **simplest one that handles your actual complexity**. Most projects fail not from too little architecture, but from too much too early. A 3-endpoint CRUD API does not need hexagonal architecture. A complex multi-provider AI platform does not survive with flat files. The goal: **match structural investment to actual c