nextjs-caching
Configure Next.js cache layers, invalidation, and cache-component APIs. Use when choosing `fetch` caching, `use cache`, tags, or stale-data debugging in Next.js.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 4
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 411b554e912de03e… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Caching Architecture
Priority: P1 (HIGH)
Decision Map
- HTTP reads: start with
fetchcache controls (force-cache,no-store,next.revalidate, tags). For content updated a few times per day, ISR withrevalidateis often the right default. - Custom function/component caching: prefer
use cachewithcacheLife()andcacheTag()when the project uses cache components. - Per-render dedupe: use React
cache()for repeated server reads in one render pass. - Mutation invalidation:
revalidateTag()for data ownership,revalidatePath()for route-level refresh,router.refresh()for client view refresh after mutation.
Recipe
- Classify the read: static, periodically fresh, request-specific, or user-specific.
- Pick the narrowest cache: request memoization before persistent cache, tag invalidation before path-wide invalidation.
- Tag what mutates together: align tags with data ownership, not page names by habit.
- Keep personal data private: avoid broad route caching for request-specific state.
- Test stale paths: mutation -> invalidation -> refreshed UI.
Verify
- Cache choice matches data ownership and freshness needs.
- Mutations revalidate the tags or paths they invalidate.
- User-specific data does not leak into shared cache.
- Slow reads stream behind
Suspenseinstead of blocking the whole route. - Existing code using
unstable_cachehas a migration note if cache components are now enabled.
| Layer | Where | Control |
|---|---|---|
| Request Memoization | Server render | React cache() |
| Data Cache | Server | fetch, use cache, tags |
| Full Route Cache | Server | static rendering / revalidation |
| Router Cache | Client | router.refresh() |
Anti-Patterns
- No shared cache for personal data: request-specific state needs a private strategy or no-store path.
- No path-wide invalidation by habit: prefer tags when data ownership is narrower.
- No mutation without revalidation: stale writes are correctness bugs.
- No cache folklore: verify with official cache docs for the project's enabled features.
References
Files
4- SKILL.md
23ae51f20f2.7 KB - evals/evals.json
1cbf9970822.3 KB - references/CACHE_COMPONENTS.md
69270012c31.8 KB - references/implementation.md
5e4d52547c482 B
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from HoangNguyen0403/agent-skills-standard8
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci
Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.
Related frontend skillsscan passed
Combines all of the `better-*` skills into a single review across accessibility, layout, writing, typography, color and UI polish.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
PostHog logs for Next.js
Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with DESIGN.md rationale and an interactive HTML preview, score the UI across 10 dimensions, and flag AI-slo