backend-code

Build REST or GraphQL endpoints with database operations and generate API_SUMMARY.md contracts.

3|2|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/sami-abdul/claude-predev-setup --skill backend-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-code
Source: https://github.com/sami-abdul/claude-predev-setup/tree/main/scaffold/.claude/skills/backend-code
Command: npx skills add https://github.com/sami-abdul/claude-predev-setup --skill backend-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building scalable backend APIs that reliably interact with real databases and provide a clear API contract for frontend teams controlling data flows and expectations.

Core Features & Use Cases

  • Implement REST or GraphQL endpoints with integrated database operations (read/write/update/delete).
  • Design and seed database schemas, handle migrations, and produce a formal API contract for frontend handoff.
  • Generate an API_SUMMARY.md detailing endpoints, authentication, and seed data for reliable integration.

Quick Start

Scaffolds backend APIs, wires them to the database, and generates a frontend-ready API contract.

Frequently Asked Questions about backend-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build backend APIs with real database integration for frontend teams?

Build backend APIs with real database integration by scaffolding endpoints that reliably read, write, update, and delete database records while generating a formal API contract for frontend teams. This ensures controlled data flows and clear expectations.

How do I generate an API contract summary for frontend handoff?

Generate an API contract summary for frontend handoff by producing an API_SUMMARY.md file that details endpoint routes, authentication methods, and seed data. This provides a formal contract for reliable frontend integration.

Can I use this approach for both REST and GraphQL endpoint development?

Yes, this approach applies to both REST and GraphQL endpoint development. It enforces that every endpoint reads or writes to the database, validates inputs, and returns proper status codes regardless of the API paradigm chosen.

What's the best way to design and seed database schemas with proper migrations?

Design and seed database schemas with proper migrations by scaffolding the backend API layer to wire directly to the database. This process handles schema creation and seeding while ensuring endpoints interact reliably with the data layer.

Why does my backend API endpoint need to return proper status codes and validate inputs?

Backend API endpoints need to return proper status codes and validate inputs to enforce end-to-end API quality checks. This ensures reliable database operations and provides a formal, predictable contract for frontend integration.

Does this backend API scaffolding enforce database operations for every endpoint?

Yes, this backend API scaffolding enforces that every endpoint reads or writes to the database. It prevents mock data usage by validating inputs, returning proper status codes, and generating a detailed API contract for handoff.