nuxt-api-endpoint

To build Nuxt API endpoints with a layered architecture, route requests from HTTP controllers in server/api to domain use-cases, then to data repositories, and finally return DTOs. This enforces maintainability and strict separation of concerns.

To validate API requests in a Nuxt backend, define schemas using Valibot. The endpoint creation flow requires validation through these schemas to ensure data integrity before passing it to the domain logic layer.

Yes, this Nuxt API endpoint generator works without external dependencies. It relies on internal project architectural guidelines to enforce the flow from HTTP controllers to domain logic and data repositories.

The best way to structure a Nuxt server route is to follow a strict flow: define the HTTP controller in server/api, implement business logic in a domain use-case, handle persistence via a repository, and return a DTO.

You should use a repository pattern in Nuxt API development when you need to separate data persistence from business logic. This Skill enforces this pattern to ensure consistency and maintainability across your endpoints.