# Presentation Design

> Presentation Design

- Skill: `sethdford/presentation-design` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add sethdford/presentation-design`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sethdford/presentation-design/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sethdford (https://skillmd.com/u/sethdford)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sethdford/presentation-design

---

# Presentation Design

Build decks that **persuade and stick**: one idea per slide, a clear narrative, and visuals that support a decision—not a wall of text masquerading as slides.


## When to Use
- Pitches, reviews, training, status updates, or any slide-based storytelling the user asks you to shape or outline.

## Workflow
**Agent order:** **Narrative arc first** (problem → insight → recommendation → ask), **then** slide-by-slide content. **Per slide:** **one** main idea; apply **“so what?”**; prefer charts/diagrams over paragraphs. **Framing:** lead with the **conclusion** (pyramid principle). **Structure:** **rule of three**—three pillars, acts, or takeaways. **Delivery notes:** smooth **transitions** between slides; **rehearse** them aloud. **Close:** one **clear ask** (decision, resource, next step). If it reads like a doc, split into an appendix or handout.

## Examples
**Example 1:** Executive review: slide 1 states the recommendation; next three prove it with one metric, one risk, one mitigation; final slide is “Decision needed: A or B by Friday.”

**Example 2:** Training deck: story of a user failing today → three concepts → one demo flow → exercise; speaker notes carry detail, slides stay sparse.