How Agents Work
Triage, nine phases and the mind test.
How the agent animates, and how it checks what it made.
The agent animates like a motion designer: a container first, the content staggered in reading order while the container still moves, an accent last, and a quicker exit. It learns from runnable recipes in the animation catalog — a layered strap, a score change accent, a full-time result card, a league table re-rank and a stinger — each checked by Glider's tests.
| Tool action | Does |
|---|---|
| animations set_motion_style | Saves the page's motion style — calm, broadcast or energetic — to motion-style.json. Durations, easings, staggers and travel follow from it. |
| animations storyboard | Plans a take and describes each moment: which components wait, move, have landed or loop. Nothing renders. |
| animations frames | Renders the take off screen, in the Glider desktop app or an installed Chrome, and returns one contact sheet of up to nine frames for the agent to look at. |
| animations check | The motion rules and the motion checks together. |
| Motion check | Level |
|---|---|
| A package that only fades in, linear moves, or three or more components landing in one frame | Fail — the page is not ready. |
| Layers that wait for each other, an exit as slow as the entrance, a strap over 1.2 s or a full-frame build over 3 s | Review. |
| A 3D turn with no hinge, more than two loops on one scene, a bound number that changes with no accent, a clip far from the motion style | Review. |