Docs /
docs/guides/README.mdGuides
Task guides for people. Each one says what to tell your coding agent, the commands it runs, the files you get,
how long it took on a named machine, the phrases that change the result, the honest limits, and an example to
look at. The references in skills/showtime/references/ are written for your agent; these are written for you.
| Guide | When you want |
|---|---|
| Dress up a talking head | cards over an interview or a founder update, captions with emphasis, a word behind the speaker, 16:9 and 9:16 |
| Turn a Claude Design animation into an MP4 | a Claude Design HTML export rendered as a video, then music, voice and captions |
| Turn a long recording into short clips | the best 30-60 s moments of a talk, panel or podcast as vertical clips |
| Make a launch video from your repo | a launch or promo in your product's own colours, type, words and screens |
| Make a video in another language | the same video re-voiced, re-timed and captioned in Spanish, French or another language |
| Make a video of a pull request | a short video for a PR's description in one command, and the GitHub Action |
| Make an explainer that stops and asks | questions the web version stops on, links to a moment or a stretch, link previews |
| Go all out: a showreel | a hype reel with flash words, a shutter blur on snaps, and WebGL looks |
| Leave notes on a video and get them fixed | point at a frame or a stretch, get each note fixed and answered, the critic's findings |
| Work on a slow machine, or one without a GPU | what to expect without a GPU, drafts, splices and background runs |
Times in these guides are measured, never guessed. Each one names its machine: a 6-core Intel Mac that other jobs kept busy, or a 64-core Linux machine with no GPU. Where nothing was measured, the guide says so.
New to showtime? Start with the README. The documentation map lists every reference your agent reads.