All skills
controller-api-implementation
FoundationJIT onlytask-agent: use when implementing routes, request parsing, validation handoff, auth context, responses, or status/error mapping; skip work without a controller/API boundary.
- Group
- Backend engineering
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- implement controller routing request parsing validation response and status codes
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local controller api implementation 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
- controller implementation decision with transport parsing, validation handoff, identity provenance, application boundary, contract response and error mapping, resource bounds, and focused evidence
Escalation signals
When this skill must hand the decision back
- Controller mistakes leak transport details and inconsistent error semantics
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 |
|---|---|---|---|
| boundary-patterns.mdbenchmark-pattern | Route ownership, DTO mapping, authorization, or idempotency boundaries are unclear. | The controller remains a thin transport adapter. | Task |
| checklist.mddecision-checklist | Route changes touch validation, auth context, errors, or response shape. | No transport-facing controller behavior changes. | Task |
| evidence-patterns.mdevidence-pattern | Controller claims require fresh routes, specs, generated files, and tests. | Current route and transport artifacts prove boundary completeness. | Task |