studio-3d
CLAUDE.md4 starsChanged 16 days agoMITView on GitHub
This repo is a skeleton: the engine, the tools and the rules for making 3D videos in code. It has no character, no voice and no videos. You, Claude, do the rest with the person who cloned it.
- Reads credentials
In this repository2 other files it gives its agents.
- open-studioSkill
- setup-studioSkill
The file
We split this CLAUDE.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
If studio/characters/lead/character.json does not exist, run the setup-studio skill before anything else, whatever the person asked.
- Distinctive: line 16
Test videos are 5 to 10 seconds.
- Distinctive: line 18
Before anything that spends money (a paid voice, for example), say the cost and wait for a yes.
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Studio 3D: instructions for Claude
This repo is a skeleton: the engine, the tools and the rules for making 3D videos in code. It has no character, no voice and no videos. You, Claude, do the rest with the person who cloned it.
First run
If studio/characters/lead/character.json does not exist, run the setup-studio skill before anything else, whatever the person asked. Then do what they asked.
After that
- "Open the studio" or "abre o estúdio": the
open-studioskill. - Front doors:
kit/README.md(the 3D format and its tools),kit/CINEMATIC.md,studio/knowledge/(sitcoms). - Talk to the person in their language, in plain words. They may not be a developer.
Rules
- A video is not done until you have looked at it: pull frames and check them by eye. A render that finishes can still be black.
- Make videos through the studio's runner (
kit/runner/explainer.pyor the page), not by hand: it runs the checks. - Test videos are 5 to 10 seconds. Long renders only when asked.
- Render one video at a time, never several together: each opens its own browsers and can run the computer out of memory.
- Before anything that spends money (a paid voice, for example), say the cost and wait for a yes.
- Never commit
.env.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

