Skip to content
Agentmart
Submit a tool

redis-cache-design

Design Redis caching strategy with clear keys, TTL, invalidation, and consistency trade-offs.

Skill by cong1ling

IndexedMIT★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/cong1ling-redis-cache-design

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Design Redis caching strategy with clear keys, TTL, invalidation, and consistency trade-offs.

Use cases: design

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/redis-cache-design

What's inside

Skill name
redis-cache-design
Description
Design Redis caching strategy with clear keys, TTL, invalidation, and consistency trade-offs.
License
MIT
Instructions
71 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Redis Cache Design

Use this skill when deciding whether to cache, how to cache, or how to debug cache-related behavior in Java backend systems.

## Rules

- Do not add cache by default; justify it.
- Make cache keys, TTL, and invalidation explicit.
- State consistency trade-offs clearly.
- Separate read optimization concerns from write correctness concerns.

## Workflow

1. **Confirm the goal**
   - reduce read latency
   - reduce database pressure
   - smooth traffic spikes
   - reuse expensive computed results

2. **Decide whether cache is needed**
   - is the underlying operation actually expensive?
   - is the data hot enough to benefit?
   - is the correctness risk acceptable?

3. **Define the cache key strategy**
   - key naming format
   - tenant/user/environment scoping if needed
   - versioning strategy for future key evolution

4. **Define the value and TTL**
   - full object vs partial projection
   - TTL length and why it is appropriate
   - whether null/empty results should be cached

5. **Define invalidation/update behavior**
   - delete-on-write
   - write-through
   - delayed rebuild
   - background refresh

6. **Review failure modes**
   - cache penetration
   - cache breakdown
   - cache avalanche
   - stale reads
   - double-write inconsistency

7. **Define observability**
   - hit rate
   - miss rate
   - rebuild frequency
   - latency impact
   - error paths when Redis is unavailable

## Output format

1. Caching goal
2. Whether cache is justified
3. Key and value design
4. TTL and invalidation strategy
5. Consistency trade-offs
6. Failure-mode handling
7. Monitoring and verification

## Common reminders

- Explicitly discuss cache penetration, breakdown, avalanche, and stale data risks when relevant.
- If strong consistency is required, say so and challenge the cache design.
- Prefer simple, debuggable cache flows over over-engineered cache patterns.

From cong1ling/pi-java-enterprise, MIT.

More from cong1ling/pi-java-enterprise

Signals

Stars
1
Forks
0
Open issues
0
Last commit (this folder)
May 7, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from cong1ling

Cite this page

redis-cache-design skill. Agent Mart. https://agentmart.dev/skills/cong1ling-redis-cache-design (last updated 2026-10-24)