next-best-practices
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.
Pinned to revision 642453129152, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/next-best-practices/SKILL.md
- skills/next-best-practices/async-patterns.md
- skills/next-best-practices/bundling.md
- skills/next-best-practices/data-patterns.md
- skills/next-best-practices/debug-tricks.md
- skills/next-best-practices/directives.md
- skills/next-best-practices/error-handling.md
- skills/next-best-practices/file-conventions.md
- skills/next-best-practices/font.md
- skills/next-best-practices/functions.md
- skills/next-best-practices/hydration-error.md
- skills/next-best-practices/image.md
- skills/next-best-practices/metadata.md
- skills/next-best-practices/parallel-routes.md
- skills/next-best-practices/route-handlers.md
- skills/next-best-practices/rsc-boundaries.md
- skills/next-best-practices/runtime-selection.md
- skills/next-best-practices/scripts.md
- skills/next-best-practices/self-hosting.md
- skills/next-best-practices/suspense-boundaries.md
Every link opens the file at its source, pinned to the revision this page describes.