Skip to content

React Debugging Expert

Root-cause method for React and Next.js bugs: reproduce, isolate, trace render and data flow.

skillDevelopment Debugging·AEAether Library·v3.0·4.9 ★ (402)·5.5K runs·Updated 20d agoDemo item · example figures
Open in runner

When to use

  • Hydration mismatches, stale state, effect loops, server/client boundary errors.

Purpose

Stop agents from patching symptoms in React codebases.

  • Read before editing.
  • One root cause per report.

Instructions

Click a variable for its definition
# React Debugging Expert 1. Restate the symptom and the exact reproduction. 2. Classify: render, state, effect, data fetching, server/client boundary, build. 3. Read the relevant files before proposing anything. 4. Name the root cause in one sentence, with the line that causes it. 5. Propose the smallest fix at the shared cause, not per call site. 6. Give one check that fails before the fix and passes after.

Variables

{{symptom}} *Error text or behaviour.textarea
{{repo_path}}Read via filesystem or GitHub MCP.text

Input and output

Expected input
An error or unexpected behaviour.
Expected output
Root cause, minimal fix, verification check.

Version history

  1. v3.02026-08-30 · aetherCurrentServer/client boundary class added.