Use when requests involve cache design, stale data bugs, slow repeated reads, edge or API caching, invalidation strategy, or deciding whether caching should exist at all. Design application caching across server, database, network, and edge boundaries: cache scope, freshness models, invalidation, read and write paths, stampede prevention, and cost-performance tradeoffs.