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.
Profile →npx skills add softaworks/agent-toolkit --skill frontend-to-backend-requirements --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. --- ##
What does the frontend-to-backend-requirements skill do?
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.
How do I install it?
Run `npx skills add softaworks/agent-toolkit --skill frontend-to-backend-requirements --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From softaworks/agent-toolkit, a repository with 2,276 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.