Skip to content

framefields for agents

View .mdllms.txt

framefields is made to be driven by a coding agent. A film is a TypeScript file, every check is a function that returns data, and every review step produces a file the agent can open and look at. You describe the video; the agent writes, renders, inspects and fixes it.

/plugin install framefields

Then ask for a video:

Set up framefields in this project and render a 3-second title card that says "Hello".

The skills are instructions only: no MCP servers, hooks or executables, and they send no data anywhere. Details per agent are on Install the skills.

Plain code A video is a Composition in TypeScript. Diffs, reviews, tests and git all work.
Deterministic (composition, frame) → pixels. The same frame renders the same way every time, so checks are repeatable.
Checks return data comp.lint() and renderVideo({ qa }) return { severity, code, message } objects, not logs to parse.
Cheap feedback One PNG frame or a contact-sheet grid in seconds, long before a full render.
People in the loop The live preview saves notes a person pins on the picture to notes.json — exact feedback an agent can act on.
No creative suite One npm package; no browser, no desktop apps, no licenses.
  1. Write film.ts exporting buildFilm().
  2. Check — tsc --noEmit, then comp.lint().
  3. Look — render key frames to PNG and open them.
  4. Look at motion — render a frame grid.
  5. Show — start the live preview; read the person’s pinned notes.
  6. Ship — renderVideo({ qa: true }); stop if qa.passed is false.

Full detail in The agent workflow.