Api contract boundary
Skill jukrap/ai-agent-playbook/skills/backend/api-contract-boundary
Use when implementing, debugging, or reviewing frontend/backend API integration, DTO mapping, mock-vs-remote behavior, payloads, adapters, or uncertain contracts.From its SKILL.md
npx -y skills add jukrap/ai-agent-playbook --skill api-contract-boundaryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.9 KB, 140 tokens by cl100k_base, as published. Nobody here has run it
API Contract Boundary
Keep backend uncertainty at the API boundary instead of leaking it through the UI.
Workflow
- Inspect existing API client, env mode, mock/remote switch, endpoint usage, and adapter patterns.
- Confirm request/response shape from available backend docs, DTOs, mappers, logs, or actual network responses.
- Keep backend DTOs and frontend domain types separate.
- Handle wrapper responses, naming conversion, nullable values, and error shapes at the API boundary.
- Do not hide remote failures with mock fallback unless explicitly requested.
Reference
Read references/api-boundary-checklist.md before changing API integration or diagnosing contract bugs.
What ships with it: 1 file
984 B alongside SKILL.md