I’ve been exploring what happens when a React component library drops floating cards, soft shadows, and 60fps spring physics in favor of production mechanics from sequential print layout and traditional cel animation.
The result is FRAME/12 ( GitHub (MIT) · Live Motion Studio ), a zero-dependency copy-in React + TypeScript registry ( shadcn -compatible) and AI agent skill.
Here are the four most interesting React & DOM problems we had to solve while building it:
1. Quantizing an easing curve "on twos" (useOnTwos)
In hand-drawn animation, most movement is shot "on twos"—each drawing is held for two frames at 24fps ( 83.33ms per pose, 12 poses per second). Simply applying CSS steps(4) with linear timing feels robotic because every jump covers the exact same distance.
Instead, useOnTwos samples a cubic ease-out spacing chart inside requestAnimationFrame , bucketed into 83.33ms ( 1000 / 12 ) intervals.…