2D Character Rig Animation

2D character rig animation

Use this skill after the character design and approved model/reference sheets exist. Its job is to turn that design into a reusable performance system whose parts stay connected, poses remain on-model, facial states read clearly, and animation can be reproduced across shots and runtimes.

The rig may be SVG, layered vector art, raster cutouts, a bone-and-mesh puppet, or a hybrid. Runtime APIs differ; the production contract does not.

Boundaries

This skill owns:

• part decomposition, draw order, hierarchy, pivots, controls, and constraints;
• bind/rest pose and coordinate conventions;
• rigid cutout versus deforming mesh decisions;
• reusable body poses, facial states, visemes, gestures, and cycles;
• acting and choreography using the approved character;
• deterministic animation handoff and rig-specific QA;
• rig asset rights, likeness limits, provenance, and delivery notes.

It does not own:

• the character's visual identity, costume continuity, or reference-generation strategy;
• 3D armatures, volumetric deformation, or DCC-specific rigging;
• capture, cleanup, or retargeting of motion-capture data;
• voice performance, lip-sync provider selection, or final compositing;
• redesigning an approved character to hide a rig defect.

Evidence stance

• Documented fact: behavior from SVG/W3C, browser, accessibility, or other authoritative technical documentation.
• Production heuristic: an animation or rigging practice that must be adapted to the design and runtime.
• Empirical observation: measured behavior from the actual rig preview, frame samples, render, or delivery crop.

Technical references were checked 2026-07-12. Runtime-specific transform, clipping, mesh-deformation, IK, and export behavior is volatile; verify the selected renderer and version before committing the rig architecture.

Lock the rig contract

Collect or create:

• approved turnaround/model sheet and character bible;
• exact deliverables, aspect ratios, resolution, fps, duration, and runtime candidates;
• required views, actions, emotional range, dialogue languages, props, and interactions;
• whether the rig uses rigid pieces, deforming meshes, replacements, or a hybrid;
• maximum limb bends, reaches, squash/stretch, head turns, and perspective cheats;
• body and facial control list;
• naming, coordinate, unit, pivot, and transform-order rules;
• source-art, performer-likeness, font, prop, and brand rights;
• deterministic timeline format and renderer handoff;
• approval poses and test actions.

If the approved design cannot separate or deform without visible damage, return to design with a specific production constraint. Do not quietly alter anatomy, costume, logo placement, disability representation, or signature features.

Decompose the artwork by motion responsibility

Split the character where independent motion, occlusion, deformation, replacement, or attachment requires it. Too few parts limit acting; too many parts produce seams, draw-order problems, and maintenance cost.

Typical roles:

character-root
+- shadow
+- rear-accessories
+- pelvis
|  +- torso-chain
|  |  +- chest
|  |  |  +- neck
|  |  |  |  `- head
|  |  |  +- arm-left
|  |  |  `- arm-right
|  |  `- clothing-overlap
|  +- leg-left
|  `- leg-right
+- front-accessories
`- fx-and-contact-guides

The face can use nested controls for brows, lids, pupils, mouth replacements/deformation, cheeks, and optional head-turn features.

Production heuristics:

• Separate at natural joints, seams, hair clumps, garment layers, and rigid accessories.
• Add overlap beyond visible edges so rotation does not open gaps.
• Preserve a clean silhouette at intended playback size.
• Keep left/right names from the character's perspective and document that convention.
• Separate draw order from transform hierarchy when the runtime permits it.
• Use stable ASCII IDs that survive export; avoid names based only on layer numbers.

Coordinate systems and SVG structure

Documented fact: SVG establishes viewports and user coordinate systems. viewBox maps a specified rectangle into the viewport, and transforms can be applied to elements and groups. Nested group transforms compose through the hierarchy.

For SVG rigs:

• set one intentional root viewBox and document character scale/origin;
• place each rotating group around an authored pivot;
• avoid mixing unexplained transforms from design tools with runtime transforms;
• flatten only transforms that do not destroy editable pivots or hierarchy;
• preserve clipping paths, masks, gradients, IDs, and references through optimization;
• scope IDs when multiple character instances may share a document;
• test the exported SVG rather than only the design-tool preview.

Use a neutral root pose with known local transforms. Store pivots numerically in the rig manifest even when the runtime can infer transform origins, because browser and export behavior can differ.

Choose rigid, replacement, or deforming parts

Rigid cutout parts

Best for graphic, mechanical, paper-puppet, or limited-animation styles. Rotate/translate/scale whole parts around joints. Protect seams with overlap art and occlusion layers.

Replacement parts

Best for discrete hand shapes, mouth poses, eye shapes, perspective turns, and props. Define mutually exclusive groups and transition rules. A replacement is not a tween unless an actual in-between design exists.

Deforming meshes or paths

Best where bending a rigid piece would create an obvious elbow, torso, cloth, tail, or facial defect. Define control influences and limits, then test extreme poses. Keep deformation local; excessive influence creates rubbery volume loss.

Hybrid

Often appropriate: rigid forearm plus replacement hands, deforming torso, replacement mouths, and layered hair chains. Choose per visual requirement rather than forcing the whole character into one technique.

Build the hierarchy and controls

Every control should have:

• stable ID and human-readable name;
• parent and optional visual-part binding;
• local pivot and rest transform;
• allowed translation, rotation, scale, or replacement values;
• hard/soft limits;
• preferred direction and neutral value;
• draw-order or visibility effects;
• test poses and known exceptions.

FK and IK planning

Use forward kinematics when rotations should flow from parent to child and arcs are artist-directed: spine, head, tail, hair, loose gestures. Use inverse kinematics when an endpoint must stay attached: planted foot, hand on a desk, prop grip. A hybrid arm/leg rig may switch modes only with an explicit match procedure so the limb does not pop.

IK requirements:

• target and bend/pole direction;
• chain length and reach limits;
• soft behavior near full extension;
• stretch policy;
• fallback when the target is unreachable;
• FK/IK match pose and keyed switch frame.

Never let the solver choose an arbitrary elbow/knee direction at a singularity.

Pose library as production vocabulary

Create poses that represent performance intent, not only technical extremes:

• neutral/default and breathing idle;
• attention/listening;
• positive, negative, uncertain, surprised, concentrated, and character-specific emotional states;
• open/closed hand, point, present, hold, reach, and contact poses;
• walk/run/contact/pass/up/down keys where locomotion is required;
• seated, crouched, turn, enter, exit, and prop-specific poses;
• safety/extreme tests for every joint and deformation region.

Each pose record should include body controls, face state, hand/prop state, view variant, hold suitability, and approved transitions. Pose libraries accelerate work only when they preserve character-specific acting; generic emoji poses are not a performance system.

Facial rig and dialogue states

Separate controls for:

• eye direction and convergence;
• upper/lower lids and blink closure;
• brows and asymmetry;
• mouth open/close, corners, width, roundness, and jaw where relevant;
• optional cheek, nose, ear, or accessory motion;
• head-turn replacement features.

Viseme count should match the style, language, shot size, and schedule. Do not prescribe a universal inventory. Group phonemes that look similar at the target resolution, but preserve closures and distinctive shapes needed for intelligibility. Record which languages the set has actually been tested against.

Dialogue direction:

• mouth shapes follow timed speech, not arbitrary frame cycling;
• preserve complete closure where bilabial sounds require it;
• lead or lag only as an intentional style decision;
• add blinks, gaze, brows, head motion, and gestures as performance, not noise;
• avoid changing every control on every syllable;
• hold readable facial poses across fast cuts.

Do not infer emotion or personality solely from an automatic transcript. Use the approved performance direction.

Animate performance, not controls

Plan each beat with:

• objective and emotional change;
• line/action timing;
• primary pose and silhouette;
• anticipation;
• main action and contact;
• settle, overlap, and hold;
• gaze and hand intention;
• camera/crop relationship.

Production heuristics from animation craft:

• Pose the line of action and silhouette before polishing limbs.
• Move the character's center/root consistently with weight and contact.
• Let secondary chains such as ears, hair, clothing, or tails follow the primary action with controlled delay.
• Favor arcs for organic joints unless the style is deliberately mechanical.
• Use stillness. A held, specific pose can read better than constant idle motion.
• Apply squash/stretch only where the construction and material permit it; preserve intended volume unless the style says otherwise.

Cycles and contacts

For a cycle, define exact first/last compatibility, contact phases, root travel, and whether it is in-place or translating.

Walk-cycle QA:

• planted feet remain fixed relative to the ground during contact;
• root travel matches stride length;
• knees and elbows keep intended bend direction;
• limb lengths do not jump;
• torso/hip counter-motion supports weight;
• first/last frames do not create a duplicate-frame hitch;
• accessories loop without a snap.

For object contact, decide which system owns the attachment. A prop should not be independently animated while also parented to a hand unless the offset is intentional and documented.

Deterministic timeline handoff

Deliver animation as explicit time-addressable state. A renderer may request frames backward or out of order.

Recommended shot record:

{
  "shot_id": "explain-step-two",
  "fps": 30,
  "start_frame": 0,
  "end_frame": 179,
  "rig_version": "presenter-rig-03",
  "view": "three-quarter-right",
  "tracks": {
    "root.position": [[0, [0, 0]], [72, [8, -3]], [179, [0, 0]]],
    "arm_right.rotation": [[42, 4], [64, 28], [110, 28], [142, 6]],
    "mouth.pose": [[51, "M"], [55, "AH"], [60, "rest"]]
  }
}

This is an example schema, not a repository requirement.

Handoff rules:

• use frame numbers or exact rational timing consistently;
• state degrees versus radians and coordinate orientation;
• record interpolation/ease per segment;
• avoid unseeded random blink/idle timing in final renders;
• keep visibility and replacement changes explicit;
• ensure any solver produces the same state from the same frame;
• test forward, backward, first, last, and isolated frames.