agentmods.dev

nextjs-best-practices

nextjs-best-practices is a skill for Claude Code from xenitV1/Antigravity-Workflows. It costs 22 tokens per session (942 once invoked), scanned A, original, MIT.

A set of best practices for building Next.js applications with the App Router, which is Next.js’s file-based routing system. It explains when to use server or client components, how to fetch data, and how to organize routes.

In plain words
What is it for?
Use it when creating Next.js routes, deciding between server and client components, fetching data from databases or APIs, handling user input, and configuring caching or revalidation.
Why use it?
It helps avoid common mistakes such as making too much code run in the browser or choosing the wrong data-caching behavior. It also gives consistent conventions for loading, error, and not-found states.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

not rated 128repo +1 9mo ago A scan 22 tokens original MIT

Good fit Use it when creating Next.js routes, deciding between server and client components, fetching data from databases or APIs, handling user input, and configuring caching or revalidation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xenitv1/antigravity-workflows/nextjs-best-practices
View source ↗ xenitV1/Antigravity-Workflows
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 xenitV1/Antigravity-Workflows --skill nextjs-best-practices
Clone the repo
git clone --depth 1 https://github.com/xenitV1/Antigravity-Workflows

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-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/xenitv1/antigravity-workflows/nextjs-best-practices/github.svg)](https://agentmods.dev/skills/xenitv1/antigravity-workflows/nextjs-best-practices)
Your own site
<a href="https://agentmods.dev/skills/xenitv1/antigravity-workflows/nextjs-best-practices"><img src="https://agentmods.dev/badge/skills/xenitv1/antigravity-workflows/nextjs-best-practices/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-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/xenitv1/antigravity-workflows/nextjs-best-practices"><img src="https://agentmods.dev/badge/skills/xenitv1/antigravity-workflows/nextjs-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 942 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.00022 $0.00942
Opus 5.5 $0.00009 $0.00377
Sonnet 5.5 $0.00004 $0.00188
Haiku 4.5 $0.00002 $0.00094

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

Security

Grade A, and why

nextjs-best-practices 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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

skills/nextjs-best-practices/SKILL.md · 204 lines

How it starts

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

Next.js Best Practices

Principles for Next.js App Router development.

1. Server vs Client Components

Decision Tree

Does it need...?
│
├── useState, useEffect, event handlers
│   └── Client Component ('use client')
│
├── Direct data fetching, no interactivity
│   └── Server Component (default)
│
└── Both? 
    └── Split: Server parent + Client child

By Default

Type Use
Server Data fetching, layout, static content
Client Forms, buttons, interactive UI

2. Data Fetching Patterns

Fetch Strategy

Pattern Use
Default Static (cached at build)
Revalidate ISR (time-based refresh)
No-store Dynamic (every request)

Data Flow

Source Pattern
Database Server Component fetch
API fetch with caching
User input Client state + server action

3. Routing Principles

File Conventions

File Purpose
page.tsx Route UI
layout.tsx Shared layout
loading.tsx Loading state
error.tsx Error boundary
not-found.tsx 404 page

Route Organization

Pattern Use
Route groups (name) Organize without URL
Parallel routes @slot Multiple same-level pages
Intercepting (.) Modal overlays

4. API Routes

Route Handlers

Method Use
GET Read data
POST Create data
PUT/PATCH Update data
DELETE Remove data

Best Practices

  • Validate input with Zod
  • Return proper status codes
  • Handle errors gracefully
  • Use Edge runtime when possible

5. Performance Principles

Image Optimization

  • Use next/image component
  • Set priority for above-fold
  • Provide blur placeholder
  • Use responsive sizes

Bundle Optimization

  • Dynamic imports for heavy components
  • Route-based code splitting (automatic)
  • Analyze with bundle analyzer

Read the full file on GitHub · 204 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. 2mo ago First seen · 204 lines · 22 tokens per session scan A 50bf04377ef5

Subscribe to this mod's changes

nextjs-best-practices is a skill published in the GitHub repository xenitV1/Antigravity-Workflows (128 stars, last pushed 9mo ago), licensed MIT. It adds 22 tokens to every session and 942 once invoked, about $0.0001 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-30.

FrontendReact
Related

nextjs-best-practices compared with skills from other repositories

nextjs-best-practices next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
nextjs-best-practicesxenitV1/Antigravity-WorkflowsSkill1289mo agoMITA22Claude Code
build-ghost-appTryGhost/GhostSkill56kyesterdayMITA44Claude Code, Codex
chakra-ui-builderchakra-ui/chakra-uiSkill41kyesterdayMITA214Claude Code, Codex
material-ui-tailwindmui/material-uiSkill99kyesterdayMITA67Claude Code, Codex
fuzzy-rankingTanStack/tableSkill29k4d agoMITA62Claude Code, Codex
r3f-best-practiceszebbern/claude-code-guideSkill4.7k3d agoMITA74Claude Code, Codex
git-safetytamagui/tamaguiSkill14ktodayMITA0Claude Code