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

parallel-routes.md

View on GitHub
# Parallel and intercepted navigation

Slots render in the owning layout. Provide documented fallback/default behavior
for hard navigation and unmatched slots, including implicit children where
needed. A slot's `default.tsx` returns `null` or calls `notFound()` for the
intended fallback. An unmatched
implicit `children` slot without a default returns 404 on hard navigation.

Interceptors count route segments, not filesystem folders. A direct visit to an
intercepted URL normally renders its full page; a client transition can show a
modal. Implement both paths.

`router.back()` is useful for closing a modal opened by navigation. Closing or
navigating elsewhere must also clear the slot; use documented null/catch-all
routes where needed. A persistent modal is not always caused by using push.

Test open, close, forward/back, direct load and refresh, including nested
slots and route groups. Respect accessibility/focus behavior of the chosen dialog.

Read [Parallel Routes](https://nextjs.org/docs/app/api-reference/file-conventions/parallel-routes)
and [Intercepting Routes](https://nextjs.org/docs/app/api-reference/file-conventions/intercepting-routes).
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