redis-core

Select Redis data structures and enforce colon-separated key naming conventions.

4|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/mymx2/foreman --skill redis-core-mymx2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redis-core
Source: https://github.com/mymx2/foreman/tree/main/.qoder/skills.collected/skills/redis-core
Command: npx skills add https://github.com/mymx2/foreman --skill redis-core-mymx2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the common pitfalls of inefficient Redis data modeling and inconsistent key naming, which often lead to memory bloat, performance bottlenecks, and difficult-to-maintain codebases.

Core Features & Use Cases

  • Data Structure Selection: Provides expert guidance on choosing the optimal Redis type (String, Hash, List, Set, Sorted Set, JSON, Stream, Vector Set) based on specific access patterns.
  • Key Naming Conventions: Enforces a standardized, colon-separated hierarchy to ensure keys are readable, memory-efficient, and easy to scan.
  • Use Case: When designing a new service, use this skill to determine whether to store user session data in a Hash or a JSON document, and to define a consistent key pattern like user:1001:session.

Quick Start

Use the redis-core skill to recommend the best data structure and key naming pattern for a new leaderboard feature in my game.

Frequently Asked Questions about redis-core

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

FAQPage Schema
What's the best way to model data in Redis for caching?

Modeling data in Redis requires selecting the optimal data structure for your access patterns and enforcing a standardized, colon-separated key hierarchy to ensure memory efficiency and maintainable key-space organization.

How do I choose the right Redis data structure for my use case?

Choose the right Redis data structure by matching your specific access pattern to the appropriate type, selecting between String, Hash, List, Set, Sorted Set, JSON, Stream, or Vector Set to optimize performance and memory usage.

What are the key naming conventions for Redis?

Redis key naming conventions enforce a standardized, colon-separated hierarchy to ensure keys are readable, memory-efficient, and easy to scan, such as defining a pattern like user:1001:session for user session data.

Should I store user session data in a Redis Hash or JSON document?

Whether to store user session data in a Redis Hash or JSON document depends on your specific access patterns; foundational modeling guidance helps determine the optimal structure and define a consistent key pattern like user:1001:session.

Why does inefficient Redis data modeling cause memory bloat?

Inefficient Redis data modeling causes memory bloat and performance bottlenecks because of inappropriate data structure selection and inconsistent key naming, which ultimately leads to difficult-to-maintain codebases.