plugins/pokayokay/skills/error-handling/SKILL.md
Use when designing error hierarchies, implementing React error boundaries, adding retry logic or fallbacks, creating API error responses, integrating error tracking (Sentry), or improving user-facing error communication.
npx skillsauth add srstomp/pokayokay error-handlingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Design resilient applications through intentional error handling strategies. Errors are data, not just exceptions — design them intentionally.
| Situation | Pattern | Reference | |-----------|---------|-----------| | Typed error categories | Custom error classes | error-patterns.md | | Explicit handling (no throws) | Result/Either type | error-patterns.md | | React component crash | Error boundary | react-errors.md | | API error response | Structured API errors | api-errors.md | | Network calls that fail | Retry with backoff | recovery-patterns.md | | Unreliable downstream service | Circuit breaker | recovery-patterns.md |
| Reference | Description | |-----------|-------------| | error-patterns.md | Custom errors, Result types, error hierarchies | | react-errors.md | Error boundaries, Suspense, React error handling | | api-errors.md | HTTP errors, response shapes, status codes | | recovery-patterns.md | Retry, circuit breaker, fallbacks, degradation | | overview.md | Error types, Result pattern, user messages, tracking, anti-patterns | | anti-rationalization.md | Iron Law, common rationalizations, red flag STOP list for error handling discipline | | tdd-patterns.md | Test-first patterns for error paths, retry logic, boundaries | | review-checklist.md | Error handling review checklist (classes, messages, recovery, tracking) |
development
Git worktree management for isolated task development
development
Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
testing
Use before claiming work is done, fixed, passing, ready to commit, ready to PR, or ready to mark complete. Requires fresh verification evidence and explicit command output before success claims.
development
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.