nextjs-core

nextjs-core is a skill for Claude Code from t-code4change/nextjs-claude-skills. It costs 73 tokens per session (1,760 once invoked), scanned A, original, MIT.

A guide to building and reviewing Next.js applications with the App Router, the newer system for organizing pages and layouts. It covers server and browser components, routing, server actions, TypeScript, and hydration errors.

In plain words
What is it for?
Use it when creating or reviewing App Router pages, migrating from the older Pages Router, fixing hydration errors, or handling server actions.
Why use it?
It helps avoid common Next.js mistakes and diagnose problems caused by incorrect component boundaries or routing patterns.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it when creating or reviewing App Router pages, migrating from the older Pages Router, fixing hydration errors, or handling server actions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/t-code4change/nextjs-claude-skills/nextjs-core
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 t-code4change/nextjs-claude-skills --skill nextjs-core
Clone the repo
git clone --depth 1 https://github.com/t-code4change/nextjs-claude-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-core

README.md
[![agentmods](https://agentmods.dev/badge/skills/t-code4change/nextjs-claude-skills/nextjs-core.svg)](https://agentmods.dev/skills/t-code4change/nextjs-claude-skills/nextjs-core)
Your own site
<a href="https://agentmods.dev/skills/t-code4change/nextjs-claude-skills/nextjs-core"><img src="https://agentmods.dev/badge/skills/t-code4change/nextjs-claude-skills/nextjs-core.svg" alt="Measured on agentmods" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,760 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.00073 $0.01760
Opus 5 $0.00036 $0.00880
Sonnet 5 $0.00015 $0.00352
Haiku 4.5 $0.00007 $0.00176

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

Security

Grade A, and why

nextjs-core 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 7d 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-core/SKILL.md · 284 lines

How it starts

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

Next.js Core Patterns & Anti-patterns


TypeScript: NEVER Use any

// ❌ WRONG
function handleSubmit(e: any) { }
const data: any[] = [];

// ✅ CORRECT
function handleSubmit(e: React.FormEvent<HTMLFormElement>) { }
const handleChange = (e: React.ChangeEvent<HTMLInputElement>) => { };
// Page props (Next.js 15+)
async function Page({ params }: { params: Promise<{ slug: string }> }) {
  const { slug } = await params;
}

Server vs Client Components

Need useState/useReducer/useEffect/Browser APIs/event handlers?
├── YES → 'use client' (at leaf — smallest possible boundary)
└── NO  → Server Component (default — better SEO, smaller bundle)
// ✅ CORRECT: Server wraps Client
// app/page.tsx (Server Component)
export default async function Page() {
  const data = await fetchData();           // server-side
  return <div><InteractiveButton /></div>;  // only button is client
}

// ✅ CORRECT: Server Component as children of Client
<Modal>
  <ServerComponent />   {/* Server passed as children prop */}
</Modal>

// ❌ WRONG: Client Component imports Server Component
'use client';
import { ServerComponent } from './server'; // breaks — pass as children instead

Anti-patterns

1. useEffect for Data Fetching

// ❌ WRONG: waterfall + no SSR + bad SEO
'use client';
export default function List() {
  const [items, setItems] = useState([]);
  useEffect(() => { fetch('/api/items').then(r=>r.json()).then(setItems); }, []);
  return <ul>{items.map(i => <li key={i.id}>{i.name}</li>)}</ul>;
}

// ✅ CORRECT: Server Component — fast, cached, SEO-friendly
export default async function List() {
  const items = await getItems();
  return <ul>{items.map(i => <li key={i.id}>{i.name}</li>)}</ul>;
}

2. Browser Detection Causing Hydration Mismatch

// ❌ WRONG: different value on server vs client → hydration error
const [isMobile, setIsMobile] = useState(
  typeof window !== 'undefined' && window.innerWidth < 768
);

// ✅ CORRECT: consistent initial state, detect after mount
const [isMobile, setIsMobile] = useState(false);
useEffect(() => {
  const check = () => setIsMobile(window.innerWidth < 768);
  check();
  window.addEventListener('resize', check);
  return () => window.removeEventListener('resize', check);
}, []);

Read the full file on GitHub · 284 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. 7d ago First seen · 284 lines · 73 tokens per session scan A cf248052dc69

Subscribe to this mod's changes

nextjs-core is a skill published in the GitHub repository t-code4change/nextjs-claude-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 1,760 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

fast-typescript-check

Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…

internet-development/www-sacred · 84 tokens

onejs-setup-and-overview

Use this skill whenever the user wants to build or set up user interface in a Unity project using OneJS, React, TypeScript, or JSX, e.g. 'add a main menu to my game', 'build a settings screen', 'make a HUD', 'set up OneJS', 'my OneJS panel is blank', 'the UI is not hot reloading'. Covers confirming OneJS is installed…

Singtaa/OneJS · 199 tokens

coding-standards

A set of general coding standards and practical patterns for TypeScript, JavaScript, React, and Node.js. It covers readable naming, simple designs, avoiding repetition, and delaying unnecessary features.

loulanyue/awesome-claude-notes · 41 tokens

typescript-rules

React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.

shinpr/claude-code-workflows · 39 tokens

electron-development

Electron development guidelines for building cross-platform desktop applications with JavaScript/TypeScript.

Mindrally/skills · 18 tokens

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

cursor/plugins · 24 tokens