nextjs-anti-patterns

nextjs-anti-patterns is a skill for Claude Code from wsimmonds/claude-nextjs-skills. It costs 97 tokens per session (5,354 once invoked), scanned A, original, MIT.

A guide for finding and correcting common mistakes in Next.js App Router code, the system used to build pages and routes in modern Next.js applications. It covers issues such as misplaced client logic, data loading, state, component boundaries, and TypeScript types.

In plain words
What is it for?
Use it during code reviews, performance debugging, App Router migrations, and checks for incorrect useEffect, data fetching, client state, component boundaries, or the TypeScript any type.
Why use it?
It helps prevent code patterns that can cause build failures, slow pages, or unnecessary browser-side work. It is also useful when updating code from the older Pages Router approach.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it during code reviews, performance debugging, App Router migrations, and checks for incorrect useEffect, data fetching, client state, component boundaries, or the TypeScript any type.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wsimmonds/claude-nextjs-skills/nextjs-anti-patterns
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.

Any agent
npx skills add wsimmonds/claude-nextjs-skills --skill nextjs-anti-patterns
Clone the repo
git clone --depth 1 https://github.com/wsimmonds/claude-nextjs-skills

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-anti-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/wsimmonds/claude-nextjs-skills/nextjs-anti-patterns/github.svg)](https://agentmods.dev/skills/wsimmonds/claude-nextjs-skills/nextjs-anti-patterns)
Your own site
<a href="https://agentmods.dev/skills/wsimmonds/claude-nextjs-skills/nextjs-anti-patterns"><img src="https://agentmods.dev/badge/skills/wsimmonds/claude-nextjs-skills/nextjs-anti-patterns/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-anti-patterns

Your own site · 80×15
<a href="https://agentmods.dev/skills/wsimmonds/claude-nextjs-skills/nextjs-anti-patterns"><img src="https://agentmods.dev/badge/skills/wsimmonds/claude-nextjs-skills/nextjs-anti-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,354 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00097 $0.05354
Opus 5 $0.00048 $0.02677
Sonnet 5 $0.00019 $0.01071
Haiku 4.5 $0.00010 $0.00535

Measured 10d ago against content hash de7cf7fa4e2c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

nextjs-anti-patterns 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 10d 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.

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.

nextjs-anti-patterns/SKILL.md · 945 lines

How it starts

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

Next.js Anti-Patterns

Overview

Identify and correct common anti-patterns in Next.js App Router applications, focusing on misuse of useEffect, improper data fetching, unnecessary client-side state, and incorrect component boundaries.

TypeScript: NEVER Use any Type

CRITICAL RULE: This codebase has @typescript-eslint/no-explicit-any enabled. Using any will cause build failures.

❌ WRONG:

function handleSubmit(e: any) { ... }
const data: any[] = [];

✅ CORRECT:

function handleSubmit(e: React.FormEvent<HTMLFormElement>) { ... }
const data: string[] = [];

Common Next.js Type Patterns

// Page props
function Page({ params }: { params: { slug: string } }) { ... }
function Page({ searchParams }: { searchParams: { [key: string]: string | string[] | undefined } }) { ... }

// Form events
const handleSubmit = (e: React.FormEvent<HTMLFormElement>) => { ... }
const handleChange = (e: React.ChangeEvent<HTMLInputElement>) => { ... }

// Server actions
async function myAction(formData: FormData) { ... }

When to Use This Skill

Use this skill when:

  • Reviewing Next.js code for best practices
  • Debugging performance issues in App Router apps
  • Migrating from Pages Router with legacy patterns
  • Code shows excessive client-side JavaScript
  • Components are using useEffect unnecessarily
  • Detecting waterfall data fetching patterns
  • Identifying incorrect Server/Client component usage

Rendering Responsibilities

When requirements call for a page or component to present specific UI (e.g., display a banner or guard message), place that rendering responsibility in the exported component that callers actually use. Helper components are fine, but make sure they are composed so the main entry point still outputs the expected elements.

Recommended Pattern

// page.tsx
'use client';

import { BrowserGuard } from './BrowserGuard';

export default function Page() {
  return <BrowserGuard />;
}

// BrowserGuard.tsx
'use client';

export function BrowserGuard() {
  const isSafari = typeof navigator !== 'undefined' &&
    /Safari/.test(navigator.userAgent) &&
    !/Chrome/.test(navigator.userAgent);

  if (isSafari) {
    return <h1>Unsupported Browser</h1>;
  }

  return <h1>Welcome</h1>;
}

Read the full file on GitHub · 945 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. 10d ago First seen · 945 lines · 0 tokens per session scan A de7cf7fa4e2c

Subscribe to this mod's changes

nextjs-anti-patterns is a skill published in the GitHub repository wsimmonds/claude-nextjs-skills (108 stars, last pushed 10mo ago), licensed MIT. It adds 97 tokens to every session and 5,354 once invoked, about $0.0005 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-08-30.

Related

Other skills, from other repositories

inspecting-hermes-desktop-dom

Read the live Hermes desktop DOM/CSS over CDP.

NousResearch/hermes-agent · 20 tokens

a11y-debugging

Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.

ChromeDevTools/chrome-devtools-mcp · 50 tokens

devtools

Drop-in inspector panel for any json-render app. Use when the user wants to debug a generative UI, inspect the spec tree, edit state at runtime, see dispatched actions, follow stream patches live, browse a catalog, or pick DOM elements to find their spec keys. Triggers include "add devtools", "debug json-render"…

vercel-labs/json-render · 108 tokens

copilotkit-debug

Use when diagnosing CopilotKit issues -- runtime connectivity failures, agent not responding, streaming errors, tool execution problems, transcription failures, version mismatches, and AG-UI event tracing.

CopilotKit/CopilotKit · 42 tokens

migrate-oxlint

Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.

oxc-project/oxc · 44 tokens

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens