Easily give Claude eyes and hands on your app

@zerotopete

16.2K followers · usually 3.6K views a post

Views

75.7K

Likes

4.2K

Comments

105

Shares

484

SoundTikTok sound · Everything In Its Right Place

Promoted product

Zero to Pete Substackzerotopete.com

Tech, AI, and building what's next. "You're part of the 1% signal on a topic that's 99% noise." — paid subscriber. Click to read Zero to Pete, a Substack publication with thousands of subscribers.

8 videos

Why it worked

The video provides immediate, high-value technical utility to a specific niche (developers) while using a 'problem-solution' framework that builds authority and trust before the soft CTA.

Summary

The creator demonstrates a workflow improvement for developers using Claude Code by connecting it directly to the iOS simulator via an MCP server. He explains how this eliminates the need for manual screenshots and directs viewers to his Substack for the full technical walkthrough.

Structure

1Identify the pain point of manual screenshotting
2Introduce the solution of wiring Claude to the simulator
3Explain the technical mechanism using MCP and IDB

Original caption

Substack article dropping at 9pm EST. Subscribe (for free) to get notified when it drops #anthropic #claude #ai #claudecode #entrepreneur

More from @zerotopete

Product placement

The video promotes the creator's Substack newsletter as the source for the technical tutorial and code.

Call to action

The full walkthrough is on my Substack, link in my bio.

On-screen text

Easily give Claude eyes and hands on your app If you're building an app with claude code and still sending it screenshots of your app for it to see what's broken, you're wasting a ton of time. I'm gonna show you how to give claude code eyes and hands on your app. I'm Pete. I own a software development agency in New York City, and Fortune 500 companies to bring their products to market. In the last six weeks, I built my dream social network using Claude Code, and early on my workflow looks something like this: make a change, screenshot the simulator, find the screenshot in Finder, drag the screenshot into Claude, explain what broke, and repeat that over and over and over again. That loop was killing my momentum, and I know it's killing yours too. I get questions all the time about this in my comments and DMs. So I wired Claude straight into the iOS simulator. Now I can see the screen, swipe the screen, tap buttons, and run tests. I describe the change, Claude builds it, tests it, and shows me the result. I use Facebook's IDB. To control the simulator from the command line. So Claude talks to it through an MCP server. You tell Claude what to do, the MCP Server translates that into commands. Claude executes them through IDB That's it. This works for web and Android too. Same concept, just different MCP. Servers. So You never have to screenshot again From the exact commands I use to my Claude MD and test prompts. The full walkthrough is on my Substack, link in my bio.

Transcript

If you're building an app with Claude Code and still sending it screenshots of your app for it to see what's broken, you're wasting a ton of time. I'm gonna show you how to give Claude Code eyes and hands on your app. I'm Pete. I own a software development agency in New York City, and we work with startups and Fortune 500 companies to bring their products to market. In the last six weeks, I built my dream social network using Claude Code, and early on my workflow looks something like this: make a change, screenshot the simulator, find the screenshot in Finder, drag the screenshot into Claude, explain what broke, and repeat that over and over and over again. That loop was killing my momentum, and I know it's killing yours too. I get questions all the time about this in my comments and DMs. So I wired Claude straight into the iOS simulator. Now I can see the screen, swipe the screen, tap buttons, and run tests. I describe the change, Claude builds it, tests it, and shows me the result. I use Facebook's IDB to control the simulator from the command line. So Claude talks to it through an MCP server. You tell Claude what to do, the MCP Server translates that into commands. Claude executes them through IDB. That's it. This works for web and Android too. Same concept, just different MCP Servers. So you never have to screenshot again. From the exact commands I use to my Claude MD and test prompts. The full walkthrough is on my Substack, link in my bio.