Define motion system contracts with timing, easing, and reduced-motion fallbacks.
npx skills add https://github.com/vTRKA/supervibe --skill motion-effect-system
Please help me install this Agent Skill. Skill: motion-effect-system Source: https://github.com/vTRKA/supervibe/tree/main/skills/motion-effect-system Command: npx skills add https://github.com/vTRKA/supervibe --skill motion-effect-system
Motion requirements often stay informal, causing accessibility gaps, inconsistent easing/timing, missing reduced-motion parity, and unprovable runtime claims during design and handoff.
Use motion-effect-system to define a token-governed animation recipe and its reduced-motion/no-motion fallback before routing implementation to runtime specialists for a specific UI state or handoff artifact.
High-intent search queries and answers about installing and using this skill.
An accessible motion design system requires defining named timing tiers, easing tokens, and choreography rules while enforcing reduced-motion and no-motion equivalents. This creates a verifiable design contract that separates static review from required runtime proof.
A motion system contract for design handoff is a defined set of named timing tiers, easing tokens, and approval boundaries dictating when motion is allowed or must be removed. It enforces anti-slop evidence and gate IDs for verifiable runtime claims.
You enforce reduced-motion accessibility in animation tokens by requiring no-motion equivalents and reduced-motion handling tied to evidence rather than taste. The system separates static approval from required browser runtime proof to prevent accessibility gaps.
Yes, this motion design approach handles state-transition choreography across interaction, route, media, and runtime boundaries for app surfaces. It defines choreography rules and delegates actual playback implementation to runtime-focused specialists.
The best way to document animation tokens for handoff is generating an output report that separates static approval from required browser runtime proof. This enforces anti-AI-slop evidence and gate IDs to verify all motion claims.
You should not use a system-level motion contract for prototypes if you need actual playback or implementation, as this approach solely defines the token-governed animation recipe. It routes runtime execution to specialized skills after setting the contract.
vTRKAGuides web UI motion and micro-interaction design with output contracts.
vTRKAEnforce reduced-motion fallbacks and validate with browser/runtime evidence.
catlog22Design and validate motion systems for UI animation and reduced-motion accessibility.
Shaarav4795Define UI motion guidelines for timing, easing, reduced-motion, and transitions.
