Paper to PPT Pipeline
Boundary
Use only papers and assets the user has lawful access to. Reusing original figures, tables, or long text may require citation, permission, or redrawing depending on the use case. For public/commercial decks, prefer original redraws or summarized diagrams with clear citations.
Do not fabricate results, citations, figures, tables, equations, or experimental claims. If the paper does not support a slide, mark the gap.
Workflow
- Intake the paper: confirm PDF/source file, target audience, language, slide count, presentation length, purpose, and reuse permissions.
- Read and reconstruct logic: use
references/paper-logic.md to identify problem, gap, question, method, evidence, results, contribution, limitations, and implications.
- Build the deck outline: create a top-level table of contents before writing slides.
- Generate slide titles: break each section into small slide titles that each make one clear point.
- Map paper content: use
references/content-mapping.md to connect every slide to exact paper sections, claims, figures, tables, formulas, and citations.
- Design slide storyboard: decide layout, visual hierarchy, figure/table treatment, and speaker logic for every slide.
- Create slide images: render each slide as a consistent full-slide image or visual preview using
references/visual-style.md. Keep typography, colors, margins, labels, and figure styles unified.
- Assemble PPT/PPTX: use the rendered slide images and/or editable text/figures to create the final deck. Prefer editable PPT elements when the user needs later editing; prefer slide images when visual fidelity matters.
- Quality check: verify slide order, narrative continuity, citations, figure/table provenance, text fit, contrast, image resolution, and missing evidence.
- Deliver artifacts: output the
.pptx, slide image folder, content map, source/citation map, and unresolved issues.
马斯克 Supervision
Delete weak slides before designing them. Do not turn every paper section into a slide. Keep only slides that move the argument forward. Simplify the story before polishing the visual style.
Output
- paper logic map
- deck table of contents
- slide-by-slide title list
- slide content map
- figure/table/equation inventory
- style specification
- rendered slide images
- final PPT/PPTX
- citation/provenance report
- quality-check report
Resources
references/paper-logic.mdreferences/content-mapping.mdreferences/visual-style.md
1---2name: paper-to-ppt-pipeline3description: Turn a research paper into a structured, styled PowerPoint deck: read a lawful paper/PDF, reconstruct the paper logic, create a top-level presentation outline, generate slide-level titles, map each slide to paper text/figures/tables/equations, create consistent slide images, and export a final PPT/PPTX. Use when Codex is asked to make a PPT from a paper, article, thesis chapter, technical report, or research PDF.4---56# Paper to PPT Pipeline78## Boundary910Use only papers and assets the user has lawful access to. Reusing original figures, tables, or long text may require citation, permission, or redrawing depending on the use case. For public/commercial decks, prefer original redraws or summarized diagrams with clear citations.1112Do not fabricate results, citations, figures, tables, equations, or experimental claims. If the paper does not support a slide, mark the gap.1314## Workflow15161. **Intake the paper**: confirm PDF/source file, target audience, language, slide count, presentation length, purpose, and reuse permissions.172. **Read and reconstruct logic**: use `references/paper-logic.md` to identify problem, gap, question, method, evidence, results, contribution, limitations, and implications.183. **Build the deck outline**: create a top-level table of contents before writing slides.194. **Generate slide titles**: break each section into small slide titles that each make one clear point.205. **Map paper content**: use `references/content-mapping.md` to connect every slide to exact paper sections, claims, figures, tables, formulas, and citations.216. **Design slide storyboard**: decide layout, visual hierarchy, figure/table treatment, and speaker logic for every slide.227. **Create slide images**: render each slide as a consistent full-slide image or visual preview using `references/visual-style.md`. Keep typography, colors, margins, labels, and figure styles unified.238. **Assemble PPT/PPTX**: use the rendered slide images and/or editable text/figures to create the final deck. Prefer editable PPT elements when the user needs later editing; prefer slide images when visual fidelity matters.249. **Quality check**: verify slide order, narrative continuity, citations, figure/table provenance, text fit, contrast, image resolution, and missing evidence.2510. **Deliver artifacts**: output the `.pptx`, slide image folder, content map, source/citation map, and unresolved issues.2627## 马斯克 Supervision2829Delete weak slides before designing them. Do not turn every paper section into a slide. Keep only slides that move the argument forward. Simplify the story before polishing the visual style.3031## Output3233- paper logic map34- deck table of contents35- slide-by-slide title list36- slide content map37- figure/table/equation inventory38- style specification39- rendered slide images40- final PPT/PPTX41- citation/provenance report42- quality-check report4344## Resources4546- `references/paper-logic.md`47- `references/content-mapping.md`48- `references/visual-style.md`
walterkken