All skills
dto-schema-design
FoundationJIT onlytask-agent: use when DTO fields, validation, nullability, defaults, serialization, or compatibility change; skip persistence/domain-only work without an external schema.
- Group
- Data & API contracts
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- design DTO schemas fields validation defaults nullability and serialization
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local dto schema design decision is required
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- DTO schema contract with fields types defaults validation and examples
Escalation signals
When this skill must hand the decision back
- Schema drift causes client defects and inconsistent validation behavior
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | Field semantics, mapping, trust strictness, or compatibility needs selection. | No DTO boundary or exposed field behavior changes. | Task |
| checklist.mddecision-checklist | DTO changes nullability, unknown fields, sensitivity, or generated consumers. | Only internal model names change behind stable mappings. | Task |
| evidence-patterns.mdevidence-pattern | Contract claims require fresh schemas, mappers, clients, or tests. | No DTO compatibility or privacy claim awaits proof. | Task |