Route NestJS changes through module architecture and dependency-injection conventions.
npx skills add https://github.com/ulpi-io/skills --skill nestjs-ulpi-io
Please help me install this Agent Skill. Skill: nestjs Source: https://github.com/ulpi-io/skills/tree/main/nestjs Command: npx skills add https://github.com/ulpi-io/skills --skill nestjs-ulpi-io
This Skill prevents NestJS changes from bypassing a project's established module boundaries, dependency injection patterns, validation rules, and request lifecycle conventions.
Ask the NestJS skill to implement or review a module, endpoint, or subsystem while first reading the stack contract and then loading only the relevant architecture references.
High-intent search queries and answers about installing and using this skill.
NestJS module structure requires organizing domain modules with explicit imports, providers, controllers, exports, and co-located DTOs. Use constructor injection for dependencies and validate inputs with DTOs to maintain established architecture boundaries and request lifecycle conventions.
Keeping NestJS controllers thin requires delegating business logic to injected services. Controllers should handle request mapping and response formatting, while services manage data persistence, transaction boundaries, and domain operations, ensuring separation of concerns and review-ready code.
Adding an authenticated NestJS endpoint involves implementing guards for authentication, validating inputs with DTOs, delegating to injected services, and generating OpenAPI documentation. This ensures the endpoint is secure, validated, and properly documented for API consumers.
NestJS dependency injection works across WebSockets and microservices by routing changes through established module architecture. The framework supports queues, interceptors, pipes, and exception filters within these transport layers while maintaining consistent dependency injection patterns.
NestJS changes bypass module boundaries when they skip reading the stack contract, ignore dependency injection conventions, or fail to use DTO validation. Establishing explicit module imports, exports, and provider boundaries prevents breaking the request lifecycle and architecture patterns.
cookeyholderDefine stable REST or GraphQL API contracts before implementation.
Axel-DaMageGenerate and configure NestJS modules, controllers, services, DTOs, guards, and interceptors.
giuseppe-trisciuoglioDevelop NestJS applications with Drizzle ORM for REST and GraphQL APIs.
Serg28Generate NestJS modules, controllers, and services with dependency injection.
