# Slide Deck

> Design slide decks and presentations using an HTML-first visual prototyping workflow. Invoke whenever the user asks to create, redesign, or materially modify a presentation, slide deck, PowerPoint, pitch deck, report deck, or individual slides where content placement or visual design must be decided.

- Skill: `adityahegde712/slide-deck` (Agent Skill)
- Install (CLI): `npx skillmds@latest add adityahegde712/slide-deck`
- Raw SKILL.md: https://api.skillmd.com/api/skills/adityahegde712/slide-deck/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: AdityaHegde712 (https://skillmd.com/u/adityahegde712)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/adityahegde712/slide-deck

---


# Slide Deck Design Workflow

Design presentation slides visually in HTML before treating the deck design as final.

## 1. Resolve Presentation Direction
Determine relevant presentation constraints: purpose, audience, narrative, desired takeaway, content requirements, tone, visual direction, branding, slide count/presentation length, density, aspect ratio, existing templates/references. Resolve material ambiguities before locking visual decisions.

## 2. Design Slides in HTML
Create proposed slides using HTML/CSS as the primary visual design surface for direct control over content, placement, hierarchy, typography, spacing, imagery, composition, sizing, and visual rhythm. HTML must represent intended final slides, not rough placeholders.

## 3. Render the Slides
Render HTML slides in a browser. Inspect output for: clipping, overflow, alignment, hierarchy, readability, density, consistency, balance, and visual defects. Correct rendering issues before presenting.

## 4. Capture Screenshots
Capture screenshots of rendered slides and present them to the user to judge content, layout, and visual direction from the rendered composition.

## 5. Iterate With the User
If changes are requested: (1) Modify HTML/CSS -> (2) Rerender affected slides -> (3) Inspect results -> (4) Capture updated screenshots -> (5) Present to user. Repeat until approved. Treat approved rendered slides as the visual reference for the final artifact.

## Completion Check
Before finalization, verify:
- [ ] Purpose, audience, and constraints resolved.
- [ ] Non-placeholder HTML/CSS slides created and browser-rendered.
- [ ] Rendered slides visually inspected for defects.
- [ ] Screenshots captured, presented to user, and iterated upon until explicit user approval.