proflead/codex-skills-library / skills/api/api-error-taxonomy
api-error-taxonomy
UnverifiedDefine consistent API error codes and responses. Use when a mid-level developer needs error standardization.
API Error Taxonomy
Purpose
Define consistent API error codes and responses.
Inputs to request
- Current error responses and status usage.
- Client expectations for retries and messaging.
- Logging and observability requirements.
Workflow
- List common error categories and HTTP mappings.
- Define error payload shape and fields.
- Set guidelines for logging and client messaging.
Output
- Error taxonomy table and examples.
Quality bar
- Ensure errors are machine-parseable.
- Align retryable vs non-retryable semantics.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |