The skill
# Motion score:
The plan for motion, written before the code (motion-direction.md ). Fill only the parts the scope needs: a single fix needs the gate and one life cycle.
# Character
Action and flow · Why, from the subject Tokens motion_tokens.mjs --action <action> --flow <flow> → Out of character
# Layers in use
Layer In this project What it contains Feedback yes Continuity yes / no Arrival yes / no Signature yes / no Narrative yes / no
# The gate
Every candidate, including the ones rejected. What does not move is part of the design.
Candidate How often seen Kind (feedback, continuity, explanation, identity, narrative) Decision animate / do not animate, because
# Sequence:
One table per event that moves two or more things.
Trigger:
Element Role (lead, support, decoration, still) Starts Lasts Motion Relation (together, overlap, sequence, carry)
Cast as still, and why:
# Life of one interaction:
Stage Decision Rest Trigger Response within 100 ms Timing and easing <tokens, by job> Origin Continuity Interruption Reversal Completion Reduced motion Touch, keyboard, assistive technology
# Signature moment
Fact and device it comes from How it is discovered What the visitor understands afterwards What it hands on to Fallbacks: touch, keyboard, reduced motion, no script, a slow device
# Seen
Moment Command Strip Questions raised, and the answer Entrance motion_strip.mjs <url> --trigger load --reducedmotion_strip.mjs <url> --trigger "click:<selector>" --interrupt 120 --exit undo
Not checked by a person on a device:
On this page
Character Layers in use The gate Sequence: Life of one interaction: Signature moment Seen