Next.js API Route Debugger skill for Claude and Codex
Gets a failing Next.js API route working again: ranks the likely causes behind the error message, tells you exactly what to log where, and hands you a fix you…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when a Next.js API route throws or returns the wrong thing and the error message needs tracing to a cause and a fix. Do not use for writing a new route from a spec or tuning a working route for performance. Related topics: coding, next.js.
What it will ask you for
- Route path (free text, e.g. "/api/example")
- HTTP method (choose one: GET, POST, PUT, DELETE, PATCH)
- Error message (longer free text)
- Route source (optional) (longer free text)
- Request body sample (longer free text)
- Expected response (longer free text)
- Environment (choose one: Development, Production)
How it works
- Parse the error name, the thing it names, and the top stack frame to locate the failing layer before proposing anything.
- Rank candidate causes by fit with the message, method, body sample, and environment, most likely first.
- Give each cause one confirming log line or curl command and where to place it.
- Write the corrected handler or exact line changes plus a guard against the same class of bug.
- Deliver the document with Problem Summary, Common Causes, Step-by-step Debugging Steps, Sample Fix Code, and Checklist in that order.
What you get
A markdown document with sections in this exact order: Problem Summary, Common Causes (ranked list), Step-by-step Debugging Steps, Sample Fix Code (fenced), Checklist.
What it watches out for
- Guessing a cause that contradicts the stack trace because it is the most common bug in general.
- Suggesting console.log of the whole request object, which prints secrets into production logs.
- Fixing the symptom with a null check and leaving the missing await that caused it.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.