redis-core

Guides Redis data structure selection and consistent colon-separated key naming conventions.

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/kaannakiin/turborepo_template --skill redis-core-kaannakiin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redis-core
Source: https://github.com/kaannakiin/turborepo_template/tree/main/.agents/skills/redis-core
Command: npx skills add https://github.com/kaannakiin/turborepo_template --skill redis-core-kaannakiin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about redis-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right Redis data type for my use case?

Match the Redis type to your access pattern: Strings for counters, Hashes for objects with field updates, Lists for queues, Sets for membership, Sorted Sets for rankings, JSON for nested data, Streams for event logs, and Vector Sets for similarity search.

Redis Hash vs JSON: which should I use for storing objects?

Use a Hash when you need atomic per-field reads and writes on a flat object. Use Redis JSON when your data is nested or hierarchical and requires path-level updates or indexing of nested arrays.

What is the best Redis key naming convention?

Use lowercase, colon-separated segments in a stable hierarchy like `user:1001:profile`. Keep keys short but readable, avoid spaces and mixed casing, and add tenant prefixes such as `tenant:42:user:7:cart` for multi-tenant apps.

Why is storing objects as serialized strings in Redis bad?

Storing a flat object as a serialized string forces a fetch, parse, mutate, and rewrite cycle for every single-field update. A Redis Hash allows atomic field-level updates without touching the rest of the object.

Should I use full URLs as Redis keys?

No. Full URLs waste memory and slow key comparisons. Extract a short identifier like `product:8361` from the URL, or use a hash digest of the URL as the key instead.