redis-presentation-decks

---
name: redis-presentation-decks
description: Create Redis-focused Reveal.js presentation decks for solution architecture, customer briefings, technical workshops, product narratives, QBRs, and sales engineering storytelling. Use when a user asks for Redis-branded slides, decks, or presentations that need Reveal.js HTML, speaker notes, charts, architecture flows, screenshot review, and overflow validation.
license: MIT
---

# Redis Presentation Decks

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

## Authority

- Authorized: create or modify Redis Reveal.js deck artifacts and validation scripts for deck output.
- Requires explicit request: publish, deploy, or export customer-facing files beyond the requested artifact.
- Assessment-only default: for deck review requests, report findings and stop unless edits are requested.

## 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](references/redis-deck-patterns.md).
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](references/revealjs-reference.md) for notes, fragments, code, and backgrounds.
7. **Validate charts before visual review.** Read [charts reference](references/charts.md) 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`.

```bash
node <skill-dir>/scripts/create-presentation.js \
  --structure 1,1,d,3,1,d,1 \
  --title "Redis Solution Architecture" \
  --output deck/presentation.html
```

Useful scripts:

- `scripts/create-presentation.js`: generate a Redis-branded Reveal.js HTML scaffold and copy `references/base-styles.css` as `styles.css`.
- `scripts/check-charts.js`: validate `canvas[data-chart]` blocks for supported chart types, parseable JSON or CSV, datasets, and `maintainAspectRatio: false`.
- `scripts/check-overflow.js`: open the deck in Playwright Chromium and report slide content that exceeds slide bounds.

Install optional validation dependencies once when overflow checking is needed:

```bash
cd <skill-dir>
npm install
npx playwright install chromium
```

Run checks from the deck directory:

```bash
node <skill-dir>/scripts/check-charts.js presentation.html
node <skill-dir>/scripts/check-overflow.js presentation.html
npx decktape reveal "presentation.html?export" presentation.pdf --screenshots --screenshots-directory screenshots
```

Use `?export` when exporting so chart animations are disabled and screenshots capture final chart states.

## Redis Deck Requirements

- Use Redis Red for brand ownership, primary Redis components, active paths, and decisive emphasis. Do not flood every element with red.
- Use dark evidence blocks for `redis-cli`, JSON documents, Query Engine syntax, metrics, configs, and topology facts.
- Distinguish Redis Open Source, Redis Software, Redis Cloud, Redis Enterprise for Kubernetes, Redis Query Engine, RedisVL, LangCache, Streams, Cluster, Sentinel, and Active-Active when relevant.
- Show architecture behavior through layout: request path, cache hit/miss, write-through/write-behind, stream processing, vector retrieval, failover, replication, cluster sharding, and observability loops.
- Prefer source-backed numbers and short labels over generic claims. Add footnotes for benchmark conditions, customer-provided data, Redis docs, or assumptions.
- Use speaker notes for discovery context, objection handling, demo steps, and timing. Do not put presenter-only detail on the slide.

## Anti-Patterns

DO NOT:

- Use generic SaaS pitch-deck layouts when the request is a Redis technical or solution architecture deck.
- Use non-brand reds, pure black `#000000`, system fonts, or Space Mono for body paragraphs.
- Paste long paragraphs, API docs, or architecture prose onto slides. Convert detail into diagrams, evidence blocks, charts, or speaker notes.
- Show Redis as a vague box between app and database when Redis commands, data structures, modules, topology, or latency claims are central to the story.
- Include charts without `maintainAspectRatio: false` and a bounded flex/grid container.
- Deliver HTML based only on DOM inspection. Always inspect rendered screenshots for customer-facing decks.
- Use this skill for a generic slide request with no Redis product, architecture, or technical content (e.g. a generic team offsite icebreaker deck) — build plain Reveal.js/HTML directly instead.
- Produce `.pptx`, Google Slides, or other non-Reveal.js deck formats with this skill; it only generates Reveal.js HTML.

## Common Rationalizations

| Rationalization | Reality |
|---|---|
| "The slides look right in the HTML editor" | Always run overflow and screenshot checks; DOM inspection misses clipping and rendering issues. |
| "Detailed architecture prose on the slide helps the audience" | Convert detail into diagrams, evidence blocks, charts, or speaker notes; slides are not documents. |
| "Any red is close enough for Redis branding" | Use exactly Redis Red `#FF4438`; non-brand reds, pure black, and system fonts violate brand defaults. |
| "Speaker notes are optional for technical slides" | Every slide needing a talk track must have `<aside class="notes">`; presenter-only detail stays off the visible slide. |
| "Charts don't need maintainAspectRatio: false" | Charts without `maintainAspectRatio: false` in a bounded container will break on resize. |
| "This generic deck template works for a Redis architecture talk" | Do not use generic SaaS layouts for Redis technical or solution architecture decks. |

## Verification

- [ ] Slide deck uses the Redis brand template — `grep -c '#FF4438' presentation.html` returns at least 1, and `grep -c 'Space Grotesk' presentation.html` returns at least 1.
- [ ] All diagrams and charts render correctly — `node <skill-dir>/scripts/check-charts.js presentation.html` exits `0` and `node <skill-dir>/scripts/check-overflow.js presentation.html` exits `0`.
- [ ] Speaker notes are present for key slides — `grep -c '<aside class="notes">' presentation.html` returns a count matching or exceeding the number of content slides that need a talk track.
- [ ] No proprietary customer data appears in slides — `grep -riE '(confidential|internal.only|customer.name|NDA)' presentation.html` returns no matches, or every match is inside a speaker note with explicit clearance.

## Reference Index

| File | Load When |
| --- | --- |
| [base-styles.css](references/base-styles.css) | The scaffold copies this into deck projects as the editable Redis Reveal.js theme. |
| [redis-deck-patterns.md](references/redis-deck-patterns.md) | Planning solution architecture stories, slide archetypes, Redis proof points, and anti-patterns. |
| [charts.md](references/charts.md) | Adding Chart.js visuals, KPI slides, latency/cost charts, or benchmark comparisons. |
| [revealjs-reference.md](references/revealjs-reference.md) | Using speaker notes, fragments, backgrounds, code highlighting, transitions, and exports. |

## Done Checklist (must be literally verifiable)

Each item must be proved by a command output or file read from this session, not by memory or prior conversation.

- [ ] Slide outline lists one message per slide and names the audience (executive/practitioner/workshop/implementation-review).
- [ ] Every slide's Redis Red, text, and font usage matches the brand defaults in step 4 of Required Workflow (no non-brand red, no pure black, no system fonts for body/H1).
- [ ] Every slide needing a talk track has an `<aside class="notes">` block; no presenter-only detail is on the visible slide.
- [ ] `node <skill-dir>/scripts/check-charts.js presentation.html` exits `0` when the deck contains any `canvas[data-chart]`.
- [ ] `node <skill-dir>/scripts/check-overflow.js presentation.html` exits `0` (no slide content exceeds slide bounds).
- [ ] Every exported screenshot (Decktape or manual) has been visually opened and inspected, not just generated.
- [ ] If the request had no Redis product/architecture content, confirm this skill was NOT used.