api-endpoint-generator

Define the resource entity and schema, then generate routes for POST, GET, PATCH, and DELETE with a controller, Zod validation middleware, and typed ApiResponse interfaces. The pattern includes pagination, error handling, and consistent response formats.

Create Zod schemas for body, query, and params, then apply a validateRequest middleware that parses each part before the controller runs. Validation failures return a 400 response with field-level error details from error.flatten().fieldErrors.

Zod is preferred in TypeScript projects because it infers static types directly from schemas via z.infer, keeping DTOs and validation in sync. Joi works well in plain JavaScript codebases but lacks native type inference.

Yes, the Skill includes framework-specific patterns: NestJS controllers with DTO classes and Swagger decorators, and FastAPI routers with Pydantic models and dependency injection. The same response format and status code conventions apply across all three.

Use 200 for successful reads and updates, 201 for resource creation, 204 for deletes with no body, 400 for validation errors, 401 and 403 for auth failures, 404 for missing resources, and 409 for conflicts.