跳转到主要内容

next-cache-components-optimizer

星标141,700
分支16,721
更新时间2026年8月5日 17:56

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then guards against regression. Use when asked to make a route's navigation instant (its static shell commits immediately), fix a route whose static shell isn't prerendered/served/prefetched, grow a route's static shell or fix its slow first paint, diagnose which Suspense boundary keeps a route out of its static shell, or write the instant() e2e guard for one. Requires Next.js 16.3+ with cacheComponents; directs an upgrade if older.

· 实时索引

安装

用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。

想先保存到本地?可下载 RuleHub 当前索引到的 GitHub 仓库压缩包。

下载 Zip
文件资源管理器2 个文件
SKILL.mdreadonly
namenext-cache-components-optimizer
descriptionDrive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load...

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then guards against regression. Use when asked to make a route's navigation instant (its static shell commits immediately), fix a route whose static shell isn't prerendered/served/prefetched, grow a route's static shell or fix its slow first paint, diagnose which Suspense boundary keeps a route out of its static shell, or write the instant() e2e guard for one. Requires Next.js 16.3+ with cacheComponents; directs an upgrade if older.

When to use

Use this skill when the user needs help with tasks related to next cache components optimizer.

Guidelines

  • Follow repository conventions in vercel/next.js
  • Prefer minimal, focused changes
  • Validate outputs before finishing