PPTX creation, editing, and analysis
Overview
A user may ask you to create, edit, or analyze the contents of a .pptx file. A .pptx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks.
Reading and analyzing content
Text extraction
If you just need to read the text contents of a presentation, you should convert the document to markdown:
# Convert document to markdown
python -m markitdown path-to-file.pptx
Raw XML access
You need raw XML access for: comments, speaker notes, slide layouts, animations, design elements, and complex formatting. For any of these features, you'll need to unpack a presentation and read its raw XML contents.
Unpacking a file
python ooxml/scripts/unpack.py <office_file> <output_dir>
Note: Resolve script paths from this skill directory. Prefer $SKILLS_ROOT/pptx/ooxml/scripts/unpack.py when $SKILLS_ROOT is available; otherwise resolve ooxml/scripts/unpack.py relative to this SKILL.md file's directory. Do not assume a workspace-relative skills/pptx/... path.
Key file structures
ppt/presentation.xml - Main presentation metadata and slide references
ppt/slides/slide{N}.xml - Individual slide contents (slide1.xml, slide2.xml, etc.)
ppt/notesSlides/notesSlide{N}.xml - Speaker notes for each slide
ppt/comments/modernComment_*.xml - Comments for specific slides
ppt/slideLayouts/ - Layout templates for slides
ppt/slideMasters/ - Master slide templates
ppt/theme/ - Theme and styling information
ppt/media/ - Images and other media files
Typography and color extraction
When given an example design to emulate: Always analyze the presentation's typography and colors first using the methods below:
- Read theme file: Check
ppt/theme/theme1.xml for colors (<a:clrScheme>) and fonts (<a:fontScheme>)
- Sample slide content: Examine
ppt/slides/slide1.xml for actual font usage (<a:rPr>) and colors
- Search for patterns: Use grep to find color (
<a:solidFill>, <a:srgbClr>) and font references across all XML files
Creating a new PowerPoint presentation without a template
When creating a new PowerPoint presentation from scratch, use the html2pptx workflow to convert HTML slides to PowerPoint with accurate positioning.
Design Principles
CRITICAL: Before creating any presentation, analyze the content and choose appropriate design elements:
- Consider the subject matter: What is this presentation about? What tone, industry, or mood does it suggest?
- Check for branding: If the user mentions a company/organization, consider their brand colors and identity
- Match palette to content: Select colors that reflect the subject
- State your approach: Explain your design choices before writing code
Requirements:
- ✅ State your content-informed design approach BEFORE writing code
- ✅ Use web-safe fonts only: Arial, Helvetica, Times New Roman, Georgia, Courier New, Verdana, Tahoma, Trebuchet MS, Impact
- ✅ Create clear visual hierarchy through size, weight, and color
- ✅ Ensure readability: strong contrast, appropriately sized text, clean alignment
- ✅ Be consistent: repeat patterns, spacing, and visual language across slides
Color Palette Selection
Choosing colors creatively:
- Think beyond defaults: What colors genuinely match this specific topic? Avoid autopilot choices.
- Consider multiple angles: Topic, industry, mood, energy level, target audience, brand identity (if mentioned)
- Be adventurous: Try unexpected combinations - a healthcare presentation doesn't have to be green, finance doesn't have to be navy
- Build your palette: Pick 3-5 colors that work together (dominant colors + supporting tones + accent)
- Ensure contrast: Text must be clearly readable on backgrounds
Example color palettes (use these to spark creativity - choose one, adapt it, or create your own):
- Classic Blue: Deep navy (#1C2833), slate gray (#2E4053), silver (#AAB7B8), off-white (#F4F6F6)
- Teal & Coral: Teal (#5EA8A7), deep teal (#277884), coral (#FE4447), white (#FFFFFF)
- Bold Red: Red (#C0392B), bright red (#E74C3C), orange (#F39C12), yellow (#F1C40F), green (#2ECC71)
- Warm Blush: Mauve (#A49393), blush (#EED6D3), rose (#E8B4B8), cream (#FAF7F2)
- Burgundy Luxury: Burgundy (#5D1D2E), crimson (#951233), rust (#C15937), gold (#997929)
- Deep Purple & Emerald: Purple (#B165FB), dark blue (#181B24), emerald (#40695B), white (#FFFFFF)
- Cream & Forest Green: Cream (#FFE1C7), forest green (#40695B), white (#FCFCFC)
- Pink & Purple: Pink (#F8275B), coral (#FF574A), rose (#FF737D), purple (#3D2F68)
- Lime & Plum: Lime (#C5DE82), plum (#7C3A5F), coral (#FD8C6E), blue-gray (#98ACB5)
- Black & Gold: Gold (#BF9A4A), black (#000000), cream (#F4F6F6)
- Sage & Terracotta: Sage (#87A96B), terracotta (#E07A5F), cream (#F4F1DE), charcoal (#2C2C2C)
- Charcoal & Red: Charcoal (#292929), red (#E33737), light gray (#CCCBCB)
- Vibrant Orange: Orange (#F96D00), light gray (#F2F2F2), charcoal (#222831)
- Forest Green: Black (#191A19), green (#4E9F3D), dark green (#1E5128), white (#FFFFFF)
- Retro Rainbow: Purple (#722880), pink (#D72D51), orange (#EB5C18), amber (#F08800), gold (#DEB600)
- Vintage Earthy: Mustard (#E3B448), sage (#CBD18F), forest green (#3A6B35), cream (#F4F1DE)
- Coastal Rose: Old rose (#AD7670), beaver (#B49886), eggshell (#F3ECDC), ash gray (#BFD5BE)
- Orange & Turquoise: Light orange (#FC993E), grayish turquoise (#667C6F), white (#FCFCFC)
Visual Details Options
Geometric Patterns:
- Diagonal section dividers instead of horizontal
- Asymmetric column widths (30/70, 40/60, 25/75)
- Rotated text headers at 90° or 270°
- Circular/hexagonal frames for images
- Triangular accent shapes in corners
- Overlapping shapes for depth
Border & Frame Treatments:
- Thick single-color borders (10-20pt) on one side only
- Double-line borders with contrasting colors
- Corner brackets instead of full frames
- L-shaped borders (top+left or bottom+right)
- Underline accents beneath headers (3-5pt thick)
Typography Treatments:
- Extreme size contrast (72pt headlines vs 11pt body)
- All-caps headers with wide letter spacing
- Numbered sections in oversized display type
- Monospace (Courier New) for data/stats/technical content
- Condensed fonts (Arial Narrow) for dense information
- Outlined text for emphasis
Chart & Data Styling:
- Monochrome charts with single accent color for key data
- Horizontal bar charts instead of vertical
- Dot plots instead of bar charts
- Minimal gridlines or none at all
- Data labels directly on elements (no legends)
- Oversized numbers for key metrics
Layout Innovations:
- Full-bleed images with text overlays
- Sidebar column (20-30% width) for navigation/context
- Modular grid systems (3×3, 4×4 blocks)
- Z-pattern or F-pattern content flow
- Floating text boxes over colored shapes
- Magazine-style multi-column layouts
Background Treatments:
- Solid color blocks occupying 40-60% of slide
- Gradient fills (vertical or diagonal only)
- Split backgrounds (two colors, diagonal or vertical)
- Edge-to-edge color bands
- Negative space as a design element
Layout Tips
When creating slides with charts or tables:
- Two-column layout (PREFERRED): Use a header spanning the full width, then two columns below - text/bullets in one column and the featured content in the other. This provides better balance and makes charts/tables more readable. Use flexbox with unequal column widths (e.g., 40%/60% split) to optimize space for each content type.
- Full-slide layout: Let the featured content (chart/table) take up the entire slide for maximum impact and readability
- NEVER vertically stack: Do not place charts/tables below text in a single column - this causes poor readability and layout issues
Workflow
- MANDATORY - READ ENTIRE FILE: Read
html2pptx.md from the same directory as this SKILL.md (installed default: $SKILLS_ROOT/pptx/html2pptx.md) completely from start to finish. NEVER set any range limits when reading this file. Read the full file content for detailed syntax, critical formatting rules, and best practices before proceeding with presentation creation.
- Create an HTML file for each slide with proper dimensions (e.g., 720pt × 405pt for 16:9)
- Use
<p>, <h1>-<h6>, <ul>, <ol> for all text content
- Use
class="placeholder" for areas where charts/tables will be added (render with gray background for visibility)
- CRITICAL: Rasterize gradients and icons as PNG images FIRST using Sharp, then reference in HTML
- LAYOUT: For slides with charts/tables/images, use either full-slide layout or two-column layout for better readability
- Create and run a JavaScript file using the
html2pptx.js library to convert HTML slides to PowerPoint and save the presentation
- Use the
html2pptx() function to process each HTML file
- Add charts and tables to placeholder areas using PptxGenJS API
- Save the presentation using
pptx.writeFile()
- Visual validation: Generate thumbnails and inspect for layout issues
- Create thumbnail grid:
python scripts/thumbnail.py output.pptx workspace/thumbnails --cols 4
- Read and carefully examine the thumbnail image for:
- Text cutoff: Text being cut off by header bars, shapes, or slide edges
- Text overlap: Text overlapping with other text or shapes
- Positioning issues: Content too close to slide boundaries or other elements
- Contrast issues: Insufficient contrast between text and backgrounds
- If issues found, adjust HTML margins/spacing/colors and regenerate the presentation
- Repeat until all slides are visually correct
Editing an existing PowerPoint presentation
When edit slides in an existing PowerPoint presentation, you need to work with the raw Office Open XML (OOXML) format. This involves unpacking the .pptx file, editing the XML content, and repacking it.
Workflow
- MANDATORY - READ ENTIRE FILE: Read
ooxml.md from the same directory as this SKILL.md (installed default: $SKILLS_ROOT/pptx/ooxml.md) (~500 lines) completely from start to finish. NEVER set any range limits when reading this file. Read the full file content for detailed guidance on OOXML structure and editing workflows before any presentation editing.
- Unpack the presentation:
python ooxml/scripts/unpack.py <office_file> <output_dir>
- Edit the XML files (primarily
ppt/slides/slide{N}.xml and related files)
- CRITICAL: Validate immediately after each edit and fix any validation errors before proceeding:
python ooxml/scripts/validate.py <dir> --original <file>
- Pack the final presentation:
python ooxml/scripts/pack.py <input_directory> <office_file>
Creating a new PowerPoint presentation using a template
When you need to create a presentation that follows an existing template's design, you'll need to duplicate and re-arrange template slides before then replacing placeholder context.
Workflow
Extract template text AND create visual thumbnail grid:
- Extract text:
python -m markitdown template.pptx > template-content.md
- Read
template-content.md: Read the entire file to understand the contents of the template presentation. NEVER set any range limits when reading this file.
- Create thumbnail grids:
python scripts/thumbnail.py template.pptx
- See Creating Thumbnail Grids section for more details
Analyze template and save inventory to a file:
- Visual Analysis: Review thumbnail grid(s) to understand slide layouts, design patterns, and visual structure
- Create and save a template inventory file at
template-inventory.md containing:# Template Inventory Analysis
**Total Slides: [count]**
**IMPORTANT: Slides are 0-indexed (first slide = 0, last slide = count-1)**
## [Category Name]
- Slide 0: [Layout code if available] - Description/purpose
- Slide 1: [Layout code] - Description/purpose
- Slide 2: [Layout code] - Description/purpose
[... EVERY slide must be listed individually with its index ...]
- Using the thumbnail grid: Reference the visual thumbnails to identify:
- Layout patterns (title slides, content layouts, section dividers)
- Image placeholder locations and counts
- Design consistency across slide groups
- Visual hierarchy and structure
- This inventory file is REQUIRED for selecting appropriate templates in the next step
Create presentation outline based on template inventory:
- Review available templates from step 2.
- Choose an intro or title template for the first slide. This should be one of the first templates.
- Choose safe, text-based layouts for the other slides.
- CRITICAL: Match layout structure to actual content:
- Single-column layouts: Use for unified narrative or single topic
- Two-column layouts: Use ONLY when you have exactly 2 distinct items/concepts
- Three-column layouts: Use ONLY when you have exactly 3 distinct items/concepts
- Image + text layouts: Use ONLY when you have actual images to insert
- Quote layouts: Use ONLY for actual quotes from people (with attribution), never for emphasis
- Never use layouts with more placeholders than you have content
- If you have 2 items, don't force them into a 3-column layout
- If you have 4+ items, consider breaking into multiple slides or using a list format
- Count your actual content pieces BEFORE selecting the layout
- Verify each placeholder in the chosen layout will be filled with meaningful content
- Select one option representing the best layout for each content section.
- Save
outline.md with content AND template mapping that leverages available designs
- Example template mapping:
# Template slides to use (0-based indexing)
# WARNING: Verify indices are within range! Template with 73 slides has indices 0-72
# Mapping: slide numbers from outline -> template slide indices
template_mapping = [
0, # Use slide 0 (Title/Cover)
34, # Use slide 34 (B1: Title and body)
34, # Use slide 34 again (duplicate for second B1)
50, # Use slide 50 (E1: Quote)
54, # Use slide 54 (F2: Closing + Text)
]
Duplicate, reorder, and delete slides using rearrange.py:
- Use the
scripts/rearrange.py script to create a new presentation with slides in the desired order:python scripts/rearrange.py template.pptx working.pptx 0,34,34,50,52
- The script handles duplicating repeated slides, deleting unused slides, and reordering automatically
- Slide indices are 0-based (first slide is 0, second is 1, etc.)
- The same slide index can appear multiple times to duplicate that slide
Extract ALL text using the inventory.py script:
Run inventory extraction:
python scripts/inventory.py working.pptx text-inventory.json
Read text-inventory.json: Read the entire text-inventory.json file to understand all shapes and their properties. NEVER set any range limits when reading this file.
The inventory JSON structure:
{
"slide-0": {
"shape-0": {
"placeholder_type": "TITLE", // or null for non-placeholders
"left": 1.5, // position in inches
"top": 2.0,
"width": 7.5,
"height": 1.2,
"paragraphs": [
{
"text": "Paragraph text",
// Optional properties (only included when non-default):
"bullet": true, // explicit bullet detected
"level": 0, // only included when bullet is true
"alignment": "CENTER", // CENTER, RIGHT (not LEFT)
"space_before": 10.0, // space before paragraph in points
"space_after": 6.0, // space after paragraph in points
"line_spacing": 22.4, // line spacing in points
"font_name": "Arial", // from first run
"font_size": 14.0, // in points
"bold": true,
"italic": false,
"underline": false,
"color": "FF0000" // RGB color
}
]
}
}
}
Key features:
- Slides: Named as "slide-0", "slide-1", etc.
- Shapes: Ordered by visual position (top-to-bottom, left-to-right) as "shape-0", "shape-1", etc.
- Placeholder types: TITLE, CENTER_TITLE, SUBTITLE, BODY, OBJECT, or null
- Default font size:
default_font_size in points extracted from layout placeholders (when available)
- Slide numbers are filtered: Shapes with SLIDE_NUMBER placeholder type are automatically excluded from inventory
- Bullets: When
bullet: true, level is always included (even if 0)
- Spacing:
space_before, space_after, and line_spacing in points (only included when set)
- Colors:
color for RGB (e.g., "FF0000"), theme_color for theme colors (e.g., "DARK_1")
- Properties: Only non-default values are included in the output
Generate replacement text and save the data to a JSON file
Based on the text inventory from the previous step:
- CRITICAL: First verify which shapes exist in the inventory - only reference shapes that are actually present
- VALIDATION: The replace.py script will validate that all shapes in your replacement JSON exist in the inventory
- If you reference a non-existent shape, you'll get an error showing available shapes
- If you reference a non-existent slide, you'll get an error indicating the slide doesn't exist
- All validation errors are shown at once before the script exits
- IMPORTANT: The replace.py script uses inventory.py internally to identify ALL text shapes
- AUTOMATIC CLEARING: ALL text shapes from the inventory will be cleared unless you provide "paragraphs" for them
- Add a "paragraphs" field to shapes that need content (not "replacement_paragraphs")
- Shapes without "paragraphs" in the replacement JSON will have their text cleared automatically
- Paragraphs with bullets will be automatically left aligned. Don't set the
alignment property on when "bullet": true
- Generate appropriate replacement content for placeholder text
- Use shape size to determine appropriate content length
- CRITICAL: Include paragraph properties from the original inventory - don't just provide text
- IMPORTANT: When bullet: true, do NOT include bullet symbols (•, -, *) in text - they're added automatically
- ESSENTIAL FORMATTING RULES:
- Headers/titles should typically have
"bold": true
- List items should have
"bullet": true, "level": 0 (level is required when bullet is true)
- Preserve any alignment properties (e.g.,
"alignment": "CENTER" for centered text)
- Include font properties when different from default (e.g.,
"font_size": 14.0, "font_name": "Lora")
- Colors: Use
"color": "FF0000" for RGB or "theme_color": "DARK_1" for theme colors
- The replacement script expects properly formatted paragraphs, not just text strings
- Overlapping shapes: Prefer shapes with larger default_font_size or more appropriate placeholder_type
- Save the updated inventory with replacements to
replacement-text.json
- WARNING: Different template layouts have different shape counts - always check the actual inventory before creating replacements
Example paragraphs field showing proper formatting:
"paragraphs": [
{
"text": "New presentation title text",
"alignment": "CENTER",
"bold": true
},
{
"text": "Section Header",
"bold": true
},
{
"text": "First bullet point without bullet symbol",
"bullet": true,
"level": 0
},
{
"text": "Red colored text",
"color": "FF0000"
},
{
"text": "Theme colored text",
"theme_color": "DARK_1"
},
{
"text": "Regular paragraph text without special formatting"
}
]
Shapes not listed in the replacement JSON are automatically cleared:
{
"slide-0": {
"shape-0": {
"paragraphs": [...] // This shape gets new text
}
// shape-1 and shape-2 from inventory will be cleared automatically
}
}
Common formatting patterns for presentations:
- Title slides: Bold text, sometimes centered
- Section headers within slides: Bold text
- Bullet lists: Each item needs
"bullet": true, "level": 0
- Body text: Usually no special properties needed
- Quotes: May have special alignment or font properties
Apply replacements using the replace.py script
python scripts/replace.py working.pptx replacement-text.json output.pptx
The script will:
- First extract the inventory of ALL text shapes using functions from inventory.py
- Validate that all shapes in the replacement JSON exist in the inventory
- Clear text from ALL shapes identified in the inventory
- Apply new text only to shapes with "paragraphs" defined in the replacement JSON
- Preserve formatting by applying paragraph properties from the JSON
- Handle bullets, alignment, font properties, and colors automatically
- Save the updated presentation
Example validation errors:
ERROR: Invalid shapes in replacement JSON:
- Shape 'shape-99' not found on 'slide-0'. Available shapes: shape-0, shape-1, shape-4
- Slide 'slide-999' not found in inventory
ERROR: Replacement text made overflow worse in these shapes:
- slide-0/shape-2: overflow worsened by 1.25" (was 0.00", now 1.25")
Creating Thumbnail Grids
To create visual thumbnail grids of PowerPoint slides for quick analysis and reference:
python scripts/thumbnail.py template.pptx [output_prefix]
Features:
- Creates:
thumbnails.jpg (or thumbnails-1.jpg, thumbnails-2.jpg, etc. for large decks)
- Default: 5 columns, max 30 slides per grid (5×6)
- Custom prefix:
python scripts/thumbnail.py template.pptx my-grid
- Note: The output prefix should include the path if you want output in a specific directory (e.g.,
workspace/my-grid)
- Adjust columns:
--cols 4 (range: 3-6, affects slides per grid)
- Grid limits: 3 cols = 12 slides/grid, 4 cols = 20, 5 cols = 30, 6 cols = 42
- Slides are zero-indexed (Slide 0, Slide 1, etc.)
Use cases:
- Template analysis: Quickly understand slide layouts and design patterns
- Content review: Visual overview of entire presentation
- Navigation reference: Find specific slides by their visual appearance
- Quality check: Verify all slides are properly formatted
Examples:
# Basic usage
python scripts/thumbnail.py presentation.pptx
# Combine options: custom name, columns
python scripts/thumbnail.py template.pptx analysis --cols 4
Converting Slides to Images
To visually analyze PowerPoint slides, convert them to images using a two-step process:
Convert PPTX to PDF:
soffice --headless --convert-to pdf template.pptx
Convert PDF pages to JPEG images:
pdftoppm -jpeg -r 150 template.pdf slide
This creates files like slide-1.jpg, slide-2.jpg, etc.
Options:
-r 150: Sets resolution to 150 DPI (adjust for quality/size balance)
-jpeg: Output JPEG format (use -png for PNG if preferred)
-f N: First page to convert (e.g., -f 2 starts from page 2)
-l N: Last page to convert (e.g., -l 5 stops at page 5)
slide: Prefix for output files
Example for specific range:
pdftoppm -jpeg -r 150 -f 2 -l 5 template.pdf slide # Converts only pages 2-5
Code Style Guidelines
IMPORTANT: When generating code for PPTX operations:
- Write concise code
- Avoid verbose variable names and redundant operations
- Avoid unnecessary print statements
Dependencies
Required dependencies (should already be installed):
- markitdown:
pip install "markitdown[pptx]" (for text extraction from presentations)
- pptxgenjs:
npm install -g pptxgenjs (for creating presentations via html2pptx)
- playwright:
npm install -g playwright (for HTML rendering in html2pptx)
- react-icons:
npm install -g react-icons react react-dom (for icons)
- sharp:
npm install -g sharp (for SVG rasterization and image processing)
- LibreOffice:
sudo apt-get install libreoffice (for PDF conversion)
- Poppler:
sudo apt-get install poppler-utils (for pdftoppm to convert PDF to images)
- defusedxml:
pip install defusedxml (for secure XML parsing)
1---
2name: pptx
3description: "Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks"
4license: Proprietary. LICENSE.txt has complete terms
5official: true
6metadata:
7 source: https://skillmd.com/skills/netease-youdao/pptx
8---
9
10# PPTX creation, editing, and analysis
11
12## Overview
13
14A user may ask you to create, edit, or analyze the contents of a .pptx file. A .pptx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks.
15
16## Reading and analyzing content
17
18### Text extraction
19If you just need to read the text contents of a presentation, you should convert the document to markdown:
20
21```bash
22# Convert document to markdown
23python -m markitdown path-to-file.pptx
24```
25
26### Raw XML access
27You need raw XML access for: comments, speaker notes, slide layouts, animations, design elements, and complex formatting. For any of these features, you'll need to unpack a presentation and read its raw XML contents.
28
29#### Unpacking a file
30`python ooxml/scripts/unpack.py <office_file> <output_dir>`
31
32**Note**: Resolve script paths from this skill directory. Prefer `$SKILLS_ROOT/pptx/ooxml/scripts/unpack.py` when `$SKILLS_ROOT` is available; otherwise resolve `ooxml/scripts/unpack.py` relative to this `SKILL.md` file's directory. Do not assume a workspace-relative `skills/pptx/...` path.
33
34#### Key file structures
35* `ppt/presentation.xml` - Main presentation metadata and slide references
36* `ppt/slides/slide{N}.xml` - Individual slide contents (slide1.xml, slide2.xml, etc.)
37* `ppt/notesSlides/notesSlide{N}.xml` - Speaker notes for each slide
38* `ppt/comments/modernComment_*.xml` - Comments for specific slides
39* `ppt/slideLayouts/` - Layout templates for slides
40* `ppt/slideMasters/` - Master slide templates
41* `ppt/theme/` - Theme and styling information
42* `ppt/media/` - Images and other media files
43
44#### Typography and color extraction
45**When given an example design to emulate**: Always analyze the presentation's typography and colors first using the methods below:
461. **Read theme file**: Check `ppt/theme/theme1.xml` for colors (`<a:clrScheme>`) and fonts (`<a:fontScheme>`)
472. **Sample slide content**: Examine `ppt/slides/slide1.xml` for actual font usage (`<a:rPr>`) and colors
483. **Search for patterns**: Use grep to find color (`<a:solidFill>`, `<a:srgbClr>`) and font references across all XML files
49
50## Creating a new PowerPoint presentation **without a template**
51
52When creating a new PowerPoint presentation from scratch, use the **html2pptx** workflow to convert HTML slides to PowerPoint with accurate positioning.
53
54### Design Principles
55
56**CRITICAL**: Before creating any presentation, analyze the content and choose appropriate design elements:
571. **Consider the subject matter**: What is this presentation about? What tone, industry, or mood does it suggest?
582. **Check for branding**: If the user mentions a company/organization, consider their brand colors and identity
593. **Match palette to content**: Select colors that reflect the subject
604. **State your approach**: Explain your design choices before writing code
61
62**Requirements**:
63- ✅ State your content-informed design approach BEFORE writing code
64- ✅ Use web-safe fonts only: Arial, Helvetica, Times New Roman, Georgia, Courier New, Verdana, Tahoma, Trebuchet MS, Impact
65- ✅ Create clear visual hierarchy through size, weight, and color
66- ✅ Ensure readability: strong contrast, appropriately sized text, clean alignment
67- ✅ Be consistent: repeat patterns, spacing, and visual language across slides
68
69#### Color Palette Selection
70
71**Choosing colors creatively**:
72- **Think beyond defaults**: What colors genuinely match this specific topic? Avoid autopilot choices.
73- **Consider multiple angles**: Topic, industry, mood, energy level, target audience, brand identity (if mentioned)
74- **Be adventurous**: Try unexpected combinations - a healthcare presentation doesn't have to be green, finance doesn't have to be navy
75- **Build your palette**: Pick 3-5 colors that work together (dominant colors + supporting tones + accent)
76- **Ensure contrast**: Text must be clearly readable on backgrounds
77
78**Example color palettes** (use these to spark creativity - choose one, adapt it, or create your own):
79
801. **Classic Blue**: Deep navy (#1C2833), slate gray (#2E4053), silver (#AAB7B8), off-white (#F4F6F6)
812. **Teal & Coral**: Teal (#5EA8A7), deep teal (#277884), coral (#FE4447), white (#FFFFFF)
823. **Bold Red**: Red (#C0392B), bright red (#E74C3C), orange (#F39C12), yellow (#F1C40F), green (#2ECC71)
834. **Warm Blush**: Mauve (#A49393), blush (#EED6D3), rose (#E8B4B8), cream (#FAF7F2)
845. **Burgundy Luxury**: Burgundy (#5D1D2E), crimson (#951233), rust (#C15937), gold (#997929)
856. **Deep Purple & Emerald**: Purple (#B165FB), dark blue (#181B24), emerald (#40695B), white (#FFFFFF)
867. **Cream & Forest Green**: Cream (#FFE1C7), forest green (#40695B), white (#FCFCFC)
878. **Pink & Purple**: Pink (#F8275B), coral (#FF574A), rose (#FF737D), purple (#3D2F68)
889. **Lime & Plum**: Lime (#C5DE82), plum (#7C3A5F), coral (#FD8C6E), blue-gray (#98ACB5)
8910. **Black & Gold**: Gold (#BF9A4A), black (#000000), cream (#F4F6F6)
9011. **Sage & Terracotta**: Sage (#87A96B), terracotta (#E07A5F), cream (#F4F1DE), charcoal (#2C2C2C)
9112. **Charcoal & Red**: Charcoal (#292929), red (#E33737), light gray (#CCCBCB)
9213. **Vibrant Orange**: Orange (#F96D00), light gray (#F2F2F2), charcoal (#222831)
9314. **Forest Green**: Black (#191A19), green (#4E9F3D), dark green (#1E5128), white (#FFFFFF)
9415. **Retro Rainbow**: Purple (#722880), pink (#D72D51), orange (#EB5C18), amber (#F08800), gold (#DEB600)
9516. **Vintage Earthy**: Mustard (#E3B448), sage (#CBD18F), forest green (#3A6B35), cream (#F4F1DE)
9617. **Coastal Rose**: Old rose (#AD7670), beaver (#B49886), eggshell (#F3ECDC), ash gray (#BFD5BE)
9718. **Orange & Turquoise**: Light orange (#FC993E), grayish turquoise (#667C6F), white (#FCFCFC)
98
99#### Visual Details Options
100
101**Geometric Patterns**:
102- Diagonal section dividers instead of horizontal
103- Asymmetric column widths (30/70, 40/60, 25/75)
104- Rotated text headers at 90° or 270°
105- Circular/hexagonal frames for images
106- Triangular accent shapes in corners
107- Overlapping shapes for depth
108
109**Border & Frame Treatments**:
110- Thick single-color borders (10-20pt) on one side only
111- Double-line borders with contrasting colors
112- Corner brackets instead of full frames
113- L-shaped borders (top+left or bottom+right)
114- Underline accents beneath headers (3-5pt thick)
115
116**Typography Treatments**:
117- Extreme size contrast (72pt headlines vs 11pt body)
118- All-caps headers with wide letter spacing
119- Numbered sections in oversized display type
120- Monospace (Courier New) for data/stats/technical content
121- Condensed fonts (Arial Narrow) for dense information
122- Outlined text for emphasis
123
124**Chart & Data Styling**:
125- Monochrome charts with single accent color for key data
126- Horizontal bar charts instead of vertical
127- Dot plots instead of bar charts
128- Minimal gridlines or none at all
129- Data labels directly on elements (no legends)
130- Oversized numbers for key metrics
131
132**Layout Innovations**:
133- Full-bleed images with text overlays
134- Sidebar column (20-30% width) for navigation/context
135- Modular grid systems (3×3, 4×4 blocks)
136- Z-pattern or F-pattern content flow
137- Floating text boxes over colored shapes
138- Magazine-style multi-column layouts
139
140**Background Treatments**:
141- Solid color blocks occupying 40-60% of slide
142- Gradient fills (vertical or diagonal only)
143- Split backgrounds (two colors, diagonal or vertical)
144- Edge-to-edge color bands
145- Negative space as a design element
146
147### Layout Tips
148**When creating slides with charts or tables:**
149- **Two-column layout (PREFERRED)**: Use a header spanning the full width, then two columns below - text/bullets in one column and the featured content in the other. This provides better balance and makes charts/tables more readable. Use flexbox with unequal column widths (e.g., 40%/60% split) to optimize space for each content type.
150- **Full-slide layout**: Let the featured content (chart/table) take up the entire slide for maximum impact and readability
151- **NEVER vertically stack**: Do not place charts/tables below text in a single column - this causes poor readability and layout issues
152
153### Workflow
1541. **MANDATORY - READ ENTIRE FILE**: Read `html2pptx.md` from the same directory as this `SKILL.md` (installed default: `$SKILLS_ROOT/pptx/html2pptx.md`) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for detailed syntax, critical formatting rules, and best practices before proceeding with presentation creation.
1552. Create an HTML file for each slide with proper dimensions (e.g., 720pt × 405pt for 16:9)
156 - Use `<p>`, `<h1>`-`<h6>`, `<ul>`, `<ol>` for all text content
157 - Use `class="placeholder"` for areas where charts/tables will be added (render with gray background for visibility)
158 - **CRITICAL**: Rasterize gradients and icons as PNG images FIRST using Sharp, then reference in HTML
159 - **LAYOUT**: For slides with charts/tables/images, use either full-slide layout or two-column layout for better readability
1603. Create and run a JavaScript file using the [`html2pptx.js`](scripts/html2pptx.js) library to convert HTML slides to PowerPoint and save the presentation
161 - Use the `html2pptx()` function to process each HTML file
162 - Add charts and tables to placeholder areas using PptxGenJS API
163 - Save the presentation using `pptx.writeFile()`
1644. **Visual validation**: Generate thumbnails and inspect for layout issues
165 - Create thumbnail grid: `python scripts/thumbnail.py output.pptx workspace/thumbnails --cols 4`
166 - Read and carefully examine the thumbnail image for:
167 - **Text cutoff**: Text being cut off by header bars, shapes, or slide edges
168 - **Text overlap**: Text overlapping with other text or shapes
169 - **Positioning issues**: Content too close to slide boundaries or other elements
170 - **Contrast issues**: Insufficient contrast between text and backgrounds
171 - If issues found, adjust HTML margins/spacing/colors and regenerate the presentation
172 - Repeat until all slides are visually correct
173
174## Editing an existing PowerPoint presentation
175
176When edit slides in an existing PowerPoint presentation, you need to work with the raw Office Open XML (OOXML) format. This involves unpacking the .pptx file, editing the XML content, and repacking it.
177
178### Workflow
1791. **MANDATORY - READ ENTIRE FILE**: Read `ooxml.md` from the same directory as this `SKILL.md` (installed default: `$SKILLS_ROOT/pptx/ooxml.md`) (~500 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for detailed guidance on OOXML structure and editing workflows before any presentation editing.
1802. Unpack the presentation: `python ooxml/scripts/unpack.py <office_file> <output_dir>`
1813. Edit the XML files (primarily `ppt/slides/slide{N}.xml` and related files)
1824. **CRITICAL**: Validate immediately after each edit and fix any validation errors before proceeding: `python ooxml/scripts/validate.py <dir> --original <file>`
1835. Pack the final presentation: `python ooxml/scripts/pack.py <input_directory> <office_file>`
184
185## Creating a new PowerPoint presentation **using a template**
186
187When you need to create a presentation that follows an existing template's design, you'll need to duplicate and re-arrange template slides before then replacing placeholder context.
188
189### Workflow
1901. **Extract template text AND create visual thumbnail grid**:
191 * Extract text: `python -m markitdown template.pptx > template-content.md`
192 * Read `template-content.md`: Read the entire file to understand the contents of the template presentation. **NEVER set any range limits when reading this file.**
193 * Create thumbnail grids: `python scripts/thumbnail.py template.pptx`
194 * See [Creating Thumbnail Grids](#creating-thumbnail-grids) section for more details
195
1962. **Analyze template and save inventory to a file**:
197 * **Visual Analysis**: Review thumbnail grid(s) to understand slide layouts, design patterns, and visual structure
198 * Create and save a template inventory file at `template-inventory.md` containing:
199 ```markdown
200 # Template Inventory Analysis
201 **Total Slides: [count]**
202 **IMPORTANT: Slides are 0-indexed (first slide = 0, last slide = count-1)**
203
204 ## [Category Name]
205 - Slide 0: [Layout code if available] - Description/purpose
206 - Slide 1: [Layout code] - Description/purpose
207 - Slide 2: [Layout code] - Description/purpose
208 [... EVERY slide must be listed individually with its index ...]
209 ```
210 * **Using the thumbnail grid**: Reference the visual thumbnails to identify:
211 - Layout patterns (title slides, content layouts, section dividers)
212 - Image placeholder locations and counts
213 - Design consistency across slide groups
214 - Visual hierarchy and structure
215 * This inventory file is REQUIRED for selecting appropriate templates in the next step
216
2173. **Create presentation outline based on template inventory**:
218 * Review available templates from step 2.
219 * Choose an intro or title template for the first slide. This should be one of the first templates.
220 * Choose safe, text-based layouts for the other slides.
221 * **CRITICAL: Match layout structure to actual content**:
222 - Single-column layouts: Use for unified narrative or single topic
223 - Two-column layouts: Use ONLY when you have exactly 2 distinct items/concepts
224 - Three-column layouts: Use ONLY when you have exactly 3 distinct items/concepts
225 - Image + text layouts: Use ONLY when you have actual images to insert
226 - Quote layouts: Use ONLY for actual quotes from people (with attribution), never for emphasis
227 - Never use layouts with more placeholders than you have content
228 - If you have 2 items, don't force them into a 3-column layout
229 - If you have 4+ items, consider breaking into multiple slides or using a list format
230 * Count your actual content pieces BEFORE selecting the layout
231 * Verify each placeholder in the chosen layout will be filled with meaningful content
232 * Select one option representing the **best** layout for each content section.
233 * Save `outline.md` with content AND template mapping that leverages available designs
234 * Example template mapping:
235 ```
236 # Template slides to use (0-based indexing)
237 # WARNING: Verify indices are within range! Template with 73 slides has indices 0-72
238 # Mapping: slide numbers from outline -> template slide indices
239 template_mapping = [
240 0, # Use slide 0 (Title/Cover)
241 34, # Use slide 34 (B1: Title and body)
242 34, # Use slide 34 again (duplicate for second B1)
243 50, # Use slide 50 (E1: Quote)
244 54, # Use slide 54 (F2: Closing + Text)
245 ]
246 ```
247
2484. **Duplicate, reorder, and delete slides using `rearrange.py`**:
249 * Use the `scripts/rearrange.py` script to create a new presentation with slides in the desired order:
250 ```bash
251 python scripts/rearrange.py template.pptx working.pptx 0,34,34,50,52
252 ```
253 * The script handles duplicating repeated slides, deleting unused slides, and reordering automatically
254 * Slide indices are 0-based (first slide is 0, second is 1, etc.)
255 * The same slide index can appear multiple times to duplicate that slide
256
2575. **Extract ALL text using the `inventory.py` script**:
258 * **Run inventory extraction**:
259 ```bash
260 python scripts/inventory.py working.pptx text-inventory.json
261 ```
262 * **Read text-inventory.json**: Read the entire text-inventory.json file to understand all shapes and their properties. **NEVER set any range limits when reading this file.**
263
264 * The inventory JSON structure:
265 ```json
266 {
267 "slide-0": {
268 "shape-0": {
269 "placeholder_type": "TITLE", // or null for non-placeholders
270 "left": 1.5, // position in inches
271 "top": 2.0,
272 "width": 7.5,
273 "height": 1.2,
274 "paragraphs": [
275 {
276 "text": "Paragraph text",
277 // Optional properties (only included when non-default):
278 "bullet": true, // explicit bullet detected
279 "level": 0, // only included when bullet is true
280 "alignment": "CENTER", // CENTER, RIGHT (not LEFT)
281 "space_before": 10.0, // space before paragraph in points
282 "space_after": 6.0, // space after paragraph in points
283 "line_spacing": 22.4, // line spacing in points
284 "font_name": "Arial", // from first run
285 "font_size": 14.0, // in points
286 "bold": true,
287 "italic": false,
288 "underline": false,
289 "color": "FF0000" // RGB color
290 }
291 ]
292 }
293 }
294 }
295 ```
296
297 * Key features:
298 - **Slides**: Named as "slide-0", "slide-1", etc.
299 - **Shapes**: Ordered by visual position (top-to-bottom, left-to-right) as "shape-0", "shape-1", etc.
300 - **Placeholder types**: TITLE, CENTER_TITLE, SUBTITLE, BODY, OBJECT, or null
301 - **Default font size**: `default_font_size` in points extracted from layout placeholders (when available)
302 - **Slide numbers are filtered**: Shapes with SLIDE_NUMBER placeholder type are automatically excluded from inventory
303 - **Bullets**: When `bullet: true`, `level` is always included (even if 0)
304 - **Spacing**: `space_before`, `space_after`, and `line_spacing` in points (only included when set)
305 - **Colors**: `color` for RGB (e.g., "FF0000"), `theme_color` for theme colors (e.g., "DARK_1")
306 - **Properties**: Only non-default values are included in the output
307
3086. **Generate replacement text and save the data to a JSON file**
309 Based on the text inventory from the previous step:
310 - **CRITICAL**: First verify which shapes exist in the inventory - only reference shapes that are actually present
311 - **VALIDATION**: The replace.py script will validate that all shapes in your replacement JSON exist in the inventory
312 - If you reference a non-existent shape, you'll get an error showing available shapes
313 - If you reference a non-existent slide, you'll get an error indicating the slide doesn't exist
314 - All validation errors are shown at once before the script exits
315 - **IMPORTANT**: The replace.py script uses inventory.py internally to identify ALL text shapes
316 - **AUTOMATIC CLEARING**: ALL text shapes from the inventory will be cleared unless you provide "paragraphs" for them
317 - Add a "paragraphs" field to shapes that need content (not "replacement_paragraphs")
318 - Shapes without "paragraphs" in the replacement JSON will have their text cleared automatically
319 - Paragraphs with bullets will be automatically left aligned. Don't set the `alignment` property on when `"bullet": true`
320 - Generate appropriate replacement content for placeholder text
321 - Use shape size to determine appropriate content length
322 - **CRITICAL**: Include paragraph properties from the original inventory - don't just provide text
323 - **IMPORTANT**: When bullet: true, do NOT include bullet symbols (•, -, *) in text - they're added automatically
324 - **ESSENTIAL FORMATTING RULES**:
325 - Headers/titles should typically have `"bold": true`
326 - List items should have `"bullet": true, "level": 0` (level is required when bullet is true)
327 - Preserve any alignment properties (e.g., `"alignment": "CENTER"` for centered text)
328 - Include font properties when different from default (e.g., `"font_size": 14.0`, `"font_name": "Lora"`)
329 - Colors: Use `"color": "FF0000"` for RGB or `"theme_color": "DARK_1"` for theme colors
330 - The replacement script expects **properly formatted paragraphs**, not just text strings
331 - **Overlapping shapes**: Prefer shapes with larger default_font_size or more appropriate placeholder_type
332 - Save the updated inventory with replacements to `replacement-text.json`
333 - **WARNING**: Different template layouts have different shape counts - always check the actual inventory before creating replacements
334
335 Example paragraphs field showing proper formatting:
336 ```json
337 "paragraphs": [
338 {
339 "text": "New presentation title text",
340 "alignment": "CENTER",
341 "bold": true
342 },
343 {
344 "text": "Section Header",
345 "bold": true
346 },
347 {
348 "text": "First bullet point without bullet symbol",
349 "bullet": true,
350 "level": 0
351 },
352 {
353 "text": "Red colored text",
354 "color": "FF0000"
355 },
356 {
357 "text": "Theme colored text",
358 "theme_color": "DARK_1"
359 },
360 {
361 "text": "Regular paragraph text without special formatting"
362 }
363 ]
364 ```
365
366 **Shapes not listed in the replacement JSON are automatically cleared**:
367 ```json
368 {
369 "slide-0": {
370 "shape-0": {
371 "paragraphs": [...] // This shape gets new text
372 }
373 // shape-1 and shape-2 from inventory will be cleared automatically
374 }
375 }
376 ```
377
378 **Common formatting patterns for presentations**:
379 - Title slides: Bold text, sometimes centered
380 - Section headers within slides: Bold text
381 - Bullet lists: Each item needs `"bullet": true, "level": 0`
382 - Body text: Usually no special properties needed
383 - Quotes: May have special alignment or font properties
384
3857. **Apply replacements using the `replace.py` script**
386 ```bash
387 python scripts/replace.py working.pptx replacement-text.json output.pptx
388 ```
389
390 The script will:
391 - First extract the inventory of ALL text shapes using functions from inventory.py
392 - Validate that all shapes in the replacement JSON exist in the inventory
393 - Clear text from ALL shapes identified in the inventory
394 - Apply new text only to shapes with "paragraphs" defined in the replacement JSON
395 - Preserve formatting by applying paragraph properties from the JSON
396 - Handle bullets, alignment, font properties, and colors automatically
397 - Save the updated presentation
398
399 Example validation errors:
400 ```
401 ERROR: Invalid shapes in replacement JSON:
402 - Shape 'shape-99' not found on 'slide-0'. Available shapes: shape-0, shape-1, shape-4
403 - Slide 'slide-999' not found in inventory
404 ```
405
406 ```
407 ERROR: Replacement text made overflow worse in these shapes:
408 - slide-0/shape-2: overflow worsened by 1.25" (was 0.00", now 1.25")
409 ```
410
411## Creating Thumbnail Grids
412
413To create visual thumbnail grids of PowerPoint slides for quick analysis and reference:
414
415```bash
416python scripts/thumbnail.py template.pptx [output_prefix]
417```
418
419**Features**:
420- Creates: `thumbnails.jpg` (or `thumbnails-1.jpg`, `thumbnails-2.jpg`, etc. for large decks)
421- Default: 5 columns, max 30 slides per grid (5×6)
422- Custom prefix: `python scripts/thumbnail.py template.pptx my-grid`
423 - Note: The output prefix should include the path if you want output in a specific directory (e.g., `workspace/my-grid`)
424- Adjust columns: `--cols 4` (range: 3-6, affects slides per grid)
425- Grid limits: 3 cols = 12 slides/grid, 4 cols = 20, 5 cols = 30, 6 cols = 42
426- Slides are zero-indexed (Slide 0, Slide 1, etc.)
427
428**Use cases**:
429- Template analysis: Quickly understand slide layouts and design patterns
430- Content review: Visual overview of entire presentation
431- Navigation reference: Find specific slides by their visual appearance
432- Quality check: Verify all slides are properly formatted
433
434**Examples**:
435```bash
436# Basic usage
437python scripts/thumbnail.py presentation.pptx
438
439# Combine options: custom name, columns
440python scripts/thumbnail.py template.pptx analysis --cols 4
441```
442
443## Converting Slides to Images
444
445To visually analyze PowerPoint slides, convert them to images using a two-step process:
446
4471. **Convert PPTX to PDF**:
448 ```bash
449 soffice --headless --convert-to pdf template.pptx
450 ```
451
4522. **Convert PDF pages to JPEG images**:
453 ```bash
454 pdftoppm -jpeg -r 150 template.pdf slide
455 ```
456 This creates files like `slide-1.jpg`, `slide-2.jpg`, etc.
457
458Options:
459- `-r 150`: Sets resolution to 150 DPI (adjust for quality/size balance)
460- `-jpeg`: Output JPEG format (use `-png` for PNG if preferred)
461- `-f N`: First page to convert (e.g., `-f 2` starts from page 2)
462- `-l N`: Last page to convert (e.g., `-l 5` stops at page 5)
463- `slide`: Prefix for output files
464
465Example for specific range:
466```bash
467pdftoppm -jpeg -r 150 -f 2 -l 5 template.pdf slide # Converts only pages 2-5
468```
469
470## Code Style Guidelines
471**IMPORTANT**: When generating code for PPTX operations:
472- Write concise code
473- Avoid verbose variable names and redundant operations
474- Avoid unnecessary print statements
475
476## Dependencies
477
478Required dependencies (should already be installed):
479
480- **markitdown**: `pip install "markitdown[pptx]"` (for text extraction from presentations)
481- **pptxgenjs**: `npm install -g pptxgenjs` (for creating presentations via html2pptx)
482- **playwright**: `npm install -g playwright` (for HTML rendering in html2pptx)
483- **react-icons**: `npm install -g react-icons react react-dom` (for icons)
484- **sharp**: `npm install -g sharp` (for SVG rasterization and image processing)
485- **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)
486- **Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)
487- **defusedxml**: `pip install defusedxml` (for secure XML parsing)