Claude Code Frontend-to-Backend Requirements for UI Data Needs
Describe what a screen displays, what users can do, and what happens in edge cases. Create a Markdown requirements file that backend developers can review before designing the API.
中文Install in Claude Code
Use Claude Code with the pinned skill directory. Bring a mockup or flow description, user roles, and expected results for key actions.
- Get the complete `cli-tool/components/skills/enterprise-communication/frontend-to-backend-requirements` directory from the pinned GitHub checkout.
- Copy it into the target project's `.claude/skills/` directory. Confirm `.claude/skills/frontend-to-backend-requirements/SKILL.md`, open Claude Code at the project root, and call `/frontend-to-backend-requirements`.
Example task
Specify a fictional community-room booking list. Staff can see the time slot and whether cancellation is available. Describe empty, failed-load, and expired states separately. Ask whether expired bookings can be canceled.What to check
Expect `.claude/docs/ai/room-bookings/backend-requirements.md` with visible information, cancellation feedback, and the three states. Eligibility for expired bookings remains an open question.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should the frontend handoff choose endpoint URLs and field names up front?
Start with the meaning of the required data, the states, and the feedback. Resolve the interface names and backend structure during API design.