A Really Good Work Inc. project
One scene in. Every asset your brand needs out.
Write an asset once, as JSON. Optical renders it as a PNG, GIF, MP4 or PDF, in your brand, fast enough for an agent to try ten versions.
Brand work still gets made one size at a time.
A launch needs a story, a square, a banner, a share card, a GIF and a PDF. Someone builds the same thing six times. Then the copy changes and they do it again.
Agents can write the copy now. They can’t make it look like you. That part still lands on a designer’s desk, one file at a time.
Write the scene. Get the files.
- 01Describe the asset as layers: text, images, video, shapes, even real HTML. Each layer gets timing and motion.
- 02Point it at your brand. Colours, fonts and type styles come from tokens, not hex codes.
- 03Optical draws every frame in Rust. No headless browser.
- 04Out come the formats and sizes you asked for, all in one call.
{
"size": "instagram-story",
"duration": 6,
"layers": [
{ "type": "video", "src": "launch.mp4", "trim": [2, 8] },
{ "id": "headline", "type": "text", "text": "Summon the crew.",
"textStyle": "display", "position": "bottom-left", "width": "80%",
"enter": "rise" },
{ "id": "logo", "type": "image", "src": "$assets.logo",
"position": "top-left", "width": "30%",
"enter": { "preset": "fade", "delay": 0.4 } }
]
}Render it as ["mp4", "gif", "png"] in ["instagram-story", "square", "og"] and you get nine files back.
Three sizzle reels. No footage.
Made for Demons, a test brand with a crew of mascots. Each reel is one JSON file cut to a 120 BPM beat: kinetic type, colour wipes, bobbing characters, ticking counters.
@keyframes, driven by the scene’s clock.One scene, every format.
Stills, loops, video and print come from the same file. Change a word once and every version follows.
Fast enough to try ten versions.
An agent learns by looking, so looking has to be cheap. Measured on a small 2-core server:
Why it’s cheap to run.
Most of a brand video doesn’t move. A logo sits still for two seconds. A headline holds. So Optical only draws what changed.
Their device when it can. Your server when it should.
The same scene renders in the browser with WebAssembly and WebCodecs, or on Node with ffmpeg. Same pixels either way, so you pick by cost, not by look.
Built for agents to drive.
Models are good at JSON and bad at pixels. So the agent writes the scene, Optical does the drawing, and every call hands back a picture the model can check.
[
{ "op": "set", "target": "headline", "path": "text", "value": "Meet the crew." },
{ "op": "merge", "target": "logo", "value": { "enter": "pop" } },
{ "op": "retime", "target": "logo", "start": 1.2 }
]Plug it into Claude, Cursor or anything that speaks MCP with optical mcp --brand brand.json. Or call the same tools from your own code.
Checked against Chrome on every pull request.
91 CSS cases render in Optical and in Chrome, then get compared pixel by pixel. The results post to the pull request.
Render the reels yourself.
git clone https://github.com/reallygoodwork/optical cd optical npm install npm run demons # renders the three reels into examples/demons/videos
Node 20 and ffmpeg. To use it in your own project, install it straight from GitHub: npm install github:reallygoodwork/optical. The README covers the rest. Get the code
Made by Really Good Work Inc.