frontend-to-backend-requirements
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.
- License 许可
- MIT
- 最近更新
- 2026-08-16
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- 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.
02 资源文件 1
- 参考文档README.md5.0 KB
03 SKILL.md 正文
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.mdNo 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:
- What is this? — Screen, flow, component
- Who uses it? — User type, permissions
- What's the goal? — What does success look like?
Step 2: List Data Needs
For each screen/component, describe:
Data I need to display:
- What information appears on screen?
- What's the relationship between pieces?
- What determines visibility/state?
Actions user can perform:
- What can the user do?
- What's the expected outcome?
- What feedback should they see?
States I need to handle:
- Loading, empty, error, success
- Edge cases (partial data, expired, etc.)
Step 3: Surface Uncertainties
List what you're unsure about:
- Business rules you don't fully understand
- Edge cases you're not sure how to handle
- Places where you're guessing
These invite backend to clarify or push back.
Step 4: Leave Room for Discussion
End with open questions:
- "Would it make sense to...?"
- "Should I expect...?"
- "Is there a simpler way to...?"
Output Format
Create .claude/docs/ai/<feature-name>/backend-requirements.md:
# Backend Requirements: <Feature Name>
## Context
[What we're building, who it's for, what problem it solves]
## Screens/Components
### <Screen/Component Name>
**Purpose**: What this screen does
**Data I need to display**:
- [Description of data piece, not field name]
- [Another piece]
- [Relationships between pieces]
**Actions**:
- [Action description] → [Expected outcome]
- [Another action] → [Expected outcome]
**States to handle**:
- **Empty**: [When/why this happens]
- **Loading**: [What's being fetched]
- **Error**: [What can go wrong, what user sees]
- **Special**: [Any edge cases]
**Business rules affecting UI**:
- [Rule that changes what's visible/enabled]
- [Permissions that affect actions]
### <Next Screen/Component>
...
## Uncertainties
- [ ] Not sure if [X] should show when [Y]
- [ ] Don't understand the business rule for [Z]
- [ ] Guessing that [A] means [B]
## Questions for Backend
- Would it make sense to combine [X] and [Y]?
- Should I expect [Z] to always be present?
- Is there existing data I can reuse for [W]?
## Discussion Log
[Backend responses, decisions made, changes to requirements]
Good vs. Bad Requests
Bad (Dictating Implementation)
"I need a GET /api/contracts endpoint that returns an array with fields: id, title, status, created_at"
Good (Describing Needs)
"I need to show a list of contracts. Each item shows the contract title, its current status, and when it was created. User should be able to filter by status."
Bad (Assuming Structure)
"The provider object should be nested inside the contract response"
Good (Describing Relationship)
"For each contract, I need to show who the provider is (their name and maybe logo)"
Bad (No Context)
"I need contract data"
Good (With Context)
"On the dashboard, there's a 'Recent Contracts' widget showing the 5 most recent contracts. User clicks one to go to detail page."
Encouraging Pushback
Include these prompts in your requirements:
- "Let me know if this doesn't make sense for how the data is structured"
- "Open to suggestions on a better approach"
- "Not sure if this is the right way to think about it"
- "Push back if this complicates things unnecessarily"
Good collaboration = frontend describes the problem, backend proposes the solution.
Rules
- NO IMPLEMENTATION DETAILS—don't specify endpoints, methods, field names
- DESCRIBE, DON'T PRESCRIBE—say what you need, not how to provide it
- INCLUDE CONTEXT—why you need it helps backend make better choices
- SURFACE UNKNOWNS—don't hide confusion, invite clarification
- INVITE PUSHBACK—explicitly ask for backend's input
- UPDATE THE DOC—add backend responses to Discussion Log
- STAY HUMBLE—you're asking, not demanding
After Backend Responds
Update the requirements doc:
- Add responses to Discussion Log
- Adjust requirements based on feedback
- Mark resolved uncertainties
- Note any decisions made
The doc becomes the source of truth for what was agreed.
04 同仓库更多 Skills
zapier-make-patterns
No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
workflow-automation
Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off. This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation. Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility
trigger-dev
Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.
slack-automation
Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.
planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.