Reviews DTO mapping in Node.js TypeScript code, focusing on transport contracts, normalization, validation boundaries, and safe mapping in backend services and scripts.
Scanned 10/2/2026
npx -y skills add janpereira-dev/ngAutoPilot --skill typescript--dto-mappers--node-dto-mappers-v18 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Typescript Dto Mappers Node Dto Mappers V18?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/janpereira-dev-typescript-dto-mappers-node-dto-mappers-v18)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
id: typescript.dto-mappers.node-dto-mappers-v18
name: Node DTO Mappers v18+
description: >
Reviews DTO mapping in Node.js TypeScript code, focusing on transport contracts, normalization, validation boundaries, and safe mapping in backend services and scripts.
stack:
- TypeScript
- Node.js
category: dto-mappers
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
- node dto mapping
- node dto mappers
- backend mapping
- normalization boundary
- api contract mapping
compatibility:
runtime:
node: "18+"
---
# Node DTO Mappers v18+
## Purpose
Use this skill for DTO mapping in Node.js TypeScript code.
This variant emphasizes transport contracts, normalization, and server-side mapping boundaries where validation and persistence may differ from browser-facing view models.
## When to Use
Use this skill when:
- backend services map transport DTOs to domain or persistence shapes
- scripts normalize external payloads
- mapping must sit near validation boundaries
## Do
Keep mapping pure and explicit.
Validate untrusted inputs before relying on the shape.
Separate transport DTOs from internal domain or persistence models.
## Do Not
Avoid leaking raw transport payloads into core logic.
Avoid skipping validation when the payload is untrusted.
## Review Checklist
- [ ] Node mapping boundary is explicit.
- [ ] Validation happens before trust.
- [ ] Transport and internal shapes are separate.
- [ ] Mapping remains deterministic.
## Expected Output
1. Identify Node DTO boundaries.
2. Recommend validation plus mapping.
3. Keep contracts separate from internal models.
4. Avoid raw payload leakage.
5. Produce backend-safe mapping guidance.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!