Motion, written as data.
Reelify Motion Kit is a library for product films, explainers and on-video graphics. A scene is JSON: components with knobs, timed in seconds. A design system gives it its look and a product gives it its words, so one film serves any brand, and an agent can write one or change one without writing animation code.
89components in 14 categories
20behaviors
5design systems
6example films
90film × system × product combinations that compile
0.1 previewnot on a package registry yet
The idea
A film is dataScenes, pieces and timing in one JSON record of 900 to 1,700 characters. No animation code, nothing to compile but the record itself.
The look is separateColours, typefaces, what a card looks like, how springs feel: a design system of about 1,100 characters. A film never writes a colour.
The words are separateA product record supplies names, claims and the rows of mock screens as tokens. Swap it and the same film is another company's.
Edits are as small as the changeReordering two scenes is one operation of 85 characters. Whatever an edit does not name is untouched by construction.
Checks that name the fixThe compiler lists problems with the place and the valid options. An audit measures what overlaps on the built scene.
Made for agentsAn 8 KB index, one file per job, a registry to copy from. A model given only those files wrote two films that compiled first try.
Start here
IntroductionWhat Reelify Motion Kit is, how its four layers fit together, and what it can and cannot do today.Quick startUse the kit from the repository today: write a scene, check it with the CLI, compile it and draw it in a page.ScenesThe scene record, the five elements and their props, how layout works, how time works, and how ids and parts are named.ExpressionsThe four ways a value can be computed instead of written: "$name", "=expr", "{expr}" in text, and signals, plus $each, $if and colour mixes.BehaviorsWhat a behavior is, how a node's motion list adds up, poses and their 15 channels, curves and springs, stagger, drive, and defining a behavior as data.Design systemsThe config record that gives a film its colours, typefaces, surfaces and springs, how withConfig and mergeConfigs apply it, and why a film never writes a colour.FilmsScenes in sequence with Sequence, the duration rule, writing a film against tokens, the product record, dressing a film in a design system, and the registry items to copy.Custom componentsThe four levels of making a component your own, from setting props to a build function, where a component can live, and how to check it.MediaThe img element with a still, a sprite sheet or a video; wrapping media in a phone, a window, a camera or a 3D card; and what media work is not supported yet.EditingThree ways to change a scene without rewriting it: patch operations with JSON Pointer paths, the bridge (snapshot, act, history), and Motion Lang for edits on a talking video.DirectorEditing a talking video: skills, the stage and its three states, seats, the arranger and its decisions, the caption lane, pictures, follow-ups and the audit.Using it with agentsWhat an agent reads, in what order, and the loop it follows to write a film or change one without inventing a prop.BenchmarksWhat has been measured so far, how, and what the numbers do not show.DirectionWhere the kit is going, what is missing today, and the order the gaps will be closed in.Film editor playgroundA product film, open on the bench.Films, systems, products playgroundEach film is written once against names.Scene playground playgroundPaste or edit any scene and it compiles as you type.
Status. A working preview. It draws in the browser only: there is no export to a video file yet. It is not published to a package registry. The components have not had a designer's review. See Direction for what is missing and in what order.