pptx-generation

What this skill does

# PowerPoint Generation Skill

## Overview

This skill implements a systematic framework for generating professional-quality PowerPoint presentations using AI. It addresses the unique challenges of PowerPoint as a medium that combines data analysis, narrative structure, visual design, and spatial layout—making it one of the most complex AI generation tasks in corporate knowledge work.

The skill applies evidence-based prompting techniques (plan-and-solve, program-of-thought, self-consistency), structural optimization principles (workflow enforcement, constraint-based design, validation gates), and proven spatial layout patterns to ensure consistent, high-quality outputs.

## Core Principles

### 1. Workflow Enforcement

AI systems exhibit tool degradation—silently switching to suboptimal alternatives when primary tools encounter difficulties. For spatial/visual tasks, this creates unreliable outputs.

**Implementation**: Explicitly specify the html2pptx technical workflow and prohibit alternative approaches. Require documentation review before execution.

**Rationale**: PowerPoint generation requires precise spatial calculations. The html2pptx skill provides reliable pixel-level control. Preventing tool switching eliminates the primary source of layout inconsistencies.

### 2. Constraint-Based Design Over Decorative Specification

Simple visual rules scale reliably; complex decorative elements create brittleness in AI generation.

**Implementation**: Define what NOT to do (negative constraints) before specifying positive behaviors. Prohibit border boxes, outline shapes, and rounded rectangles. Emphasize spacing, typography, and subtle color blocks.

**Rationale**: Visual design has exponentially more failure modes than success modes. Eliminating known problematic patterns focuses generative capacity within reliable boundaries. Clean design enables AI to prioritize content synthesis over visual parsing.

### 3. Pre-Execution Design Planning

Separating planning from execution prevents premature commitment to suboptimal visual approaches.

**Implementation**: Require written design plan specifying layout approach, color palette, typography hierarchy, and visual emphasis strategy before code generation.

**Rationale**: Mimics human design process. Creates audit trail for review. Establishes coherent visual system before implementation begins. Dramatically improves consistency across multi-slide decks.

### 4. Quantified Visual Specifications

Vague instructions ("clean margins") force the AI to guess intent. Precise specifications eliminate ambiguity.

**Implementation**: Convert qualitative requirements to measurable parameters (contrast ratios, font sizes, margin measurements, element counts).

**Rationale**: Spatial relationships are inherently quantitative. Explicit measurements create reproducible results and enable automated validation.

### 5. Multi-Chat Architecture for Complex Decks

Visual elements consume tokens faster than text or data. Single-context generation becomes unreliable beyond ~15 slides.

**Implementation**: Separate architect (narrative structure), generator (slide production), and assembly (consistency validation) into distinct conversations for 30+ slide decks.

**Rationale**: Manages context window limitations. Allows focused expertise in each phase. Enables section-level iteration without full deck regeneration.

## When to Use This Skill

**Primary Use Cases**:
- Board decks and executive presentations requiring professional polish
- Financial reports integrating data from multiple sources
- Strategic analyses combining quantitative and qualitative content
- Project updates demanding consistent visual language
- Any presentation where visual quality impacts stakeholder perception

**Skill Triggers**:
- User requests "create a presentation," "make slides," "build a deck"
- User asks to "analyze [data] and present findings"
- User mentions specific output formats: .pptx, PowerPoint, slides
- User provides business data (CSV, financial reports, memos) requesting visualization
- Task requires integrating analysis with narrative in visual format

**When NOT to Use**:
- Simple 1-3 slide requests (use default PowerPoint generation without full workflow)
- Requests for slide content only without visual implementation
- Non-presentation visualization tasks (use charts, graphs, or documents instead)

## PowerPoint Generation Workflow

### Phase 1: Requirements Analysis

**Objective**: Establish scope, constraints, and success criteria before design.

**Process**:
1. Identify data sources and required analyses
2. Determine slide count and narrative structure  
3. Establish visual constraints (brand guidelines, accessibility requirements, template restrictions)
4. Clarify audience expertise level and presentation context
5. Define output quality standards

**Decision Point**: Simple deck (≤15 slides, single context) vs. Complex deck (30+ slides, multi-chat architecture)?

### Phase 2: Pre-Execution Design Plan

**Objective**: Establish coherent visual system before implementation.

**Required Elements**:
- **Layout Philosophy**: Describe approach to spacing, element positioning, visual hierarchy
- **Color Palette**: Specify exact hex values, contrast ratios, usage rules
- **Typography System**: Font families, size hierarchy (titles, headers, body, captions), line spacing
- **Visual Emphasis Strategy**: How information priority translates to visual weight (color blocks, spacing, sizing)

**Format**: Written description in structured format. Must be completed before any code generation begins.

**Validation**: Design plan must explicitly address all items in Design Restrictions (see below).

### Phase 3: Implementation

**For Simple Decks (≤15 slides)**:
Execute in single conversation following the prompt template in `references/simple-deck-template.md`.

**For Complex Decks (30+ slides)**:
Follow multi-chat architecture in `references/complex-deck-architecture.md`:
1. Architect Chat: Generate narrative structure and slide-level outline
2. Generator Chat(s): Produce sections of 10-15 slides each
3. Assembly Chat: Ensure consistency, validate against design plan

**Technical Requirements**:
- Always use html2pptx workflow
- Generate slides iteratively (never all at once for complex decks)
- Validate after each section before proceeding
- Maintain state document tracking completed slides and remaining work

### Phase 4: Validation

**Automated Checks**:
- Contrast ratio verification (minimum 4.5:1 for all text)
- Font size validation (18pt minimum, 24pt titles)
- Margin measurements (0.5" minimum all sides)
- Element overlap detection
- Bullet count per slide (maximum 3)

**Manual Review Points**:
- Thumbnail readability test
- Visual consistency across slides
- Narrative flow and logical progression
- Data accuracy and source attribution

**Failure Response**: If validation fails, identify root cause, adjust design plan or implementation approach, and regenerate affected sections. Never apply band-aid fixes.

## Design Restrictions

These constraints are absolute and apply to every slide in every deck. They eliminate known failure modes and ensure reliable spatial layout.

### Prohibited Elements

**NEVER include these in any slide**:
- Border boxes around text elements
- Outline shapes containing text content
- Rounded rectangles with text inside
- Text containers or frames
- Decorative borders or dividing lines as separate elements
- Overlapping text elements
- Dark text on dark backgrounds

### Required Patterns

**ALWAYS implement these in every deck**:
- Text directly on slide background or solid color areas
- Visual separation through spacing and typography (not containers)
- Colored accent bars or background sections (not outlined boxes)
- Subtle background color zones for emphasis (not bordered elements)
- Clean white or light-colored backgrounds
- High-contrast text (4.5:1 minimum ratio)
- Single visual element per slide (maxi