skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
laurigates/claude-plugins55 installs

configure-cache-busting

Check and configure cache-busting strategies for Next.js and Vite projects. Use when configuring content hashing for Next.js or Vite builds, setting up CDN cache headers for Vercel or Cloudflare, adding build verification scripts for hashed assets, or auditing static asset caching strategy. Natural triggers: "configure cache busting", "set up CDN cache headers", "add content hashing".

How do I install this agent skill?

npx skills add https://github.com/laurigates/claude-plugins --skill configure-cache-busting
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill audits and configures cache-busting for Next.js and Vite projects. It reads project configuration and environment variables to generate build verification scripts and update configuration files. Security considerations include the processing of untrusted project data (indirect prompt injection) and the generation of local executable scripts.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerfail

    2/2 files flagged

What does this agent skill do?

When to Use This Skill

Use this skill when...Use another approach when...
Configuring content hashing for Next.js or Vite buildsOptimizing server-side caching (nginx, CDN config directly)
Setting up CDN cache headers for Vercel or CloudflareDebugging build output issues (system-debugging agent)
Verifying cache-busting compliance after a framework upgradeConfiguring general CI/CD workflows (/configure:workflows)
Adding build verification scripts for hashed assetsSetting up container builds (/configure:container)
Auditing static asset caching strategy across a projectProfiling frontend performance (browser devtools)

Context

  • Project root: !pwd
  • Package files: !find . -maxdepth 1 -name 'package.json'
  • Next.js config: !find . -maxdepth 1 -name 'next.config.*'
  • Vite config: !find . -maxdepth 1 -name 'vite.config.*'
  • Build output: !find . -maxdepth 1 -type d \( -name '.next' -o -name 'dist' -o -name 'out' \)
  • CDN config: !find . -maxdepth 2 \( -path './vercel.json' -o -path './_headers' -o -path './_redirects' -o -path './public/_headers' \)
  • Project standards: !find . -maxdepth 1 -name '.project-standards.yaml'

Parameters

Parse from command arguments:

  • --check-only: Report compliance status without modifications (CI/CD mode)
  • --fix: Apply fixes automatically without prompting
  • --framework <nextjs|vite>: Override framework detection
  • --cdn <cloudflare|vercel|none>: Specify CDN provider for cache header configuration

Execution

Execute this cache-busting configuration check:

Step 1: Detect project framework

Identify the framework from file structure:

IndicatorFrameworkConfig File
next.config.js or next.config.mjsNext.jsnext.config.*
next.config.tsNext.jsnext.config.ts
vite.config.js or vite.config.tsVitevite.config.*
.next/ directoryNext.js (built)Detection only
dist/ directory + vite in package.jsonVite (built)Detection only

Check package.json dependencies for "next" or "vite".

If both detected, prompt user to specify with --framework. If neither detected, report unsupported and exit.

Step 2: Analyze current cache-busting state

For the detected framework, read config files and check:

Next.js - Read next.config.js/ts and check:

  • generateBuildId configured for deterministic builds
  • assetPrefix configured for CDN
  • compress: true enabled
  • poweredByHeader: false for security
  • generateEtags configured
  • Cache headers configured in headers() function

Vite - Read vite.config.js/ts and check:

  • build.rollupOptions.output.entryFileNames uses [hash]
  • build.rollupOptions.output.chunkFileNames uses [hash]
  • build.rollupOptions.output.assetFileNames uses [hash]
  • build.manifest: true for SSR/manifest-based routing
  • build.cssCodeSplit configured appropriately

Step 3: Detect CDN provider

Identify CDN from project files:

IndicatorCDN Provider
vercel.json existsVercel
.vercelignore existsVercel
_headers in root or public/Cloudflare Pages
_redirects existsCloudflare Pages / Netlify
wrangler.toml existsCloudflare Workers/Pages
None of the aboveGeneric / None

Step 4: Generate compliance report

Print a formatted compliance report:

Cache-Busting Compliance Report
================================
Project: [name]
Framework: [Next.js 14.x | Vite 5.x]
CDN Provider: [Vercel | Cloudflare | None detected]

Framework Configuration:
  Config file             next.config.js              [EXISTS | MISSING]
  Asset hashing           [hash] in filenames         [ENABLED | DISABLED]
  Build manifest          manifest files              [GENERATED | MISSING]
  Deterministic builds    Build ID configured         [PASS | NOT SET]
  Compression             gzip/brotli enabled         [PASS | DISABLED]

Cache Headers:
  Static assets           immutable, 1y               [CONFIGURED | MISSING]
  HTML files              no-cache, must-revalidate   [CONFIGURED | MISSING]
  API routes              varies by route             [CONFIGURED | N/A]
  CDN configuration       vercel.json/_headers        [EXISTS | MISSING]

Build Output (if built):
  Hashed filenames        app.[hash].js               [DETECTED | NOT BUILT]
  Content addressing      Unique hashes per version   [PASS | DUPLICATE]
  Manifest integrity      Valid manifest.json         [PASS | INVALID]

Overall: [X issues found]

Recommendations:
  [List specific fixes needed]

If --check-only, stop here.

Step 5: Apply configuration (if --fix or user confirms)

Based on detected framework, create or update config files using templates from REFERENCE.md:

  1. Next.js: Update next.config.js/ts with deterministic builds, compression, cache headers
  2. Vite: Update vite.config.js/ts with content hashing, manifest, chunk splitting

Step 6: Configure CDN cache headers

Based on detected CDN provider, create or update cache header configuration using templates from REFERENCE.md:

  • Vercel: Create/update vercel.json with header rules
  • Cloudflare Pages: Create public/_headers with cache rules
  • Generic: Provide nginx configuration reference

Step 7: Add build verification

Create scripts/verify-cache-busting.js to verify content hashing works after build. Add package.json scripts for build verification. Use the verification script template from REFERENCE.md.

Step 8: Configure CI/CD verification

Add cache-busting verification step to GitHub Actions workflow. Use the CI workflow template from REFERENCE.md.

Step 9: Update standards tracking

Update .project-standards.yaml:

standards_version: "2025.1"
last_configured: "[timestamp]"
components:
  cache-busting: "2025.1"
  cache-busting-framework: "[nextjs|vite]"
  cache-busting-cdn: "[vercel|cloudflare|none]"
  cache-busting-verified: true

Step 10: Print final report

Print a summary of changes applied, cache strategy overview, and next steps for verification.

For detailed configuration templates and code examples, see REFERENCE.md.

Agentic Optimizations

ContextCommand
Quick compliance check/configure:cache-busting --check-only
Auto-fix all issues/configure:cache-busting --fix
Next.js project only/configure:cache-busting --fix --framework nextjs
Vite project only/configure:cache-busting --fix --framework vite
Cloudflare CDN headers/configure:cache-busting --fix --cdn cloudflare
Vercel CDN headers/configure:cache-busting --fix --cdn vercel

Output

Provide:

  1. Compliance report with framework and CDN configuration status
  2. List of changes made (if --fix) or proposed (if interactive)
  3. Verification instructions and commands
  4. CDN cache header examples
  5. Next steps for deployment and monitoring

See Also

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/laurigates/claude-plugins/configure-cache-busting">View configure-cache-busting on skillZs</a>