Keep your backend code cleanly split into layers.
What it does
Guides backend implementation toward consistent, layered microservices with validation, error handling, and tests.
When to use it
Use when creating or modifying backend APIs, controllers, services, repositories, middleware, database operations, validation, configuration, or tests.
How to use it
It changes how the agent implements backend features by separating layers and requiring validation, error tracking, tests, and unified configuration.
What you provide
- An existing project
What you need · 5
The backend patterns target services running on Node.js; no runtime version is specified.
The routing and middleware examples use Express and import its request, response, and router APIs.
The guidelines require Zod for input validation and show importing its schema API.
The database patterns use Prisma Client and its types.
Access · 0
No additional actions listed.