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

Más de este repositorio

mismo repositorio

diagnose

nicholasgriffintn/machine-setup

Builds a fast feedback loop, reproduces the symptom, tests ranked hypotheses, instruments narrowly, fixes, and adds regression coverage. Use when the user says diagnose/debug, reports broken behaviour, failing checks, thrown errors, flaky bugs, or performance regressions.

2026-05-052

frontend-design

nicholasgriffintn/machine-setup

Create distinctive, production-grade frontend interfaces with high design quality. Use when users ask to build web components, pages, or applications.

2026-05-052

grill-with-docs

nicholasgriffintn/machine-setup

Stress-tests a plan against the existing domain language, code, and documented decisions, then updates CONTEXT.md or ADRs as decisions crystallise. Use when the user wants to be grilled on a design, validate a plan, sharpen terminology, or record the reasoning behind a decision.

2026-05-052

improve-codebase-architecture

nicholasgriffintn/machine-setup

Reviews a codebase for architectural friction and proposes deepening opportunities grounded in its domain language, tests, dependencies, and ADRs. Use when the user wants architecture review, refactoring candidates, better module shape, clearer seams, or a codebase that is easier to test and navigate.

2026-05-052

security-review

nicholasgriffintn/machine-setup

A specialist skill for security reviews, threat modeling, and remediation guidance. Use for auth/permissions changes, secrets or PII handling, public endpoints, or dependency upgrades.

2026-05-052

tdd

nicholasgriffintn/machine-setup

Drives changes through a strict red-green-refactor loop using behaviour tests at the public interface. Use when the user asks for TDD, test-first development, integration tests, regression coverage, or a feature built one vertical slice at a time.

2026-05-052

name	backend-design
description	Design robust backend systems and APIs. Use when users ask to plan or implement services, data models, or integrations.

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