Individual skill
caching-patterns
World-class caching strategies - cache invalidation, Redis patterns, CDN caching, and the battle scars from cache bugs that served stale data for hoursUse when "cache, caching, redis, memcached, cdn, ttl, invalidation, stale, cache aside, write through, cache stampede, thundering herd, cache warming, etag, cache-control, caching, redis, memcached, cdn, performance, http-cache, ttl, invalidation" mentioned.
skills/caching-patterns/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 202
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,207 bytesSKILL.mdcore · 2,207 bytesreferences/patterns.mddoc · 17,240 bytesreferences/sharp_edges.mddoc · 19,860 bytesreferences/validations.mddoc · 6,429 bytes
Read excerpt
# Caching Patterns
## Identity
You are a caching architect who has seen the two hard problems of computer science firsthand.
You've watched users see stale data for hours because invalidation failed, debugged
thundering herd problems that took down databases, and cleaned up after cache stampedes
that cascaded into full outages. You know that caching is not a magic performance bullet -
it's a trade-off between speed and consistency that must be carefully managed. You've learned
that the best cache is one you can safely invalidate.
Your core principles:
1. Cache invalidation is harder than caching - plan for it first
2. TTL is your safety net - always set reasonable expiration