API Error Response Designer

Use your real inputs to develop api error response designer while keeping facts, assumptions, decisions, and remaining questions clearly separated. It helps...

Prompt

Develop **api error response designer** in a way another person can review and use. Ground the response to “api error response design prompt” in provided facts, and make uncertainty visible rather than smoothing it over.

## Evidence and constraints — API Error Response Designer
- [REPRODUCTION_STEPS] — for API Error Response Designer, supply the relevant reproduction steps. If unavailable, label [REPRODUCTION_STEPS] `unknown`; never infer it.
- [CODE] — for API Error Response Designer, supply the relevant code. If unavailable, label [CODE] `unknown`; never infer it.
- [RUNTIME] — for API Error Response Designer, supply the relevant runtime. If unavailable, label [RUNTIME] `unknown`; never infer it.
- [ERROR_OUTPUT] — for API Error Response Designer, supply the relevant error output. If unavailable, label [ERROR_OUTPUT] `unknown`; never infer it.
- [TESTS] — for API Error Response Designer, supply the relevant tests. If unavailable, label [TESTS] `unknown`; never infer it.
- [FRAMEWORK] — for API Error Response Designer, supply the relevant framework. If unavailable, label [FRAMEWORK] `unknown`; never infer it.
- [REPOSITORY_CONTEXT] — for API Error Response Designer, supply the relevant repository context. If unavailable, label [REPOSITORY_CONTEXT] `unknown`; never infer it.

## Reasoning route — API Error Response Designer
1. Trace observable behavior through the relevant code path before editing anything.
2. Provide the smallest defensible patch, regression tests, and exact verification steps.
3. Reproduce or reason from the observed failure before proposing a fix.
4. Identify the smallest causal code path.
5. Separate confirmed behavior from hypotheses.
6. Consider edge cases, security, and backward compatibility.
7. Boundary for API Error Response Designer: Do not invent APIs, packages, files, runtime behavior, command output, or successful test results.

## Response format — API Error Response Designer
- **Technical finding for API Error Response Designer** — ready-to-use API Error Response Designer, formatted for api error response design prompt.
- **Evidence or reproduction for API Error Response Designer** — API Error Response Designer weak points, unknowns, and api error response design prompt limits.
- **Minimal change for API Error Response Designer** — api error response design prompt → verify API Error Response Designer before use.
- **Test coverage for API Error Response Designer** — api error response design prompt evidence → API Error Response Designer; omit preamble.
- **Verification command for API Error Response Designer** — material inputs for API Error Response Designer, each connected to api error response design prompt.

## Acceptance test — API Error Response Designer
Audit the final API Error Response Designer against the original request. If an essential input is absent, say exactly how that limits the result.

How to use this prompt

Replace only the bracketed fields relevant to your situation. Keep unknown information marked as unknown, paste the completed prompt into a capable AI assistant, and review the result before using it.

Best AI model

ChatGPT • Gemini • capable reasoning assistants

Related prompts

Coding Workflow

API Design Critic

Turn api design critic into a usable result with focused inputs, task-specific guidance, clear constraints,...

Ready for ChatGPT Gemini

View Workflow
Coding Workflow

API Documentation Writer

A focused prompt for api documentation writer, designed to organize real context, prevent unsupported claim...

Ready for ChatGPT Gemini

View Workflow
Coding Workflow

Type Error Debugging Assistant

A focused prompt for type error debugging assistant, designed to organize real context, prevent unsupported...

Ready for ChatGPT Gemini

View Workflow