Redis Excalidraw Diagram Skill

Create .excalidraw JSON diagrams that explain Redis systems through structure, flow, and concrete evidence. Do not produce generic boxes-and-arrows diagrams.

Required Workflow

1. Classify depth first.
   • Simple/conceptual: mental models, high-level cache patterns, trade-off explanations.
   • Comprehensive/technical: real Redis architectures, commands, protocols, schemas, production topologies, or customer-facing technical diagrams.
2. Research before technical diagrams. For comprehensive diagrams, verify Redis-specific facts in current Redis docs or the user's source material before drawing. Use exact command names, index syntax, topology terms, metrics, and product names.
3. Load the Redis palette. Read color palette before choosing any fill, stroke, text, or evidence-artifact color. It is the single source of truth for diagram colors.
4. Choose visual patterns by behavior. Use fan-out for pub/sub or read replicas, convergence for aggregation, timelines for Streams and lifecycle flows, trees for cluster slots and hierarchy, cycles for cache-aside refresh loops, and swimlanes for application/database/observability boundaries.
5. Generate Excalidraw JSON. Use element templates and JSON schema. For large diagrams, build one section per edit with readable IDs and section-specific seed ranges.
6. Render, inspect, and fix. Run the renderer, view the PNG, then revise until there is no clipping, overlap, ambiguous arrow routing, or unreadable evidence.

Redis Diagram Requirements

For technical diagrams, include concrete evidence artifacts when relevant: