Agent skill · Databases

frontend-backend-mapper

Analyzes and maps frontend API calls to backend endpoints. Detects missing endpoints, unused endpoints, and integration gaps. Optional: trace complete data flows to database and design tokens. Related: api-contract-validator for detailed type analysis.

majiayu000github.com/majiayu000GitHub ↗
copilotclaude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill frontend-backend-mapper-okgoogle13-careercopilot-2 --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/analysis/frontend-backend-mapper-okgoogle13-careercopilot-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Frontend-Backend Mapper Workflow This skill analyzes the integration between frontend API services and backend endpoints to ensure complete coverage. It can optionally trace complete data flows including database operations and design token usage. ## Workflow Steps 1. **Scan frontend API services:** - Read all files in `frontend/src/api/*.ts` - Extract API call patterns: - Function names (e.g., `generateKscResponses`) - HTTP methods (GET, POST, PUT, DELETE) - URL paths (e.g., `/api/v1/ksc/generate`) - Request/response TypeScript interfaces - Build frontend API inventory 2. **Scan backend endpoints:** - Read all files in `backend/app/api/endpoints/*.py` - Extract route definitions: - Route decorators (`@router.post`, `@router.get`) - URL paths - Request/response Pydantic models - Function names - Build backend endpoint inventory 3. **Perform integration analysis:** - Match frontend calls to backend endpoints - Identify ✅ **MAPPED** integrations (frontend ↔ backend) - Identify ❌ **MISSING BACKEND** endpoints (frontend calls with no backend) - Identify ❌ **UNUSED BACKEND** endpoints (backend routes with no frontend) - Identify ⚠️ **TYPE MISMATCHES** (field name inconsistencies, type

What's inside
Steps it walks through
  1. Workflow Steps
  2. Analysis Output Structure
  3. Integration Map Report
  4. Visual Diagram
  5. Template Variables
  6. Usage Tips
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the frontend-backend-mapper skill do?

Analyzes and maps frontend API calls to backend endpoints. Detects missing endpoints, unused endpoints, and integration gaps. Optional: trace complete data flows to database and design tokens. Related: api-contract-validator for detailed type analysis.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill frontend-backend-mapper-okgoogle13-careercopilot-2 --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 majiayu000/claude-skill-registry, a repository with 534 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.

Keep going