AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Search 2,000+ real iOS interaction clips by describing the motion you want, then get compile-checked SwiftUI back. MCP server plus skill for Cursor, Grok and Claude Code.
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
Describe the motion you want. Get back a real iOS clip that does it, and a SwiftUI file that
recreates it.
The library holds 2,000+ interaction clips from apps that shipped. Each one comes with a written
breakdown of its motion: the start state, the transition, the end state, and the timing and easing
behind it. Use it instead of guessing numbers.
Skills come with it. Each one teaches the agent a bigger job, using the same tools:檢視完整 README ↗Describe the motion you want. Get back a real iOS clip that does it, and a SwiftUI file that recreates it.
The library holds 2,000+ interaction clips from apps that shipped. Each one comes with a written breakdown of its motion: the start state, the transition, the end state, and the timing and easing behind it. Use it instead of guessing numbers.
| Tool | What it does |
|---|---|
60fps_search_shots | Semantic search. Describe the motion, not keywords. |
60fps_list_filters | Every filter the library uses, for exact search filters. |
60fps_get_shot | One shot in full, with keyframes. |
60fps_get_motion_breakdown | Start, transition, end, plus timing and easing. |
60fps_get_motion_code | A self-contained SwiftUI file for that shot. |
60fps_get_related_shots | For when the first pick is close but not right. |
Skills come with it. Each one teaches the agent a bigger job, using the same tools:
find-animation-opportunities answers "where should my app animate?". The agent reads your
SwiftUI code, finds the few moments where motion helps, flags motion that is broken or overdone,
says what to leave still, and recommends real shots to copy for each.motion-system gives the app one set of timings, springs and haptics in a single Motion.swift,
based on your own code and on real apps with the same feel.feedback-states designs the loading, success, empty, error and retry states of one feature, with
the motion, haptics and words for each.motion-spec turns a shot into a handoff spec a developer can build from, with the timing taken
from the shot's recreation and judgement kept apart.motion-reference tells the agent when to use the library and when to leave it alone.None of them changes your code until you say so.
Any coding agent (Claude Code, Cursor, Codex and more) can add the skills on their own:
npx skills add 60fps-Design/plugin
That adds the skills only. Connect the server as below so they can use it.
The server is hosted, so there is nothing to run locally. Signing in opens OAuth in your browser.
Cursor: add the server from Settings > MCP with the URL below, or copy mcp.json.
Grok Build: add the server by URL.
Gemini CLI: install this repo as an extension.
gemini extensions install https://github.com/60fps-Design/plugin
Claude Code: add this repo as a marketplace, then install the plugin.
/plugin marketplace add 60fps-Design/plugin
/plugin install 60fps@60fps-design
Or skip the plugin and add only the server:
claude mcp add --transport http 60fps https://mcp.60fps.design/mcp
Anything else that speaks MCP: point it at https://mcp.60fps.design/mcp over streamable
HTTP. See mcp.json.
You need a 60fps licence key: a 60fps MCP key, or a 60fps PRO key bought on or before 12 Sep 2026. PRO bought after that date does not include the MCP. Without a key the tools connect but return a 401. That is intended, not a fault.
Xcode 26.3 and later ship their own MCP server, so an agent can drive the build system, the Simulator, Previews and the debugger. Point that agent at 60fps at the same time and the loop closes: it finds a real interaction, reads the motion breakdown, writes the SwiftUI, builds it, and looks at the result.
Xcode launches the agent for you, with its own tools already wired in:
xcrun mcpbridge run-agent claude
Anything you have installed in that agent comes along, so with this plugin the session has both toolsets. A prompt like "find how Threads does pull to refresh, then build it in this project and show me the Preview" is one agent turn rather than three tools and a copy and paste.
xcrun mcpbridge --help lists the rest, including --no-xcode-tools to leave Xcode's tools out and
run-agent skills export to dump the skills Xcode ships. The bridge needs Xcode open on a project,
and agent access enabled in Xcode's settings, before it will hand anything over.
iOS only, and motion only.
It will not help with Android, Material, Flutter, React Native or web. It will not design icons, palettes, logos or brands. It has nothing to do with frame-rate profiling, which shares the name and nothing else. The skill tells the agent to answer those directly instead of searching.
Search always returns something, because it ranks the whole library by closeness. Judge the results on their merits, not on how many were searched.
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 your own design system. The motion is the part worth keeping.
mcp.60fps.design sets no cookies and runs no analytics. It makes exactly one outbound third-party
request, for storyboard frames from Framer's image CDN, and sends nothing about the caller.
MIT, for this repository only: the manifests, the skill text and the logo.
It does not license the 60fps library, the hosted service, or the clips and code they return. Those stay under the terms.