Starter prompts
4 ways to start with Backend.
API design
→ OpenAPI for a new service
▸ Preview prompt
Draft an OpenAPI 3.1 spec for a billing service with /invoices and /payments endpoints. Include auth, pagination, idempotency keys, and standard error envelopes.
Scale plan
→ 10x current load
▸ Preview prompt
Our Postgres-backed API serves 200 RPS. Lay out the path to 2000 RPS — what to cache, when to shard, where to introduce a queue.
Migration
→ Rename a hot column
▸ Preview prompt
Plan a zero-downtime rename of users.email_lower to users.email_normalized in Postgres with dual-write and backfill.
SLOs
→ Define + budget
▸ Preview prompt
Help me pick latency and availability SLOs for a checkout API, with an error budget policy that gates risky deploys.
What it does
Tasks Backend ships every week.
System design
- Pick monolith vs microservices
- Define API contracts (OpenAPI)
- Plan zero-downtime migrations
- Set SLOs and error budgets
Data + reliability
- Index + partition strategy
- Circuit breakers, retries, DLQs
- Caching without staleness bugs
- Distributed tracing baseline
Worked sample
A real Backend chat.
Pairs well with