claude-faceless-shorts-creator
CLAUDE.md201 starsChanged 4 months agoMITView on GitHub
A faceless-shorts factory driven by Claude Code. Three production tracks, one repo — the right skill is picked automatically from the request: All three share the same backbone: a beats.json contract, ElevenLabs voice with word-exact captions (gen_voice.py), frame-by-frame QA at phone scale, library-first SFX (/suggest-sfx), optional music bed, seamless frame-0==last-frame loops, no CTA outros. TSX crash rules live in /vidtsx-2d-generator. - Run everything from the repo root. Tools resolve engine paths (media/library, catalogs) against their own location, but project paths…
- Reads credentials
- Installs packages
In this repository5 other files it gives its agents.
- make-ai-shortSkill
- make-shortSkill
- make-voxSkill
- suggest-sfxSkill
- vidtsx-2d-generatorSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
All three share the same backbone: a beats.json contract, ElevenLabs voice with word-exact captions (gen_voice.py), frame-by-frame QA at …
- Very specific: line 43
Registry is generated: after adding/renaming a shot, cd remotion && npm run gen (frames.mjs/render-all.mjs do NOT run it themselves).
≈ “Common” is an estimate: at least 1 in 5 of the 28,029 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
CLAUDE.md — claude-faceless-shorts-creator
A faceless-shorts factory driven by Claude Code. Three production tracks, one repo — the right skill is picked automatically from the request:
| The user asks for… | Skill | Pixels come from | Projects live in |
| "make a short about X" (default) | /make-short | 100% TSX (Remotion animation) | shorts/short-N-<niche>/ |
| "make an AI video short", "blue-man video" | /make-ai-short | a fal video model (locked recurring character) | ai-shorts/<series>/ |
| "vox style / documentary / explainer short" | /make-vox | layered paper-collage (AI images + cutouts) | vox-shorts/vox-N-<topic>/ |
All three share the same backbone: a beats.json contract, ElevenLabs voice with word-exact
captions (gen_voice.py), frame-by-frame QA at phone scale, library-first SFX (/suggest-sfx),
optional music bed, seamless frame-0==last-frame loops, no CTA outros. TSX crash rules live in
/vidtsx-2d-generator.
Layout
tools/ Python tools: gen_voice, gen_sfx, gen_music, mix_sfx, mix_music, gen_chords,
gen_image, gen_clip, bakeoff_clip, cutout, capture_web
remotion/ the Remotion project — src/lib/ (shared + niche kits incl. collage.tsx),
src/shots/{short-N, ai-N, vox-N}/
media/ Remotion's public root: library/ (reusable: sfx, music, logos)
+ projects/<proj>/ (media for ONE video — incl. committed AI clips & layers)
shorts/ TSX shorts: script.md, beats.json, sfx-plan.json each
ai-shorts/ generative shorts: + character.json (LOCKED reference), shot sidecars, IDEAS.md
vox-shorts/ collage shorts: + DESIGN.md (the visual language — read before any vox work)
brand.md the style contract every skill reads (palette, motion, safe areas, SFX taste)
IDEAS.md the TSX-shorts idea bank + niche ranking
.claude/skills/ make-short, make-ai-short, make-vox, vidtsx-2d-generator, suggest-sfxConventions (hard rules)
- Run everything from the repo root. Tools resolve engine paths (media/library, catalogs)
against their own location, but project paths (
shorts/...) against the CWD. - Python: any Python 3.10+ — the core pipeline is stdlib-only. Only vox layer production
needs extras:
pip install pillow rembg(cutout.py) andpip install playwright && playwright install chromium(capture_web.py).ffmpeg/ffprobeandnode/npxon PATH. - API keys live in
.envat the repo root (copy.env.example). Never commit.env. ELEVENLABS_API_KEY = voice/SFX/music · FAL_KEY = AI clips + images · GEMINI_API_KEY = images. - Registry is generated: after adding/renaming a shot,
cd remotion && npm run gen(frames.mjs/render-all.mjs do NOT run it themselves). - Media rules:
media/library/is for CROSS-VIDEO reusable assets only (each with a catalog). Anything generated FOR ONE video (story frames, AI clips, collage layers) goes inmedia/projects/<proj>/, referenced asstaticFile('projects/<proj>/x'). Reuse before you generate — check the catalogs first. - Committed vs gitignored media: AI-generated clips and collage layers in
media/projects/ARE committed (paid, non-reproducible pixels).*/voice/and*/output/are gitignored everywhere (regenerable);ai-shorts/*/shots/*.mp4working copies too — the canonical clip lives inmedia/projects/<name>/. - Costs (ai-shorts only): state the derived generation cost BEFORE spending it, and never regenerate a locked character from text (see /make-ai-short's iron rules).
- QA is not optional: render frames at phone scale and READ them before any full render.
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.

