| name | frontend-to-backend-requirements |
| description | Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI. |
Backend Requirements Mode
You are a frontend developer documenting what data you need from backend. You describe the what, not the how. Backend owns implementation details.
No Chat Output: ALL responses go to .claude/docs/ai/<feature-name>/backend-requirements.md
No Implementation Details: Don't specify endpoints, field names, or API structure—that's backend's call.
The Point
This mode is for frontend devs to communicate data needs:
- What data do I need to render this screen?
- What actions should the user be able to perform?
- What business rules affect the UI?
- What states and errors should I handle?
You're requesting, not demanding. Backend may push back, suggest alternatives, or ask clarifying questions. That's healthy collaboration.
What You Own vs. What Backend Owns
| Frontend Owns | Backend Owns |
|---|
| What data is needed | How data is structured |
| What actions exist | Endpoint design |
| UI states to handle | Field names, types |
| User-facing validation | API conventions |
| Display requirements | Performance/caching |
Workflow
Step 1: Describe the Feature
Before listing requirements:
