backend

Guide backend engineering for REST/GraphQL APIs, service logic, and persistence changes.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/alvarovillalbaa/plugins --skill backend-alvarovillalbaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend
Source: https://github.com/alvarovillalbaa/plugins/tree/main/engineering/skills/backend
Command: npx skills add https://github.com/alvarovillalbaa/plugins --skill backend-alvarovillalbaa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents backend changes from drifting into inconsistent, fragile, or unsafe API and persistence patterns by providing a single authoritative playbook for backend engineering decisions and implementation boundaries.

Core Features & Use Cases

  • Own the backend slice end-to-end: service-layer logic, schemas/models shape, API contracts, persistence, queues, and operational debugging.
  • Route work to the correct layer: controllers/serializers stay thin while business rules and orchestration live in services and models remain persistence-focused.
  • Ship safely with repeatable heuristics: contract-first development, failure modes, observability signals, and safe migration/rollout thinking.
  • Apply targeted backend tooling: API linting/scoring, breaking-change detection, scaffolding from OpenAPI, and database migration/index helpers.

Quick Start

Use the backend skill to refactor a REST endpoint by mapping the authoritative ownership path, confirming request/response contracts and failure modes, then implementing the smallest coherent change in the service and persistence layers.

Frequently Asked Questions about backend

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

FAQPage Schema
How do I design a backend API that enforces strict service-layer boundaries?

Designing a backend API with strict service-layer boundaries requires keeping controllers thin and routing business rules to services. This Skill guides that architecture by enforcing layer ownership and contract-first development for reliable REST or GraphQL endpoints.

What is the best way to manage database migrations and schema changes safely?

Safe database migrations require careful schema design and index assistance to prevent breaking changes. This Skill provides bundled scripts and heuristics for safe persistence changes, helping you implement models and roll out migrations without fragile patterns.

How do I detect breaking changes in my API contracts?

Detecting breaking changes in API contracts involves linting and scoring endpoint definitions against previous versions. This Skill applies targeted tooling to evaluate OpenAPI scaffolding and verify contract compliance during refactoring.

How do I route async jobs and background operations through a queue system?

Routing async jobs through a queue system requires mapping background operations to the correct service layer. This Skill guides implementing async task routing while maintaining observability signals for operational debugging.

Why does my backend service have inconsistent API and persistence patterns?

Inconsistent backend API and persistence patterns happen when engineering decisions drift without an authoritative playbook. This Skill prevents fragility by providing a single playbook for backend layer ownership, contract-first design, and safe migrations.

Does this approach support contract-first development for both REST and GraphQL?

Contract-first development for both REST and GraphQL is supported by this Skill. It enforces defining request and response contracts, mapping failure modes, and confirming endpoint boundaries before implementing service and persistence layers.