saranskumar Goal
Design Express APIs that are explicit about validation, auth, and service boundaries.
When to Use
- The API uses Express or a similar middleware-based Node server.
- Route structure and handler layering need design.
- Existing middleware chains are getting messy.
Instructions
- Define route groups and shared middleware concerns.
- Separate validation, auth, handlers, and domain services.
- Define error translation and response conventions.
- Plan tests and operational instrumentation.
Constraints
- Do not bury business logic in middleware.
- Keep request validation explicit.
- Avoid middleware stacks that hide security-critical behavior.
Output Format
- route map
- middleware and service layering
- validation/auth notes
- implementation guidance
Examples
- "Design an Express API for file processing."
- "How should this middleware-heavy API be cleaned up?"