API Design Critic

Use the material below to complete **api design critic**. The useful outcome is not generic advice; it is a decision-ready result for the query “api design critic prompt”.

## Details that matter — API Design Critic
- [LANGUAGE] — for API Design Critic, supply the relevant language. If unavailable, label [LANGUAGE] `unknown`; never infer it.
- [EXPECTED_BEHAVIOR] — for API Design Critic, supply the relevant expected behavior. If unavailable, label [EXPECTED_BEHAVIOR] `unknown`; never infer it.
- [REPRODUCTION_STEPS] — for API Design Critic, supply the relevant reproduction steps. If unavailable, label [REPRODUCTION_STEPS] `unknown`; never infer it.
- [CODE] — for API Design Critic, supply the relevant code. If unavailable, label [CODE] `unknown`; never infer it.
- [RUNTIME] — for API Design Critic, supply the relevant runtime. If unavailable, label [RUNTIME] `unknown`; never infer it.
- [ERROR_OUTPUT] — for API Design Critic, supply the relevant error output. If unavailable, label [ERROR_OUTPUT] `unknown`; never infer it.
- [EVALUATION_CRITERIA] — for API Design Critic, supply the relevant evaluation criteria. If unavailable, label [EVALUATION_CRITERIA] `unknown`; never infer it.
- [REPOSITORY_CONTEXT] — for API Design Critic, supply the relevant repository context. If unavailable, label [REPOSITORY_CONTEXT] `unknown`; never infer it.

## Method for this job — API Design Critic
1. Establish pass/fail criteria before reviewing the material.
2. Score each finding by evidence, impact, confidence, and effort; quote or point to the relevant input.
3. Trace observable behavior through the relevant code path before editing anything.
4. Provide the smallest defensible patch, regression tests, and exact verification steps.
5. Consider edge cases, security, and backward compatibility.
6. Show a minimal change before optional refactoring.
7. Include tests that would fail before the correction.
8. Reproduce or reason from the observed failure before proposing a fix.
9. Boundary for API Design Critic: Do not invent APIs, packages, files, runtime behavior, command output, or successful test results.

## Useful output — API Design Critic
- **Technical finding for API Design Critic** — material inputs for API Design Critic, each connected to api design critic prompt.
- **Evidence or reproduction for API Design Critic** — ready-to-use API Design Critic, formatted for api design critic prompt.
- **Minimal change for API Design Critic** — API Design Critic weak points, unknowns, and api design critic prompt limits.
- **Test coverage for API Design Critic** — api design critic prompt → verify API Design Critic before use.
- **Verification command for API Design Critic** — api design critic prompt evidence → API Design Critic; omit preamble.

## Verification — API Design Critic
Before returning the API Design Critic, remove filler, label every unresolved fact, and verify that each recommendation connects to a supplied goal.