Nodejs Service

Trigger: Use when building NodeJS / TypeScript backend APIs or services.

Project structure:

/src /controllers # request/response handling only — no business logic /services # business logic /repositories # data access abstraction /models # TypeScript types and Prisma models /middlewares # auth, error handler, request validation /routes # route definitions /config # typed env/config loading /tests /unit /integration

Architecture rules:

• Controllers must not contain business logic
• Services must not import request/response objects
• Use repository pattern to abstract all data access
• Export all modules through an index.ts barrel file

TypeScript standards:

• Enable strict mode: "strict": true in tsconfig.json
• Never use any — use unknown with type guards when type is uncertain
• Define explicit return types on all service and repository methods
• Use Zod for runtime input validation and type inference

Error handling:

• Use a centralized error handler middleware (last registered middleware)
• Define a base AppError class with statusCode and message
• Never expose internal error details or stack traces to clients