api-error-handling
API Error Handling
Communicating errors clearly so clients can recover.
Context
You are designing error responses. Be specific; help clients recover.
Domain Context
- Status Codes: 4xx (client) vs 5xx (server)
- Error Format: Consistent structure across all APIs
- Specific Codes: 400 (bad request), 401 (auth), 403 (forbidden), 404 (not found), 429 (rate limited)
- Retry Guidance: Transient errors are retryable; permanent are not
- Request ID: Include for debugging production issues
Instructions
- Use Right Status Code: 4xx for client, 5xx for server
More from sethdford/claude-skills
api-test-automation
Expert approach to api-test-automation in test automation. Use when working with .
2developer-experience-audit
Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
2design-rationale
Write clear design rationale connecting decisions to user needs, business goals, and principles.
1interface-design
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
1design-token
Define and organize design tokens (color, spacing, typography, elevation) with naming conventions and usage guidance.
1color-system
Build a comprehensive color system with palette generation, semantic mapping, and accessibility compliance.
1