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 |
route-handlers.md
View on GitHub# Route Handler contracts
A `route.ts` owns HTTP handling at its route; it cannot coexist with a
`page.tsx` for that same segment. It is not a React render context.
Set auth, validation, response content type, cache policy and cancellation for
the actual endpoint. Do not assume every Route Handler has Node.js APIs if the
project selected another runtime.
GET caching depends on the installed version and Cache Components mode.
It is uncached by default from 15; without Cache Components,
`dynamic = 'force-static'` opts it in. With Cache Components, GET can prerender
until request or uncached data access, and `use cache` belongs in a helper,
not the handler export/body. A request-time endpoint may still call a cached
read helper; do not cache its side effects. Non-GET methods run per request. Generated
`RouteContext<'/users/[id]'>` supplies the async params type.
For a streamed response, proxies and terminal errors matter after HTTP headers
are sent. Returning an async stream is not itself a durable job.
Read [Route Handlers](https://nextjs.org/docs/app/api-reference/file-conventions/route)
and the project's API conventions rather than copying a generic CRUD handler.
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 |