agentsclimarketplace
Sign in

Nestjs validation pipes

Skill dkmqflx/claude-tools/.claude/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

Install
npx -y skills add dkmqflx/claude-tools --skill nestjs-validation-pipes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 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-validator decorators.
  • Coercing param types with built-in parse pipes (ParseIntPipe, ParseUUIDPipe, ...).
  • Writing a reusable custom pipe via PipeTransform.

Rules

  • global-validation-pipe - Register ValidationPipe once in main.ts so every endpoint is validated.
  • whitelist-strip-unknown - Use whitelist + forbidNonWhitelisted to strip or reject unexpected properties.
  • transform-payloads - Enable transform: true to 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 with class-validator decorators.
  • nested-object-validation - Use @ValidateNested + @Type to validate nested DTOs and arrays.
  • built-in-parse-pipes - Use ParseIntPipe/ParseUUIDPipe/ParseBoolPipe to coerce and validate params.
  • custom-pipe-implementation - Implement PipeTransform for 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

rules/

Keep looking

Skills are one crate of 326,851. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.