All skills
cache-design
FoundationJIT onlyUse with task-agent or review-agent for task-local cache scope, freshness, invalidation, and source-load risk. Do not use without a cache decision or as task owner.
- Group
- Data & middleware
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- design cache keys TTL invalidation stampede protection and freshness policy
- Redis ElastiCache Cloud Memorystore Memcached Redis Cluster Redis Sentinel Redis ACL RDB AOF maxmemory eviction hot key pipeline cache stampede cache penetration cache avalanche
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local cache design decision is required
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- cache strategy with keys freshness invalidation and fallback behavior
Escalation signals
When this skill must hand the decision back
- Cache mistakes serve stale data or overload the source of truth
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | Read/write pattern, invalidation, fallback, or load protection remains open. | No cache topology or source-load decision changes. | TaskReview |
| checklist.mddecision-checklist | Cache behavior spans scope collisions, staleness, outages, or hot keys. | The cache is absent from the affected correctness path. | TaskReview |
| evidence-patterns.mdevidence-pattern | Cache safety claims need current topology and failure-path tests. | No freshness, isolation, or source-load claim needs proof. | TaskReview |