amvcp-anim-handoffs

Coordinate cross-skill animation handoffs for amvcp pages across print and touch contexts.

Updated May 8, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-visual-communicator-plugin --skill amvcp-anim-handoffs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amvcp-anim-handoffs
Source: https://github.com/Emasoft/ai-maestro-visual-communicator-plugin/tree/main/skills/amvcp-anim-handoffs
Command: npx skills add https://github.com/Emasoft/ai-maestro-visual-communicator-plugin --skill amvcp-anim-handoffs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents mismatched animation behavior when multiple amvcp skills (charts, diagrams, steppers, slide decks, and interactive controls) need to work together on the same page, especially across reduced-motion, print/PDF export, and touch/keyboard parity.

Core Features & Use Cases

  • Cross-skill animation handoffs: shares concrete animation contracts (chart counter primitive, diagram scroll-reveal + SVG edge reveals, stepper spin keyframe, and slide entrance/transition moods) so consumers wire into one consistent animation surface.
  • Counter and reveal coordination: supports KPI card counter animations via animateStat(el) and standardized data-va-reveal patterns to align entrance timing.
  • Print + PDF intelligibility: defines the expected behavior that animated elements render at final state under @media print, avoiding invisible stagger items and loading placeholders in exported documents.
  • Touch and keyboard parity: ensures hover-driven affordances have keyboard equivalents via :focus-visible, and documents which animations naturally degrade on touch.

Quick Start

Tell your AI to wire charts, flow diagrams, slide decks, and interactive steppers to this shared animation contract while ensuring print and keyboard/touch parity match the documented handoffs.

Frequently Asked Questions about amvcp-anim-handoffs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep scroll reveal animations consistent when combining charts and diagrams on the same page?

Scroll reveal animation consistency is maintained by sharing standardized data-va-reveal contracts and the animateStat primitive, ensuring all interactive components wire into one unified animation surface without timing conflicts.

Why do my animated elements disappear when exporting a page to PDF?

Animated elements disappear in PDF export because they lack defined print media behavior; applying documented print substitutes forces elements to render at their final state under @media print, avoiding invisible stagger items.

What is the best way to add keyboard parity to hover-driven animation affordances?

Keyboard parity for hover-driven animations is achieved by implementing :focus-visible pseudo-classes, ensuring interactive steppers and controls remain fully navigable and functional when users interact via keyboard instead of mouse.

How do I handle reduced motion preferences for KPI counter animations?

Reduced motion preferences for KPI counter animations are handled by applying documented reduced-motion substitutes, ensuring animateStat behaviors degrade gracefully and display final values immediately without visual movement.

Can I coordinate slide deck entrance transitions with chart counter animations?

Slide deck entrance transitions and chart counter animations can be coordinated using shared mood and transition selections, allowing multiple amvcp animation consumers to align their entrance timing and visual behaviors seamlessly.

Do I need shared animation contracts to run interactive steppers across touch and desktop?

Shared animation contracts are required for interactive steppers across touch and desktop, providing the spin keyframe usage and focus-visible parity needed to ensure consistent behavior and degradation on touch devices.