A set of conventions for building Next.js applications with the App Router, a system for organising pages and rendering them in a Next.js project.

Use it when creating routes or pages, choosing where code belongs, generating pages, adding metadata, or checking a Next.js application.

It gives developers consistent rules for project structure, TypeScript, server and client code, metadata, documentation, and verification.

How techtankto/techtank-site configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to techtankto/techtank-site. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/techtankto/techtank-site/main/.agents/skills/nextjs/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/techtankto/techtank-site

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/techtankto/techtank-site/nextjs/github.svg)](https://agentmods.dev/skills/techtankto/techtank-site/nextjs)

Your own site

<a href="https://agentmods.dev/skills/techtankto/techtank-site/nextjs"><img src="https://agentmods.dev/badge/skills/techtankto/techtank-site/nextjs/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/techtankto/techtank-site/nextjs"><img src="https://agentmods.dev/badge/skills/techtankto/techtank-site/nextjs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 881 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.

Model	Per session	Once invoked
Fable 5.1	$0.00063	$0.00881
Opus 5.5	$0.00025	$0.00352
Sonnet 5.5	$0.00013	$0.00176
Haiku 4.5	$0.00006	$0.00088

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

Security

Grade A, and why

nextjs 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 2mo 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.

.agents/skills/nextjs/SKILL.md · 50 lines

How it starts

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

Next.js

How the framework is used: App Router, rendering, and the built-in primitives.

Foundations

Runtime, language, and what "done" requires.

pnpm only. Never npm or yarn. Node ≥ 24.
TypeScript strict. No any escape hatches; domain types live in types/.
Exported constants, hooks, types, and utils carry TSDoc. Every export in constants/, hooks/, types/, and utils/ opens with a /** */ block: a one-line summary, plus @param/@returns for functions where the signature does not already say it, and per-member docs on non-obvious type fields; the doc is the contract a caller reads without opening the body. Components document themselves through their props types, not TSDoc.
A server started for verification is killed when the check ends: a pnpm dev or pnpm start run to confirm a change holds the port and outlives the task otherwise, so the next run collides or, worse, verifies against stale output. Long-running servers the human started are theirs to stop.
A verification server runs on its own port and dies by its own pid. Start it with an explicit -p well clear of 3000, capture the pid (pnpm start -p 3987 & echo $!), and kill that pid. Never pkill -f next-server or any name match: it matches every Next process on the machine, including the human's dev server, and rule 4 leaves that one theirs to stop.

Concepts

App Router conventions. One root layout; pages compose section components inside <main>; the app/ route tree mirrors the site's information architecture.
Server components by default. 'use client' only where state or browser APIs demand it (overlays, accordions, marquees, motion-driven sections), and as low in the tree as possible.
Static generation everywhere. No runtime content fetching. Dynamic routes prebuild with generateStaticParams over their id lists and return notFound() for unknown ids.
All images render through next/image with explicit width and height. (Video loops are not images; they render as media elements with their own posters and dimensions.)
Fonts load through next/font/local, exposed as CSS variables and applied on <body>.
Metadata via the Metadata API : a full root export plus per-page overrides (never hand-rolled <head> tags).

Read the full file on GitHub · 50 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.

2mo ago First seen · 50 lines · 63 tokens per session scan A 37ed99a9c177

Subscribe to this mod's changes

nextjs is a skill published in the GitHub repository techtankto/techtank-site (5 stars, last pushed 3d ago), licensed MIT. It adds 63 tokens to every session and 881 once invoked, about $0.0003 per session on Opus 5.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.

Frontend

nextjs next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
nextjstechtankto/techtank-site	Skill	5	3d ago	MIT	A	63	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

techtank-site: Skill for Claude Code