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
# Font delivery

Choose typography for the product's language, density and tone. Use the existing
font setup or `next/font` where it fits; no family is mandatory.

Load only needed weights/styles and ensure glyph coverage. Shared loader
instances prevent redundant downloads; route-specific fonts need not preload
globally. Verify fallback metrics, font display and CSP/network behavior in
the actual environment.

`next/font` can reduce layout shift, but it does not prove zero CLS for the
page. Google-font build downloads may be unavailable in restricted environments;
use real local licensed assets when that is the deployment contract.

Read the installed [font reference](https://nextjs.org/docs/app/api-reference/components/font)
for framework/Tailwind integration rather than copying version-specific theme code.
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