API Design Spec

Designs a clean, consistent API with the contract written out.

Updated Jun 14, 2026

Why it works: Working through resources, endpoints, errors, and cross-cutting concerns in that order mirrors how real API specs get written, and asking for the reasoning behind two decisions keeps trade-offs visible instead of buried.

💡 The original prompt — works in any model. Start here, then tune per model.

Fill in the blanks — your answers carry across every model

Requirementse.g. let users create, update, and cancel appointments, with reminders sent 24h before · sync inventory counts across warehouses in near real-timeContexte.g. internal mobile app + web dashboard, ~50 req/s peak, OAuth2 service-to-service · public third-party developers, rate-limited, must version cleanly

fill the blanks above ↑

🔀 Remix this prompt — make it yoursremixes credit the lineage & grow your garden

← NeLocker vault

API Design Spec

Designs a clean, consistent API with the contract written out.

Updated Jun 14, 2026

💡 The original prompt — works in any model. Start here, then tune per model.

Fill in the blanks — your answers carry across every model

fill the blanks above ↑

🔀 Remix this prompt — make it yoursremixes credit the lineage & grow your garden