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

metadata.md

View on GitHub
# Metadata boundaries

Use the installed Metadata API/file conventions. Static metadata and
`generateMetadata` belong to server route modules and cannot both be exported
in the same segment. Interactive children can remain client components.

Metadata merges shallowly: replacing a nested object can drop inherited images,
descriptions or robot fields. Homepage canonical/social URLs should not
misidentify child pages. File-based metadata has priority over matching config.

Viewport settings have a separate export. Async route params, image IDs and
sitemap IDs need the installed signature. In 16, the image-generating function
receives `params` and `id` as promises, but `generateImageMetadata` itself
continues to receive synchronous `params`. The sitemap generator receives
`id: Promise<string>`. Cache Components also imposes
serialization/freshness requirements on cached metadata output.

Use `ImageResponse` only when generated images are useful. Its CSS/fonts/bundle
constraints differ from browser rendering. A static social image is often enough.

For crawlability, structured data, bots and production metadata verification,
use `nextjs-seo`. Start from
[generateMetadata](https://nextjs.org/docs/app/api-reference/functions/generate-metadata).
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