Who it is forA motion designer or marketer who has a draft storyboard for a software promo and wants to confirm it does not repeat effects.
The problemFilm drafts often reuse the same transition, entrance or ease across shots, which makes the result feel like a template rather than a new film.
The outcomeA list of repeated transitions, entrances, eases, directions and uniform shot lengths, plus any missing surprise, so you can fix or mark them as deliberate motifs before the build.
What you need first
- Python to run the tools in tools/
- A copy of the repo, or a new repo created from the template with Use this template
- A storyboard file written from templates/STORYBOARD.md
- HyperFrames, if you build the film itself (the README links to it but does not describe the install steps)
- Claude Code, if you want the /saas-motion-video skill to run the process with you
Steps
- Clone Saas Motion Kit, or click Use this template to start your own film repo.
- Copy templates/STORYBOARD.md and fill in the Message & tone sentence and one ledger row per shot.
- Run
python tools/variety_audit.py STORYBOARD.md. - Fix each repeat, or mark it as a deliberate motif: in the storyboard.
- Run the audit again until the storyboard passes, then move to the build stage.
Prompt for your agent
Use the saas-motion-kit repo. Fill templates/STORYBOARD.md for <product name> with a Message & tone sentence and one ledger row per shot, then run `python tools/variety_audit.py STORYBOARD.md`. Expected output: the audit report of repeats. Verify that the report is empty or that each repeat is marked as a motif before you hand the storyboard on.
Caveat. The audit checks the storyboard file you give it, so it cannot judge the finished film, and it only works if the ledger is filled 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