Nestjs validation pipes
Skill dkmqflx/nestjs-best-practices-plugin/plugins/nestjs-best-practices/skills/nestjs-validation-pipes
NestJS validation and pipes best practices. Use when validating or transforming request input in NestJS — DTO validation, ValidationPipe, class-validator/class-transformer, or custom pipes. Triggers on ValidationPipe, @IsString/@IsEmail, ParseIntPipe, whitelist, or transform.From its SKILL.md
npx -y skills add dkmqflx/nestjs-best-practices-plugin --skill nestjs-validation-pipesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.0 KB, 392 tokens by cl100k_base, as published. Nobody here has run it
NestJS Validation & Pipes
Pipes run before route handlers to validate and transform incoming request data. Combined with class-validator and class-transformer, they keep DTOs the single source of truth for input shape and constraints.
When to Apply
- Validating request bodies, query params, or route params in a NestJS app.
- Configuring
ValidationPipe(globally or per-route). - Annotating DTOs with
class-validatordecorators. - Coercing param types with built-in parse pipes (
ParseIntPipe,ParseUUIDPipe, ...). - Writing a reusable custom pipe via
PipeTransform.
Rules
global-validation-pipe- RegisterValidationPipeonce inmain.tsso every endpoint is validated.whitelist-strip-unknown- Usewhitelist+forbidNonWhitelistedto strip or reject unexpected properties.transform-payloads- Enabletransform: trueto auto-instantiate DTO classes and coerce primitive types.dto-classes-not-interfaces- Define DTOs as classes; interfaces are erased at runtime and carry no metadata.class-validator-decorators- Annotate every DTO field withclass-validatordecorators.nested-object-validation- Use@ValidateNested+@Typeto validate nested DTOs and arrays.built-in-parse-pipes- UseParseIntPipe/ParseUUIDPipe/ParseBoolPipeto coerce and validate params.custom-pipe-implementation- ImplementPipeTransformfor reusable custom validation or transformation.
How to Use
Read the relevant file under rules/ for the topic at hand. Each rule states why it matters and shows an incorrect vs. correct example. Apply them when writing or reviewing NestJS input-handling code.
What ships with it: 8 files
6.3 KB alongside SKILL.md