🗺️ Backend Engineering · Journey Playbooks
Playbook: Take payments without duplicates
Process money mutations with idempotency guarantees and clean audit trails.
journey~90 minBackend EngineersAPI DevelopersPlatform Engineers
Journey Steps
- 1Step 1 — Make writes safe with idempotency keys: start with "Require an Idempotency-Key header on POST payments, orders, and signups"
- 2Step 2 — Validate all external input at the boundary: start with "Define schemas per endpoint covering body, query, params, headers"
- 3Step 3 — Build trustworthy background job processing: start with "Make handlers idempotent; assume at-least-once delivery"
- 4How it fits together: Money endpoints get idempotency keys, validation schemas, and job-based side effects. No exceptions.
Commands
Install all referenced skills
$ npx skills add aniruddhaadak80/skills --skill api-design-idempotency-keys && npx skills add aniruddhaadak80/skills --skill auth-security-input-validation-zod && npx skills add aniruddhaadak80/skills --skill caching-queues-background-jobsTags
#playbook#journey#backend-engineering