Hook

Their other posts in the index, biggest breakout first.
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.