DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to plan a motion film beat by beat before rendering with Onetake

Use the rhythm and carry method to write a beat sheet where shot lengths vary and every boundary has a carried element.

  • Content
  • Beginner
  • 30 minutes
  • From the README
  • Claude Code
  • Codex

Who it is forA motion designer or content lead who wants to plan a teaser or feature film on paper before anyone renders it.

The problemPlans often list scenes in order with no thought for what links them, and every shot ends up the same length.

The outcomeA beat sheet with varied shot lengths and a named survivor at every boundary, ready to hand to the render step.

What you need first

  • A coding agent that reads skills, such as Claude Code or Codex
  • python3 with playwright (chromium), numpy, scipy, Pillow and matplotlib
  • ffmpeg and node
  • Screenshots of the product if you want the interface rebuilt in the film
  • A noncommercial use case, since the license is PolyForm Noncommercial 1.0.0

Steps

  1. Install the skill for Claude Code: git clone https://github.com/feitangyuan/onetake.git ~/.claude/skills/onetake
  2. Open the references folder in the repo to read the rhythm and carry notes.
  3. Ask the agent: "Three concepts, pick one" and describe the product and the feeling you want.
  4. Review the beat sheet. Confirm that shot lengths differ by at least four times and that each boundary names what survives it.

Prompt for your agent

Using the onetake skill in the feitangyuan/onetake repo, write a beat sheet for a <length> teaser for <product>. Output one sentence per concept, then the chosen beat sheet with shot lengths and a named survivor at every boundary. Verify that shot lengths vary by at least four times and that no boundary is left without a carried element.

Caveat. The beat sheet is a planning output only, and the README's rules still need the render and verify steps before any film exists.

Share: 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