Motion 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

1. 60fps_search_shots. Write natural language, not keywords. "Springy bottom sheet for checkout" works. "Sheet" does not. Only set app or filters if the user named one.
2. 60fps_get_motion_breakdown. This gives you the start state, the transition, the end state, and the timing and easing. Design from this.
3. 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.
4. 60fps_get_related_shots if the first pick is close but not right.

Read the results honestly