Skip to content

proflead/codex-skills-library / skills/api/api-error-taxonomy

api-error-taxonomy

Unverified

Define 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

  1. List common error categories and HTTP mappings.
  2. Define error payload shape and fields.
  3. 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.
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 implementationStars: 318kUpdated Claude CodeCodexUnverifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexUnverifiedInstall
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 fallbackStars: 318kUpdated Claude CodeCodexUnverifiedInstall
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 alwaysStars: 318kUpdated Claude CodeCodexUnverifiedInstall