backend-dev

Designs backend architectures covering API contracts, database schemas, and concurrency patterns.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/joySUSY/violet-plugin-place --skill backend-dev-joysusy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-dev
Source: https://github.com/joySUSY/violet-plugin-place/tree/main/plugins/backend-dev
Command: npx skills add https://github.com/joySUSY/violet-plugin-place --skill backend-dev-joysusy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Backend systems fail when schemas are designed after routes, mutations lack idempotency, and synchronous work blocks event loops. This Skill enforces architecture-first design so data models, API contracts, and concurrency strategies are proven before implementation begins. ## Core Features & Use Cases - Database Architecture Guidance: Normalization to 3NF, index strategy (B-Tree, GIN), transaction boundaries, and ORM pitfalls like the N+1 problem for Postgres and Prisma. - API Contract Design: REST resource modeling, idempotency keys, cursor-based pagination, JWT/session authentication, and RBAC enforcement. - Concurrency & Async Patterns: Background job queues, optimistic concurrency control, connection pool management, and event-loop starvation prevention. - Use Case: When asked to design a multi-tenant SaaS billing backend, the Skill produces a normalized ERD with indexes, an idempotent REST contract, and an async invoice-generation pipeline before any route handler is written. ## Quick Start Ask the assistant to design the database schema and REST API contract for your new feature using the backend-dev engine.

Frequently Asked Questions about backend-dev

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

FAQPage Schema
How do I design a database schema before writing API routes?▼

Start with an ERD normalized to third normal form, add explicit B-Tree indexes on every foreign key, and define transaction boundaries for multi-write operations. Only after the schema is proven should you model REST resources on top of it.

What is cursor-based pagination vs offset pagination in REST APIs?▼

Cursor pagination uses an indexed column like an id with WHERE id > cursor, giving constant query time at any depth. Offset pagination forces the database to scan and discard rows, degrading badly on large tables.

How do idempotency keys prevent duplicate API requests?▼

The client sends a unique X-Idempotency-Key header with each mutating request. The server stores the key and returns the cached result on retries, so a network failure cannot cause duplicate charges or records.

When should synchronous work move to a background queue?▼

Any HTTP request taking longer than about one second should be offloaded. Return 202 Accepted immediately, push the job to a queue like Redis or SQS, and let a separate worker process it and update status in the database.

Does this Skill cover language-specific backend implementation?▼

No. It owns architecture-level decisions like data modeling, API contracts, and concurrency patterns. Language-specific implementation in Rust, Python, Go, or TypeScript is delegated to the corresponding language engines.