Skill

redis-deep

Redis deep-dive: 8 data structures with use cases, Redlock distributed locking algorithm, sliding window rate limiter with sorted sets, pub/sub patterns, streams for event log, pipeline batching, keyspace notifications, memory eviction policies, Redis Cluster vs Sentinel. Use when implementing caching, distributed locks, rate limiting, real-time features.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milligan

Tool Access

This skill is limited to using the following tools:

ReadGrepGlob

Preview

- Implementing distributed locking (Redlock)

Supporting Assets

references/caching-patterns.mdreferences/cluster-sentinel.mdreferences/data-structures.md

SKILL.md

Similar Skills

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

156.2k

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

156.2k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitFeb 23, 2026

Actions

View Source View Plugin View on GitHub View README

redis-deep

Core Principles

Redis is not a database for data you cannot afford to lose — AOF/RDB persistence is best-effort; design for Redis to be empty

One connection per operation is wasteful — use pipelining for batch operations (10× throughput improvement)

Key naming convention is critical — resource:id:field prevents collisions and enables pattern scanning

TTL everything — unbounded keys accumulate until OOM; if no TTL makes sense, use a large one (7 days)

Redlock requires majority quorum — N/2+1 nodes must confirm; never use single-node lock for distributed coordination

References available

references/data-structures.md — 8 data structures with TypeScript examples, Redlock, sliding window rate limiter, pub/sub

references/caching-patterns.md — eviction policies, pipeline batching, keyspace notifications, cache-aside pattern

references/cluster-sentinel.md — Redis Cluster vs Sentinel, topology decisions, failover behavior

Redis Deep Dive

When to Use This Skill

Implementing distributed locking (Redlock)
Building rate limiters with sliding windows
Designing pub/sub for real-time features
Using Redis Streams for event log
Choosing memory eviction policy

Core Principles

Redis is not a database for data you cannot afford to lose — AOF/RDB persistence is best-effort; design for Redis to be empty
One connection per operation is wasteful — use pipelining for batch operations (10× throughput improvement)
Key naming convention is critical — resource:id:field prevents collisions and enables pattern scanning
TTL everything — unbounded keys accumulate until OOM; if no TTL makes sense, use a large one (7 days)
Redlock requires majority quorum — N/2+1 nodes must confirm; never use single-node lock for distributed coordination

References available

references/data-structures.md — 8 data structures with TypeScript examples, Redlock, sliding window rate limiter, pub/sub
references/caching-patterns.md — eviction policies, pipeline batching, keyspace notifications, cache-aside pattern
references/cluster-sentinel.md — Redis Cluster vs Sentinel, topology decisions, failover behavior