Backend Design Skill
This skill guides the design of reliable backend systems, APIs, and data models with clear trade-offs, strong correctness guarantees, and operational readiness.
Design Thinking
- Scope: Identify core use cases, data flows, and integration points.
- Constraints: Latency, throughput, availability, compliance, and deployment limits.
- Data: Define entities, relationships, invariants, and lifecycle.
- Reliability: Error handling, retries, idempotency, and consistency model.
Architecture Guidelines
- API Design: Explicit contracts, versioning, validation, and error shape.
- Storage: Choose stores based on access patterns and durability needs.
- Performance: Indexing, caching, batching, and async processing.
- Security: AuthN/AuthZ, least privilege, secrets handling, auditability.
- Observability: Logging, metrics, tracing, and alerting signals.
- Scalability: Stateless services where possible, clear scaling boundaries.
Output Requirements
Provide a clear backend plan or implementation that includes:
- Data model and key invariants
- API endpoints or service interfaces
- Failure modes and recovery strategy
- Performance and scaling considerations
- Security and observability notes
Response Checklist
Backend Design Checklist
- [ ] Confirm requirements and constraints
- [ ] Define data model and invariants
- [ ] Specify API contracts and error shape
- [ ] Address failure modes and consistency
- [ ] Cover performance, scaling, and caching
- [ ] Include security and observability plans
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: backend-design-33description: Design robust backend systems and APIs. Use when users ask to plan or implement services, data models, or integrations. Use when this capability is needed.4---56# Backend Design Skill78This skill guides the design of reliable backend systems, APIs, and data models with clear trade-offs, strong correctness guarantees, and operational readiness.910## Design Thinking1112- **Scope**: Identify core use cases, data flows, and integration points.13- **Constraints**: Latency, throughput, availability, compliance, and deployment limits.14- **Data**: Define entities, relationships, invariants, and lifecycle.15- **Reliability**: Error handling, retries, idempotency, and consistency model.1617## Architecture Guidelines1819- **API Design**: Explicit contracts, versioning, validation, and error shape.20- **Storage**: Choose stores based on access patterns and durability needs.21- **Performance**: Indexing, caching, batching, and async processing.22- **Security**: AuthN/AuthZ, least privilege, secrets handling, auditability.23- **Observability**: Logging, metrics, tracing, and alerting signals.24- **Scalability**: Stateless services where possible, clear scaling boundaries.2526## Output Requirements2728Provide a clear backend plan or implementation that includes:2930- Data model and key invariants31- API endpoints or service interfaces32- Failure modes and recovery strategy33- Performance and scaling considerations34- Security and observability notes3536## Response Checklist3738```markdown39Backend Design Checklist4041- [ ] Confirm requirements and constraints42- [ ] Define data model and invariants43- [ ] Specify API contracts and error shape44- [ ] Address failure modes and consistency45- [ ] Cover performance, scaling, and caching46- [ ] Include security and observability plans47```4849---50> Converted and distributed by [TomeVault](https://tomevault.io/claim/nicholasgriffintn) — claim your Tome and manage your conversions.51<!-- tomevault:4.0:skill_md:2026-04-13 -->
tomevault-io