error-boundary-creator — Claude Code skill: what it does and install
error-boundary-creator sets up error boundaries, fallback UIs, and crash reporting for React and Next.js apps. Keeps uncaught component crashes from breaking the entire page.
MIT 316 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill error-boundary-creator -a claude-codeWhat error-boundary-creator does
This skill guides coding agents through error isolation patterns across React and Next.js App Router projects. It provides instructions for standard class boundaries as well as setups based on react-error-boundary. For Next.js, it creates route segment files like error.tsx, global-error.tsx, and not-found.tsx.
Standard React boundaries miss unhandled promise rejections and event handler exceptions. To fix this, the skill pairs boundaries with a useAsync hook and a central reportError integration. Generated fallback views apply accessibility markup like role="alert" alongside reset or retry actions.
Component isolation is best placed at route levels and around flaky third-party widgets, while caught failures should go straight to your monitoring sink.
What it helps with
- scaffold
error.tsxandglobal-error.tsxsegments in Next.js App Router - wrap third-party widgets with
react-error-boundary - catch unhandled async errors and promise rejections with
useAsync - build accessible fallback views with
role="alert"and reset actions
Example prompts for the agent
- Generate an
error.tsxboundary with a retry button for the dashboard route - Wrap our checkout widget in
react-error-boundaryand send failures to our error sink - Handle promise rejections in our data form using the
useAsyncpattern
How to install error-boundary-creator
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill error-boundary-creator -a claude-code2Manually: put the files in place
~/.claude/skills/error-boundary-creator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/error-boundary-creator/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill error-boundary-creator -a codex2Manually: put the files in place
.agents/skills/error-boundary-creator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill error-boundary-creator -a cursor2Manually: put the files in place
.cursor/skills/error-boundary-creator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills error-boundary-creator2Manually: put the files in place
.github/skills/error-boundary-creator/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill error-boundary-creator -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path error-boundary-creatorManually: put the files in place
.devin/skills/error-boundary-creator/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill error-boundary-creator -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about error-boundary-creator
How do I install error-boundary-creator in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill error-boundary-creator -a claude-code in your terminal.
What does error-boundary-creator do?
It provides patterns for React and Next.js error isolation, route-level fallback screens, and crash reporting integration.
Does it handle errors inside event handlers and promises?
React boundaries do not catch asynchronous failures by default, so this skill introduces a useAsync hook and reportError module to handle them.
Source text
SKILL.md · MIT
--- name: error-boundary-creator description: Create error boundaries, error handling, and fallback UIs for React applications. Use when implementing error handling, creating fallback components, or setting up error reporting. --- # Error Boundary Creator Add resilient error handling to React and Next.js apps: error boundaries, fallback UIs, async error handling, and error reporting. ## Workflow 1. Identify error-prone areas: async operations, third-party integrations, and route-level entry points. 2. Wrap components in an error boundary. Use a class boundary or the `react-error-boundary` library. See references/class-boundaries.md. 3. For Next.js App Router, add the relevant `error.tsx`, `global-error.tsx`, and `not-found.tsx` segment files. See references/nextjs-error-handling.md. 4. Handle errors that boundaries miss (event handlers, promises) and wire up reporting. See references/async-and-reporting.md. 5. Design fallback UIs with `role="alert"` and a recovery action (reset or reload). 6. Route caught errors to a single reporting sink and test error states before shipping. ## Contents - references/class-boundaries.md — Basic, resettable, and `react-error-boundary` patterns. - references/nextjs-error-handling.md — App Router `error.tsx`, `global-error.tsx`, `not-found.tsx`. - references/async-and-reporting.md — `useAsync` hook and the `reportError` integration module. ## Best Practices 1. Wrap at the route level for page-level isolation, and wrap third-party components separately. 2. Provide meaningful fallbacks with a recovery option. 3. Log every caught error to the monitoring service. 4. Do not catch errors the code cannot meaningfully handle. 5. Test error states in development.
© OneWave-AI · MIT · OneWave-AI/claude-skills