next-best-practices
by tuanvidev
Web & Frontend DevelopmentBrief
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling.
Description
What This Skill Does
A coding assistant skill that enforces Next.js conventions during code writing and review. Covers RSC boundaries, async API migration for Next.js 15+, metadata, image and font optimization, error handling, and bundling.
Consolidates Next.js-specific rules that are otherwise spread across multiple official docs pages, covering patterns that generic linters miss.
When to Use It
- Catching async client component errors before they reach production
- Migrating to Next.js 15 async params, cookies, and headers APIs
- Generating OG images with next/og for social sharing
- Debugging hydration errors caused by browser API misuse
- Configuring next/image for remote sources and LCP priority loading
Example Workflow
User asks: review my Next.js page component that uses params and cookies
- 1
Check if params and cookies are awaited per Next.js 15 async API rules
- 2
Detect any async client components, which are invalid in RSC boundaries
- 3
Verify error boundaries (error.tsx, not-found.tsx) exist for the route
- 4
Check that images use next/image instead of bare img tags
- 5
Flag any non-serializable props passed across RSC boundaries
A list of violations with specific fixes referencing Next.js 15 patterns
Installation
clawhub install tuanvidev/next-best-practicesRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.