error-handling

A rule for handling loading screens and errors in Next.js pages that fetch data. Next.js is a web framework, and its loading and error files control what users see while a page loads or fails.

In plain words
What is it for?
Use it when adding or reviewing pages in the app router that fetch data, including their required loading.tsx and client-side error.tsx files.
Why use it?
It ensures data-fetching pages provide a visible loading state and a recoverable error boundary instead of exposing internal errors or leaving users without feedback.

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/vibestackdev/vibe-stack/error-handling
Clone the repo
git clone --depth 1 https://github.com/vibestackdev/vibe-stack

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 899 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.00000 $0.00899
Opus 5 $0.00000 $0.00449
Sonnet 5 $0.00000 $0.00180
Haiku 4.5 $0.00000 $0.00090

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

Security

Grade A, and why

error-handling 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/error-handling.mdc · 136 lines

How it starts

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

Error Handling and Loading States

RULE 1: Every Data-Fetching Page Needs Sibling Files

EVERY page in app/ router that does data fetching MUST have:

  • loading.tsx (Suspense boundary — shown during streaming)
  • error.tsx (Error boundary — must be 'use client')

loading.tsx template:

export default function Loading() {
  return (
    <div className="flex items-center justify-center min-h-[200px]">
      <div className="animate-spin rounded-full h-8 w-8 border-b-2 border-primary" />
    </div>
  )
}

error.tsx template:

'use client'

export default function Error({ 
  error, 
  reset 
}: { 
  error: Error & { digest?: string }
  reset: () => void 
}) {
  return (
    <div className="flex flex-col items-center justify-center min-h-[200px] gap-4">
      <h2 className="text-xl font-semibold">Something went wrong</h2>
      <p className="text-muted-foreground">An unexpected error occurred.</p>
      <button 
        onClick={reset}
        className="px-4 py-2 bg-primary text-primary-foreground rounded-md"
      >
        Try again
      </button>
    </div>
  )
}

RULE 2: NEVER Expose Internal Errors to Clients

Server errors, database errors, and stack traces MUST stay server-side. Return generic messages to the client. Log the real error.

✅ CORRECT:

try {
  const { data, error } = await supabase.from('posts').select()
  if (error) throw error
  return data
} catch (error) {
  console.error('[POSTS_FETCH_ERROR]', error) // Detailed log server-side
  return NextResponse.json(
    { error: 'Failed to fetch posts' }, // Generic message to client
    { status: 500 }
  )
}

❌ WRONG:

} catch (error) {
  return NextResponse.json(
    { error: error.message }, // Leaks: "relation 'posts' does not exist"
    { status: 500 }
  )
}

RULE 3: Use ActionResponse for All Server Actions

Every Server Action MUST return a typed response — never throw.

type ActionResponse<T = void> = 
  | { success: true; data: T }
  | { success: false; error: string }

// Usage:
export async function createPost(input: unknown): Promise<ActionResponse<Post>> {
  const supabase = await createClient()
  const { data: { user } } = await supabase.auth.getUser()
  if (!user) return { success: false, error: 'Unauthorized' }

  const parsed = PostSchema.safeParse(input)
  if (!parsed.success) return { success: false, error: 'Invalid input' }

  const { data, error } = await supabase
    .from('posts')
    .insert({ ...parsed.data, user_id: user.id })
    .select()
    .single()

  if (error) {
    console.error('[CREATE_POST_ERROR]', error)
    return { success: false, error: 'Failed to create post' }
  }

  revalidatePath('/dashboard')
  return { success: true, data }
}

Read the full file on GitHub · 136 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 · 136 lines · 0 tokens per session scan A 849ac3029c4d

Subscribe to this mod's changes

error-handling is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 899 tokens. 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-08-31.