[Skills] next-cache-components-optimizer: clarify private-cache scope rule#94113
Merged
Conversation
… guidance and verify-recipe failure modes - instant-nav-loop.md: retarget the third-lever sentence from "the I/O function" to "the scope that encloses the request-API read"; add an explicit scope rule for the split-frame case (page reads cookies, helper does fetch); state that private-cache results are browser-resident only; add a guard noting that identical before/after screenshots can mean either lever-didn't-apply or no-I/O-resolved-either-time. - SKILL.md: add gotcha that dev doesn't fire prefetch traffic; point at the cookie-locked SPA-nav recipe as the canonical primitive instead.
gaojude
changed the title
Contributor
Stats from current PR🟢 1 improvement
📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles
Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📝 Changed Files (13 files)Files with changes:
View diffsapp-page-exp..ntime.dev.jsfailed to diffapp-page-exp..time.prod.jsfailed to diffapp-page-tur..ntime.dev.jsfailed to diffapp-page-tur..time.prod.jsfailed to diffapp-page-tur..ntime.dev.jsfailed to diffapp-page-tur..time.prod.jsfailed to diffapp-page.runtime.dev.jsfailed to diffapp-page.runtime.prod.jsfailed to diffserver.runtime.prod.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display 📎 Tarball URLCommit: d8596ed |
Contributor
Tests PassedCommit: d8596ed |
aurorascharff
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agent friction report flagged three gaps in the instant-nav loop's third-lever guidance:
cookies()/headers()/searchParamsread, not whatever function does the downstream fetch. When those are split across frames (page reads cookies, helper does the fetch), the natural reading puts'use cache: private'on the helper alone and the page stays dynamic. Compiles fine, types fine — only runtime tells you.Also a separate gotcha bullet in
SKILL.md: dev doesn't fire prefetch traffic at all (seepackages/next/src/client/components/links.ts:247), so the network tab won't tell you whether your code works. Use the cookie-locked SPA-nav recipe instead.Skill markdown only. No runtime changes.