Pre-talk rehearsal flow — walks through the deck end to end, times the run, surfaces missing notes, and produces a punch list of what to fix before going live.
Use this when the user is about to give a talk and wants to do a serious rehearsal. The output is a punch list of things to fix BEFORE the live run, not a vague "looks good."
presentations/<deck>/deck.jspresentations/<deck>/config.js — for timer.target (the budget)js/timer.js, js/notes.js, js/overview.js — to understand the
rehearsal helpersConfirm the target time.
Look at config.timer.target (in minutes). Ask the user if it's right.
If not, update it before rehearsing — the timer goes amber at 80% and
red past 100%.
Open the deck cleanly.
python3 -m http.server 8000
Visit http://localhost:8000?deck=<deck-id>&nointro to skip the intro
for rehearsal speed. Press T to show the timer. Press N to open
the speaker notes pane (close it again before screen-sharing!).
Walk every slide once, all the way through, in real time.
Use → for each step. Don't skim. Speak the words you'd say to the
audience out loud (or in your head — but full sentences).
As you go, capture issues into a punch list. For each slide, check:
Note the elapsed time per act.
Press Esc to open the overview between acts and screenshot/record
the timer reading. After the run, you'll know which acts are bleeding
minutes.
Stop when the timer hits the target. That's your real run length. If you're not done yet, you're over budget — see the "Cutting" section below.
Run the punch list. For each captured issue:
add-slide skill to add or merge slides if needed.theme-deck skill if the issue is visual.write-diagram skill if a diagram needs work.Do a second clean run. This one should hit the target time without surprises. If it doesn't, do a third.
Final dress rehearsal in fullscreen.
F for browser fullscreen.N).In order of pain (least to most):