Using AI to drive Domotion

Domotion faithfully renders whatever HTML/CSS and timing you give it. Whether the result is good is a design problem — and Domotion is built so an AI agent can own that loop end to end.

Point your agent at llms.txt

The package ships an llms.txt at the repo root — a concise, self-contained guide for an agent using Domotion as a tool: the CLIs, the config schema, the template library, the API, the gotchas, and a full design playbook. It’s distinct from contributor docs. Point Claude / Cursor / your agent at it.

Use Studio for durable, reviewed projects

For work that outgrows one capture or animation config, Domotion Studio provides a versioned project model shared by human and AI review. Its generation and review adapters preserve the authored story and scenes, while findings enter the same project-, scene-, time-, or region-scoped annotation history as human feedback. Run domotion-studio --no-open in automation and drive the printed loopback URL; the project remains portable JSON inside the explicitly scoped workspace.

You don’t have to hand-write the markup

Because Domotion renders whatever markup it’s given and an agent can look at the result and iterate, you can describe the demo you want — “a pricing page with three tiers, the middle one highlighted, that assembles top-down” — and let the agent write the HTML/CSS, render it, check the pixels, and refine. Designers and non-coders get a polished, on-brand demo without touching the markup themselves.

Work the loop: build → render → look → critique → iterate

The output is an ordinary, standards-compliant SVG, so an agent can look at it cheaply and judge it:

1. Render, then rasterize and actually open the pixels — for a still, svg-to-image out.svg -o out-review.png; for an animation, open meaningful beats with svg-to-image out.svg -o beat.png --at <ms>, then render with svg-to-video out.svg -o out-review.mp4 and watch one complete loop.
2. Critique against the checklist (hierarchy, contrast, easing, pacing, restraint). Name the single weakest thing.
3. Fix that one thing and re-render. Iterate.

Before handing an SVG back for human review, the agent should inspect the whole intrinsic-size raster for clipping, layout, text, effects, missing assets, and background/alpha errors. For animation it should also open the beginning, a transition midpoint, the payoff, and the final pre-loop state; svg-scrubber is the frame-step/timeline fallback. When a Chromium reference exists, svg-review adds the source-versus-SVG diff. The handoff should name the previews and times actually inspected—or disclose that a browser, ffmpeg, image viewer, or video player was unavailable. A successful command alone is not a visual review. The shipped llms.txt contains the complete gate and checklist.

Capture, rasterization, and export already use headless Chromium. domotion-studio, svg-review, and svg-scrubber are interactive local servers that otherwise open the system browser, so agents must pass --no-open and drive the printed local URL through headless browser automation. All three also honor DOMOTION_NO_OPEN=1. Do not open a desktop browser unless the user asks.

The playbook in one breath

The llms.txt design section distills established practice (Disney’s principles, Material/HIG motion specs, WCAG contrast, Tufte) into Domotion’s actual levers: override linear easing on every animation; hold frames long enough to read; one focal motion at a time; one accent color, 60-30-10, real contrast; pick the transition for what the cut means; and default to restraint.

This site’s own showcase and the built-in chart defaults follow that playbook — e.g. single-series charts emphasize one bar in the accent rather than rainbow-coloring every bar.