home / skills / jeremylongshore / claude-code-plugins-plus-skills / redis-cache-manager

redis-cache-manager skill

/skills/06-backend-dev/redis-cache-manager

This skill automates redis cache manager guidance, generating production-ready configurations and best-practice patterns for backend development.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill redis-cache-manager

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.1 KB
---
name: "redis-cache-manager"
description: |
  Manage redis cache manager operations. Auto-activating skill for Backend Development.
  Triggers on: redis cache manager, redis cache manager
  Part of the Backend Development skill category. Use when working with redis cache manager functionality. Trigger with phrases like "redis cache manager", "redis manager", "redis".
allowed-tools: "Read, Write, Edit, Bash(cmd:*), Grep"
version: 1.0.0
license: MIT
author: "Jeremy Longshore <[email protected]>"
---

# Redis Cache Manager

## Overview

This skill provides automated assistance for redis cache manager tasks within the Backend Development domain.

## When to Use

This skill activates automatically when you:
- Mention "redis cache manager" in your request
- Ask about redis cache manager patterns or best practices
- Need help with backend skills covering node.js, python, go, database design, caching, messaging, and microservices architecture.

## Instructions

1. Provides step-by-step guidance for redis cache manager
2. Follows industry best practices and patterns
3. Generates production-ready code and configurations
4. Validates outputs against common standards

## Examples

**Example: Basic Usage**
Request: "Help me with redis cache manager"
Result: Provides step-by-step guidance and generates appropriate configurations


## Prerequisites

- Relevant development environment configured
- Access to necessary tools and services
- Basic understanding of backend development concepts


## Output

- Generated configurations and code
- Best practice recommendations
- Validation results


## Error Handling

| Error | Cause | Solution |
|-------|-------|----------|
| Configuration invalid | Missing required fields | Check documentation for required parameters |
| Tool not found | Dependency not installed | Install required tools per prerequisites |
| Permission denied | Insufficient access | Verify credentials and permissions |


## Resources

- Official documentation for related tools
- Best practices guides
- Community examples and tutorials

## Related Skills

Part of the **Backend Development** skill category.
Tags: nodejs, python, go, microservices, database

Overview

This skill automates common Redis cache manager tasks for backend development teams. It provides guided workflows, production-ready code snippets, and configuration templates to implement, validate, and maintain Redis-based caching in services. Use it to standardize caching patterns across Node.js, Python, and Go services.

How this skill works

The skill inspects requests for Redis cache manager intents and returns step-by-step guidance, code samples, and config snippets tailored to the target stack. It enforces industry best practices, validates configuration options against common standards, and surfaces remediation steps for common errors. When needed it provides patterns for key design, TTL strategies, eviction, and cache invalidation.

When to use it

  • Setting up a new Redis cache layer for microservices
  • Designing key schemas, TTLs, and eviction policies
  • Adding cache-aside, write-through, or read-through patterns
  • Diagnosing cache-related errors or misconfigurations
  • Generating environment-specific Redis configs and connection code

Best practices

  • Use short, namespaced keys and include service context to avoid collisions
  • Prefer cache-aside for simplicity; use write-through for strong consistency needs
  • Set sensible TTLs and consider tiered caching for hot items
  • Avoid storing large objects; use compression or reference IDs for large payloads
  • Instrument cache hit/miss metrics and add alerts for abnormal patterns

Example use cases

  • Generate Node.js and Python client code with connection pooling and retry logic
  • Create a cache invalidation strategy for user profile updates in a microservice
  • Produce Redis config tuned for latency-sensitive workloads and persistence tradeoffs
  • Validate an existing Redis deployment for permission or connection issues and suggest fixes
  • Provide unit test scaffolding and examples for cache behavior and edge cases

FAQ

Which caching pattern should I choose for microservices?

Start with cache-aside for its simplicity and control; use write-through when you need writes to be automatically cached and can tolerate added write latency.

How do I prevent cache key collisions?

Namespace keys by service and resource, include version or schema identifiers, and avoid using raw user-provided strings without normalization.

What metrics should I monitor?

Track cache hits, misses, eviction count, latency, memory usage, and connection errors to detect regressions and tuning opportunities.