{
  "id": "service-worker-cache-strategy-review",
  "name": "Service Worker Cache Strategy Review",
  "type": "skill",
  "provider": "frontend",
  "harnesses": [
    "claude-code",
    "cursor",
    "codex",
    "gemini",
    "kiro",
    "other"
  ],
  "summary": "Reviews service-worker route-matching and caching-strategy choices (precache vs. cache-first vs. network-first vs. stale-while-revalidate) against request type and security sensitivity, rejecting uniform blanket strategies and flagging authenticated/PII responses cached in the Cache API.",
  "source_type": "original",
  "official_docs": [
    "https://developer.chrome.com/docs/workbox/",
    "https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API",
    "https://developer.mozilla.org/en-US/docs/Web/API/Cache",
    "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Vary",
    "https://web.dev/articles/service-worker-caching-and-http-caching",
    "https://owasp.org/www-community/attacks/Cache_Poisoning"
  ],
  "security_notes": "Hard-block caching of any response carrying Set-Cookie, an echoed Authorization value, or clearly PII/payment-bearing JSON without explicit, reviewed justification. Hard-block a service-worker scope broader than the routes it is meant to control unless justified. Flag cache.put() calls on opaque (no-cors) cross-origin responses as an unreviewable-content risk per OWASP cache-poisoning concerns. Do not paste real user session data, cookies, or authenticated response bodies into review examples.",
  "last_verified": "2026-07-02",
  "path": "skills/frontend/service-worker-cache-strategy-review",
  "author": "github: VincentChuWaiChow",
  "version": "0.1.0"
}
