lottie-rive-animation

What problem does it solve?

Broken or unverified Lottie/Rive motion commonly fails in real browsers due to missing assets, unsupported runtime features, invisible frames, reduced-motion gaps, or absent fallbacks—leaving product states unclear and delivery confidence low.

Core Features & Use Cases

• Evidence-first runtime verification: plans and insists on browser proof for load, nonblank render, playback behavior, reduced-motion handling, interaction, performance, and cleanup.
• Purpose-driven runtime selection: guides choosing the lightest viable option (native CSS/WAAPI/SVG/DOM first, then Lottie or Rive) and rejects decorative-only motion.
• Anti-AI-Slop artifact governance: requires an artifact-scoped anti-slop report with gate taxonomy evidence before approval or handoff, preventing generic “looks good” claims.
• Rive state-machine and fallback discipline: validates artboard/state-machine inputs and ensures interaction, fallback, and disabled/error states are covered.
• Video-adjacent integrity: supports storyboard/poster alternatives when rendered video capability or media proof is unavailable.

Quick Start

Ask your AI tool to run the Lottie/Rive animation skill to plan, implement, and produce a browser-proof report with required anti-slop gates for your target asset.