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

data-patterns.md

View on GitHub
# Data and action boundaries

Read directly in Server Components when that fits rendering; avoid calling the
app's own Route Handler just to wrap the same server-side data access. Use
client fetching where the interaction needs independent/refreshed data.

Server Actions fit UI mutations. They use POST and are externally reachable
endpoints: `use server` does not make a function private. Authenticate,
authorize and validate on every call. Reading through an Action is possible,
but can serialize client calls and is not a general read API.

Route Handlers fit external APIs, webhooks, downloads and independent HTTP
behavior. UI mutations may use them too when that contract is appropriate;
neither boundary prohibits the other mechanically.

Caching depends on actual options/configuration, not merely the location of a
read. Invalidate affected cached data after a committed write; pick immediate
read-your-writes or stale-while-revalidate deliberately.

Parallelize genuinely independent reads, and stream meaningful sections when
latency requires it. Preserve data dependencies and failure semantics.

Read [data security](https://nextjs.org/docs/app/guides/data-security),
[fetching data](https://nextjs.org/docs/app/getting-started/fetching-data)
and the installed caching model.
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