Codex API scaffolder — REST endpoint from a plain-English spec

Paste into the Codex CLI or as a task in Cursor:

'Generate a complete, production-ready [LANGUAGE, e.g. TypeScript / Python] REST API endpoint with the following spec:

Endpoint: [METHOD] [PATH, e.g. POST /api/users/invite]
Purpose: [ONE SENTENCE — what this route does]
Request body: [DESCRIBE FIELDS, types, and which are required]
Auth: [Bearer token / API key / none — and what it should check]
Success response: [HTTP status + shape of the response JSON]
Error cases to handle: [e.g. duplicate email 409, invalid input 422, unauthorized 401]

Generate:
1. The route handler with input validation (use [zod / pydantic / joi] for schema enforcement)
2. Typed request/response interfaces
3. Inline error handling — no try/catch around the whole function; handle each error case explicitly
4. A brief JSDoc/docstring comment on the handler function
5. A cURL example showing a valid request and the expected 200 response

Style rules: [framework, e.g. Express / Fastify / Flask / Next.js API routes]. No placeholder comments. No TODO. The output must run without modification.'

Tip: paste your existing route file first and say 'following the patterns in this file, add:' — Codex will match your naming conventions, error format, and middleware usage exactly rather than introducing a new style.