Agent skill

Browser Caching

by thedaviddias in thedaviddias/Front-End-Checklist

A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Enable browser caching.

MITAuto-check passedBackend & APIs

Install Browser Caching

skills CLI
$ npx skills add thedaviddias/Front-End-Checklist --skill browser-caching -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thedaviddias/Front-End-Checklist browser-caching --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/browser-caching .claude/skills/browser-caching && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
browser-caching
GitHub stars
74k
Token cost
~399 tokens
SKILL.md length
142 words
Files
2 (incl. references)
Skills in repo
390
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Enable browser caching.

  • Auditing slow page loads
  • SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Rendering delays related to Enable browser caching

What it does

Browser Caching is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing slow page loads, heavy assets, or rendering delays related to Enable browser caching. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Its SKILL.md is about 400 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).

It sits in Backend & APIs, covering Caching and Web performance. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.

When your agent uses it

  • Auditing slow page loads
  • Rendering delays related to Enable browser caching

Example prompts

  • “/browser-caching”

What it can do on your machine

Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • frontendchecklist.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Browser Caching loads about 399 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 142 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~399
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 142 words, ~399 tokens.

Download SKILL.mdSave it as .claude/skills/browser-caching/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
browser-caching
description
Use when auditing slow page loads, heavy assets, or rendering delays related to Enable browser caching. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
metadata.category
performance
metadata.priority
high
metadata.difficulty
intermediate
metadata.estimatedTime
20
metadata.source
frontendchecklist.io
metadata.url
https://frontendchecklist.io/rules/performance/browser-caching

Enable browser caching

Proper caching eliminates redundant downloads on repeat visits—returning users see near-instant page loads when assets are served from browser cache.

Quick Reference

  • Use immutable caching for hashed assets (1 year max-age)
  • Use short cache + revalidation for HTML pages
  • ETags enable efficient cache validation
  • stale-while-revalidate improves perceived performance

Check

Verify that proper cache headers are set for static resources to enable browser caching.

Fix

Configure appropriate Cache-Control and ETag headers for different resource types.

Explain

Explain how browser caching reduces server requests and improves repeat visit performance.

Code Review

Review the routes, assets, and loading behavior that affect Enable browser caching. Flag exact files, requests, or rendering steps that add unnecessary network, CPU, or layout cost, and describe the measurement method used to confirm the issue.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/performance/browser-caching

© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/browser-caching of thedaviddias/Front-End-Checklist.

  • SKILL.md
  • references/rule.md

Open the folder on GitHubat commit e8d14d0

Compare with similar skills

Browser Caching next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Browser Caching compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Browser Caching this skillthedaviddias/Front-End-Checklist74k—~399Automated safety check: PassMIT
Cloudflare Workers Performancesecondsky/claude-skills227—~1.6kAutomated safety check: PassMIT
Vercel Performance Tuningjeremylongshore/tons-of-skills-marketplace2.8k—~2.1kAutomated safety check: PassMIT
Nextjsericrisco/rsc-harness174—~5.1kAutomated safety check: PassMIT
Angular Clean Architecturefmflurry/settings-opencode171—~3.6kAutomated safety check: PassMIT
Performance Capacitymajiayu000/spellbook287—~501Automated safety check: PassMIT

Similar skills

  • Cloudflare Workers Performance

    secondsky/claude-skills

    Cloudflare Workers performance optimization with CPU, memory, caching, bundle size.

    227 GitHub stars~1.6k tokensUpdated 11 days ago
    Backend & APIsAuto-check passed
  • Vercel Performance Tuning

    jeremylongshore/tons-of-skills-marketplace

    Optimize Vercel deployment performance with caching, bundle optimization, and cold start reduction.

    2.8k GitHub stars~2.1k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Nextjs

    ericrisco/rsc-harness

    A skill your agent uses when building, reviewing, testing, securing, or optimizing a Next.js App Router app: Server vs Client boundaries, use server actions, route handlers, the v15 vs v16 use cache…

    174 GitHub stars~5.1k tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed
  • Angular Clean Architecture

    fmflurry/settings-opencode

    Scaffolds and extends Angular standalone feature MODULES under src/app/modules/{name} using Clean Architecture layering (presentation/application/core/infrastructure), a self-registering module…

    171 GitHub stars~3.6k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Performance Capacity

    majiayu000/spellbook

    Plan, diagnose, and verify performance budgets, latency targets, load tests, capacity estimates, bottleneck analysis, caching strategy, query efficiency, queue throughput, and regression gates.

    287 GitHub stars~501 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • High Perf Browser

    wondelai/skills

    Optimize web performance through network protocols, resource loading, and browser rendering internals.

    2.4k GitHub stars~4k tokensUpdated 29 days ago
    Frontend & DesignAuto-check passed

More from thedaviddias/Front-End-Checklist

All 390 skills in this repo
  • Content Dates Audit

    thedaviddias/Front-End-Checklist

    Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.

    74k GitHub stars~691 tokensUpdated 3 days ago
    Auto-check passed
  • FAQPage Schema Markup

    thedaviddias/Front-End-Checklist

    Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.

    74k GitHub stars~774 tokensUpdated 3 days ago
    Auto-check passed
  • Favicon Audit and Setup

    thedaviddias/Front-End-Checklist

    Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.

    74k GitHub stars~731 tokensUpdated 3 days ago
    Auto-check passed
  • Content Freshness Signals

    thedaviddias/Front-End-Checklist

    Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.

    74k GitHub stars~741 tokensUpdated 3 days ago
    Auto-check passed
  • Geo Meta Tags Audit

    thedaviddias/Front-End-Checklist

    Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).

    74k GitHub stars~763 tokensUpdated 3 days ago
    Auto-check passed
  • Improve a Front-End Checklist Rule

    thedaviddias/Front-End-Checklist

    Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.

    74k GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Browser Caching

What does Browser Caching do?

A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Enable browser caching. Browser Caching is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing slow page loads, heavy assets, or rendering delays related to Enable browser caching.

When should I use Browser Caching?

Browser Caching fits situations like: auditing slow page loads; rendering delays related to Enable browser caching.

How do I install Browser Caching in Claude Code?

Run `npx skills add thedaviddias/Front-End-Checklist --skill browser-caching -a claude-code`. Or copy the skill folder (skills/browser-caching in thedaviddias/Front-End-Checklist) into .claude/skills/browser-caching in your project. Claude Code loads it when a task matches its description.

How do I install Browser Caching in Codex?

Run `npx skills add thedaviddias/Front-End-Checklist --skill browser-caching -a codex`. Or copy the skill folder (skills/browser-caching in thedaviddias/Front-End-Checklist) into .agents/skills/browser-caching in your project. Codex loads it when a task matches its description.

Can I use Browser Caching in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill browser-caching -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser-caching, .gemini/skills/browser-caching, .github/skills/browser-caching and .opencode/skills/browser-caching in your project.

What does Browser Caching need to run?

SKILL.md names no scripts, command-line tools or credentials: Browser Caching is instructions for the agent only.

Does Browser Caching access the network?

SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.

Is Browser Caching safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Browser Caching use?

Browser Caching is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Browser Caching use?

About 399 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.

What are the alternatives to Browser Caching?

Skills that share tags, products or a category with Browser Caching: Cloudflare Workers Performance (secondsky/claude-skills, 227 stars), Vercel Performance Tuning (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Nextjs (ericrisco/rsc-harness, 174 stars) and Angular Clean Architecture (fmflurry/settings-opencode, 171 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Browser Caching?

thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,412 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.

Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.