team-motion-design

Design and validate motion systems for UI animation and reduced-motion accessibility.

76|5|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catlog22/pi-maestro-flow --skill team-motion-design-catlog22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-motion-design
Source: https://github.com/catlog22/pi-maestro-flow/tree/main/.pi/skills/team-motion-design
Command: npx skills add https://github.com/catlog22/pi-maestro-flow --skill team-motion-design-catlog22

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns motion design from ad hoc animation work into a structured pipeline, helping teams create consistent transitions, scroll choreography, and accessible reduced-motion fallbacks without sacrificing performance.

Core Features & Use Cases

  • Motion token systems: Define easing, duration, and stagger tokens so animation styles stay consistent across a product.
  • Component and page choreography: Plan and implement entry, exit, hover, focus, and scroll-triggered sequences with compositor-safe properties.
  • Performance and accessibility validation: Verify FPS, layout thrashing, will-change budgets, and prefers-reduced-motion compliance before shipping.
  • Use case: A product team can use this Skill to research existing animations, design a motion system, generate implementation artifacts, and test them for 60fps performance.

Quick Start

Ask for a motion design workflow for your target component or page, and the Skill will analyze the scope, design the animation system, implement the motion artifacts, and validate performance and accessibility.

Frequently Asked Questions about team-motion-design

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

FAQPage Schema
How do I design a motion system with consistent CSS animations and scroll choreography?

To design a motion system, define easing, duration, and stagger tokens for consistent UI animation styles, then plan scroll choreography and component sequences using compositor-safe properties to ensure smooth transitions across the product.

What is performance testing for UI animation and how does it enforce will-change limits?

Performance testing for UI animation validates FPS, checks layout thrashing, and enforces will-change budgets to prevent janky transitions. It ensures component animations run at 60fps before shipping.

How do I add reduced motion accessibility fallbacks to existing animation systems?

Reduced motion accessibility is added by enforcing prefers-reduced-motion compliance within the animation system. This involves generating alternative orchestration logic and fallbacks that disable or simplify scroll choreography for sensitive users.

Can I use token-based motion design workflows for page-level reveal sequences?

Yes, token-based motion design workflows apply to page-level reveal sequences. You can plan and implement entry, exit, hover, and scroll-triggered sequences using structured motion tokens to maintain consistency.

What is the best way to structure component animations to avoid layout thrashing?

The best way to avoid layout thrashing in component animations is to generate compositor-safe CSS and orchestration logic. This approach restricts animations to specific properties and limits will-change usage to maintain performance.