What problem does it solve? Choosing the wrong Redis data type or using inconsistent key names leads to wasted memory, slow updates, and unmaintainable code. This Skill provides clear guidance for matching Redis data structures to access patterns and enforcing clean key naming conventions. ## Core Features & Use Cases - Data Structure Selection: Decision table mapping use cases (counters, queues, leaderboards, membership sets, event logs, vector search) to the right Redis type: String, Hash, List, Set, Sorted Set, JSON, Stream, or Vector Set. - Key Naming Conventions: Rules for lowercase, colon-separated hierarchical keys like user:1001:profile, including multi-tenant prefixing and avoiding long URL-based keys. - Hash vs JSON Guidance: Helps decide between a Redis Hash and a JSON document when modeling entities, with Python (redis-py) and Java (Jedis) code examples. - Use Case: When designing a session store or leaderboard, consult this Skill to pick a Sorted Set over a serialized string and name keys consistently across your service. ## Quick Start Ask the AI to help design a Redis data model for caching user profiles and building a game leaderboard with proper key names.