backend-designer-skill
Design backend architecture, API contracts, core business logic boundaries, and language/framework choices based on architecture/story artifacts. Use when selecting backend stack, auth strategy, and service design.
Best use case
backend-designer-skill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Design backend architecture, API contracts, core business logic boundaries, and language/framework choices based on architecture/story artifacts. Use when selecting backend stack, auth strategy, and service design.
Teams using backend-designer-skill should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/backend-designer-skill/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How backend-designer-skill Compares
| Feature / Agent | backend-designer-skill | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Design backend architecture, API contracts, core business logic boundaries, and language/framework choices based on architecture/story artifacts. Use when selecting backend stack, auth strategy, and service design.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Backend Designer Skill ## Purpose Produce backend design artifacts that define the API surface, core logic boundaries, and platform choices (language, framework, runtime). Provide recommended defaults and alternatives with pros/cons. ## Inputs (authoritative order) 1. `docs/architecture.packet.json` 2. `docs/architecture.handoff.backend.md` 3. `docs/story-map.json` and `docs/prd.packet.json` (fallback) If required inputs are missing, ask targeted questions and proceed with clearly labeled TBDs. ## Output Files (write under `docs/`) - `docs/backend.design.packet.json` (authoritative) - `docs/backend.design.md` (derived summary) ## Required Decisions - **Language + framework**: recommend and justify (e.g., Python + FastAPI vs Django; Node + NestJS; Go). - **API style**: REST vs GraphQL vs RPC (aligned with frontend and architecture). - **Core logic boundaries**: domain services/modules and responsibilities. - **Authn/Authz**: JWT/session/OAuth/SSO; role/permission model. - **Data access strategy**: integrate with chosen database (SQL vs NoSQL; Firestore vs Supabase where relevant). - **Error handling, retries, observability**: define expected behaviors. ## Relentless Clarification (Always Use) Proactively ask questions whenever a decision affects APIs, data access, auth, or reliability. Do not rely on implicit assumptions. Offer up to 3 options with pros/cons and ask the user to choose. Continue until the plan leaves no open decisions. Example format: 1) **Question**: (precise decision) 2) **Options**: - Option A: pros/cons - Option B: pros/cons 3) **Ask**: "Which option should I proceed with?" ## Sync Rules - Backend defines the **canonical API contract** unless explicitly delegated. - Record any API mismatches or unclear data dependencies for the Design Synchronizer. - Preserve traceability to story IDs and FR/NFR IDs.
Related Skills
backend-patterns
Backend patterns for ORPC routers, Drizzle schemas, and server-side code. Use when creating API endpoints, database tables, or services.
backend-passport-js
Authentication middleware for Express.js and Node.js applications. Use when building Express APIs that need JWT authentication, OAuth, or custom auth strategies. Provides 500+ authentication strategies. Choose Passport.js over Auth.js for Express backends, pure API servers, or when you need maximum control over auth flow.
backend-nodejs
Node.js/TypeScript backend expert. Handles Express/Fastify API routes, TypeScript strict mode, Prisma ORM, Zod validation, error handling, configuration management. Use when project is Node.js backend (package.json + TypeScript server).
Backend Node.js Expert
专注于 Node.js 后端开发模式与最佳实践。
Backend Migrations
Create and manage database schema migrations with reversible operations, zero-downtime deployments, and safe rollback strategies. Use this skill when writing database migrations for PostgreSQL, MySQL, SQLite, MongoDB, or any database system; when using ORMs like Prisma, Sequelize, TypeORM, ActiveRecord, Django ORM, or similar migration tools; when implementing schema changes (adding tables, columns, indexes, constraints); when performing data migrations or transformations; when creating indexes on large tables with concurrent options to avoid locks; when separating schema changes from data migrations for safer rollbacks; when implementing zero-downtime deployment strategies for high-availability systems; when versioning database schemas and managing migration order; or when working with database change management in production environments.
backend
Skill para diseñar y construir backends y APIs **modulares**, **auditables**, **resilientes** y **multi-tenant**, con seguridad fuerte, modelado correcto (incl. ledger cuando aplique), datos y jobs/colas operables.
backend-guidelines
Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.
backend-guide
Complete backend development guide covering Node.js, Python, Go, Java, PHP, databases, APIs, authentication, and server architecture. Use when building server applications, APIs, or backend systems.
Backend Expert Pro
A complete back-end specialist skill for designing scalable architectures, robust APIs, and secure server-side systems.
backend-expert-advisor
Backend expert guidance for API/DB/Security/Architecture
backend-development
Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance. Use when: the task directly matches tdd orchestrator responsibilities within plugin backend-development. Do not use when: a more specific framework or task-focused skill is clearly a better match.