So after five hundred hours using Cloud Code, here are 27 tips that I wish somebody told me when I was getting started because it would have saved me so much time. We're gonna be moving through this really quickly. Let's get started right away. The first one is that if you're just getting started, you should download Versus Code or Anti Gravity. Both are free. They're code workspaces that allow you to integrate Claude code into it. All you have to do is head over to the plugins,
download Claude code, and you're ready to go. Tip number two is that if you wanna build beautiful websites that do not look like AI slop like this one in front of us, here's a couple options. Number one is you can head over to the site Dribbble. This is a graphic site where you can draw inspiration. So just type in a word like website, find one that looks beautiful to you, take a screenshot of it, and then head back into Cloud Code. And in this slash command down at the bottom here, you can attach a file, load in that screenshot, and then you can clone that graphic pixel for pixel. You can also add in a URL
where CloudCode will go to that study the site and then make a duplicate. Here is my example of cloning Railway.
Another option is that you can add in beautiful
three d graphics to a website just like we have right over here. There's a ton of different options that you can import into your site for free using Spline. Here's another one. We can also have these cubes in the background following our cursor or even having these, uh, these balls following our cursor as well. It's absolutely stunning. Makes a website look like it's $10,000.
Probably one of the biggest game changing tips that I'm ashamed to say I learned way too late in my journey with Cloud Code is the fact that you can have multiple tabs open running multiple different tasks at the same time, and you can even drag a task or a conversation down and have a split screen presented where you're working on two different projects simultaneously.
You can also drag it horizontally so you could literally have dozens of these well, maybe not dozens, but tons of these different conversations running all simultaneously
at the same time. Moving on to the next tip, you'll see that in this conversation,
Claude is asking for permission to move forward, which is a giant pain to ask. Because if you're working in parallel with other projects and you return back twenty minutes later to realize nothing has happened because it's waiting for your approval, this is obviously a nightmare. So how we can bypass that is by switching the mode here to something called bypass permissions
so it doesn't ask you questions like that. If we hit the three dots and we go into configure editor,
we can search for bypass permissions,
and we just need to toggle this on. Once that's set, then you have access to the bypass permissions mode down here, and you won't have to deal with that again. Now moving on, you can also add in dictation because obviously speaking is way faster than typing.
Hey. Can you hear me?
Awesome. And so that's how you can add dictation.
I'm just using the built in Mac default by hitting the f n button twice. I'm not sure what it is on Windows. The next tip is for those of you just getting started with Claude Code. It's really hard to get started in a platform like this because there's a lot going on, but I would prompt Claude to ask or tell you what questions you should be asking. Because if you at least know the questions to ask, then you can eventually find the answers. But if you don't even know the questions to ask, then you don't really have a direction to go in. And so provide context,
like, for example, I'm building a website from scratch, and then ask Claude what questions you should be asking it, and then it will surface the questions. Okay. What's the job of your website?
What does success look like? And then you answer them, and then eventually going down this chain of thought, you'll come to the conclusion you're looking for. The next tip is having two files inside every project you create. The claud dot m d file and the projects underscore specs file.
These are non negotiables for me. The claud dot m d file is how Claude should behave. So imagine hiring an employee and giving them training. That's essentially what claude.m d is. If you hired somebody and you didn't train them on the job, they're probably not gonna do a very good job, obviously, and the same thing goes for Claude.
The next, uh, file is the project underscore specs file, which is essentially telling Claude what it is you're building out. Imagine hiring somebody and they don't even know what your company does. Again, they're not gonna do a good job. These are both living documents where as you build inside Claude code on top of your project, they should evolve over time.
The next series of tips, I'll have to do with the claude.md file, and these are things that honestly should have been out of the box with Claude. But, unfortunately, I did learn them the hard way and put them into my own file, and I'm sure they'll serve you well as well. The first one is to challenge your direction. Nobody likes a yes man like telling you you're you're special every two seconds. Instead,
have Claude challenge you so that you get the best results. The next tip is to have a quality gate. So if you're writing, for example, a LinkedIn post over here, instead of it saying, hey. You're awesome. It's a three out of 10. We should post it. It should give you a non b s answer on how you can improve that to nine out of 10 so that you get the best results possible.
The next thing is that it should test before it sends the final product to you because if it builds a website and it's broken, broken, if you're the one having to figure this out, it could take you five hours. With Claude, it's gonna take it five seconds. So just get all the heavy lifting to be done by Claude so that it gives you the finished product. The testing should be baked in before it ever arrives arrives on your plate. The next one is context. So anytime you're dealing with a claw down here, these conversation windows can be absolutely massive.
And if they get too large, then they compact the conversation, which means they shrink down. But a lot of the context is lost.
And so with this rule, what it's saying is make sure that you have context at the top of mind so that you don't aggressively use tokens that you otherwise should not be using.
The last tip inside this Claude dot m d file is having an upgrade suggestion.
So every time you're communicating back and forth with Claude code, it should give you a suggestion on how you can improve. Right? We all kind of to some degree have blinders on. We don't know. We don't know. And this is a great way to uncover things that we never would have thought to do otherwise.
Another tip
is using this auto research package,
which essentially has AI do the testing and the upgrading for you without you even having to be present. It just takes care of everything. The next tip is about having Claude reply back to us the right way. Oftentimes, you can build very complicated projects, and it can be very overwhelming if it doesn't structure the response properly. Here's how I do it. First of all, Claude tells me what it did so I understand what the hell just happened. Number two is it tells me what it needs from me because oftentimes,
it might do something on its end, but unless we do something on our end, we can't have the project project be completed. Then it tells me why it matters and explains it like it's a like I'm a 15 year old. Then it tells me the next steps so that we can move forward, and then it tells me any area errors that are encountered and any context that I need in order to understand what's actually going on. If you guys want that free Claude dot m d file, it's gonna be in the description down below for free. The next tip is that Claude has memory on you, and this is not a file in your project. This is actually like a secret file that Claude stores that persists across every single project you create, and you can add to it, you can update it, and you can delete from it. So in this example, I messaged Claude saying, can you please add my name in the space that I'm in? And it has gone ahead and created this memory file. And I can open it up, but you can see that it's not actually in my project file. If I were to create another project and ask it what my name was, it would be able to remember what I wrote over here. The next tip is the fact that you can have message queuing.
So we can see here that we can actually send multiple messages at the same time and it's going to work through those messages one by one. You don't actually have to wait for the previous message to be finished before you can send the next one. The next tip is you have access to multiple plugins by hitting slash plugin,
and you can download prebuilt
solutions
like this front end designed where you can create beautiful interfaces pretty much out of the box. We're gonna go over the next couple skills simultaneously,
which are workflows and reference files. In order to explain this, I wanna take a step back and explain my three layered approach to most projects inside of Claude code. So you need a Claude dot MD file, and this just determines how your project behaves,
what to do, and what not to do. And every single time you send off a message, by default, Claude is always gonna read that file first.
The next layer is workflows, and these are tasks that you're doing manually that you can automate. For example, creating LinkedIn posts or replying to incoming emails or creating a proposal for a client and sending it off. The distinction between workflows and and the claw dot m d file is that this is called on demand. Okay? The claw dot m d file is always triggered every time you send a message, but with skills, you have to actually trigger it by calling it down here. Okay? And so I've set up a custom skill replying to emails.
I've pasted in an email, and then automatically it's generated a response for me down here. The beautiful thing about skills is that you just set it up one time and you run it as many times as you want forever, and you keep constantly improving it so that the hundredth time is way better than the first because the alternative would be starting a fresh new chat and then you have to spend so long giving the context that you actually want to give to it to get the job done properly. The third layer is the reference files. Okay? These are reusable
templates that you create once and we reuse across all of the skills that require them. So in all of these three instances, creating LinkedIn posts, creating emails,
and also creating proposals, you wanna reference your tone. It's the way you write. And so instead of having these baked in at the skill level three times, you have one source of truth where all the skills reference it so that when you make a change to one reference file, it's updated in all three workflows.
The next tip is using sub agents inside Cloud Code. So let's say that you're building on a five page website. It's a lot of stuff going on at the same time. Traditionally, you would have to do this in a sequential order where you send a prompt, you build out the first page, then the second page, then the third page. But with parallel sub agents,
you can send that prompt and it's gonna delegate a responsibility to sub agents. One is gonna be the home page, next is gonna be the about page, the next is going to be a contact page, and this will lead to faster responses
that are better because the context is separated. You have one agent
that specializes in one thing. The next tip over here is the fact that when you're using Claude code, okay, and let's say you send over a prompt over here, anytime
that things are not going well or it's going off the rails or it's hallucinating or doing something wrong, you can always hit the escape button, and this is going to automatically interrupt it and stop it from actually continuing building anything. And if you go to a previous message, you have this rewind button that can restart or rewind the code to a previous step. The next tip is the fact that if you are using Versus Code or Antigravity,
a lot of the times it's not set up by default to pre save
your changes.
And so what you can do here is you can hit this config file and then you can type in auto save and you should be able to check this off and now automatically everything's gonna save. I can't tell you how big of a nightmare it is to build out projects only for it not to save and you waste a ton of your time. The next tip over here is about compacting. So let's take a look at this conversation.
83%
of the context window is gone. That means that in this conversation,
it's received so much information that it's overloaded. Loaded. And so by default, when it hits a 100, it's going to compact. But you can also compact before it and then add on a tip or a reminder to not forget special details that you do not want it to forget. This is gonna lead to better, uh, retention of the important information. The next tip is typing in insights.
And when you do this, it's gonna open up a report telling you your entire
lifetime
experience
with Claude. It's gonna give you insights insights at at a a glance. Glance. It's It's gonna gonna tell you what you're working on. It's gonna tell you how you use Claude,
and it's gonna tell you impressive things that you've done, and it's gonna tell you where you've gone wrong and so on and so forth. So if you ever wanna dig into your experience and figure out and get feedback from Claude directly, you can always type in the in insights results and take a look at what it says. So that's it for this video, guys. Thanks so much for watching. If you found value in it, make sure to check out my four point five hour masterclass on Claude code for free on YouTube.
I also have a free community, uh, that you can find tons of resources and blueprints in. And if you guys are looking for more help, I have a paid community where there's two transformations.
The first is how you can create your own AI automation agency, selling cloud code solutions to other businesses begging for this kind of stuff. I'll show you how you can find, close, and fulfill your first deal within thirty days or less. And the second transformation is for those of you who have an existing business. I'll show you how I automated up to 80% of my business with blueprints that you can copy and paste into your own business and get similar results as well. And if you don't wanna have to do any of the work yourself, you can take a look at my agency where we can implement these solutions for you. Thanks, for watching, and I'll see you in the next