Who it is forA founder or marketer preparing a product launch who needs a short video for social and the landing page.
The problemMaking a launch video usually means hiring an editor, animator and composer, which takes days and money.
The outcomeA launch film rendered in 16:9, 1:1, 4:5 and 9:16 with poster frames, captions (.srt and .vtt) and a score composed for the film.
What you need first
- Claude Code, Codex, Grok Build, or another agent that reads skills
- Node.js to run the repo's tools (inferred from the node commands in the README)
- The anidoodle repository cloned or installed from its Install link
- Optional: about 373 MB of free disk space for the sound pack
Steps
- Install the Anidoodle skill in your agent (inferred) from the repo's Install link.
- Run
launch.mjs newto create a spec, then fill in your product's name, prompts, answers and install lines. - Choose the look: drawn ink or clean for a UI-first product, at 30 or 60 fps.
- Run
launch.mjs shipto render every shape with its poster frame and captions. - Check the output: the ship step verifies audio-to-video sync and peak level, and fails any frame where text is cut off.
Prompt for your agent
Use the anidoodle repo to create a launch film for <product name>. Fill the launch spec with the product's prompts, screens and install lines, then run launch.mjs ship and return the rendered files for all four shapes. Verify that the ship step reports no cut-off text and passes the audio sync and peak checks.
Caveat. The README's launch.mjs commands show no full argument list, so check the launch-video kit reference for the exact spec fields before filling them in.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page