← ClaudeAtlas

swift-motion-reviewlisted

Reviews and audits motion in a Swift app's UI code (SwiftUI) - animations, transitions, gestures, haptics, Reduce Motion and performance - with plain-language explanations and exact fixes. Four modes: Review a diff, PR or file into severity-ranked findings with a Block, Request changes or Approve verdict; Audit a codebase into a prioritized report and executable plans; Find places that should animate but don't; Remove motion that should go, by subtraction only. Use it whenever someone asks to review, audit, critique, clean up or tone down animations, asks "is this animation right?", "why does this feel janky or slow?", "where should this animate?" or "is there too much animation?", or shares code using withAnimation, .animation(, .transition(, matchedGeometryEffect, springs, sensoryFeedback or DragGesture and asks if it is right or what to change. Not for building new motion (swift-motion-animate) or gestures (swift-motion-gestures), or stress-testing a layout with worst-case data (swift-motion-break-ui).
v-murygin/swift-motion · ★ 0 · Code & Development · score 72
Install: claude install-skill v-murygin/swift-motion
# Motion Review Judge motion in a Swift app's UI code (SwiftUI today), explain what is wrong in words the developer can learn from, and say exactly what to change. The bar is high on purpose: every animation is defensible alone, and together they make an app feel slow. Agents and developers add motion by default, so a reviewer's default is to flag. Approval is earned, not assumed. A transition that "works" but feels sluggish, lands from the wrong origin, fires too often, ignores Reduce Motion or drops frames is a regression, not a pass. Baseline is iOS 17. Newer APIs are marked **(iOS 18)**, **(iOS 26)** or **(iOS 27)**. Some 2023 animation APIs show an earlier version in current docs because they are back-deployed; cite them as iOS 17. The `@Animatable` macro needs the Xcode 26+ toolchain but deploys back below iOS 17, so it is fine at the baseline. ## Pick the mode Read the request and pick one mode. Name it in the first line of the output. | The request sounds like | Mode | Touches code? | |---|---|---| | "Review this diff / PR / file", "is this animation right?", "check my transition" | **1. Review** | No. Findings only | | "Audit the motion in this app", "plan the animation cleanup", "where is motion wrong across the app?" | **2. Audit** | No. Report and plan files only | | "Where should this animate?", "this feels static", "make it feel more alive" | **3. Find opportunities** | No. Proposals only | | "Remove / tone down / cut the motion", "strip the extra animatio