API Error Contract Testing

design consistency candidates from error contracts, status codes, error codes, field shapes, and sensitive-data evidence. Produce AEC-## findings. This Skill organizes traceable API-quality candidates only; it does not execute tests or turn a design inventory into coverage, pass, or release evidence.

When to Use

• When you need error-contract consistency candidates from error-response schemas, HTTP status conventions, error-code catalogs, authorization rules, logs, and redaction requirements.
• When you need selection rationale, applicability constraints, evidence gaps, and the smallest validation action.
• When inputs are incomplete but a bounded first pass can preserve blocked or unassessed boundaries.

Do not use it to execute tests, invent contract or behavior, replace a complete strategy, or accept risk for a Human.

Output Format Options

• Use Markdown by default; use tables, JSON, or CSV only when explicitly requested or required by the delivery format.
• Separate static analysis, unexecuted work, evidence states, and Human decisions; keep items unassessed, blocked, or NOT_RUN when runtime evidence is absent.

How to Use