Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
62
45%
Does it follow best practices?
Impact
90%
1.09xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/next-best-practices/SKILL.mdNext.js 15 async APIs and data patterns
Async params awaited
100%
100%
Async searchParams awaited
100%
70%
Async cookies awaited
100%
100%
No async client component
100%
100%
Date serialized to string
100%
100%
Parallel data fetching
58%
66%
redirect outside try-catch
100%
100%
Server Component for data reads
100%
100%
Suspense for useSearchParams
100%
100%
generateMetadata async params
100%
100%
Image, font, script, and metadata optimization
next/image for hero
100%
100%
priority on hero image
100%
100%
sizes on customer logos
0%
100%
remotePatterns configured
100%
100%
next/font with subset
100%
100%
Font imported once in layout
100%
100%
@next/third-parties for GA
0%
100%
Inline script has id
0%
100%
next/og not @vercel/og
100%
100%
No edge runtime for OG image
100%
100%
OG image uses route params
100%
100%
Metadata in server component
100%
100%
Self-hosting, parallel routes, and third-party bundling
output: standalone
100%
100%
HOSTNAME env var
100%
100%
Static assets copied separately
100%
100%
ISR cache handler configured
100%
100%
cacheMaxMemorySize: 0
100%
100%
recharts with ssr: false
0%
0%
default.tsx for modal slot
100%
100%
router.back() closes modal
100%
100%
Suspense for useSearchParams
0%
0%
Health check endpoint
100%
100%
dc1de9c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.