Presentation Generator
Version: 1.0
Generate a lecture-ready PowerPoint presentation from an intelligent textbook project. The presentation is designed for live delivery — visual, story-driven, with progressive disclosure, audience interaction beats, and speaker notes that script the entire performance.
Core Philosophy: The Medium IS the Message
The presentation doesn't teach about communication or subject-matter frameworks. It is the framework in action. The audience should experience principles before being told about them. Every slide must answer: "Is this slide itself an example of the principle it discusses?"
This means:
- When teaching structure, the presentation IS structured (Pyramid Principle — governing thought in minute 2, not minute 55)
- When teaching brevity, the slide has seven words maximum
- When teaching storytelling, the lecture IS a story (4-act arc)
- When teaching about cognitive load, no slide overloads the audience
- Meta-moments: The speaker reveals "what I just did was [framework name]" AFTER demonstrating it. The audience learns through experience, then gets the vocabulary.
When to Use This Skill
Use when:
- An intelligent textbook exists (MkDocs project with chapters, course-description.md, learning graph)
- The user wants a lecture presentation for live delivery
- The user wants to convert textbook content into a slide deck
- The user says "create a presentation", "make slides", "build a deck", "lecture slides"
Do NOT use when:
- No textbook content exists yet (use course-description-analyzer and chapter generators first)
- The user wants a document, not a presentation (use docx skill)
- The user wants to edit an existing presentation (use the pptx editing workflow)
Prerequisites
- Node.js installed
npm install pptxgenjs (install locally in the output directory)
- An intelligent textbook project with:
docs/course-description.md
docs/chapters/ with chapter content
CLAUDE.md with project conventions (optional but helpful)
Workflow
Step 1: Read the Textbook
Read these files to understand the content:
- Course description (
docs/course-description.md) — extract title, audience, key topics, learning outcomes
- CLAUDE.md — extract tone, style, color palette, mascot info
- Chapter index files — scan
docs/chapters/*/index.md for chapter titles, key concepts, and the pedagogical flow
- Student feedback (if available in
input-knowledge/) — what resonated with prior audiences
- Original lecture notes (if available) — the speaker's natural flow and stories
Step 2: Design the Presentation Structure
Design a 4-act structure following Klein's storytelling model applied to the lecture itself:
| Act |
Purpose |
Slides |
Time |
| I: The Wake-Up Call |
Hook, establish stakes, live challenge |
6-8 |
~10 min |
| II: The Toolkit |
Core frameworks with before/after demos |
10-14 |
~20 min |
| III: The Power Tools |
Advanced techniques, persuasion, AI |
6-10 |
~12 min |
| IV: The Close |
Action plan, textbook link, final quote |
4-6 |
~8 min |
Target: 25-35 slides for a 50-60 minute lecture. At ~1.5 min/slide average. Fewer slides = more speaker time per slide = more engaging.
Present the proposed structure to the user for approval before generating.
Step 3: Design the Visual System
Extract or create a color palette from the textbook's CLAUDE.md:
const C = {
primary: "XXXXXX", // From CLAUDE.md palette
primaryDark: "XXXXXX",
primaryLight: "XXXXXX",
accent: "XXXXXX", // Highlight color
white: "FFFFFF",
offWhite: "F5F5F5",
black: "212121",
gray: "757575",
red: "C62828", // For "before" / negative examples
green: "2E7D32", // For "after" / positive examples
};
Typography:
- Title font: Georgia (or serif from CLAUDE.md)
- Body font: Calibri (or sans-serif from CLAUDE.md)
- Title size: 32-44pt
- Body size: 14-20pt (never below 13pt)
Layout rules:
- No more than 7 words per line of body text
- One idea per slide
- Dark backgrounds (primary dark) for section dividers, title, close
- Light backgrounds (white) for content slides
- Accent color for emphasis bars, numbers, highlights
Step 4: Generate the Presentation
Create a Node.js script that uses pptxgenjs to generate the .pptx file. Read references/slide-patterns.md for the reusable slide pattern library.
Slide categories and their patterns:
- Title slide — dark bg, large title, subtitle, author, accent bar
- Section divider — dark bg, large text, subtitle, accent bar
- Big number — dark bg, one massive stat (80-120pt), context below
- Before/After comparison — two columns, red accent (before) vs green (after)
- Framework visual — shapes/diagrams illustrating a model (pyramid, stages, pillars)
- Evidence stack — 3 cards with accent bars showing research findings
- Interactive beat — light bg, challenge prompt in a card, instructions
- Quote — dark bg, large italic text, attribution
- Action items — numbered circles with titles and descriptions
- Resource/CTA — textbook link, QR code placeholder, stats
Step 5: Write Speaker Notes
Every slide gets detailed speaker notes. These are the real script — the slides are just visual anchors. Notes include:
- TIMING: Cumulative minutes (e.g., "TIMING: 15:00")
- SAY: The exact narrative to deliver (2-4 sentences, conversational)
- META-MOMENT: Where the speaker reveals the framework AFTER demonstrating it (e.g., "Notice what I just did? That was Klein's Dilemma stage.")
- TRANSITION: The bridge sentence to the next slide
- AUDIENCE PULSE: When to pause, ask a question, or let silence work
Step 6: Generate and Verify
- Run the Node.js script to generate the .pptx
- Verify slide count matches the design
- Extract text with
python -m markitdown output.pptx to confirm content
- Report the result to the user with slide count and timing estimate
Output
The presentation file should be saved to:
{project-root}/presentation/{kebab-case-title}.pptx
Along with the generation script:
{project-root}/presentation/generate.js
Adapting for Different Subjects
This skill works for ANY intelligent textbook, not just communication. The key adaptations:
- Subject-specific stories: Open with a story from the textbook's domain (engineering, science, business)
- Framework names: Use whatever frameworks the textbook teaches (not just Minto, Klein, etc.)
- Color palette: Derive from the textbook's CLAUDE.md
- Audience: Match the course-description.md target audience
- Interactive beats: Design exercises relevant to the subject matter
The 4-act structure and McLuhan principle remain constant regardless of subject.
References
references/slide-patterns.md — Reusable pptxgenjs code patterns for each slide type
references/speaker-notes-guide.md — How to write effective speaker notes
Best Practices
- Cut aggressively: If a slide doesn't change understanding, delete it. The Dilution Effect applies to slide decks too.
- Story first, framework second: Always demonstrate a principle through a story or example before naming the framework.
- One idea per slide: If you need two sentences to explain what a slide is about, split it into two slides.
- Speaker notes ARE the presentation: The slides are visual anchors. The speaker's narrative, pauses, and meta-moments are where learning happens.
- Test the McLuhan principle: For every slide, ask "Is this slide itself an example of what it teaches?" If not, redesign it.
1---2name: textbook-to-presentation-generator3description: Generates a lecture PowerPoint from an intelligent textbook using pptxgenjs — visual design, 4-act storytelling structure, and speaker notes. Use when converting a textbook into slides for classroom delivery.4metadata:5 source: https://skillmd.com/skills/dmccreary/textbook-to-presentation-generator6---78# Presentation Generator910**Version:** 1.01112Generate a lecture-ready PowerPoint presentation from an intelligent textbook project. The presentation is designed for live delivery — visual, story-driven, with progressive disclosure, audience interaction beats, and speaker notes that script the entire performance.1314## Core Philosophy: The Medium IS the Message1516The presentation doesn't *teach about* communication or subject-matter frameworks. It *is* the framework in action. The audience should experience principles before being told about them. Every slide must answer: **"Is this slide itself an example of the principle it discusses?"**1718This means:19- When teaching structure, the presentation IS structured (Pyramid Principle — governing thought in minute 2, not minute 55)20- When teaching brevity, the slide has seven words maximum21- When teaching storytelling, the lecture IS a story (4-act arc)22- When teaching about cognitive load, no slide overloads the audience23- **Meta-moments**: The speaker reveals "what I just did was [framework name]" AFTER demonstrating it. The audience learns through experience, then gets the vocabulary.2425## When to Use This Skill2627Use when:28- An intelligent textbook exists (MkDocs project with chapters, course-description.md, learning graph)29- The user wants a lecture presentation for live delivery30- The user wants to convert textbook content into a slide deck31- The user says "create a presentation", "make slides", "build a deck", "lecture slides"3233Do NOT use when:34- No textbook content exists yet (use course-description-analyzer and chapter generators first)35- The user wants a document, not a presentation (use docx skill)36- The user wants to edit an existing presentation (use the pptx editing workflow)3738## Prerequisites3940- Node.js installed41- `npm install pptxgenjs` (install locally in the output directory)42- An intelligent textbook project with:43 - `docs/course-description.md`44 - `docs/chapters/` with chapter content45 - `CLAUDE.md` with project conventions (optional but helpful)4647## Workflow4849### Step 1: Read the Textbook5051Read these files to understand the content:52531. **Course description** (`docs/course-description.md`) — extract title, audience, key topics, learning outcomes542. **CLAUDE.md** — extract tone, style, color palette, mascot info553. **Chapter index files** — scan `docs/chapters/*/index.md` for chapter titles, key concepts, and the pedagogical flow564. **Student feedback** (if available in `input-knowledge/`) — what resonated with prior audiences575. **Original lecture notes** (if available) — the speaker's natural flow and stories5859### Step 2: Design the Presentation Structure6061Design a **4-act structure** following Klein's storytelling model applied to the lecture itself:6263| Act | Purpose | Slides | Time |64|-----|---------|--------|------|65| **I: The Wake-Up Call** | Hook, establish stakes, live challenge | 6-8 | ~10 min |66| **II: The Toolkit** | Core frameworks with before/after demos | 10-14 | ~20 min |67| **III: The Power Tools** | Advanced techniques, persuasion, AI | 6-10 | ~12 min |68| **IV: The Close** | Action plan, textbook link, final quote | 4-6 | ~8 min |6970**Target: 25-35 slides for a 50-60 minute lecture.** At ~1.5 min/slide average. Fewer slides = more speaker time per slide = more engaging.7172Present the proposed structure to the user for approval before generating.7374### Step 3: Design the Visual System7576Extract or create a color palette from the textbook's CLAUDE.md:7778```javascript79const C = {80 primary: "XXXXXX", // From CLAUDE.md palette81 primaryDark: "XXXXXX",82 primaryLight: "XXXXXX",83 accent: "XXXXXX", // Highlight color84 white: "FFFFFF",85 offWhite: "F5F5F5",86 black: "212121",87 gray: "757575",88 red: "C62828", // For "before" / negative examples89 green: "2E7D32", // For "after" / positive examples90};91```9293**Typography:**94- Title font: Georgia (or serif from CLAUDE.md)95- Body font: Calibri (or sans-serif from CLAUDE.md)96- Title size: 32-44pt97- Body size: 14-20pt (never below 13pt)9899**Layout rules:**100- No more than 7 words per line of body text101- One idea per slide102- Dark backgrounds (primary dark) for section dividers, title, close103- Light backgrounds (white) for content slides104- Accent color for emphasis bars, numbers, highlights105106### Step 4: Generate the Presentation107108Create a Node.js script that uses pptxgenjs to generate the .pptx file. Read `references/slide-patterns.md` for the reusable slide pattern library.109110**Slide categories and their patterns:**1111121. **Title slide** — dark bg, large title, subtitle, author, accent bar1132. **Section divider** — dark bg, large text, subtitle, accent bar1143. **Big number** — dark bg, one massive stat (80-120pt), context below1154. **Before/After comparison** — two columns, red accent (before) vs green (after)1165. **Framework visual** — shapes/diagrams illustrating a model (pyramid, stages, pillars)1176. **Evidence stack** — 3 cards with accent bars showing research findings1187. **Interactive beat** — light bg, challenge prompt in a card, instructions1198. **Quote** — dark bg, large italic text, attribution1209. **Action items** — numbered circles with titles and descriptions12110. **Resource/CTA** — textbook link, QR code placeholder, stats122123### Step 5: Write Speaker Notes124125Every slide gets detailed speaker notes. These are the real script — the slides are just visual anchors. Notes include:126127- **TIMING**: Cumulative minutes (e.g., "TIMING: 15:00")128- **SAY**: The exact narrative to deliver (2-4 sentences, conversational)129- **META-MOMENT**: Where the speaker reveals the framework AFTER demonstrating it (e.g., "Notice what I just did? That was Klein's Dilemma stage.")130- **TRANSITION**: The bridge sentence to the next slide131- **AUDIENCE PULSE**: When to pause, ask a question, or let silence work132133### Step 6: Generate and Verify1341351. Run the Node.js script to generate the .pptx1362. Verify slide count matches the design1373. Extract text with `python -m markitdown output.pptx` to confirm content1384. Report the result to the user with slide count and timing estimate139140## Output141142The presentation file should be saved to:143```144{project-root}/presentation/{kebab-case-title}.pptx145```146147Along with the generation script:148```149{project-root}/presentation/generate.js150```151152## Adapting for Different Subjects153154This skill works for ANY intelligent textbook, not just communication. The key adaptations:155156- **Subject-specific stories**: Open with a story from the textbook's domain (engineering, science, business)157- **Framework names**: Use whatever frameworks the textbook teaches (not just Minto, Klein, etc.)158- **Color palette**: Derive from the textbook's CLAUDE.md159- **Audience**: Match the course-description.md target audience160- **Interactive beats**: Design exercises relevant to the subject matter161162The 4-act structure and McLuhan principle remain constant regardless of subject.163164## References165166- `references/slide-patterns.md` — Reusable pptxgenjs code patterns for each slide type167- `references/speaker-notes-guide.md` — How to write effective speaker notes168169## Best Practices1701711. **Cut aggressively**: If a slide doesn't change understanding, delete it. The Dilution Effect applies to slide decks too.1722. **Story first, framework second**: Always demonstrate a principle through a story or example before naming the framework.1733. **One idea per slide**: If you need two sentences to explain what a slide is about, split it into two slides.1744. **Speaker notes ARE the presentation**: The slides are visual anchors. The speaker's narrative, pauses, and meta-moments are where learning happens.1755. **Test the McLuhan principle**: For every slide, ask "Is this slide itself an example of what it teaches?" If not, redesign it.