web-animation-design
Web Animation Design
Scope and ownership
Use when the task involves animation, motion or interaction feel, or ADS identifies a specific motion defect. For ordinary UI work, the baseline motion reference is sufficient. ADS owns the task, authority, review and repair budget; this is its implementation specialist, not a second harness.
Start from the actual request and existing primitive, states and project tokens. Identify the state, hierarchy, causality or feedback job. Preserve clear static feedback when motion would add no value. A review request stays read-only; an implementation request proceeds within its existing authorization. Do not replace an actionable request with a generic readiness response.
The examples below are implementation options informed by Emil Kowalski's "Animations on the Web" course, not a required aesthetic or dependency set. Numeric examples are starting points only where project tokens do not already define the decision.
Review output
Report observed behavior, the relevant state/element, proposed change and evidence limits in the task's existing review. A before/after table helps compare several findings; a single defect needs no format ceremony. Separate deterministic state/timing checks, actual browser interaction, measured performance and the user's judgment of clarity and feel.