super-caching
Skill0 starsChanged 19 days agoMITView on GitHub
Super caching: domain router for web (browser, CDN, service worker, HTTP Cache-Control, BFF/API route cache), mobile (on-device, offline, image cache, NSURLSession/OkHttp guidance), server (in-process L1, Redis/Memcached, cache-aside and invalidation), edge/CDN, DB buffer-pool pointers, and optional LLM prompt cache. Covers LRU/LFU/W-TinyLFU, TTL, stampede and hot-key mitigation. Use when choosing or fixing caching in web apps, mobile clients, APIs, distributed cache layers, or CDN headers — not for ORM query-plan cache, pure-function memoization, or CPU cache tuning.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/comments.mdcCursor rule
- .cursor/rules/commit-messages.mdcCursor rule
- .cursor/rules/git-workflow.mdcCursor rule
- .cursor/rules/manage-stack.mdcCursor rule
- .cursor/rules/no-worktrees.mdcCursor rule
- manage-stackSkill
- convert-as-skillSkill
- create-agentSkill
- create-agents-mdSkill
- create-commandSkill
- create-hookSkill
- create-ruleSkill
- create-skillSkill
- retrospectiveSkill
- super-architectureSkill
- super-elixirSkill
- super-nodejsSkill
- super-protobufSkill
- super-tech-blueprintSkill
- atomic-semantic-commitSkill
- code-reviewSkill
- create-bruno-collectionSkill
- create-documentationSkill
- create-ticketsSkill
- ready-specSkill
- write-adrSkill
- write-changelogSkill
- write-mr-descriptionSkill
- write-planSkill
- write-postmortemSkill
- write-runbookSkill
- noslopSkill
- output-saversSkill
- safe-refactorSkill
- tddSkill
- verifySkill
- get-movingSkill
- later-listSkill
- standupSkill
- challenge-meSkill
- codebase-learnerSkill
- researchSkill
- second-opinionSkill
- traceSkill
- color-kitSkill
- design-system-kitSkill
- diagramSkill
- infographicSkill
- product-polish-workflowSkill
- prototype-wireframeSkill
- ui-ux-kitSkill
- evidenceSkill
- find-skillsSkill
- handoffSkill
- rumblingSkill
- use-levistackSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Put hot data closer to the reader.
- Distinctive: line 33
Do this first; load only what the task needs.
- Distinctive: line 67
Read-heavy origin pain → cache-aside + TTL with jitter + invalidate on write.
- Very specific: line 70
Before adding any layer → confirm reads are the bottleneck (back-of-the-envelope).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Super caching
Put hot data closer to the reader. One router for web, mobile, backend/API, edge/CDN, and related tiers — with shared mechanics in references/core/.
Merged scope: formerly caching, caching-strategies, and caching-strategist.
Step 0: pick a domain
Do this first; load only what the task needs. Index: references/domains/README.md.
| If the task touches… | Domain | Load |
| Browser, SPA data libs, service worker, SSR/BFF routes | web | web-app.md + core pack |
| iOS/Android HTTP, offline, images, local stores | mobile | mobile-app.md + core pack |
| Services, workers, Redis, GraphQL loaders, API keys/TTL | backend | backend-api.md + core pack |
CDN, purge, edge KV/workers, s-maxage | edge | edge-cdn.md + http-caching.md |
shared_buffers, InnoDB pool, page eviction | database pool | database-buffer-pool.md |
| Prompt prefix cache, semantic answer cache | AI/LLM | ai-llm.md + backend core as needed |
Core pack (patterns, trade-offs, stress, checklist): fundamentals.md. Add depth by topic:
| You need… | Read |
| LRU, LFU, ARC, W-TinyLFU, L1 vs Redis, eviction policies | cache-mechanisms.md |
| Invalidation, single-flight, L1+L2, Redis vs Memcached | deep-dive.md |
| Redis keys, locks, Lua, pub/sub, pipelines | redis-patterns.md |
| Cache-Control, ETags, CDN, browser | http-caching.md |
| Keys, TTL table, correctness checklist | implementation-checklist.md |
| AWS, Azure, GCP managed cache | providers/generic.md, aws, azure, gcp |
Package layout
super-caching/
├── SKILL.md
└── references/
├── core/ # fundamentals, mechanisms, Redis, HTTP, checklist, providers
└── domains/ # web, mobile, backend, edge, DB pool, AI — README indexQuick defaults
- Read-heavy origin pain → cache-aside + TTL with jitter + invalidate on write.
- Multi-instance → Redis/Memcached; optional L1 on hottest keys only.
- Public static assets → HTTP/CDN first (http-caching.md).
- Before adding any layer → confirm reads are the bottleneck (
back-of-the-envelope).
Full trade-off tables, failure modes, and apply steps: fundamentals.md.
Related skills
super-architecture: decide where the cache layer sits in the system.super-nodejs: build server-side caching in a Node service.super-tech-blueprint: compare Redis, Memcached or a CDN as a stack choice.verify: prove hit rate and latency before you claim a win.
Old skill names
| Old | Use |
caching | This skill (super-caching) |
caching-strategies | super-caching |
caching-strategist | super-caching |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.