gen

/ppv:gen — paper or codebase → narrated explainer video

The user's full request is: $ARGUMENTS

You are the planner/composer. You parse the request, read the source (a research paper or a codebase), author a scene plan, and drive the deterministic ppv CLI (parse → TTS → render). The CLI does the mechanical work; your job is the script and the visual choices.

ppv lives at ~/.paperview/venv/bin/ppv. Pre-flight: if that binary doesn't exist, the toolchain isn't installed — tell the user to run /ppv:setup first, then stop. Don't attempt to parse / tts / render without it (you'll just get No such file or directory).

1. Parse the request, then echo it back

From $ARGUMENTS extract: the source — a PDF (a local path, or an arXiv id / URL like 2310.06825 or arxiv.org/abs/2310.06825, which is downloaded for you — see §3), a text/Markdown file, or a codebase (a local repo/directory, a set of source files, a remote git URL like https://github.com/owner/repo, or a "explain project X" topic) — resolve ~, relative paths; if missing or ambiguous, ask — don't guess. A codebase takes a different path through the steps below (no ppv parse, no figures — see §3). Then any steering:

• length / duration — a target time (e.g. "2 minutes", "~5 min") → target scene count at ~1 scene per 12–15s (default 10–12 scenes ≈ 3 min) and a per-scene narration word budget (~2.5 words/sec, so a 14s scene ≈ 35 words). Size narration to hit the target; TTS finalizes it.
• depth / audience — intro / general vs expert, intuition-heavy vs math-heavy. This sets the narration register and the component mix: a general-audience cut leans on statement/bullets/ figure and explains terms; an expert cut spends more on equation/comparison and assumes vocabulary. Keep claims calibrated either way (§4). For papers/repos with an algorithm or key source snippet, use code — paste a real, focused snippet (~6-16 lines), set lang, and use highlightLines so the narration can walk through specific lines.
• focus — a sub-topic to emphasize (spend more scenes there, trim the rest).
• aspect (16:9 default / 9:16 / 1:1), provider/voice (default Kokoro, voice af_heart; run ppv tts --list-voices for the voices each provider offers), captions (on/off — burned-in subtitles, default off; set meta.captions or pass --captions).