Static-first Next.js 16 architecture patterns: cached shells with dynamic slots, provider islands, 'use cache' boundaries, and link preloading strategy. Use when building or refactoring Next.js routes to maximize static rendering, implementing 'use cache' with dynamic personalization, splitting entry vs static renderers, scoping client providers, or tuning prefetch behavior. Triggers on 'static shell', 'use cache pattern', 'dynamic slots', 'provider island', 'prefetch strategy', 'static first', 'cache boundary', 'route goes dynamic unexpectedly', or any Next.js architecture work involving mixed static/dynamic rendering.
90
88%
Does it follow best practices?
Impact
98%
1.24xAverage score across 3 eval scenarios
Passed
No known issues
Static shell with dynamic slots
Entry/Static split
16%
100%
Dynamic slot as ReactNode
0%
100%
Suspense around slot
50%
100%
No request APIs in cache boundary
58%
100%
Request reads in entry
0%
100%
cacheComponents config
100%
100%
Async params awaited in entry
100%
100%
Static data fetch in cached component
30%
100%
No API layer for server data
100%
100%
Client component not async
100%
100%
Cache profiles and invalidation
cacheLife used
100%
100%
cacheTag applied
100%
100%
revalidateTag or updateTag used
100%
100%
No unstable_cache
100%
100%
'use cache' directive present
100%
100%
cacheTag import source
100%
100%
cacheLife import source
100%
100%
Server Action for mutation
100%
100%
No manual key arrays
100%
100%
cacheComponents config
0%
100%
Multiple cache profiles
100%
100%
RSC boundaries, provider islands, prefetch
useSearchParams in Suspense
100%
100%
Feature-scoped provider
100%
100%
Serializable props
100%
100%
prefetch=false on volatile links
100%
100%
Default prefetch on static links
100%
100%
Async params typing
100%
100%
No async client components
100%
100%
Server fetches data for client
100%
100%
Provider initial state from server
40%
50%
Non-serializable types converted
100%
100%
825972c
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.