New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Frontend To Backend Requirements

by davila7 in davila7/claude-code-templates

Document frontend data needs for backend developers. An agent skill from davila7/claude-code-templates.

MITAuto-check passedFrontend & Design

Install Frontend To Backend Requirements

skills CLI
$ npx skills add davila7/claude-code-templates --skill frontend-to-backend-requirements -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davila7/claude-code-templates frontend-to-backend-requirements --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/enterprise-communication/frontend-to-backend-requirements .claude/skills/frontend-to-backend-requirements && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
frontend-to-backend-requirements
GitHub stars
33k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
572 words
Files
2
Skills in repo
479
Repo updated
First seen
Licence
MIT

At a glance

Document frontend data needs for backend developers. An agent skill from davila7/claude-code-templates.

  • Works in 4 steps: Describe the Feature → List Data Needs → Surface Uncertainties → …
  • Frontend needs to communicate API requirements to backend
  • SKILL.md covers The Point, What You Own vs. What Backend…, Workflow and Output Format, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Frontend To Backend Requirements is an agent skill from davila7/claude-code-templates. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).

It sits in Frontend & Design, covering Backend development. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.

When your agent uses it

  • Frontend needs to communicate API requirements to backend
  • User says backend requirements
  • What data do I need
  • API requirements

Example prompts

  • “backend requirements”
  • “what data do I need”
  • “API requirements”
  • “/frontend-to-backend-requirements”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Describe the Feature
  2. List Data Needs
  3. Surface Uncertainties
  4. Leave Room for Discussion

What it can do on your machine

Read from SKILL.md and the folder at commit c0ca7da. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Frontend To Backend Requirements loads about 1.4k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 572 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davila7/claude-code-templates at commit c0ca7da, republished under its MIT licence (© davila7). 572 words, ~1,410 tokens.

Download SKILL.mdSave it as .claude/skills/frontend-to-backend-requirements/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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.

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 OwnsBackend Owns
What data is neededHow data is structured
What actions existEndpoint design
UI states to handleField names, types
User-facing validationAPI conventions
Display requirementsPerformance/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.

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:

markdown
# 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."

Show full SKILL.md (216 more words)Show less
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:

  1. Add responses to Discussion Log
  2. Adjust requirements based on feedback
  3. Mark resolved uncertainties
  4. Note any decisions made

The doc becomes the source of truth for what was agreed.

© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in cli-tool/components/skills/enterprise-communication/frontend-to-backend-requirements of davila7/claude-code-templates.

  • SKILL.md
  • README.md

Open the folder on GitHubat commit c0ca7da

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in davila7/claude-code-templates, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Frontend To Backend Requirements next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Frontend To Backend Requirements compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frontend To Backend Requirements this skilldavila7/claude-code-templates33k1 repos~1.4kAutomated safety check: PassMIT
MCP Developmentcoollabsio/coolify63k1 repos~949Automated safety check: PassMIT
Turnstile Spincloudflare/skills3k4 repos~7.2kAutomated safety check: NotesApache-2.0
App Feedback AdminJamailar/Beav1.8k—~1.1kAutomated safety check: PassCustom licence
Solar Iconssaoudi-h/solar-icons190—~2.1kAutomated safety check: PassMIT
Vue Component Developmentgdarko/laravel-vue-starter145—~1.1kAutomated safety check: PassMIT

Similar skills

  • MCP Development

    coollabsio/coolify

    A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 1 repo~949 tokens
    Frontend & DesignAuto-check passed

  • Turnstile Spin

    cloudflare/skills

    Official

    Set up, repair, or migrate to Cloudflare Turnstile bot verification in an existing frontend and backend, including server-side Siteverify.

    3k GitHub starsUsed in 4 repos~7.2k tokens
    Frontend & DesignAuto-check: notes

  • App Feedback Admin

    Jamailar/Beav

    Read platform-admin feedback issues through the trusted HTTP admin API, summarize user reports, and turn them into RedBox/RedConvert repair and iteration plans.

    1.8k GitHub stars~1.1k tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

  • Solar Icons

    saoudi-h/solar-icons

    Add Solar Icons via @solar-icons/cli to any React, Vue, Svelte, Solid, Angular, React Native, Nuxt, Static, vanilla JS, or Laravel Blade project.

    190 GitHub stars~2.1k tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

  • Vue Component Development

    gdarko/laravel-vue-starter

    Activate when creating or modifying Vue 3 components, pages, layouts, stores, or services in the frontend.

    145 GitHub stars~1.1k tokensUpdated 6 mo ago
    Frontend & DesignAuto-check passed

  • Nitro Kit UI

    mikker/nitro_kit

    Build or refactor Rails interfaces with Nitro Kit 2's Phlex components, layouts, blocks, FormBuilder, and theme tokens.

    105 GitHub stars~2.1k tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed

More from davila7/claude-code-templates

All 479 skills in this repo

  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    33k GitHub starsUsed in 11 repos~3.5k tokens
    Auto-check: notes

  • Neuropixels Data Analysis

    davila7/claude-code-templates

    Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.

    33k GitHub starsUsed in 9 repos~2.8k tokens
    Auto-check passed

  • Scientific Venue Templates

    davila7/claude-code-templates

    Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.

    33k GitHub starsUsed in 9 repos~5.1k tokens
    Auto-check: notes

  • Brand Voice Content Creator

    davila7/claude-code-templates

    Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.

    33k GitHub starsUsed in 3 repos~1.9k tokens
    Auto-check passed

  • CAPA Officer

    davila7/claude-code-templates

    Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.

    33k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Fda Consultant Specialist

    davila7/claude-code-templates

    Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.

    33k GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed

Categories

Questions about Frontend To Backend Requirements

What does Frontend To Backend Requirements do?

Document frontend data needs for backend developers. An agent skill from davila7/claude-code-templates. Frontend To Backend Requirements is an agent skill from davila7/claude-code-templates. Document frontend data needs for backend developers.

When should I use Frontend To Backend Requirements?

Frontend To Backend Requirements fits situations like: frontend needs to communicate API requirements to backend; user says backend requirements; what data do I need; API requirements.

How do I install Frontend To Backend Requirements in Claude Code?

Run `npx skills add davila7/claude-code-templates --skill frontend-to-backend-requirements -a claude-code`. Or copy the skill folder (cli-tool/components/skills/enterprise-communication/frontend-to-backend-requirements in davila7/claude-code-templates) into .claude/skills/frontend-to-backend-requirements in your project. Claude Code loads it when a task matches its description.

How do I install Frontend To Backend Requirements in Codex?

Run `npx skills add davila7/claude-code-templates --skill frontend-to-backend-requirements -a codex`. Or copy the skill folder (cli-tool/components/skills/enterprise-communication/frontend-to-backend-requirements in davila7/claude-code-templates) into .agents/skills/frontend-to-backend-requirements in your project. Codex loads it when a task matches its description.

Can I use Frontend To Backend Requirements in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill frontend-to-backend-requirements -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend-to-backend-requirements, .gemini/skills/frontend-to-backend-requirements, .github/skills/frontend-to-backend-requirements and .opencode/skills/frontend-to-backend-requirements in your project.

What does Frontend To Backend Requirements need to run?

SKILL.md names no scripts, command-line tools or credentials: Frontend To Backend Requirements is instructions for the agent only.

Does Frontend To Backend Requirements access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Frontend To Backend Requirements safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Frontend To Backend Requirements use?

Frontend To Backend Requirements is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Frontend To Backend Requirements use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Frontend To Backend Requirements?

Skills that share tags, products or a category with Frontend To Backend Requirements: MCP Development (coollabsio/coolify, 63k stars), Turnstile Spin (cloudflare/skills, 3k stars), App Feedback Admin (Jamailar/Beav, 1.8k stars) and Solar Icons (saoudi-h/solar-icons, 190 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frontend To Backend Requirements?

davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,512 GitHub stars. The repository holds 479 skills in this directory. The repository was last updated on October 10, 2026.

Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.