api-endpoint

The Routes → Controller → Service → Repository pattern separates concerns: routes instantiate dependencies, controllers validate input with Zod and shape responses, services contain business logic, and repositories execute database queries. All responses wrap in ApiResponse<T> for standardized error handling and consistent structure across your backend.

Use Zod for input validation on all API endpoints. Zod schemas enforce data integrity before business logic executes, preventing invalid data from reaching your database. Validation happens in the controller layer, which returns standardized ApiResponse errors if validation fails.

Create a new route that instantiates a controller, which calls service methods for GET, POST, PUT, and DELETE operations. Each service method delegates database work to the repository layer. Wrap all responses in ApiResponse<T> and handle errors through middleware for consistent API behavior.

Yes. Zod validates request payloads in the controller before passing data to services. The api-endpoint Skill integrates Zod validation directly into controller logic, ensuring all inputs conform to schema requirements before touching your database layer.

Standardize all API responses with ApiResponse<T> wrapper and propagate errors through middleware. This centralizes error formatting, simplifies debugging, and ensures clients receive consistent error structures across all endpoints regardless of where failures occur.

Yes. Routes instantiate repositories and services manually before passing them to controllers. This explicit dependency injection keeps architectural layers clear and testable, though it requires wiring each route with its required service and repository instances.