What problem does it solve? A single render or lifecycle error in one React component can unmount and blank the entire application. This Skill provides a class-based ErrorBoundary component that catches errors in a subtree, renders a fallback UI, and offers a retry action so one broken feature does not take down the whole screen. ## Core Features & Use Cases - Class-based ErrorBoundary component: Uses getDerivedStateFromError for the fallback render and componentDidCatch for logging and error-tracker reporting, since no hook equivalent exists. - Placement guidance: Wrap independent feature sections (charts, widgets, routed pages) in their own boundaries in addition to a root-level catch-all. - Boundary limitations and retry semantics: Documents that boundaries do not catch errors in event handlers, async code, SSR, or their own render, and that retry must also clear or refetch the bad underlying state. - Use Case: A dashboard widget crashes due to malformed API data; its local boundary shows a "Try again" fallback while the rest of the page keeps working. ## Quick Start Add an error boundary around my React feature components so a render error shows a fallback with a retry button instead of blanking the app.
