error-boundaries

error-boundaries is a cursor rule for Cursor from GoranErhartic/cursor-development-rules. It costs 23 tokens per session (597 once invoked), scanned A, original, MIT.

Guidelines for React Error Boundaries, which catch rendering errors in part of a component tree and show fallback content instead. They cover class-based boundaries, error logging, and placing boundaries around smaller sections.

In plain words
What is it for?
Use them when adding fallback screens and error reporting around React pages or components.
Why use it?
They stop one rendering failure from leaving the affected part of the interface without a usable fallback.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/goranerhartic/cursor-development-rules/error-boundaries
Clone the repo
git clone --depth 1 https://github.com/GoranErhartic/cursor-development-rules

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for error-boundaries

README.md
[![agentmods](https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/error-boundaries.svg)](https://agentmods.dev/rules/goranerhartic/cursor-development-rules/error-boundaries)
Your own site
<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/error-boundaries"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/error-boundaries.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 597 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00597
Opus 5 $0.00012 $0.00298
Sonnet 5 $0.00005 $0.00119
Haiku 4.5 $0.00002 $0.00060

Measured yesterday against content hash 12a72fe7b72f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

error-boundaries scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/languages/react/error-boundaries.mdc · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Error Boundaries

Error Boundaries catch JavaScript errors in the component tree and display a fallback UI. They do not catch errors in event handlers, async code, or server-side rendering. Use class components (no hook equivalent).

Basic Error Boundary

import React, { Component, ErrorInfo, ReactNode } from 'react';

interface ErrorBoundaryProps {
  children: ReactNode;
  fallback?: ReactNode;
  onError?: (error: Error, errorInfo: ErrorInfo) => void;
}

interface ErrorBoundaryState {
  hasError: boolean;
  error: Error | null;
}

export class ErrorBoundary extends Component<ErrorBoundaryProps, ErrorBoundaryState> {
  constructor(props: ErrorBoundaryProps) {
    super(props);
    this.state = { hasError: false, error: null };
  }

  static getDerivedStateFromError(error: Error): ErrorBoundaryState {
    return { hasError: true, error };
  }

  componentDidCatch(error: Error, errorInfo: ErrorInfo) {
    console.error('Error caught by boundary:', error, errorInfo);
    this.props.onError?.(error, errorInfo);
  }

  render() {
    if (this.state.hasError) {
      return this.props.fallback || (
        <ErrorFallback error={this.state.error} reset={() => this.setState({ hasError: false, error: null })} />
      );
    }
    return this.props.children;
  }
}

Error Fallback Component

interface ErrorFallbackProps {
  error: Error | null;
  reset: () => void;
}

export function ErrorFallback({ error, reset }: ErrorFallbackProps) {
  return (
    <div className="error-fallback">
      <h2>Something went wrong</h2>
      <details>
        <summary>Error details</summary>
        <pre>{error?.message}</pre>
        {import.meta.env.DEV && <pre>{error?.stack}</pre>}
      </details>
      <button onClick={reset}>Try again</button>
    </div>
  );
}

Granular Error Boundaries

Place boundaries around route segments or features so one failure does not take down the whole app.

function App() {
  return (
    <ErrorBoundary fallback={<FullPageError />}>
      <Header />
      <ErrorBoundary fallback={<SidebarError />}>
        <Sidebar />
      </ErrorBoundary>
      <main>
        <ErrorBoundary fallback={<ContentError />}>
          <Outlet />
        </ErrorBoundary>
      </main>
      <Footer />
    </ErrorBoundary>
  );
}

Read the full file on GitHub · 98 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 98 lines · 23 tokens per session scan A 12a72fe7b72f

Subscribe to this mod's changes

error-boundaries is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 597 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.