Error Boundary Generator

Before generating any output, read config/defaults.md and adapt all patterns, imports, and code examples to the user's configured stack.

Process

1. Scan the React component tree and identify components that need error boundaries.
2. For each gap, generate an error boundary with a typed fallback component.
3. For Next.js App Router, generate error.tsx and loading.tsx files where missing.

Identification Rules

Scan for components that:

• Fetch data: contain fetch(), useQuery, useSWR, server component async functions, or Prisma calls
• Use external services: Stripe, auth providers, third-party SDKs
• Have complex state logic: useReducer with many cases, complex useEffect chains
• Render user-generated content: dangerouslySetInnerHTML, rich text renderers, markdown parsers
• Are page-level route components: page.tsx files in Next.js App Router