Frontend To Backend Requirements
This forces you to document what data your frontend needs without dictating how the backend should implement it. Instead of specifying endpoints and field names, you describe what shows on screen, what actions users can perform, and what states you need to handle. Everything goes into a markdown file that becomes the collaboration point between frontend and backend. The format deliberately includes an "Uncertainties" section and encourages phrases like "push back if this complicates things" because the whole point is inviting discussion, not issuing orders. It's useful when you're building a new feature and need to communicate requirements without stepping on backend's toes about architecture decisions.
- skills.sh installs
- 441
- GitHub stars
- 33.2K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add davila7/claude-code-templates --skill frontend-to-backend-requirements --agent claude-codeInstalls into .claude/skills of the current project.
Files
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
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageDetails
- Repository
- github.com/davila7/claude-code-templates
- Categories
- Frontend Development, Backend & APIs
- First seen
- Jun 3, 2026
More from davila7/claude-code-templates
All 618- Canvas Design439
- Nowait Reasoning Optimizer438
- Code Review Checklist437
- Prompt Caching437
- Commit435
- Vercel Deployment433
- C4 Architecture430
- Information Security Manager Iso27001428
- Mlflow427
- Statsmodels426
- Prompt Library423
- Chroma421
- Telegram Mini App420
- Pricing Strategy419
- Seo419
- Evaluating Llms Harness418
- Ml Paper Writing416
- Openalex Database416
- Workflow Automation416
- Backend To Frontend Handoff Docs413
- Shopify Development411
- Nextjs Supabase Auth410
- Clinicaltrials Database409
- Writing Plans408
Recommended
More Frontend Development
eve-web-ui-testing-agent-browserincept5/eve-skillpacksWeb UI testing and browser automation. Use Vercel agent-browser for general apps, or the repo-pinned Playwright wrapper inside Eve Horizon. Use when tasks requi436skills.sh installs
react-native-architecturesickn33/antigravity-awesome-skillsreact native architecture425skills.sh installs
linear-ui-skillsihlamury/design-skillsLinear's UI design system. Use when building interfaces inspired by Linear's aesthetic - dark mode, Inter font, 4px grid.417skills.sh installs
expo-react-native-coderpproenca/dot-skillsComprehensive Expo React Native feature development guide. This skill should be used when building mobile app screens, navigation, data fetching, authentication415skills.sh installs
nuxt-serversecondsky/claude-skills| Nuxt 4 server-side development with Nitro: API routes, server middleware, database integration, and backend patterns. Use when: creating server API routes, im415skills.sh installs
backend-to-frontend-handoff-docsdavila7/claude-code-templatesCreate API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'c413skills.sh installs