murathany7murathany7/reel-studio/AGENTS.md

reel-studio

AGENTS.md5 starsChanged 10 days agoMITView on GitHub

Instructions for any coding agent working here (Claude Code, Codex, GitHub Copilot). CLAUDE.md only imports this file; keep everything shared here. Reel Studio: a brand-agnostic kit for making marketing videos, reels, ads and posts with code. One deterministic renderer, several engines plugged into one clock, one folder per brand, one folder per production. The people using this kit are mostly marketers, founders and creators, not developers. Once it's installed, be a creative partner in a conversation: ask back (2–3 questions…

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- capture-siteSkill
- character-2dSkill
- make-videoSkill
- new-brandSkill
- pick-engineSkill
- review-deskSkill
- scene-3dSkill
- setupSkill

The file

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

6 rules. About 0 are common, 2 are distinctive, and 4 are 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Read STATUS.md before starting and update it before finishing.
line 46
Distinctive:
Never invent product facts, numbers or testimonials.
line 48
Distinctive:
Never copy competitor copy.
line 49
Very specific:
Every piece passes its brand's compliance.md.
line 50
Very specific:
Every frame is a pure function of t (rules in engines/README.md).
line 52
Very specific:
Check every idea against *What makes a reel work* (make-video): hook in the first second, a voice, a face, the real product, a change every …
line 53

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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

AGENTS.md

Instructions for any coding agent working here (Claude Code, Codex, GitHub Copilot). CLAUDE.md only imports this file; keep everything shared here.

Reel Studio: a brand-agnostic kit for making marketing videos, reels, ads and posts with code. One deterministic renderer, several engines plugged into one clock, one folder per brand, one folder per production.

Where to look

Question	Read
Making a video, reel, ad or post	`.agents/skills/make-video` (the whole path), then the brand folder
The look (art direction) of a piece: cyberpunk, toon 3D, photoreal, editorial…	`looks/README.md`, `node scripts/looks.mjs <brand>`
Which engine for a look	`.agents/skills/pick-engine` and `engines/README.md`
3D (Three.js, Blender)	`.agents/skills/scene-3d`
A cartoon character or mascot	`.agents/skills/character-2d`
Recording a brand's live website	`.agents/skills/capture-site`
A new brand	`.agents/skills/new-brand`
Optional: the person reviews in the desk (frame notes, approvals)	`.agents/skills/review-desk`, `desk/README.md`
Render, audio and QA commands	`core/README.md`
What is in progress, decided, learned	`STATUS.md`

Path	What
`core/`	`render.mjs` (HTML → MP4/PNG), `lib/runtime.js` (the `Studio` clock), `lib/base.css` (stage, safe zones). `npm install` here once
`looks/`	Art directions (neon-noir, toon-3d, photoreal, editorial, kinetic-type, retro-film, paper-collage): README, `look.css`, a working `starter.html`; `fx.js` for grain, glitch, scanlines…
`engines/`	One adapter per engine: `three.js`, `pixi.js`, `svg-rig.js`, `lipsync.js`, `capture.mjs`, `blender/`
`.agents/skills/`	The skills (SKILL.md). Codex and Copilot read them here; `.claude/skills` is a symlink to it
`desk/`	Optional local review app: player, frame notes, renders, approvals, "Send to agent"; `reel-desk` MCP server (not registered by default). Nothing else depends on it
`scripts/`	Audio mix, transcription, lip sync (`lipsync.sh`, Rhubarb), video QA, frame extraction, SVG → PNG
`brands/<slug>/`	Identity: facts and their sources, colours and fonts (`tokens.css`), `assets/`, voice, Look range, `compliance.md`
`productions/<brand>/<ID>-<slug>/`	One piece: README (storyboard → explainer), `refs/`, `composition/`, `audio/`, `qa/`, `export/`
`examples/engines-demo/`	A 6 s reel using every tested engine; rebuild it to check a machine
`examples/reel-layer/`	8 s reel for captions, beat cuts, transitions and the four formats

Who you're talking to

The people using this kit are mostly marketers, founders and creators, not developers. Once it's installed, be a creative partner in a conversation: ask back (2–3 questions at a time, each with options and your pick), show pictures instead of describing, give opinions on what will work, and keep commands, file paths and engine names out of the chat unless they ask. Report outcomes, not process. Details: make-video, How to talk.

Golden rules

Read STATUS.md before starting and update it before finishing.
Brief → storyboard → approval → production → frame-by-frame QA → delivery. No production before approval.
Never invent product facts, numbers or testimonials. Every claim traces to a source listed in the brand's README. Never copy competitor copy.
Every piece passes its brand's compliance.md. Brands never borrow each other's identity, facts or voice. Looks (looks/) are shared art directions: pick one per piece, and don't let a brand's pieces all look alike.
Every frame is a pure function of t (rules in engines/README.md). If two renders of a frame differ, it is a bug.
Check every idea against What makes a reel work (make-video): hook in the first second, a voice, a face, the real product, a change every second, worth sending. A look is a treatment on the real product, not a template.

Related repos (read-only, for facts)

../marketing-reels-skill: the Yuppo-only kit this grew from (Yuppo brand kit, research, productions).
../bikelog: Bike Logger; its live page was captured for the first capture-site reel.

Checks

node --check core/render.mjs engines/capture.mjs
node core/render.mjs still examples/engines-demo/index.html /tmp/a.png --t 4.6
node core/render.mjs still examples/engines-demo/index.html /tmp/b.png --t 4.6 && md5 -q /tmp/a.png /tmp/b.png

(The demo needs its Blender plate first: see examples/engines-demo/README.md.)

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.

Check your setup, free