API Endpoint Skill
When to Apply
- •User asks to add a new API endpoint or CRUD route.
- •Existing API contract needs extension.
- •Backend changes require request validation and response contract updates.
Workflow
- •Read project specs first:
specs/specs.md, then role-specific specs as needed. - •Detect backend conventions from the repo (routing, controller/service patterns, validation style).
- •Define endpoint contract before implementation:
- •Path + method
- •Auth requirements
- •Request validation
- •Response shape and error shape
- •Implement with thin transport layer and business logic in domain/service/action classes.
- •Add focused tests for success path, validation failure, and authorization failure.
Quality Bar
- •Keep endpoint behavior idempotent where required.
- •Avoid N+1 queries and over-fetching.
- •Return consistent JSON payloads.