Skip to main content
nestjs-expert Creates and configures NestJS modules, controllers, services, DTOs, guards, and interceptors for enterprise-grade TypeScript backend applications. Use when building NestJS REST APIs or GraphQL services, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating TypeORM or Prisma, or working with .module.ts, .controller.ts, and .service.ts files. Invoke for guards, interceptors, pipes, validation, Swagger documentation, and unit/E2E testing in NestJS projects.
Aller à l'installation Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Afficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/Jeffallan/claude-skills --skill nestjs-expertLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Plus depuis ce dépôt Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing applications, managing infrastructure as code, deploying to Kubernetes clusters, configuring cloud platforms, automating releases, or responding to production incidents. Invoke for pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, or platform engineering.
Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.
Designs and implements production-grade RAG systems by chunking documents, generating embeddings, configuring vector stores, building hybrid search pipelines, applying reranking, and evaluating retrieval quality. Use when building RAG systems, vector databases, or knowledge-grounded AI applications requiring semantic search, document retrieval, context augmentation, similarity search, or embedding-based indexing.
Explorateur de fichiers
7 fichiers name nestjs-expert description Creates and configures NestJS modules, controllers, services, DTOs, guards, and interceptors for enterprise-grade TypeScript backend applications. Use when building NestJS REST APIs or GraphQL services, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating TypeORM or Prisma, or working with .module.ts, .controller.ts, and .service.ts files. Invoke for guards, interceptors, pipes, validation, Swagger documentation, and unit/E2E testing in NestJS projects. license MIT metadata {"author":"https://github.com/Jeffallan","version":"1.1.0","domain":"backend","triggers":"NestJS, Nest, Node.js backend, TypeScript backend, dependency injection, controller, service, module, guard, interceptor","role":"specialist","scope":"implementation","output-format":"code","related-skills":"fullstack-guardian, test-master, devops-engineer"}
NestJS Expert
Senior NestJS specialist with deep expertise in enterprise-grade, scalable TypeScript backend applications.
Core Workflow
Analyze requirements — Identify modules, endpoints, entities, and relationshipsDesign structure — Plan module organization and inter-module dependenciesImplement — Create modules, services, and controllers with proper DI wiringSecure — Add guards, validation pipes, and authenticationVerify — Run npm run lint,
npm run test
nest info
Test — Write unit tests for services and E2E tests for controllers
Reference Guide Load detailed guidance based on context:
Topic Reference Load When Controllers references/controllers-routing.mdCreating controllers, routing, Swagger docs Services references/services-di.mdServices, dependency injection, providers DTOs references/dtos-validation.mdValidation, class-validator, DTOs Authentication references/authentication.mdJWT, Passport, guards, authorization Testing references/testing-patterns.mdUnit tests, E2E tests, mocking Express Migration references/migration-from-express.mdMigrating from Express.js to NestJS
Code Examples
Controller with DTO Validation and Swagger
import { IsEmail , IsString , MinLength } from 'class-validator' ;
import { ApiProperty } from '@nestjs/swagger' ;
export class CreateUserDto {
@ApiProperty ({ example : 'user@example.com' })
@IsEmail ()
email : string ;
@ApiProperty ({ example : 'strongPassword123' , minLength : 8 })
@IsString ()
@MinLength (8 )
password : string ;
}
import { Body , Controller , Post , HttpCode , HttpStatus } from '@nestjs/common' ;
import { ApiCreatedResponse , ApiTags } from '@nestjs/swagger' ;
import { UsersService } from './users.service' ;
import { CreateUserDto } from './dto/create-user.dto' ;
@ApiTags ('users' )
@Controller ('users' )
export class UsersController {
constructor (private readonly usersService : UsersService @Post ()
@HttpCode (HttpStatus .CREATED )
@ApiCreatedResponse ({ description : 'User created successfully.' })
create (@Body () createUserDto : CreateUserDto return this .usersService .create (createUserDto);
}
}
Service with Dependency Injection and Error Handling
import { Injectable , ConflictException , NotFoundException } from '@nestjs/common' ;
import { InjectRepository } from '@nestjs/typeorm' ;
import { Repository } from 'typeorm' ;
import { User } from './entities/user.entity' ;
import { CreateUserDto } from './dto/create-user.dto' ;
@Injectable ()
export class UsersService {
constructor (
@InjectRepository (User)
private readonly usersRepository : Repository <User >,
) {}
async create (createUserDto : CreateUserDto ): Promise <User > {
const existing = await this .usersRepository .findOneBy ({ email : createUserDto.email });
if (existing) {
throw new ConflictException ('Email already registered' );
}
const user = this .usersRepository .create (createUserDto);
return this .usersRepository .save (user);
}
async findOne (id : number ): Promise <User > {
const user = await this .usersRepository .findOneBy ({ id });
if (!user) {
throw new NotFoundException (`User #${id} not found` );
}
return user;
}
}
Module Definition
import { Module } from '@nestjs/common' ;
import { TypeOrmModule } from '@nestjs/typeorm' ;
import { UsersController } from './users.controller' ;
import { UsersService } from './users.service' ;
import { User } from './entities/user.entity' ;
@Module ({
imports : [TypeOrmModule .forFeature ([User ])],
controllers : [UsersController ],
providers : [UsersService ],
exports : [UsersService ],
})
export class UsersModule {}
Unit Test for Service
import { Test , TestingModule } from '@nestjs/testing' ;
import { getRepositoryToken } from '@nestjs/typeorm' ;
import { ConflictException } from '@nestjs/common' ;
import { UsersService } from './users.service' ;
import { User } from './entities/user.entity' ;
const mockRepo = {
findOneBy : jest.fn (),
create : jest.fn (),
save : jest.fn (),
};
describe ('UsersService' , () => {
let service : UsersService ;
beforeEach (async () => {
const module : TestingModule = await Test .createTestingModule ({
providers : [
UsersService ,
{ provide : getRepositoryToken (User ), useValue : mockRepo },
],
}).compile ();
service = module .get <UsersService >(UsersService );
jest.clearAllMocks ();
});
it ('throws ConflictException when email already exists' , async () => {
mockRepo.findOneBy .mockResolvedValue ({ id : 1 , email : 'user@example.com' });
await expect (
service.create ({ email : 'user@example.com' , password : 'pass1234' }),
).rejects .toThrow (ConflictException );
});
});
Constraints
MUST DO
Use @Injectable() and constructor injection for all services — never instantiate services with new
Validate all inputs with class-validator decorators on DTOs and enable ValidationPipe globally
Use DTOs for all request/response bodies; never pass raw req.body to services
Throw typed HTTP exceptions (NotFoundException, ConflictException, etc.) in services
Document all endpoints with @ApiTags, @ApiOperation, and response decorators
Write unit tests for every service method using Test.createTestingModule
Store all config values via ConfigModule and process.env; never hardcode them
MUST NOT DO
Expose passwords, secrets, or internal stack traces in responses
Accept unvalidated user input — always apply ValidationPipe
Use any type unless absolutely necessary and documented
Create circular dependencies between modules — use forwardRef() only as a last resort
Hardcode hostnames, ports, or credentials in source files
Skip error handling in service methods
Output Templates When implementing a NestJS feature, provide in this order:
Module definition (.module.ts)
Controller with Swagger decorators (.controller.ts)
Service with typed error handling (.service.ts)
DTOs with class-validator decorators (dto/*.dto.ts)
Unit tests for service methods (*.service.spec.ts)
Knowledge Reference NestJS, TypeScript, TypeORM, Prisma, Passport, JWT, class-validator, class-transformer, Swagger/OpenAPI, Jest, Supertest, Guards, Interceptors, Pipes, Filters
Métiers associés SOC
Basé sur la classification professionnelle SOC
