What problem does it solve? Interfaces often suffer from motion that is missing where it would aid comprehension, excessive where it slows users down, or inconsistent with the spatial model of the UI. This Skill performs a read-only investigation of an existing UI and reports only high-confidence motion opportunities and motion debt, without modifying any source code. ## Core Features & Use Cases - Read-only UI investigation: Inspects existing motion primitives, tokens, libraries, and key interactions, then observes rendered behavior across state changes, gestures, feedback, and navigation. - Four-gate candidate filtering: Every candidate must pass frequency, purpose, interference, and spatial continuity checks before being reported, eliminating weak or decorative suggestions. - Prioritized reporting: Surviving candidates are reported with location, current behavior, purpose, frequency, observed problem, suggested motion relationship, and relevant existing tokens or primitives. - Use Case: Before a redesign sprint, run the audit on your app's navigation and list interactions to find where route transitions break spatial continuity or where async completions lack feedback, then hand the surviving candidates to an implementation pass. ## Quick Start Audit this project's UI for motion opportunities and motion debt, and report only the candidates that pass all four motion gates.
