agentleFS
hassancs91hassancs91/claude-youtube-editor/CLAUDE.md

claude-youtube-editor

CLAUDE.md368 starsChanged 11 days agoMITView on GitHub

You record the talking head. Claude Code does the rest. Every screen moment — UI walkthroughs, full-screen statements, diagrams, terminal mockups — is built as Remotion TSX and composited over your cut. No screen recording, no video editor. The right skill is picked from the request: The pipeline order is: cut → visuals → voice → SFX → packaging → upload. brand.md is the style contract every step-2+ skill reads (palette, motion, delivery specs, SFX taste). remotion/src/brand.ts + fonts.ts are…

  • Reads credentials
  • Installs packages

The file

We split this CLAUDE.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    You record the talking head. Claude Code does the rest: Every screen moment — UI walkthroughs, full-screen statements, diagrams, terminal …

    line 3
  2. Very specific:

    The Remotion registry is generated: after adding/renaming a shot, cd remotion && npm run gen (the render/frames scripts do NOT run it …

    line 79

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md — claude-youtube-editor

You record the talking head. Claude Code does the rest. Every screen moment — UI walkthroughs, full-screen statements, diagrams, terminal mockups — is built as Remotion TSX and composited over your cut. No screen recording, no video editor. The right skill is picked from the request:

The user asks to…SkillOutput
set up / change their brand, colors, fonts, wordmark/brand-setupbrand.md + remotion/src/{brand.ts,fonts.ts} + a proof render
cut the raw footage / tighten pacing / remove fillers/clean-cutmaster cut + videos/<project>/work/{analysis/cuts.json, edited-transcript.json}
build the visual beats / add overlays/make-tsx (+ /fake-screencast)shots in remotion/src/shots/<project>/ + a baked preview
write a crash-free TSX shot/vidtsx-2d-generatorthe low-level Remotion authoring rules
remove background noise / isolate voice/clean-audioa cleaned master (levels preserved)
add SFX / sound-design a beat/suggest-sfxvideos/<project>/work/sfx-plan.json + an audition mix
package a video / titles + thumbnails/packagingvideos/<project>/packaging/ (1 title × 3 thumbnail bets + rendered thumbs)
make / iterate thumbnails only/thumbnailrendered + verified frames in videos/<project>/packaging/thumbs/ (asks which style elements you want)
upload ittools/yt_upload.pya private draft on YouTube
track it / put it in Notiontools/notion_sync.pythe video's row in the Notion content tracker

The pipeline order is: cut → visuals → voice → SFX → packaging → upload.

brand.md is the style contract every step-2+ skill reads (palette, motion, delivery specs, SFX taste). remotion/src/brand.ts + fonts.ts are the same contract as code — /brand-setup owns all three together; they drift silently if you hand-edit one.

Layout

tools/            Python tools (see requirements.txt); the cut-editor UI in tools/editor/;
                  RNNoise models in tools/models/rnnoise/
remotion/         the Remotion project — src/lib/ (kit, browser, screencast, vscode),
                  src/shots/<project>/; registry is GENERATED (npm run gen)
media/            Remotion's public root: library/ (reusable: sfx, music, logos, faces)
                  + projects/<project>/ (media for ONE video — via staticFile('projects/<p>/x'))
videos/           per-video project data — EMPTY until you make one. See videos/README.md
brand.md          the style contract

The example

remotion/src/shots/example/ is 37 real shots from a published video — the worked example of the kit. They render standalone with no footage: cd remotion && npm run studio. Read a few before authoring new ones; that's the fastest way to learn remotion/src/lib/.

remotion/src/shots/brand/BrandProof.tsx is not a video beat — it's a utility shot that renders the current brand (wordmark, palette, type) so you can see it. /brand-setup uses it.

Conventions (hard rules)

  • Run everything from the repo root. Tools resolve engine paths (media/library, catalogs, remotion/out) against their own location, but project paths against the CWD — so pass the project as videos/video-1 and run from the repo root. Example: python tools/render_cuts.py videos/video-1 --style natural --mode preview.
  • Python: use a venv at the repo root. These tools have real dependencies. Create it once:
    python -m venv venv
    venv/Scripts/python -m pip install -r requirements.txt     # Windows
    ./venv/bin/pip install -r requirements.txt                 # macOS/Linux
    Then either activate the venv or call venv/Scripts/python tools/<tool>.py. A bare python that resolves to a system interpreter will hit ModuleNotFoundError (requests, Pillow, google-*) — that error means you're not on the venv. ffmpeg/ffprobe and node/npx must be on PATH (not pip).
  • API keys live in .env at the repo root (copy .env.example). Never commit .env. ASSEMBLYAI_API_KEY = transcription · ELEVENLABS_API_KEY = voice-isolate + SFX + music · GEMINI_API_KEY = thumbnails · NOTION_TOKEN + NOTION_LONGS_PAGE_ID = the content tracker. YouTube uses OAuth, not a key: tools/yt_upload.py (upload) and tools/yt_stats.py (stats) authorize via a browser and cache tokens under .youtube/ (git-ignored). One-time setup: see tools/yt_upload_SETUP.md, then python tools/yt_upload.py auth.
  • Notion is the tracker, the repo is the source of truth. python tools/notion_sync.py videos/<project> --apply pushes a project's row: properties from videos/<project>/notion.json (committed) and the page body from its script/script.md. It is a dry run without --apply, and it matches an existing row before creating one — ideas get parked in that database months early under a rough working name, so a blind create makes a duplicate. Never hand-edit the script in Notion; edit the repo and re-run with --resync. --list shows every row and its stage.
  • The Remotion registry is generated: after adding/renaming a shot, cd remotion && npm run gen (the render/frames scripts do NOT run it themselves). npm run gen discovers src/shots/** and writes src/registry.gen.tsx + src/shots.manifest.json (both git-ignored).
  • Media rules: media/library/ is for CROSS-VIDEO reusable assets only (each with a catalog). Anything generated FOR ONE video (screen-caps, example art) goes in media/projects/<project>/, referenced as staticFile('projects/<project>/x'). Reuse before you generate — check the catalogs. The face-reference kit for thumbnails is media/library/faces/ — you supply your own images (git-ignored; see its README). No face kit, no face thumbnails.
  • Committed vs git-ignored: the repo carries the reproducible pipeline — cuts.json, edit plans, timeline.json, transcripts, TSX shots, SFX/music plans, catalogs. Raw footage and master cuts NEVER go to git (videos/*/*.MP4, videos/*/reference/), and neither do rendered previews/outputs, audio work files, or rendered face thumbnails (.gitignore covers all of it). The SFX/music library clips/*.mp3 ARE committed (there is deliberately no blanket *.mp3 ignore).
  • QA is not optional: render frames and READ them before declaring a shot done; run verify_cut.py on every cut render (it catches ghost speech + A/V drift); audit the SFX cue sheet before mixing. Scratch renders/frames go in a scratch dir, not the project.
  • The brand contract is three files. brand.md, remotion/src/brand.ts, remotion/src/fonts.ts. Nothing errors when they disagree — the docs just stop describing the videos. Change them together, or run /brand-setup.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.