Agent skill · software engineering · davila7
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.
Why this skill is useful
Codifies a structured approach for frontend developers to document data needs for backend APIs, reducing ambiguity in communication.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
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: 1. What is this? — Screen, flow, component 2. Who uses it? — User type, permissions 3. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/frontend-to-backend-requirements