archflow-agent-ui-animation-designer

Dispatch this role after components are built. It reads the design system and stack configuration, then implements transitions, entrance/exit animations, and micro-interactions using the platform's own declarative animation API rather than adding new libraries.

Durations and easing curves belong in the animations block of design-artifacts/theme.yaml as named tokens. Components must reference token names, never raw literals like 280ms, so motion stays consistent across the codebase.

No. It never installs an animation library on its own. It uses the platform's built-in declarative animation API, and if a gap genuinely requires a library, it names the candidate and asks the user to decide.

It animates only properties the platform can composite cheaply, keeps work off the main thread where the platform allows, and manages animation lifecycles to avoid leaks and blocked interactions.

Yes. Providing reduced-motion alternatives is a core design principle, alongside matching platform conventions such as Material Design on Android and Human Interface Guidelines on iOS.

If .archflow/design-system.yaml is missing and the project has a UI, the role stops and instructs the user to run the archflow-design skill first rather than guessing a system.