← ClaudeAtlas

swift-motion-animatelisted

Build an animation in a Swift app (SwiftUI, iOS 17+, iOS 18/26/27 additions marked) with a decision order that ends in working code: whether to animate at all, then purpose, API, spring values, interruption, exit, Reduce Motion and haptics. Use whenever someone wants to add, build, polish or port motion, even if they only say 'animate this', 'add some motion', 'make it feel alive' or 'add a transition'. Covers withAnimation vs .animation(_:value:), springs and bounce, transitions, press-feedback ButtonStyles, toasts, menus and popovers, list insert/remove, numericText counters, symbolEffect, error shake, success checks, matchedGeometryEffect and zoom heroes, PhaseAnimator/KeyframeAnimator, staggered choreography, Liquid Glass morphs, sensoryFeedback, keeping new motion hitch-free, and porting CSS/Framer Motion. For drag, swipe, fling or sheet-drag motion use swift-motion-gestures; to critique, audit or trim existing motion use swift-motion-review; to stress-test layout use swift-motion-break-ui.
v-murygin/swift-motion · ★ 0 · Web & Frontend · score 72
Install: claude install-skill v-murygin/swift-motion
# swift-motion-animate Turn a request for motion into an implementation that would pass a strict review the first time. The answer is code plus a few lines of reasoning, never a menu of options. "This shouldn't animate" is a valid answer, and zero lines of code is sometimes the right result. **Hand off instead when:** - the motion follows a finger (drag, swipe, fling, rubber-banding, custom sheet drag, velocity hand-off, interruptible gesture) → `swift-motion-gestures` - the user wants existing motion critiqued, audited, trimmed or removed, or wants to find places that could animate → `swift-motion-review` - the user wants to see how a view breaks with long text, AX5, RTL, empty or huge data → `swift-motion-break-ui` A tap-driven animation that ends in a gesture (a toast you can also swipe away) is built here, with the drag part built per `swift-motion-gestures`. ## The posture You are building the animation yourself. Three failure modes, the first the worst: 1. **Animating something that shouldn't animate.** Each animation is defensible alone; together they make an app feel slow. The gate below exists to produce zero lines of code sometimes. That's a success, not a dodge. 2. **Animating the right thing with the wrong ingredients**: `.easeIn` on an entrance, a scale from 0, keyframes on a toast, bounce on a tap-opened panel, a duration that makes a menu feel sluggish. 3. **Changing more than was asked**: new files, app-wide extensions, a lifetime or layout no