pptx-exportlisted

*[日本語](SKILL.ja.md)* # PPTX Export for Generated Decks ## Important - **The export is a snapshot, not a linked copy.** It captures the deck as it is at export time. Always export **after** visual QA and any fix loop are finished — and re-export whenever the deck is regenerated, deleting the stale `.pptx` from the Drive folder first (same rule as superseded decks). - **Fixes happen in the spec, never in the .pptx.** On any defect, return to the originating generation skill, fix the spec, regenerate, re-run QA if it was chosen, then export again. Editing the exported file forks it from the source of truth. - **Run every command from the slide-forge root as cwd** — `${CLAUDE_PLUGIN_ROOT}` when running from an installed plugin, `/path/to/slide-forge` on a local clone. Auth and the venv are shared at the repo root (`config/`, `.venv`). - **Whether to export PPTX is settled at generation time** via the output format question in intake (`references/interactive-intake.md` §2); the default is Google Slides only. Standalone runs on an existing deck URL need no intake. - **`output: local` in `config/settings.json` makes the export automatic.** `build_deck.py` / `render_deck.py` export the deck to `localOutputDir` on every run, so don't ask the PPTX question and don't export a second time — report the path the generator printed. This skill still applies standalone, or to re-export after a manual edit (`references/settings.md`). - **From-scratch PPTX autho