Summary
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.
Install to Claude Code
npx -y skills add davila7/claude-code-templates --skill frontend-to-backend-requirements --agent claude-codeInstalls into .claude/skills of the current project.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Files
SKILL.md
Select a file.
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
