Express.js REST API

What problem does it solve?

Express REST APIs often degrade into tightly coupled route handlers where HTTP concerns, business rules, and data access get mixed together, making safe refactors risky and code reviews slow.

Core Features & Use Cases

• Layered routing and request handling: keeps endpoint definitions in src/routes, translates req/res in src/controllers, and delegates pure work to services.
• Business logic and data access separation: moves rules into src/services and persistence into src/models so storage changes don’t ripple through the app.
• Consistent middleware structure: centralizes cross-cutting concerns like validation and error handling in src/middleware, including AppError-based error responses.

Quick Start

Tell your coding agent: "Given my Express project, restructure it into routes/controllers/services/models with centralized middleware and apply the separation rules from the Express.js REST API skill."