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

How to block a scene in 3D before paying for AI video with Cozy Clay

Lay out the set, cast, and camera in a browser tab, then export a keyframe pack for an AI video model.

  • Top pick
  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forA video creator planning a short shot who wants to stop paying for repeated AI video takes that miss the blocking.

The problemA text prompt cannot hold where everyone stands, how they move, where the camera is, or when it cuts, so each miss costs another take.

The outcomeA blocked scene with timed shots and an exported first frame, last frame, greybox clip, camera, and prompt that the video model can follow.

What you need first

  • Node.js 22.19 or newer
  • A Chromium browser
  • An AI video model of your choice for the final render

Steps

  1. Run npx cozyclay (needs Node.js 22.19 or newer and a Chromium browser).
  2. Open http://127.0.0.1:5180/app/ and build the set from primitives, then add rigged characters or capsule stand-ins.
  3. Describe the action so the agent writes a motion spec, and check the QA results for collisions, foot slide, reach, and hand contact before you accept it.
  4. Put shots on the timeline, draw dolly rails, and look through the lens to set framing.
  5. Export the keyframe pack (first and last frame, greybox clip, camera, prompt) and give it to your AI video model.

Prompt for your agent

Using the NomaDamas/CozyClay repo, run `npx cozyclay`, open the studio, and block a scene of <scene description> with the cast and camera shots. Export the keyframe pack for <video model>. Verify that the export includes the first and last frame, the greybox clip, the camera, and the prompt before handing it off.

Caveat. Cozy Clay produces the blocking and export files, but the final video quality depends on the AI video model you send them to.

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