exception-taxonomy
This approach standardizes API error responses by mapping HTTP status codes to machine-readable error codes.
Install
mkdir -p .claude/skills/exception-taxonomy && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5546" && unzip -o skill.zip -d .claude/skills/exception-taxonomy && rm skill.zipInstalls to .claude/skills/exception-taxonomy
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Hierarchical exception system with HTTP status codes, machine-readable error codes, and structured responses for consistent API error handling across all endpoints.Key capabilities
- →Define hierarchical exception structures
- →Map internal errors to HTTP status codes
- →Generate machine-readable error codes for clients
- →Include retry hints for transient failures
- →Standardize error response formats
How it works
It uses a base exception class to enforce a consistent schema for error messages, status codes, and metadata across different application layers.
Inputs & outputs
When to use exception-taxonomy
- →Create consistent API error responses
- →Map internal exceptions to HTTP status codes
- →Standardize error messages for frontend consumption
About exception-taxonomy
Defines a structured approach to error management, ensuring that all API responses follow a uniform pattern. It includes mappings for HTTP status codes and machine-readable error codes to improve reliability.
Hierarchical exception system with HTTP status codes, machine-readable error codes, and structured responses for consistent API error handling across all endpoints.
When not to use it
- →When building simple scripts that do not require structured API error handling
Limitations
- →Requires consistent adoption across all API endpoints
- →Must be manually integrated into existing exception handling logic
How it compares
It replaces ad-hoc error handling with a centralized, type-safe taxonomy that simplifies client-side error parsing.
Compared to similar skills
exception-taxonomy side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| exception-taxonomy (this skill) | 1 | 6mo | No flags | Intermediate |
| salesforce-development | 14 | 6mo | No flags | Advanced |
| woocommerce-code-review | 6 | 3mo | No flags | Intermediate |
| woocommerce-backend-dev | 7 | 3mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by dadbodgeoff
View all by dadbodgeoff →You might also like
salesforce-development
davila7
Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, Connected Apps, and Salesforce DX with scratch orgs and 2nd generation packages (2GP). Use when: salesforce, sfdc, apex, lwc, lightning web components.
woocommerce-code-review
woocommerce
Review WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
woocommerce-backend-dev
woocommerce
Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.**
woocommerce-dev-cycle
woocommerce
Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.
golang
MadAppGang
Use when building Go backend services, implementing goroutines/channels, handling errors idiomatically, writing tests with testify, or following Go best practices for APIs/CLI tools.
convex-best-practices
waynesutton
Guidelines for building production-ready Convex apps covering function organization, query patterns, validation, TypeScript usage, error handling, and the Zen of Convex design philosophy