character-rigging

Split the character into independently transformable parts, define a pivot for each moving part in the artwork's coordinate space, assign explicit layer order, and add rotation constraints on joints. Store everything as a data package rather than hardcoding runtime logic.

A rig_plan is a JSON data package describing a character's parts, kinds, layers, parent hierarchy, and joint pivots with rotation limits. Renderers consume it to animate the character without character-specific runtime code.

Use explicit SVG-coordinate pivots with GSAP's svgOrigin property rather than relying on CSS transform-origin, which is browser-defined and sensitive to coordinate space. Define pivots in the same coordinate space as the artwork.

No. Remotion animations must be deterministic and driven by the current frame via useCurrentFrame. Any randomness or wall-clock timing breaks rendering consistency across frames.

Layer order often breaks because it relied on SVG source order, which is not preserved after generation. Keep layer order explicit in the rig data, and ensure every moving part has a defined pivot and parent.