motion-design-pro
Skill5 starsChanged 11 days agoMITView on GitHub
Designs, specs, implements, and reviews UI motion for SwiftUI and Jetpack Compose apps — purpose and emotional intent before properties, a motion personality and motion tokens (springs, curves, duration palette) in the design system, timing and easing tables, entrance/exit, feedback, loading, success/error, and choreography patterns, Reduce Motion alternatives, Lottie / dotLottie handoff, and a designer-facing motion spec. Use when adding or reviewing animations, transitions, micro-interactions, or loading and success states, when defining an app's motion language, or when turning a designer's motion prototype into code.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- app-intents-proSkill
- coredata-swift6-proSkill
- instruments-profiling-proSkill
- store-compliance-proSkill
- swift-accessibility-proSkill
- swift-adaptive-layout-proSkill
- swift-concurrency-proSkill
- swiftdata-proSkill
- swift-design-system-proSkill
- swift-docc-proSkill
- swift-error-handling-proSkill
- swift-logging-proSkill
- swift-memory-storage-proSkill
- swift-modularization-proSkill
- swift-package-proSkill
- swift-testing-proSkill
- swiftui-proSkill
- xcode-security-proSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Define the motion system: no motion tokens yet, a rebrand, or "make the app feel more X".
- Distinctive: line 21
If doing a partial task, load only the relevant reference file.
- Distinctive: line 37
Tokens, not numbers: Every animation in feature code references a named token.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Make motion that explains the interface: it shows where things come from, confirms that an action worked, and makes a state change legible, and it stays fast, consistent, and comfortable. This is the deep companion to the always-on apple-motion-design.md and android-motion-design.md rules. The rules steer code while it's written; this skill designs the motion system, writes the spec designers and developers share, builds the hard sequences, and audits what exists. It serves designers (the spec and the vocabulary) and developers (the tokens and the code) from the same source.
Sources. Adapted from the LottieFiles motion design skill (MIT, © 2025 LottieFiles; see
NOTICE.md): the three pillars, motion layers, personality archetypes, emotion mapping, Disney's principles for UI, timing and easing tables, patterns, and the quality checklist. Rewritten for SwiftUI and Jetpack Compose and checked against Apple's Human Interface Guidelines and Material 3 motion. Thank you to LottieFiles for publishing it openly.
Pick the mode from the request:
- Define the motion system: no motion tokens yet, a rebrand, or "make the app feel more X". Choose a personality with
references/principles.md, set tokens withreferences/timing-and-easing.md, writedocs/design/motion.mdfromreferences/motion-spec.md, and add the tokens to the DesignSystem /:core:designsystemmodule. - Spec or build an interaction: a designer's prototype, or "animate this". Work through the checklist below, pick a recipe from
references/patterns.md, and write the spec row before the code. - Review: existing animation feels slow, cheap, robotic, distracting, or janky, or before a release. Run
references/review.md(scan commands, quality checklist, smells and fixes).
If doing a partial task, load only the relevant reference file.
The Checklist (before any animation)
- Purpose: feedback, orientation, state change, attention, or delight. No purpose, no animation.
- Feeling: the emotional target (confident, calm, urgent, joyful) within the app's personality.
- Primary property: position, scale, opacity, color, or rotation, chosen from the purpose; add at most one supporting property.
- Duration from the element and travel distance; entrances longer than exits.
- Easing direction: decelerate in, accelerate out, ease both ends on screen, linear only for spinners and progress.
- Hero: one element leads; others follow 30–60 ms apart, total under ~500 ms.
- Reduced alternative: what plays under Reduce Motion / "Remove animations" (usually a crossfade, or nothing).
- Non-motion signal: the text, icon, haptic, or accessibility announcement that carries the same information.
Core Instructions
- System components first. Navigation, sheets, menus, M3 components, Liquid Glass, and predictive back already animate. Restyling their motion is a finding unless the design calls for it.
- Tokens, not numbers. Every animation in feature code references a named token. Raw durations and curves at the call site are findings, and so are two tokens that mean the same thing.
- Consistency beats flourish. The same interaction moves the same way everywhere; the motion personality covers about 90% of the app.
- Comfort and access are requirements: a reduced alternative for every spatial or looping animation, no information carried by motion alone, nothing longer than ~5 s without a pause, no blocked input.
- Performance: animate render-only properties (SwiftUI
opacity/scaleEffect/offset; ComposegraphicsLayer/ lambdaoffset), keep fewer than ~20 moving elements on screen, and profile dropped frames before guessing (instruments-profiling-proon Apple, the Compose layout inspector and Macrobenchmark on Android). - Speak both languages. Specs use the shared vocabulary (personality, duration tokens, enter / exit / standard curves, spring bounce); implementation notes map each token to SwiftUI and Compose.
- Severity by impact: blocking (motion ignores Reduce Motion for large or looping movement, motion is the only signal, animation blocks input, jank on a core flow) > degraded (wrong easing direction, linear movement, durations far off the table, overshoot on errors, stagger over 500 ms, ad hoc values instead of tokens) > polish (missing follow-through or secondary motion, inconsistent entrance direction).
- Cross-reference, don't duplicate: tokens and components go to
swift-design-system-pro/android-design-system-pro; SF Symbol effects toapple-iconography.md; VoiceOver and TalkBack details to the accessibility skills; recomposition or invalidation causes toandroid-compose-pro/swiftui-pro; visionOS motion comfort toapple-visionos-best-practices.md.
Output Format
Define mode: the chosen personality and why, the token table (role · SwiftUI · Compose · when to use), the reduced-motion policy, and the docs/design/motion.md file.
Spec / build mode: the spec rows (trigger · element · property · from → to · token · delay · reduced alternative · non-motion signal), then the code for each platform in scope.
Review mode: findings grouped by severity. Each gives file:line, what the viewer experiences, the principle it breaks, and the fix with before/after. End with the count per severity and the first three fixes.
Example finding:
Blocking — success animation is the only confirmation and ignores Reduce Motion
CheckoutView.swift:88: the order-placed state is a looping Lottie confetti with no text and no VoiceOver announcement, and it keeps looping under Reduce Motion.
// Before
LottieView(animation: .named("confetti")).playing(loopMode: .loop)
// After: plays once, still frame under Reduce Motion, and the text carries the meaning
VStack {
LottieView(animation: .named("confetti"))
.playbackMode(reduceMotion
? .paused(at: .progress(1))
: .playing(.toProgress(1, loopMode: .playOnce)))
.accessibilityHidden(true)
Text("Order placed")
}
.sensoryFeedback(.success, trigger: orderID)End of example.
References
references/principles.md: the three pillars, motion layers, personality archetypes and brand motion identity, emotion-to-motion map, Disney's principles for UI, attention budget, and context (platform, content type).references/timing-and-easing.md: duration tables, distance scaling, latency budgets, easing directions, M3 and Apple curves, springs mapped across SwiftUI and Compose, overshoot and stagger budgets.references/patterns.md: entrance and exit, press, hover and focus, toggle, success, error, loading, ambient, and multi-element recipes, with SwiftUI and Compose sketches.references/motion-spec.md: the designer–developer contract: thedocs/design/motion.mdtemplate, token files for both platforms, and Lottie / dotLottie handoff rules.references/review.md: scan commands, the quality checklist, motion smells and their fixes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

