PromptVaultDefinition of done for a new authenticated endpoint
For engineers implementing small APIs; returns a proof-based completion checklist.
Works with
- Codex
- GitHub Copilot
- Ollama
The prompt45 words · 2 blanks
What you fill in
- Endpoint exposure
[endpoint_exposure]ExamplePublic partner API - Authentication model
[auth_model]ExampleOAuth bearer token
How to use it
- 1Open it in PromptVault. Find it in Coding, or search for “Definition of done for a new authenticated endpoint”.
- 2Fill in the 2 blanks. endpoint exposure and authentication model — the only things the prompt cannot know.
- 3Copy and paste it into GitHub Copilot. It also works with Codex and Ollama.
About this prompt
“Definition of done for a new authenticated endpoint” is a beginner coding prompt. For engineers implementing small APIs; returns a proof-based completion checklist. It is 45 words long and written to get a usable answer on the first message, in Codex, GitHub Copilot and Ollama or any other chat assistant. Good for: checklist, api design, security, testing and first draft. Like every prompt in PromptVault, it was written and edited in-house, and it works offline once the app is installed.
More coding prompts
All 120 in Coding
Defensive decoding for an unstable external payloadFor integration engineers who need typed boundary code that fails with useful context.- Sensitive fields stay out of application logsFor engineers adding a reusable redaction boundary to an existing logging path.
- A manual smoke test from a feature briefFor developers who need a compact, repeatable check before handing a feature to QA.
- Hardened CI for untrusted pull requestsFor maintainers needing a ready-to-run workflow that limits token and secret exposure.
- Property-based tests shaped around real invariantsFor engineers turning domain rules into cases that shrink to useful counterexamples.
- A load test that fails on latency and error regressionsFor engineers checking an endpoint under pressure; returns one runnable repository-native script.