slideslisted

# Slides One self-contained HTML deck in the house style: bright, Geist, vertical scroll-snap, a bottom bar with **section pills** that highlight where the viewer is, **page numbers**, and a progress line. `template.html` in this folder *is* the design; copy it and replace the content. The content is agreed with the user in an interview before any slide exists — the reasoning behind it is in `references/engaging-content.md`. ## Origin Based on the ECC (Everything Claude Code) `frontend-slides` skill — its viewport-fit base CSS, density limits, `scripts/extract-pptx.py` and `scripts/export-pdf.sh` carry over. The original was removed from this repo; before changing anything structural here, clone it for reference: `git show ab57d27:plugins/frontend-slides/skills/frontend-slides/SKILL.md` in this repo's history (the whole folder lives under that path in commit `ab57d27`). <HARD-GATE> Do not write the plan file, copy `template.html`, or build any slide until the user has answered rounds 1 and 2 and said yes to the heading overview (round 3) **in chat**. The plan file is written only after that yes — it records decisions already made, it is never the thing the user is asked to approve. This holds for every deck, however much material or context the user supplied. A rich brief shortens the interview — your recommended answers get better — it never removes it. A reply approves the round actually shown. Agreeing to the main points does not approve headings that haven't been sho