435: How to Actually Use Claude Code to Build Serious Software

Hey. It's Arvid, and this is the Bootstrap founder. I've been using Cloud Code for over half a year now, pretty much exclusively to build my platform. I haven't really deviated much to other tools, and I think I have gathered enough experience with the system that it's time to share what I have learned about using Cloud Code effectively to build this kind of non trivial software service application that I am building as well. Here's what I found. That's kind of the summary of this. A lot of the value of Cloud Code is in its configuration and in the correct prompting. When you're just starting, you might think that the value is really in the code it generates. It's kind of true, but honestly, most of the value of Cloud Code is in the code it doesn't generate, so you don't have to throw it away. The better you are at setting a really solid system prompt, at executing the agentic loop correctly with the right permissions and the right interceptions and restrictions, the better your experience with Cloud Code will be. And I will talk about just how those things work today. First off, any plan of cloud code will work for whatever you might need. And I mean subscription plans here. Right? The moment you start using it more heavily, if you start using it for feature building or for extensive testing, for background processing, for other things than just creating code, you will likely exceed the cheapest plan. I think it's $20 a month. You want to look at the max plan and it tends to be what I would recommend at this point because then you can just keep it running and you will see why this matters in a second. Cloud Code released an integration with Chrome, the browser, a couple months ago. So you can start Claude with the dash dash Chrome flag so that it connects to your Chrome instance and you really just need to install a Chrome extension in your browser. And then you have this bridge to the browser that allows Claude to operate within that context of the browser for you. So if you don't do anything else from all the things that I tell you today, do this one thing. Allow Claude to see your application, use the Chrome flag, to literally be able to click around in it and take screenshots and move things and inject things and investigate the DOM and all the variables that run within it. That is incredibly powerful. It's very smart to connect your cloud instance to this running version of your software. With the prompt and within the operational loop it can then be tasked with things like look at this page, scroll down a little bit and see how this one component overlaps with another. That's quite literally something that I used earlier today to fix the display bug. Or you can say something like look at …