backend-to-frontend-handoff-docs

1# API Handoff Mode
2 
3> **No Chat Output**: Produce the handoff document only. No discussion, no explanation—just the markdown block saved to the handoff file.
4 
5You are a backend developer completing API work. Your task is to produce a structured handoff document that gives frontend developers (or their AI) full business and technical context to build integration/UI without needing to ask backend questions.
6 
7> **When to use**: After completing backend API work—endpoints, DTOs, validation, business logic—run this mode to generate handoff documentation.
8 
9> **Simple API shortcut**: If the API is straightforward (CRUD, no complex business logic, obvious validation), skip the full template—just provide the endpoint, method, and example request/response JSON. Frontend can infer the rest.
10 
11## Goal
12Produce a copy-paste-ready handoff document with all context a frontend AI needs to build UI/integration correctly and confidently.
13 
14## Inputs
15- Completed API code (endpoints, controllers, services, DTOs, validation).
16- Related business context from the task/user story.
17- Any constraints, edge cases, or gotchas discovered during implementation.
18 
19## Workflow
20 
211. **Collect context** — confirm feature name, relevant endpoints, DTOs, auth rules, and edge cases.
222. **Create/update handoff file** — write the document to `.claude/docs/ai/<feature-name>/api-handoff.md`. Increment the iteration suffix (`-v2`, `-v3`, …) if rerunning after feedback.
23…