laguagu/claude-code-nextjs-skills / skills/next-best-practices
next-best-practices
VerifiedNext.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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.5 KB |
| async-patterns.md | markdown | 788 B |
| bundling.md | markdown | 1.4 KB |
| data-patterns.md | markdown | 1.3 KB |
| debug-tricks.md | markdown | 872 B |
| directives.md | markdown | 785 B |
| error-handling.md | markdown | 1.4 KB |
| file-conventions.md | markdown | 1.1 KB |
| font.md | markdown | 821 B |
| functions.md | markdown | 911 B |
| hydration-error.md | markdown | 1.2 KB |
| image.md | markdown | 1.1 KB |
| metadata.md | markdown | 1.2 KB |
| parallel-routes.md | markdown | 1.1 KB |
| route-handlers.md | markdown | 1.2 KB |
| rsc-boundaries.md | markdown | 1.1 KB |
| runtime-selection.md | markdown | 849 B |
| scripts.md | markdown | 788 B |
| self-hosting.md | markdown | 1.7 KB |
| suspense-boundaries.md | markdown | 1.1 KB |
error-handling.md
View on GitHub# Error and control-flow boundaries
Model expected errors as safe application outcomes. Keep internal diagnostics
out of public responses. Unexpected render errors go to the appropriate
segment/root boundary.
`error.tsx` is a client boundary; it does not catch errors from the layout in
the same segment. `global-error.tsx` replaces the root layout and needs its
own html/body, styles and other required dependencies. It does not inherit the
root layout's global styles. `retry()` re-fetches and re-renders the segment
(stable in 16.3; `unstable_retry` in 16.2), while `reset()` only clears the
error state and re-renders without re-fetching. Check the installed contract.
`redirect`, `notFound` and related navigation helpers throw framework signals.
Call them outside ordinary catch blocks or call `unstable_rethrow(error)`
(`next/navigation`) first in the catch. For a component-level boundary,
`catchError` (`next/error`; stable in 16.3, `unstable_catchError` in 16.2)
lets those signals through. Redirect status can differ in Server Actions, so
do not assign one status to every context.
`forbidden()`/`unauthorized()` and their files are still experimental and need
`experimental.authInterrupts`. Check current support instead of enabling a
flag from a stale example.
Read [error handling](https://nextjs.org/docs/app/getting-started/error-handling)
and the affected helper's installed reference.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |