disney-animation-rule-skill

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: disney-animation-rule-skill
description: Apply Disney's 12 principles as practical design and engineering rules for procedural animation. Use when creating, improving, reviewing, or debugging code-driven motion in web, SVG, canvas, React, Remotion, game, UI, character, camera, or 3D scenes; especially when motion feels stiff, weightless, mechanical, unclear, or physically correct but visually weak.
---

# Disney Animation Rules for Procedural Animation

Design motion for readable intent, weight, rhythm, and personality. Treat physical simulation and interpolation as inputs, not as the final animation.

Do not force all 12 principles into every shot. Select the smallest set that fixes the perceptual problem.

## Workflow

1. Inspect the scene, code, inputs, renderer, and project constraints before changing motion.
2. State the action in one sentence: subject, intention, force, destination, and desired feeling.
3. Identify the primary action and rank all secondary actions beneath it.
4. Block semantic phases and event poses before selecting easing curves.
5. Select relevant principles from `references/twelve-principles.md`.
6. Define one deterministic state evaluator from frame or time plus explicit inputs.
7. Derive deformation, overlap, accents, and effects from primary motion or semantic events.
8. Tune timing and spacing at representative frames, then review the full motion.
9. Remove effects that hide weak posing, unclear timing, broken contacts, or poor silhouettes.

For detailed engineering patterns, read `references/implementation-patterns.md`. For the motivating jump comparison, read `references/clawd-jump-case-study.md`.

## Block the Action

Define event poses such as:

- Rest or setup
- Anticipation
- Commitment or launch
- Passing pose
- Apex, hold, or decision point
- Contact or impact
- Overshoot
- Settle or recovery

Adapt the vocabulary to the action. A button press may use rest, press, contact, overshoot, and settle. A camera move may use establish, accelerate, reveal, brake, and settle.

For each phase, specify:

- Duration or duration ratio
- Position and path
- Velocity at each boundary
- Scale, rotation, and pivot
- Contact constraints
- Silhouette or readability goal
- Secondary-action lag
- Optional accent such as smear, blink, particles, or camera shake

Prefer a phase table or explicit constants over one opaque easing expression.

## Build the Motion Hierarchy

Build in this order:

1. Preserve functional constraints, contacts, bounds, and input behavior.
2. Make the primary path and timing readable with the subject rendered as a simple shape.
3. Add pose changes and deformation around force and contact events.
4. Add follow-through and overlap with controlled phase offsets.
5. Add secondary action that reinforces, never competes with, the main action.
6. Add accents only where speed, impact, or clarity justify them.

Make the primary motion work without motion blur, particles, trails, or sound.

## Engineer Deterministically

- Compute animation state as `state = f(frameOrTime, inputs, parameters)`.
- Keep evaluation independent of previous renders and render order.
- Preserve fractional frames through interpolation and derivative calculations.
- Seed procedural variation from stable identifiers; never use unseeded randomness during rendering.
- Derive velocity and acceleration analytically or by sampling the pure state function.
- Snapshot interactive inputs at an intentional commitment event when later changes would break the action.
- Keep contact anchors fixed during squash, stretch, recoil, or settle unless sliding is intentional.
- Preserve position and velocity continuity across phase boundaries unless a deliberate hit, cut, or snap requires discontinuity.
- Normalize thresholds and amplitudes by subject size, travel distance, viewport, or scene scale.
- Clamp exaggeration to protect legibility, geometry, and interaction constraints.

For Remotion, make every frame independently calcul