Backend to frontend handoff docs

Skill jgamaraalv/delivery-loop/.claude/skills/backend-to-frontend-handoff-docs

Continuous fullstack delivery loops — orchestrates frontend, backend, and quality subagents (behaviour drivers, engineers, UI/UX specialist, code/security reviewers, architects) in a test → diagnose → fix → review → secure → re-test cycle until the work is production-ready

Install

npx -y skills add jgamaraalv/delivery-loop --skill backend-to-frontend-handoff-docs

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 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.

What its author says it does

Copied from the file, not written here

Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.

SKILL.md

2.6 KB, as published. Nobody here has run it

API Handoff Mode

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.

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.

Goal

Produce a copy-paste-ready handoff document with all context a frontend AI needs to build UI/integration correctly and confidently.

Inputs

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.

Workflow

Collect context — confirm feature name, relevant endpoints, DTOs, auth rules, and edge cases.
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.
Fill the template — read references/handoff-template.md and fill every section with concrete data. Omit subsections only when truly not applicable (note why).
Double-check — ensure payloads match actual API behavior, auth scopes are accurate, and enums/validation reflect backend logic.

Rules

NO CHAT OUTPUT—produce only the handoff markdown block, nothing else.
Be precise: types, constraints, examples—not vague prose.
Include real example payloads where helpful.
Surface non-obvious behaviors—don't assume frontend will "just know."
If backend made trade-offs or assumptions, document them.
Keep it scannable: headers, tables, bullets, code blocks.
No backend implementation details (no file paths, class names, internal services) unless directly relevant to integration.
If something is incomplete or TBD, say so explicitly.

After Generating

Write the final markdown into the handoff file only—do not echo it in chat. (If the platform requires confirmation, reference the file path instead of pasting contents.)