Redis Presentation Decks

Create polished Reveal.js decks that explain Redis systems with accurate technical evidence, Redis brand discipline, and presentation-ready visual QA.

Required Workflow

1. Clarify the deck job. Identify audience, objective, presenter, time limit, delivery format, Redis products in scope, and whether the deck is executive, practitioner, workshop, or implementation review.
2. Plan the story before HTML. Build a slide outline with one message per slide, section dividers, speaker intent, and expected proof artifacts. For solution architecture decks, read Redis deck patterns.
3. Use the scaffold. Generate the Reveal.js shell with scripts/create-presentation.js, then edit the deck HTML slide-by-slide. Do not hand-write the full Reveal.js boilerplate unless the scaffold cannot fit the request.
4. Apply Redis brand defaults. Use Redis Red #FF4438, primary text #091A23, secondary text #163341, muted text #8A99A0, Space Grotesk for body/H2/H3, and Space Mono for H1, code, commands, and compact technical labels.
5. Make Redis evidence visible. Use real commands, schemas, metrics, topology labels, or query fragments where they help the audience trust the architecture. Verify product-specific facts against current Redis docs or user-provided source material.
6. Add speaker notes. Include <aside class="notes"> on all slides that need talk track, demo cues, objections, transitions, or timing guidance. Read Reveal.js reference for notes, fragments, code, and backgrounds.
7. Validate charts before visual review. Read charts reference before adding Chart.js canvases. Run the chart checker when charts are present.
8. Run overflow and screenshot review. Run the overflow checker, export screenshots or PDF with Decktape, inspect every slide image, and revise until there is no clipping, unreadable text, bad contrast, or broken icon/chart rendering.

Scaffold And Scripts

Resolve <skill-dir> to the folder containing this SKILL.md.