backend-to-frontend-handoff-docs

Topics in the source

• API Handoff Mode
• Goal
• Inputs
• Workflow
• Output Format
• Data Models / DTOs
• Enums & Constants
• Validation Rules

No Chat Output: Produce the handoff document only. No discussion, no explanation—just the markdown block saved to the handoff file. You 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. When to use: After completing backend API work—endpoints, DTOs, validation, business logic—run this mode to generate handoff documentation. 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. Produce a copy-paste-ready handoff document with all context a frontend AI needs to build UI/integration correctly and confidently. Completed API code (endpoints, controllers, services, DTOs, validation). Related business context from the task/user story. Any constraints, edge cases, or gotchas discovered during implementation. 1. Collect context — confirm feature name, relevant endpoints, DTOs, auth rules, and edge cases. 2. Create/update handof

This is an excerpt. Refer to the complete source and its current requirements.