redis-patterns
Skill0 starsChanged 4 months agoMITView on GitHub
Redis patterns for caching, pub/sub, streams, Lua scripts, rate limiting, and distributed locks. Use when working with Redis cache, context storage, market data caching, session management, or real-time event processing. Covers Python aioredis/redis-py async patterns.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- valentinesamuel/claude-skillstheir own version, first seen Nov 8, 2026
- ahmadvahidi/skill-atlastheir own version, first seen Nov 8, 2026
- huanglei288766/claude-code-zhtheir own version, first seen Nov 8, 2026
- renepf/claude-skillstheir own version, first seen Oct 25, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- Ronnasayd/aipptheir own version, first seen Oct 20, 2026
Used with
Projects with it also use vite-patterns, orch-pipeline and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ronmkrSkillvite-patterns
Vite build tool patterns including config, plugins, HMR, env variables, proxy setup, SSR, library mode, dependency pre-bundling, and build optimization. Activate when working with vite.config.ts, Vite plugins, or Vite-based projects.
Also in 8 projects that use this
renepfSkillorch-pipeline
Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.
Also in 4 projects that use this
marcusgollSkillparallel-execution-optimizer
Identify and execute independent operations in parallel for 3-5x speedup. Auto-analyzes task dependencies, groups into batches, launches parallel Task() calls. Applies to /optimize (5 checks), /ship pre-flight (5 checks), /implement (task batching), /prototype (N screens). Auto-triggers when detecting multiple independent operations in a phase.
Also in 5 projects that use this
ronmkrSkillquarkus-security
Quarkus Security best practices for authentication, authorization, JWT/OIDC, RBAC, input validation, CSRF, secrets management, and dependency security.
Also in 5 projects that use this
renepfSkillmotion-advanced
Advanced motion patterns for React / Next.js — drag & drop, gestures, text animations, SVG path drawing, custom hooks, imperative sequences (useAnimate), loaders, and the full API decision tree. Requires motion-foundations.
Also in 4 projects that use this
RojiosSkilldefi-amm-security
Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, CEI ordering, donation or inflation attacks, oracle manipulation, slippage, admin controls, and integer math.
Also in 6 projects that use this
- +1 more from ronmkr
- +2 more from renepf
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- Fmarzochi/EGC★ 61same name
- pekral/cursor-rules★ 10same name
- gongyijie85/dsh-ecc★ 8same name
- huanglei288766/claude-code-zh★ 6same name
- nek1987/auto-agent-harness★ 4same name
- ronmkr/PromptBook★ 2same name
- yuanJewel/skills★ 2same name
- diego-tobalina/vibe-coding★ 1same name
- NISTALTALSON/essential-claude-skills★ 1same name
- productionx-in/Core-Skills★ 1same name
10 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- advanced-sql-timescaleSkill
- backtesting-disciplineSkill
- crypto-liquidity-flowSkill
- fastapi-best-practicesSkill
- llm-integrationSkill
- market-microstructureSkill
- qdrant-vector-dbSkill
- risk-managementSkill
- senior-prompt-engineerSkill
- strategy-optimizationSkill
- websocket-realtimeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 143
Use streams over pub/sub when you need:
- Distinctive: line 198
No TTL on cache entries (memory grows unbounded)
- Distinctive: line 201
Not using pipelines for batch operations
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Redis Patterns
Production Redis patterns for Python async applications. Caching, pub/sub, streams, and distributed operations.
When to Apply
- Implementing or modifying cache logic
- Working with Redis context (market data, LLM context)
- Building rate limiting
- Implementing distributed locks
- Event processing with streams
1. Cache-Aside Pattern (CRITICAL)
import json
import redis.asyncio as aioredis
redis = aioredis.from_url("redis://localhost:6379", decode_responses=True)
async def cache_aside(key: str, ttl: int, fetcher) -> dict:
"""Get from cache or fetch and cache."""
cached = await redis.get(key)
if cached:
return json.loads(cached)
value = await fetcher()
await redis.set(key, json.dumps(value, default=str), ex=ttl)
return value
# Usage
data = await cache_aside(
"market:context:btc",
ttl=300,
fetcher=lambda: build_btc_context()
)Cache invalidation
async def invalidate_pattern(pattern: str):
"""Invalidate all keys matching pattern using SCAN."""
cursor = 0
while True:
cursor, keys = await redis.scan(cursor, match=pattern, count=100)
if keys:
await redis.delete(*keys)
if cursor == 0:
break
# NEVER use KEYS * in production - blocks Redis
# ALWAYS use SCAN for pattern matching
await invalidate_pattern("market:context:*")2. Rate Limiting - Sliding Window (CRITICAL)
import time
import uuid
async def is_rate_limited(client_id: str, limit: int, window_seconds: int) -> bool:
key = f"ratelimit:{client_id}"
now = time.time()
window_start = now - window_seconds
pipe = redis.pipeline()
pipe.zremrangebyscore(key, 0, window_start)
pipe.zadd(key, {f"{now}:{uuid.uuid4().hex[:8]}": now})
pipe.zcard(key)
pipe.expire(key, window_seconds)
results = await pipe.execute()
count = results[2]
return count > limit
# Usage in FastAPI
@router.post("/chat/stream")
async def chat_stream(request: ChatRequest):
if await is_rate_limited(request.user_id, limit=10, window_seconds=60):
raise HTTPException(429, "Rate limit exceeded")
# ... process3. Pub/Sub (HIGH)
async def publish_event(channel: str, event: dict):
await redis.publish(channel, json.dumps(event, default=str))
async def subscribe_events(channels: list[str], handler):
pubsub = redis.pubsub()
await pubsub.subscribe(*channels)
async for message in pubsub.listen():
if message["type"] == "message":
event = json.loads(message["data"])
await handler(message["channel"], event)
# Usage
await publish_event("market:alerts", {
"type": "whale_transfer",
"symbol": "BTC",
"volume_usd": 50_000_000
})4. Streams for Event Processing (HIGH)
async def produce_event(stream: str, event: dict):
await redis.xadd(stream, event, maxlen=10000)
async def consume_stream(stream: str, group: str, consumer: str, handler):
# Create group if not exists
try:
await redis.xgroup_create(stream, group, "0", mkstream=True)
except Exception:
pass # Group exists
while True:
results = await redis.xreadgroup(
group, consumer,
{stream: ">"},
count=10,
block=5000
)
if not results:
continue
for stream_name, messages in results:
for msg_id, fields in messages:
await handler(fields)
await redis.xack(stream_name, group, msg_id)Use streams over pub/sub when you need:
- Message durability (pub/sub loses messages if no subscriber)
- Consumer groups (load balancing)
- Message acknowledgment
5. Distributed Lock (HIGH)
async def acquire_lock(resource: str, ttl: int = 30) -> str | None:
token = uuid.uuid4().hex
acquired = await redis.set(
f"lock:{resource}", token, nx=True, ex=ttl
)
return token if acquired else None
async def release_lock(resource: str, token: str) -> bool:
script = """
if redis.call("GET", KEYS[1]) == ARGV[1] then
return redis.call("DEL", KEYS[1])
end
return 0
"""
result = await redis.eval(script, 1, f"lock:{resource}", token)
return bool(result)
# Usage
token = await acquire_lock("update:btc_context")
if token:
try:
await update_btc_context()
finally:
await release_lock("update:btc_context", token)6. Key Naming Convention
entity:id:field - Single value
entity:id:subentity - Hash/nested
ratelimit:client_id - Rate limiting
lock:resource_name - Distributed locks
stream:event_type - Streams
cache:query_hash - Query cache
# Our project patterns:
market:context:btc - BTC market context
market:prices:latest - Latest prices
news:search:query_hash - News search cache
chat:session:user_id - Chat session
scheduler:status - Scheduler state7. Anti-Patterns
KEYS *in production (blocks Redis, use SCAN)- No TTL on cache entries (memory grows unbounded)
- Large values >100KB without compression
- Pub/sub for durable messaging (use Streams)
- Not using pipelines for batch operations
- Storing sensitive data without encryption
8. Checklist
- All keys follow naming convention
entity:id:field - All cache entries have TTL
- SCAN used instead of KEYS for pattern matching
- Pipelines used for multiple sequential commands
- Streams used when durability is needed (not pub/sub)
- Connection pooling configured
- Distributed locks have TTL and proper release
- maxmemory-policy set (allkeys-lru recommended)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

