Redis Patterns

Covers the bread and butter of Redis in production: cache-aside and write-through patterns, distributed locks with proper token-based release, sliding window rate limiting via Lua, and the difference between Pub/Sub (fire-and-forget) and Streams (durable queues with consumer groups). The connection pooling and key naming conventions alone will save you from common mistakes. Includes tag-based cache invalidation for grouped keys and session storage with hash structures. The atomic operations are correctly implemented with pipelines and Lua scripts where needed. This is the reference you reach for when adding Redis to an app, not learning it from scratch.

skills.sh installs: 1.7K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill redis-patterns --agent claude-code

Installs into .claude/skills of the current project.

Files

Redis Patterns

Quick reference for Redis best practices across common backend use cases.

How It Works

Redis is an in-memory data structure store that supports strings, hashes, lists, sets, sorted sets, streams, and more. Individual Redis commands are atomic on a single instance; multi-step workflows require Lua scripts, MULTI/EXEC transactions, or explicit synchronization to stay atomic. Data is optionally persisted via RDB snapshots or AOF logs. Clients communicate over TCP using the RESP protocol; connection pools are essential to avoid per-request handshake overhead.