Skip to content

laguagu/claude-code-nextjs-skills / skills/next-best-practices

next-best-practices

Verified

Next.js App Router best practices covering file conventions, RSC boundaries, async APIs, data patterns, hydration errors, metadata, route handlers, image/font optimization, and bundling. Use when writing or reviewing Next.js code to prevent hydration errors, RSC violations, data waterfalls, and configuration mistakes.

FileKindSize
SKILL.mdskill md6.5 KB
async-patterns.mdmarkdown788 B
bundling.mdmarkdown1.4 KB
data-patterns.mdmarkdown1.3 KB
debug-tricks.mdmarkdown872 B
directives.mdmarkdown785 B
error-handling.mdmarkdown1.4 KB
file-conventions.mdmarkdown1.1 KB
font.mdmarkdown821 B
functions.mdmarkdown911 B
hydration-error.mdmarkdown1.2 KB
image.mdmarkdown1.1 KB
metadata.mdmarkdown1.2 KB
parallel-routes.mdmarkdown1.1 KB
route-handlers.mdmarkdown1.2 KB
rsc-boundaries.mdmarkdown1.1 KB
runtime-selection.mdmarkdown849 B
scripts.mdmarkdown788 B
self-hosting.mdmarkdown1.7 KB
suspense-boundaries.mdmarkdown1.1 KB

file-conventions.md

View on GitHub
# Routing conventions

Use the [installed project-structure guide](https://nextjs.org/docs/app/getting-started/project-structure)
for special files and segment syntax.

Route groups organize layouts without entering the URL; they do not enforce
authentication. Private folders exclude routing. Layouts preserve shared
state, while templates remount their subtree.

Parallel route slots and interceptors match route segments, not raw filesystem
depth. Direct URL visits can render a different path from client navigation;
read [parallel-routes.md](parallel-routes.md) when introducing a modal.

Next.js 16 renamed Middleware to Proxy. `proxy.ts` sits alongside app/pages
(including inside `src`), and `skipMiddlewareUrlNormalize` becomes
`skipProxyUrlNormalize`.

Scope the matcher so static/image/public traffic is handled deliberately.
Proxy is suitable for routing/optimistic checks; keep authoritative data
authorization at the actual access. Read the installed
[Proxy reference](https://nextjs.org/docs/app/api-reference/file-conventions/proxy)
before changing request behavior.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall