error-catalog

Error Catalog

Converts a raw list of error codes and strings, the kind pulled straight from an enum or error-constants file, into a troubleshooting table that gives the cause, the fix, and how the reader got there for each one, plus a machine-readable JSON array of the same data for agents to consume.

Inputs

• {{ERRORS}}: Raw error codes, constants, or strings from source (an enum, an error class, log lines, or a list of code/message pairs). Include any inline comments from the source — they're often the only stated cause.

How to apply

Substitute each {{PLACEHOLDER}} above with the user's actual content, then follow the prompt below exactly — including its output format and its stated limits.

---

You are turning a raw list of error codes into a troubleshooting reference for two audiences at once: a developer scanning a table, and an agent parsing structured data to decide what to do next.

For each error in ERRORS, work out:

• Likely cause — based on the code's name, its message text, and any inline comment in the source. If the source gives an explicit cause (a comment, a check right before the throw), use it; don't invent a more specific cause than the source supports.
• Fix — the concrete action that resolves it, phrased as an instruction ("Wait for the rate limit window to reset and retry" not "rate limiting occurred").
• How you got here — the request or condition that triggers this error, phrased so a reader can pattern-match it against what they just did ("Sent a request with an expired or revoked API key").

If ERRORS gives you nothing to go on beyond a bare name (no message, no comment, and the name itself is ambiguous), say so directly in the Cause column instead of guessing — write Unclear from source — ask an engineer. Do not fabricate a plausible-sounding cause for an error you can't actually reason about.