amvcp-animation

Route animation requests by matching user intent phrases to a routing matrix that directs entrance, scroll reveal, and hover lift intents to the appropriate sibling module contract. The router itself emits no output, selecting and composing the correct sibling files instead.

To handle multiple UI animation effects together, load the foundation sibling module first, then compose additional focused siblings like scroll reveal and hover lift as needed to satisfy each animation contract.

For animation routing requests spanning multiple siblings, the router provides span handling guidance and applies a default fallback route to the foundation sibling when the specific target module is uncertain.

Yes, you need to load the DESIGN.md engine and the colocated amvcp-animation.js substrate before selecting and composing sibling SKILL.md files to ensure animation output follows the correct runtime contract.

The animation routing matrix supports motion effects including entrance, scroll reveal, hover lift, counters, performance loop considerations, and slide or print handoffs where output must follow a sibling contract.

The animation router fails to emit UI motion token output because it is designed to route intents and compose sibling files rather than generate output directly, ensuring all animation behavior follows the specific sibling's contract.