Reelify Motion Kit 0.1 preview
Docs/Working with it

Agents

What an agent reads, in what order, and the loop it follows to write a film or change one without inventing a prop.

The kit ships a folder made for agents: kit/. It is generated from the registry by kit.ts, so it cannot drift from the code. An agent that reads only those files can write a film and change one. Nothing in them needs this website.

The short version. Paste AGENTS.md into the project so it is always loaded. It points at an 8 KB index. The index points at one task file per job and one reference file per category. After every change the agent runs check, which names the valid options for anything it got wrong.

The files#

FileSizeWhat it is for
AGENTS.md0.8 KBA short block to paste into a project so it is always loaded: read the index, never invent a prop, run check.
SKILL.md2.5 KBWhen to use the kit, which file to open for which job, the check loop.
docs/index.md8.1 KBOne line for every component, behavior, surface and palette name. Read first.
docs/tasks/new-film.md2.2 KBHow to write a film: the shape and the rules that keep it copyable.
docs/tasks/edit.md0.9 KBHow to change a film with operations.
docs/tasks/reskin.md1.0 KBHow to give a film another look or another product.
docs/tasks/add-component.md1.0 KBHow to add a component, as data.
docs/reference/14 filesEvery prop of every component, by category: type, numbers-and-charts, lists-and-threads, camera-and-space, accents, frames, systems, composition, on-video, film, product-ui, worlds, explainer, moment
r/12 filesFilms, design systems and products to copy whole: film-command, film-keynote, film-walkthrough, film-code, system-reelify, system-graphite, system-paper, system-neon, system-candy, product-reelify, product-harbor, product-fieldnote

The whole kit is plain text served from this site under /kit/. llms.txt lists every file with its address.

Why it is laid out this way#

ChoiceReason
An always-loaded block, not only a skillA skill has to be chosen before it helps. A short block in AGENTS.md is in context on every turn, and its one job is to say: read the index first, your memory of other animation libraries does not apply here.
A small index, large referencesThe index is one line per component, behavior, surface and palette name: enough to pick. The props of a component are read only when it is used. A film that uses six components costs the index plus two or three reference files.
One file per jobWriting a film, reskinning one, editing one and adding a component have different rules. Each task file is 900 to 2,300 characters and ends with the command that checks the result.
A registry to copy fromkit/r/ holds every example film, design system and product record as one JSON file each. Starting from a working film and changing it is more reliable than starting from nothing.
Checks that name the fixA wrong prop returns the place, the value and the accepted values. The agent corrects itself without a person and without drawing a frame.

The loop#

  1. Read kit/docs/index.md.
  2. Open the task file for the job: new-film.md, reskin.md, edit.md or add-component.md.
  3. Open the reference file for each category of component the film uses.
  4. Write the film as JSON, or the edit as a list of operations.
  5. Run check. Fix every problem it lists. Repeat until it prints none.
text
npx tsx cli.ts example command > film.json     # a working film to start from
npx tsx cli.ts check film.json                 # problems and notes, with the valid options
npx tsx cli.ts patch film.json ops.json        # apply a list of operations, all or none
npx tsx cli.ts dress film.json graphite        # the same film in another design system
npx tsx cli.ts catalog                         # every component and its props, as JSON

Writing a film#

The agent is given a brief, the index, the task file and the references it asked for. It replies with one JSON record. Three rules carry most of the weight:

  • No colour, no typeface, no copy. A film names palette entries ("accent"), surfaces ("card") and tokens ("$tagline"). The design system and the product record fill them in. This is what lets one film be dressed for any brand.
  • The length adds up. duration equals the sum of the scenes' len. If it does not, check reports a problem.
  • Nothing invented. A component or prop that is not in the reference is a problem, not a note.

Changing a film#

An edit is a list of operations with JSON Pointer paths. The agent never sends the film back. See Editing for the format.

json
[
  { "op": "remove", "path": "/root/children/1/scenes/5" },
  { "op": "replace", "path": "/root/children/1/scenes/5/len", "value": 4 },
  { "op": "replace", "path": "/duration", "value": 27.4 }
]

That list removes a scene, holds the closing scene a second longer and corrects the length. It is 169 characters against a film of 1,724. Whatever it does not name cannot change, so an agent asked to move one scene cannot quietly rewrite another. Try it in the film editor: every change you make there is listed as the operations an agent would send.

Give an agent the kit#

WhereWhat to do
A coding agent in a repositoryCopy kit/ into the project and paste the block from AGENTS.md into the project's own agent file. Add SKILL.md as a skill if the agent supports skills.
A model called from your own codeSend docs/index.md, the task file and the reference files for the categories you allow as the system text. Run compile on the reply and send the problems back as the next message if there are any.
A chat with web accessPoint it at /llms.txt.

Not there yet. There is no installer and no hosted registry address: the kit is copied by hand. There is no tool server for agents. Both are listed under Direction.

What agents have actually done with these files is measured on the Benchmarks page.

Reelify Motion Kit 0.1 preview. Built 2026-11-21.llms.txt · SKILL.md · 109 pages