Presentation Design Skill
1. Design Thinking Process
Before generating YAML, choose an aesthetic direction based on the audience and content:
| Direction |
Best For |
Theme Combo |
Transition |
| Minimal/Clean |
Data-heavy, technical |
default or corporate |
fade |
| Bold/Dramatic |
Keynotes, product launches |
midnight or theme: black |
zoom for reveals, slide elsewhere |
| Warm/Inviting |
Training, culture, onboarding |
sunset or forest |
slide |
| Corporate/Professional |
Board decks, strategy |
corporate |
fade |
| Editorial/Magazine |
Thought leadership, creative |
default |
convex |
2. Visual Hierarchy
Structure every deck with this arc:
- Title slide (template:
title) — establish brand and topic
- Agenda (template:
agenda) — orient the audience (optional for <8 slides)
- Section dividers (template:
section) — breathing room between topics
- Evidence slides — mix of
content, metrics, comparison, split
- Summary/Close —
center with a key takeaway, or title reprise
Rules:
- One idea per slide
- Title slides should have 2-6 word headlines
- Section dividers every 4-7 slides in long decks (>12 slides)
- End with impact: a bold statement, a call to action, or a key metric
3. Template Selection Strategy
Never use 3+ of the same template in a row. Alternate between text-heavy and visual templates:
| Purpose |
Template Options |
| Argument building |
content with fragment: fade-up |
| Visual evidence |
split, split-wide, center (with image) |
| Data points |
metrics, table, comparison |
| Narrative flow |
timeline, funnel |
| Impact statement |
quote, hero, center (text only) |
| Code demonstration |
code |
| Side-by-side comparison |
columns, comparison |
Emotional arc: Open with impact (hero/title) -> build with evidence (content/metrics/comparison) -> close with aspiration (quote/center/hero)
4. Content Density Rules
| Element |
Guideline |
| Headlines |
2-6 words, action-oriented |
| Bullet text |
Max 12 words per bullet |
| Bullets per slide |
3-5 items |
| Metrics |
3 for visual balance (2 or 4 acceptable) |
| Code blocks |
Max 10 visible lines |
| Quote text |
Max 2 sentences |
| Nested lists |
Max 2 levels deep |
If a slide exceeds these limits, split it into two slides.
5. Motion & Animation Strategy
Use fragments for:
- Argument building: reveal bullets one-by-one (
fragment: fade-up)
- Metric reveals: show numbers progressively (
fragment: fade-in)
- Comparison reveals: expose rows one at a time (
fragment: fade-up)
- Progressive disclosure in training content
Do NOT use fragments for:
- Every slide (causes pacing fatigue)
- Simple lists with <3 items
- Decorative purposes
- Section dividers or title slides
Use auto-animate for:
- Before/after comparisons (matching
data_id on items)
- Progressive detail — start simple, add complexity
- Code evolution — show how code changes step by step
Per-slide transitions:
transition: zoom — only for dramatic reveals (use sparingly, max 2 per deck)
transition: fade — smooth narrative flow, section transitions
transition: none — rapid-fire comparison between similar slides
- Default
slide transition works well for most slides
6. Theme & Color Usage
Metric colors tell a story:
mint — positive outcomes, growth, success
coral — negative outcomes, problems, risks
amber — warnings, caveats, things to watch
icy — neutral data, context, baseline
Hero slides:
color should match the theme's mood (dark for midnight, warm for sunset)
- Use
background_image for photographic hero slides
- Use
background_gradient for abstract/geometric backgrounds
Comparison highlights:
highlight: right (default) — right column is the recommendation
highlight: left — left column is preferred
highlight: none — neutral comparison
Background enhancements:
background_color on section dividers for visual separation
background_gradient for mood transitions between sections
background_image sparingly — max 2-3 per deck
7. Anti-Patterns to Flag
When reviewing presentations, flag these issues:
- Wall of text: Any slide with >100 words of body content
- Template monotony: 3+ consecutive slides with the same template
- Missing section dividers: Decks >8 slides without any
section templates
- Generic titles: "Overview", "Details", "Summary" — titles should be specific
- Orphaned sections: A
section divider followed by only 1 content slide
- Fragment overuse: More than 50% of slides using fragments
- Metric overload: More than 4 metrics on a single slide
- Missing speaker notes: Important slides without
notes: field
- Image-heavy without alt text:
image fields without image_alt
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: chrisissorry-lazyslides-presentation-design3description: Presentation Design Skill4---56# Presentation Design Skill78## 1. Design Thinking Process910Before generating YAML, choose an aesthetic direction based on the audience and content:1112| Direction | Best For | Theme Combo | Transition |13|-----------|----------|-------------|------------|14| Minimal/Clean | Data-heavy, technical | `default` or `corporate` | `fade` |15| Bold/Dramatic | Keynotes, product launches | `midnight` or `theme: black` | `zoom` for reveals, `slide` elsewhere |16| Warm/Inviting | Training, culture, onboarding | `sunset` or `forest` | `slide` |17| Corporate/Professional | Board decks, strategy | `corporate` | `fade` |18| Editorial/Magazine | Thought leadership, creative | `default` | `convex` |1920## 2. Visual Hierarchy2122Structure every deck with this arc:23241. **Title slide** (template: `title`) — establish brand and topic252. **Agenda** (template: `agenda`) — orient the audience (optional for <8 slides)263. **Section dividers** (template: `section`) — breathing room between topics274. **Evidence slides** — mix of `content`, `metrics`, `comparison`, `split`285. **Summary/Close** — `center` with a key takeaway, or `title` reprise2930Rules:31- One idea per slide32- Title slides should have 2-6 word headlines33- Section dividers every 4-7 slides in long decks (>12 slides)34- End with impact: a bold statement, a call to action, or a key metric3536## 3. Template Selection Strategy3738**Never use 3+ of the same template in a row.** Alternate between text-heavy and visual templates:3940| Purpose | Template Options |41|---------|-----------------|42| Argument building | `content` with `fragment: fade-up` |43| Visual evidence | `split`, `split-wide`, `center` (with image) |44| Data points | `metrics`, `table`, `comparison` |45| Narrative flow | `timeline`, `funnel` |46| Impact statement | `quote`, `hero`, `center` (text only) |47| Code demonstration | `code` |48| Side-by-side comparison | `columns`, `comparison` |4950**Emotional arc**: Open with impact (hero/title) -> build with evidence (content/metrics/comparison) -> close with aspiration (quote/center/hero)5152## 4. Content Density Rules5354| Element | Guideline |55|---------|-----------|56| Headlines | 2-6 words, action-oriented |57| Bullet text | Max 12 words per bullet |58| Bullets per slide | 3-5 items |59| Metrics | 3 for visual balance (2 or 4 acceptable) |60| Code blocks | Max 10 visible lines |61| Quote text | Max 2 sentences |62| Nested lists | Max 2 levels deep |6364If a slide exceeds these limits, split it into two slides.6566## 5. Motion & Animation Strategy6768### Use fragments for:69- Argument building: reveal bullets one-by-one (`fragment: fade-up`)70- Metric reveals: show numbers progressively (`fragment: fade-in`)71- Comparison reveals: expose rows one at a time (`fragment: fade-up`)72- Progressive disclosure in training content7374### Do NOT use fragments for:75- Every slide (causes pacing fatigue)76- Simple lists with <3 items77- Decorative purposes78- Section dividers or title slides7980### Use auto-animate for:81- Before/after comparisons (matching `data_id` on items)82- Progressive detail — start simple, add complexity83- Code evolution — show how code changes step by step8485### Per-slide transitions:86- `transition: zoom` — only for dramatic reveals (use sparingly, max 2 per deck)87- `transition: fade` — smooth narrative flow, section transitions88- `transition: none` — rapid-fire comparison between similar slides89- Default `slide` transition works well for most slides9091## 6. Theme & Color Usage9293### Metric colors tell a story:94- `mint` — positive outcomes, growth, success95- `coral` — negative outcomes, problems, risks96- `amber` — warnings, caveats, things to watch97- `icy` — neutral data, context, baseline9899### Hero slides:100- `color` should match the theme's mood (dark for midnight, warm for sunset)101- Use `background_image` for photographic hero slides102- Use `background_gradient` for abstract/geometric backgrounds103104### Comparison highlights:105- `highlight: right` (default) — right column is the recommendation106- `highlight: left` — left column is preferred107- `highlight: none` — neutral comparison108109### Background enhancements:110- `background_color` on section dividers for visual separation111- `background_gradient` for mood transitions between sections112- `background_image` sparingly — max 2-3 per deck113114## 7. Anti-Patterns to Flag115116When reviewing presentations, flag these issues:117118- **Wall of text**: Any slide with >100 words of body content119- **Template monotony**: 3+ consecutive slides with the same template120- **Missing section dividers**: Decks >8 slides without any `section` templates121- **Generic titles**: "Overview", "Details", "Summary" — titles should be specific122- **Orphaned sections**: A `section` divider followed by only 1 content slide123- **Fragment overuse**: More than 50% of slides using fragments124- **Metric overload**: More than 4 metrics on a single slide125- **Missing speaker notes**: Important slides without `notes:` field126- **Image-heavy without alt text**: `image` fields without `image_alt`127128---129> Converted and distributed by [TomeVault](https://tomevault.io/claim/chrisissorry) — claim your Tome and manage your conversions.130<!-- tomevault:4.0:skill_md:2026-04-11 -->