Tools
Tools and stacks we use
Every MCP server and skill we give our coding agents, and the full setup for each kind of project: what each does, how to set it up and how we use it.
Stacks
Everything we use for one kind of project. Pick yours.
Expo
The MCP servers and skills we give our agent when it builds an Expo app.
- DesignMobbin MCP
- Motionanimate-expo
- Fast React codeReact best practices
- Fast mobile codeReact Native skills
- Test and profileArgent
- Docs and deploysExpo MCP
iOS
The MCP servers, skills and Swift checks we give our agent when it builds a native iOS app.
- DesignMobbin MCP
- Modern Swiftwrite-swift
- Motion (optional)apple-design
- Build and previewXcode MCP
- Test and profileArgent
- LintSwiftLint
- Formatswift-format
- Dead codePeriphery
Next.js
Mobbin and the Vercel agent skills we give our agent when it builds a Next.js app.
- DesignMobbin MCP
- Fast React codeReact best practices
- ComponentsComposition patterns
- MotionReact view transitions
- UI reviewWeb design guidelines
- Copy reviewWriting guidelines
- DeployDeploy to Vercel
- Deploy without a loginVercel CLI with tokens
- Cost and speedvercel-optimize
Tools
Every MCP server and skill across the stacks. The ones with a guide have a page of their own; the rest link to their source.
Mobbin MCP
Lets a coding agent search real app screens and flows before it designs one.
In the Expo, iOS, and Next.js stacksOur guide
Argent
Lets a coding agent tap through a mobile app in the simulator and check its own work.
In the Expo and iOS stacksOur guide
Browser tools
Claude in Chrome, Chrome Bridge, Playwright MCP and more: which one lets your agent use a browser best for each job.
Works with every stackOur guide
fast-jev-compaction
Replaces Claude Code’s built-in compaction. Instead of summarizing old turns, Jev drops the tool calls that no longer matter and keeps everything else word for word.
In the Agents stack
jev-skill-suggestion
Hides the full list of skills from the agent’s context. On each prompt, Jev picks at most one skill that fits and adds it for that turn.
In the Agents stack
test-audit
Checks every test the agent writes before it lands, and sweeps old ones for tests that assert nothing, copy each other, or break when the code is tidied up without any real bug.
In the Agents stack
animate-expo
Teaches the agent to build animations that feel right on a real phone: whether something should move at all, springs or timing, gestures and haptics. It writes the code with Reanimated, Gesture Handler, Expo Router and expo-haptics.
In the Expo stack
React best practices
Vercel’s rules for fast React and Next.js code, ranked by impact: extra re-renders, data fetching and bundle size.
In the Expo and Next.js stacks
React Native skills
Vercel’s rules for React Native and Expo: fast lists, images, animations, native navigation and safe areas.
In the Expo stack
Expo MCP
Expo’s own MCP server. It reads the current Expo docs, adds libraries at the version your SDK needs, and runs and checks EAS builds and workflows. It can also read TestFlight and Google Play crashes and reviews.
In the Expo stack
write-swift
How to write Swift the way the language wants now: value types, Swift 6 data-race safety and concurrency, some versus any, Swift Testing, macros, and features newer than the agent’s training data.
In the iOS stack
apple-design
Apple’s approach to fluid motion, from its WWDC design talks: springs, gestures, sheets and motion you can grab and reverse mid-flight. It is written for the web, so its examples are CSS, not SwiftUI.
In the iOS stack
Xcode MCP
Apple’s own MCP server, in Xcode 26.3 and later. The agent can build the project, run tests, read build errors, search Apple’s docs and look at SwiftUI previews.
In the iOS stack
SwiftLint
Over 200 rules for Swift. Run strict, so a warning fails the build, with the opt-in rules that catch real bugs: force unwraps, weak delegates, unowned captures.
In the iOS stack
swift-format
Apple’s formatter for Swift. It ships with the Swift 6 toolchain, so there is nothing to install.
In the iOS stack
Periphery
Finds unused code: declarations, parameters, enum cases and imports nothing uses.
In the iOS stack
Composition patterns
React patterns for components that stay simple as they grow: compound components, lifted state and context instead of a pile of true-or-false props.
In the Next.js stack
React view transitions
Teaches the agent React’s View Transition API: page transitions, shared elements that move between pages, and items entering, leaving and reordering.
In the Next.js stack
Web design guidelines
Reviews UI code against Vercel’s Web Interface Guidelines: accessibility, focus, forms, layout and the small details that make a page feel finished.
In the Next.js stack
Writing guidelines
Reviews docs and page copy against Vercel’s writing handbook: voice, tone and clarity.
In the Next.js stack
Deploy to Vercel
Lets the agent deploy the app to Vercel and hand back the link, for a preview or for production.
In the Next.js stack
Vercel CLI with tokens
Runs the Vercel CLI with an access token instead of an interactive login: deploys, environment variables and project setup.
In the Next.js stack
vercel-optimize
Reads a live project’s Vercel metrics, usage and config, then ranks fixes for cost and speed, each backed by a real number.
In the Next.js stack