AIPPT - AI PPT Generation Workflow
Positioning: Fully automated PPT generation workflow
Dependency: pw-image-generation skill
Core: Reference image style constraint + prompt content replacement + AI image generation + PPTX packaging
Quick Start
1. Prepare the project
bash
mkdir my-ppt-project && cd my-ppt-project
mkdir -p template prompts images
2. Prepare templates (reference images)
Method 1: Automatic PDF conversion (recommended)
bash
node ~/.claude/skills/pw-aippt/scripts/pdf-to-images.js template.pdf ./template 150
Poppler installation required:
Method 2: PowerPoint/Keynote export
Export as PNG images and save to the
directory. See
for details.
3. Generate prompts
bash
# Execute in Claude Code
/pw-aippt https://example.com/article
# or
/pw-aippt "article content..."
The skill will automatically analyze the template, split the content, and generate prompt files to the
directory.
4. Generate images
bash
node ~/.claude/skills/pw-image-generation/scripts/generate-image.js
5. Package into PPTX
bash
node ~/.claude/skills/pw-image-generation/scripts/merge-to-pptx.js ./images output.pptx
Core Concepts
Workflow
Export images → Style extraction → Template analysis → Content segmentation → Content mapping → Generate prompts → Generate images → Package PPTX
↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓
Reference Style def Layout lib Page plan Prompt file prompts/ PNG files .pptx
New step description:
- Style extraction: Extract the design aesthetics, background system, font system, color system, visual elements and style constraints of the template according to standardized specifications, and form a reusable style definition document
Prompt structure
Refer to this PPT template image: {reference image URL}
Generate a new content page.
【Style Constraints】(strictly follow)
Design Aesthetics
{Design aesthetic description extracted from template analysis}
Background System
- Color: {exact Hex value}
- Texture: {texture description}
- Gradient: {gradient information}
Font System
Title Font
- Font: {font name}
- Weight: {weight}
- Size: {size}
- Color: {Hex value}
Body Font
- Font: {font name}
- Weight: {weight}
- Size: {size}
- Color: {Hex value}
Color System
{Color table extracted from template analysis}
Visual Elements
{List of decorative elements}
Style Rules
Should be kept
- {List of features to keep}
Prohibited to change
- Do not add slide numbers, footers or Logos (unless existing in the template)
- {Other prohibited items}
【Unchangeable Area】(keep strictly as is)
- {Specific unchangeable elements}
【Modifiable Area】
- Page title changed to: {new title}
- Content area changed to: {new content}
【Generation Instruction】
Maintain professional style, content is clear and easy to read.
absolutely no watermark, clean output only
See
for detailed examples.
Style library usage:
- You can select predefined style templates from the directory
- Supported styles: corporate, minimal, technical, creative
- Copy the style definition to the [Style Constraints] section of the prompt, and fine-tune according to the actual template
Core Principles
Visual Consistency (Important)
The most common problem with series of images is inconsistent style. Elements that must be consistent:
- Visual style: Color matching, decoration, font, background are consistent with the template
- Layout ratio: Keep similar white space ratio and element position
- Decorative elements: Use the same type of decoration
- LOGO/page number: All images should include (if available in the template)
Implementation method:
- Use reference images to constrain style (image to image)
- Clearly define unchangeable areas in the prompt
- Explicitly require subsequent images to "maintain the same style as the template"
Common problems:
- Background color changed → Explicitly constrain the background in the "unchangeable area"
- Decorative elements disappeared → List the position and style of each decorative element in detail
- Inconsistent font size → Unify font size specifications in all prompts
Content Disassembly
- Cover page: Main title + subtitle, strong visual impact
- Table of contents page: Chapter list, clear navigation
- Content page: Each page focuses on 1 core idea
- Closing page: Summary/thank you/contact information
Number of pages:
- Simple content (<1500 words): 10-15 pages
- Medium complexity (1500-3000 words): 15-20 pages
- In-depth content (>3000 words): 25-30 pages
File naming: Use serial number prefix, such as
,
Reference Documents
| File | Description |
|---|
| Export PPT as images (reference images) |
references/02_PPT模板分析方法.md
| Analyze templates, output layout library and style definition |
| Split content into pages |
| Match content to layout, generate prompts |
| Prompt format example (recommended) |
references/styles/README.md
| Style library usage instructions |
references/styles/corporate.md
| Corporate style template |
references/styles/minimal.md
| Minimal style template |
references/styles/technical.md
| Technical style template |
references/styles/creative.md
| Creative style template |
Notes
- Reference image quality: The exported template image should have high resolution (1920x1080 or higher recommended)
- Prompt accuracy: Clearly describe modifiable/unchangeable areas to avoid arbitrary modification by AI
- Visual consistency: Use reference images to constrain the style to ensure consistent style of all pages
- The first image is very important: After generating the first image, carefully compare it with the template, and confirm it is correct before batch generation
- Avoid Markdown format: Do not use format markers such as in prompts