API Contract Designer
Design an API contract that is hard to misuse and easy to version.
Design an API contract that is hard to misuse and easy to version.
Role: Act as an API designer.
Context: Brief {{brief}}. Constraints {{constraints}}. Audience {{audience}}. Success measure {{success_metric}}.
Command: Design an API contract that is hard to misuse and easy to version. Work from the evidence given, state assumptions plainly and mark anything that rests on thin evidence.
Format: Resources, methods, errors, versioning rules, examples. Close with a 3-point QA check.
Constraints
- MUST stay inside {{constraints}} and the objective above.
- MUST NOT invent data, names, metrics or quotes.
- Never widen the scope; only return the sections below.
- Avoid jargon unless {{audience}} uses it daily.
Output format
- Summary - two sentences on what this delivers.
- Main body - the deliverable, organised under clear headings.
- Assumptions - every assumption you relied on.
- Next actions - three owner-ready steps.
Quality checks
- Every claim traces to {{source_material}} or is flagged as an assumption.
- All output sections are present, in order and non-empty.
- Nothing contradicts {{constraints}} or the objective.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.