Skill

caching-strategies

Caching patterns: cache-aside, write-through, stampede prevention, CDN headers, multi-level L1/L2/L3, cache invalidation. Use when designing caches or CDN strategy.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milligan

Tool Access

This skill is limited to using the following tools:

ReadGrepGlob

Preview

- Designing cache layers for high-traffic systems

Supporting Assets

assets/caching-checklist.mdreferences/cache-invalidation.mdreferences/caching-patterns.mdreferences/cdn-edge-caching.mdreferences/redis-deep-dive.md

SKILL.md

Similar Skills

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

156.2k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

156.2k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitFeb 23, 2026

Actions

View Source View Plugin View on GitHub View README

Core principles

Cache-aside is the default — application controls all cache interactions

Always add jitter to TTL — ±10% prevents synchronized expiry stampedes

Cache invalidation is harder than caching — design invalidation FIRST, then TTL

Multi-level cache reduces latency multiplicatively — L1 (in-memory) → L2 (Redis) → L3 (DB)

A cache miss should never cascade to DB overload — use lock-based prevention

References available

references/caching-patterns.md — cache-aside, write-through, write-behind, multi-level with code

references/redis-deep-dive.md — data structures for caching, eviction policies, cluster mode

references/cdn-edge-caching.md — Cache-Control headers, stale-while-revalidate, purge strategies

references/cache-invalidation.md — stampede prevention, event-driven invalidation, versioned keys

Caching Strategies

When to use

Designing cache layers for high-traffic systems
Preventing cache stampede / thundering herd
Setting CDN/HTTP cache headers or cache invalidation strategy

Core principles

Cache-aside is the default — application controls all cache interactions
Always add jitter to TTL — ±10% prevents synchronized expiry stampedes
Cache invalidation is harder than caching — design invalidation FIRST, then TTL
Multi-level cache reduces latency multiplicatively — L1 (in-memory) → L2 (Redis) → L3 (DB)
A cache miss should never cascade to DB overload — use lock-based prevention

References available

references/caching-patterns.md — cache-aside, write-through, write-behind, multi-level with code
references/redis-deep-dive.md — data structures for caching, eviction policies, cluster mode
references/cdn-edge-caching.md — Cache-Control headers, stale-while-revalidate, purge strategies
references/cache-invalidation.md — stampede prevention, event-driven invalidation, versioned keys

Assets available

assets/caching-checklist.md — what to cache, TTL recommendations, monitoring queries