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

bundling.md

View on GitHub
# Package and bundle diagnosis

Trace the actual import chain and failure before changing bundler configuration.
A client boundary can still prerender; browser-only dependencies may require
a client wrapper and an explicit SSR-disabled import there.

`serverExternalPackages` changes server bundling, while `transpilePackages`
changes package transpilation. Neither is a universal ESM/CommonJS repair.
Some native packages are already automatically externalized in current releases.

In Next.js 16, the `webpack` function that fails a default Turbopack build can
come from a plugin. Port compatible options to the top-level `turbopack` config
when migration is in scope.

Use the installed bundle analyzer and supported Turbopack/Webpack configuration.
Measure the affected route rather than marking packages incompatible from a
stale blacklist. Verify runtime dependencies in standalone output.
`next experimental-analyze` supports Turbopack from 16.1 (`next analyze` from
16.4, which keeps the old name as an alias); use `@next/bundle-analyzer` for Webpack. Next.js 16 removed the build's `First Load
JS` column, so measure the actual delivered route.

Keep CSS/fonts and polyfills under the project's asset strategy. Check actual
target browsers and Next.js' supported polyfills before adding another bundle.

Read [package bundling](https://nextjs.org/docs/app/guides/package-bundling)
and the installed configuration reference.
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