{
  "id": "nextjs-rendering-caching-review",
  "name": "Next.js Rendering & Caching Review",
  "type": "skill",
  "provider": "frontend",
  "harnesses": [
    "claude-code",
    "cursor",
    "codex",
    "gemini",
    "kiro",
    "other"
  ],
  "summary": "Reviews Next.js App Router rendering-mode selection and fetch()/Data-Cache configuration for staleness and cross-user data-leakage risk, using Next.js's own caching documentation loaded progressively and grounded via Context7 against the repo's confirmed Next.js version.",
  "source_type": "original",
  "official_docs": [
    "https://nextjs.org/docs/app/building-your-application/caching",
    "https://nextjs.org/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating",
    "https://nextjs.org/docs/app/guides/incremental-static-regeneration",
    "https://nextjs.org/docs/app/api-reference/functions/revalidateTag"
  ],
  "security_notes": "Cross-user Data Cache leakage (caching a per-user response as if it were shared/public) is a data-exposure defect, not merely a performance nit — this skill escalates such findings to HIGH severity and requires a security-review sign-off, not just a caching-strategy note. Static-review-only skill: it reads and greps route/fetch source but never executes, builds, or runs application code. Treat any hardcoded API key, token, or credential found in a fetch() call or header as a HIGH-severity finding requiring immediate escalation.",
  "last_verified": "2026-07-02",
  "path": "skills/frontend/nextjs-rendering-caching-review",
  "author": "github: VincentChuWaiChow",
  "version": "0.1.0"
}