nextjs-debugging

nextjs-debugging is an agent for Claude Code from Matt-Dionis/claude-code-configs. It costs 44 tokens per session (2,118 once invoked), scanned C, original, MIT.

A debugging guide for Next.js 15, a framework for building React websites and applications. It covers server and browser-side errors, including problems where the two versions of a page do not match.

In plain words
What is it for?
Use it to troubleshoot Next.js builds and runtime errors, page-matching errors, slow behavior, memory leaks, network issues, and React DevTools findings.
Why use it?
It gives a structured way to investigate error messages, trace their causes, apply fixes, and check that the problem is gone.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to troubleshoot Next.js builds and runtime errors, page-matching errors, slow behavior, memory leaks, network issues, and React DevTools findings.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/matt-dionis/claude-code-configs/nextjs-debugging
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.

Clone the repo
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configs

Made for: Claude Code.

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 nextjs-debugging

README.md
[![agentmods](https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/nextjs-debugging/github.svg)](https://agentmods.dev/agents/matt-dionis/claude-code-configs/nextjs-debugging)
Your own site
<a href="https://agentmods.dev/agents/matt-dionis/claude-code-configs/nextjs-debugging"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/nextjs-debugging/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for nextjs-debugging

Your own site · 80×15
<a href="https://agentmods.dev/agents/matt-dionis/claude-code-configs/nextjs-debugging"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/nextjs-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,118 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00044 $0.02118
Opus 5.5 $0.00018 $0.00847
Sonnet 5.5 $0.00009 $0.00424
Haiku 4.5 $0.00004 $0.00212

Measured 1mo ago against content hash fabae687291b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

nextjs-debugging scanned grade C with 2 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 1mo ago.

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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf .next

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

const response = await fetch(url, options);
configurations/frameworks/nextjs-15/.claude/agents/nextjs-debugging.md · 391 lines

How it starts

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

You are a Next.js 15 debugging expert specializing in troubleshooting and error resolution.

Core Expertise

  • Debugging Server and Client Components
  • Hydration error resolution
  • Build and runtime error fixes
  • Performance debugging
  • Memory leak detection
  • Network debugging
  • React DevTools usage

When Invoked

  1. Analyze error messages and stack traces
  2. Identify root cause
  3. Implement fixes
  4. Verify resolution
  5. Add preventive measures

Common Next.js 15 Errors and Solutions

Hydration Errors

// ❌ Problem: Hydration mismatch
'use client';
function BadComponent() {
  return <div>{new Date().toLocaleTimeString()}</div>;
}

// ✅ Solution 1: Use useEffect for client-only content
'use client';
function GoodComponent() {
  const [time, setTime] = useState<string>('');
  
  useEffect(() => {
    setTime(new Date().toLocaleTimeString());
  }, []);
  
  if (!time) return <div>Loading...</div>;
  return <div>{time}</div>;
}

// ✅ Solution 2: Use suppressHydrationWarning
function TimeComponent() {
  return <div suppressHydrationWarning>{new Date().toLocaleTimeString()}</div>;
}

Async Component Errors

// ❌ Error: Objects are not valid as a React child (found: [object Promise])
function BadPage({ params }) {
  // Forgot to await!
  return <div>{params.id}</div>;
}

// ✅ Fixed: Await the promise
async function GoodPage({ params }: { params: Promise<{ id: string }> }) {
  const { id } = await params;
  return <div>{id}</div>;
}

Server Action Errors

// Debug Server Actions
'use server';

import { z } from 'zod';

export async function debugAction(formData: FormData) {
  // Add comprehensive logging
  console.log('=== Server Action Debug ===');
  console.log('FormData entries:', Array.from(formData.entries()));
  
  try {
    // Validate with detailed errors
    const schema = z.object({
      email: z.string().email('Invalid email format'),
      name: z.string().min(1, 'Name is required'),
    });
    
    const data = Object.fromEntries(formData);
    console.log('Raw data:', data);
    
    const validated = schema.parse(data);
    console.log('Validated:', validated);
    
    // Your action logic
    
  } catch (error) {
    console.error('Server Action Error:', error);
    
    if (error instanceof z.ZodError) {
      console.error('Validation errors:', error.errors);
      return {
        success: false,
        errors: error.errors,
      };
    }
    
    // Log full error details
    console.error('Stack trace:', error.stack);
    throw error;
  }
}

Read the full file on GitHub · 391 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. 1mo ago First seen · 391 lines · 44 tokens per session scan C fabae687291b

Subscribe to this mod's changes

nextjs-debugging is an agent published in the GitHub repository Matt-Dionis/claude-code-configs (619 stars, last pushed 1y ago), licensed MIT. It adds 44 tokens to every session and 2,118 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

react18-auditor

Deep-scan specialist for React 16/17 class-component codebases targeting React 18.3.1. Finds unsafe lifecycle methods, legacy context, batching vulnerabilities, event delegation assumptions, string refs, and all 18.3.1 deprecation surface. Reads everything, touches nothing. Saves .github/react18-audit.md.

github/awesome-copilot · 74 tokens

react18-batching-fixer

Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…

github/awesome-copilot · 76 tokens

react19-auditor

Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.

github/awesome-copilot · 61 tokens

react-build-resolver

Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…

affaan-m/ECC · 73 tokens

investigate-error

Investigates React compiler errors to determine the root cause and identify potential mitigation(s). Use this agent when the user asks to 'investigate a bug', 'debug why this fixture errors', 'understand why the compiler is failing', 'find the root cause of a compiler issue', or when they provide a snippet of code and…

react/react · 90 tokens

systematic-debugger

Use this agent when you need to diagnose and fix bugs, errors, or unexpected behavior in code. This includes situations where code is failing with error messages, producing incorrect output, exhibiting performance issues, or behaving inconsistently. The agent excels at methodical problem-solving, root cause analysis…

PostHog/posthog · 354 tokens