pptx

Use pptxgenjs in Node for from-scratch decks with expressive layouts, or python-pptx if generation lives in an existing Python pipeline. Always set explicit positions, sizes, and font faces on text boxes and charts so rendering is consistent.

pptxgenjs offers more expressive layout primitives and is preferred for brand-new decks. python-pptx covers most of the same surface area and is pragmatic for small content edits or when you already have a Python codebase.

Use python-pptx for light edits like text fixes, image swaps, or chart data replacement, since it preserves theme, master, and fonts. For structural changes like reordering or deleting slides, unpack the .pptx as a ZIP, edit the OOXML directly, and repack from inside the folder.

The repair dialog usually means the repacked ZIP has entries prefixed with the folder name, a slide was added without a [Content_Types].xml override, or a deleted slide left a stale relationship in presentation.xml.rels. Zip from inside the unpacked directory and keep content types and rels consistent.

Render the deck to per-slide JPEGs using the render-thumbnails scripts, which pipe the .pptx through LibreOffice to PDF and then Poppler's pdftoppm. Hand the images to a fresh-context sub-agent with an inspection prompt that assumes bugs exist, then run at least one fix-and-verify cycle.

Do not use it for PDF, Word, Excel, or Google Slides output, which need different tools. It also does not apply to pure content questions where no .pptx file is produced or read, or to architecture diagrams that belong in a dedicated diagram skill.