rock3r/android-ux-skills
Agent skills for Android motion and design-engineering craft: add motion that belongs, map a codebase's motion language into a MOTION.md, and review motion adversarially.
Decide whether motion belongs and what it should feel like, then build it. Covers the frequency gate, naming a purpose, choosing the transition pattern from the relationship, MotionScheme and spring selection, interruption and velocity handoff, and how motion degrades when the user has switched animations off. Conforms to the codebase's MOTION.md where one exists. Use when adding motion, deciding how something should feel, choosing a transition between screens, tuning a spring, or deciding whether to animate at all. Does not choose between AnimatedVisibility, animate*AsState, AnimatedContent and Crossfade — that is chrisbanes/skills compose-animations; recomposition, stability and phase diagnosis are its compose-performance; XML-to-Compose migration, edge-to-edge and Navigation 3 are android/skills; Material 3 tokens, components and theming conformance are hamen/material-3-skill.
Read-only audit of motion across an Android codebase. Maps the product's motion language into a MOTION.md the team can approve and maintain, and writes self-contained plans a cheaper agent can execute without the context that produced them. Refuses to invent conventions: where no coherent motion language exists it says so and asks rather than fabricating one, and it never writes a DECIDED entry because only a human can ratify a decision. Use when auditing motion across a repository, establishing or recording a motion language, asking what a codebase's motion conventions are, or preparing motion work for another agent to carry out. Does not modify source. Does not review a single change — that is review-android-motion; does not implement — that is animate-compose.
Adversarial review of Android motion that ends in an explicit block or approve. Judges whether motion should exist at all, whether it matches the product's own motion language recorded in MOTION.md, whether it still carries meaning when the user has switched animations off, and whether it holds together as a single event. Forms its design judgment in isolation before seeing any mechanical rule findings, so that gradeable defects do not crowd out the expensive kind. Use when asked to review, critique or sanity-check motion, an animation, a transition, or whether a screen feels right. Does not review general Compose correctness, recomposition or stability — that is chrisbanes/skills; does not score Material 3 conformance — that is hamen/material-3-skill; does not implement fixes — that is animate-compose.