About motion-reference
motion-reference is a skill for people designing iOS interactions, using the 60fps library of motion breakdowns and SwiftUI recreations as references. It guides searches, evaluation, and delivery of a standalone code sample.
Key features
- 01Search clips with natural-language descriptions
- 02Review motion breakdowns and timing
- 03Retrieve standalone SwiftUI code
- 04Find related shots when a match is close
- 05Assess results by their actual fit
Use cases
- 01Reference a real iOS interaction when designing motion
- 02Inspect timing and easing for an interaction
- 03Generate a SwiftUI motion example for Xcode
MCP support
The skill uses the 60fps MCP server to search shots, retrieve motion breakdowns and code, and find related shots.
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/motion-referencein Claude Code to confirm it loaded.
Details
From the project READMEMotion reference
The 60fps MCP server holds 2,000+ clips of real iOS interactions. Each one has a written motion
breakdown, and many have a compile-checked SwiftUI recreation. Use it instead of inventing timings.
The numbers in this library came off apps that shipped.
Use the tools in this order
60fps_search_shots. Write natural language, not keywords. "Springy bottom sheet for checkout" works. "Sheet" does not. Only setapporfiltersif the user named one.60fps_get_motion_breakdown. This gives you the start state, the transition, the end state, and the timing and easing. Design from this.60fps_get_motion_code. This returns a self-contained SwiftUI file. Show it to the user in full, in a swift code block. It is the deliverable, not a citation.60fps_get_related_shotsif the first pick is close but not right.
Read the results honestly
Search ranks the whole library by closeness, so it always returns something, however far off the
question was. A high total is how many shots were searched, not how many matched. Judge each
result on its own merits, and say so when nothing fits.
When not to use it
The library is iOS only, and it is about motion.
Do not use it for Android, Material, Flutter, React Native or web. Do not use it for icon design, colour palettes, logos or brand work. Do not use it for performance or frame-rate profiling, which shares the name and nothing else. On any of those it will still return iOS clips, and they will be wrong. Answer directly instead.
Using the code
Each file is standalone. Paste it into Xcode and run it.
It carries none of the original app's words, colours, branding or assets, by design. Restyle it to the user's design system. The motion is the part worth keeping.