How do I install the Django Dto Mapper skill?

Run npx skillmds@latest add viniciusjsdev/django-dto-mapper in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Django Dto Mapper safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Django Dto Mapper?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Django Dto Mapper free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Django Dto Mapper?

viniciusjsdev (@viniciusjsdev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Django Dto Mapper by viniciusjsdev — Agent Skill

Name: Django Dto Mapper
Author: viniciusjsdev

Django Dto Mapper

Implement approved Django backend DTOs and explicit representation Mappers. Use when defining Controller request or response payloads, Service inputs or results, structural validation, request-to-Service conversion, result-to-response conversion, or repository-neutral record shapes. Do not use for endpoints, business rules, ORM queries, persistence, or implicit AutoMapper-style mapping.

viniciusjsdev bed5ec3 2 files · 2.3 KB Updated Sep 17, 2026

File contents

Django DTO Mapper

Implement explicit, testable representation boundaries from the approved API contract.

Required Context

Read AGENTS.md, docs/architecture/api-contract.md, docs/architecture/security-contract.md, docs/architecture/backend-implementation-contract.md, .codex/references/dto-controller-policy.md, .codex/references/mapping-policy.md, and .codex/references/module-documentation.md.

Require an approved implementation contract. Stop if payload fields, nullability, sensitive-field exposure, or mapping ownership are unresolved.

Workflow

Identify request DTO, Service input, Service result, and response DTO shapes for the use case.
Implement structural and field-level validation in dtos/<use_case>.py.
Implement explicit request-to-input and result-to-response functions in mappers/<use_case>.py.
Use allowlists for response and sensitive-field mapping.
Add meaningful opening module docstrings and trace behavioral mappings to approved contracts or BR-### rules.
Add focused DTO and mapper tests for valid, invalid, omitted, nullable, and sensitive fields.

Boundaries

Do not authorize users or enforce business invariants in DTOs or Mappers.
Do not import ORM Models, Repositories, QuerySets, HTTP request objects, or Service implementations.
Do not query, persist, call integrations, or use reflection-based AutoMapper dependencies.
Keep ORM/record conversion inside repositories/mappers.py, owned by $django-repository.

Finish only when Controller payloads are DTO-defined, conversions are explicit, sensitive fields are intentional, and tests cover the contract.

---name: django-dto-mapperdescription: Implement approved Django backend DTOs and explicit representation Mappers. Use when defining Controller request or response payloads, Service inputs or results, structural validation, request-to-Service conversion, result-to-response conversion, or repository-neutral record shapes. Do not use for endpoints, business rules, ORM queries, persistence, or implicit AutoMapper-style mapping.---# Django DTO MapperImplement explicit, testable representation boundaries from the approved API contract.## Required ContextRead `AGENTS.md`, `docs/architecture/api-contract.md`, `docs/architecture/security-contract.md`, `docs/architecture/backend-implementation-contract.md`, `.codex/references/dto-controller-policy.md`, `.codex/references/mapping-policy.md`, and `.codex/references/module-documentation.md`.Require an approved implementation contract. Stop if payload fields, nullability, sensitive-field exposure, or mapping ownership are unresolved.## Workflow1. Identify request DTO, Service input, Service result, and response DTO shapes for the use case.2. Implement structural and field-level validation in `dtos/<use_case>.py`.3. Implement explicit request-to-input and result-to-response functions in `mappers/<use_case>.py`.4. Use allowlists for response and sensitive-field mapping.5. Add meaningful opening module docstrings and trace behavioral mappings to approved contracts or `BR-###` rules.6. Add focused DTO and mapper tests for valid, invalid, omitted, nullable, and sensitive fields.## Boundaries- Do not authorize users or enforce business invariants in DTOs or Mappers.- Do not import ORM Models, Repositories, QuerySets, HTTP request objects, or Service implementations.- Do not query, persist, call integrations, or use reflection-based AutoMapper dependencies.- Keep ORM/record conversion inside `repositories/mappers.py`, owned by `$django-repository`.Finish only when Controller payloads are DTO-defined, conversions are explicit, sensitive fields are intentional, and tests cover the contract.

Frequently asked questions