What problem does it solve? Designing Redis usage without a clear strategy leads to memory bloat, stale cache data, race conditions, and unbounded keys. This Skill provides a structured, phase-based workflow for modeling Redis data, choosing caching patterns, and applying advanced features correctly. ## Core Features & Use Cases - Data Modeling Guidance: Select the right Redis type (String, Hash, List, Set, Sorted Set), enforce key naming standards like app:module:id, and always assign TTLs. - Caching Strategy: Implement Cache-Aside patterns with proper invalidation logic so database updates stay in sync with Redis. - Advanced Patterns: Apply Pub/Sub for inter-service messaging, atomic operations with INCR or Lua scripts to prevent race conditions, and Streams for high-volume event sourcing. - Use Case: When building a session store or leaderboard, follow the checklist to pick Sorted Sets, set eviction policies like LRU, and verify connection pooling before deployment. ## Quick Start Ask the agent to design a Redis caching layer for your service, including key naming, TTLs, eviction policy, and invalidation logic.