Claude Code Full Beginners Breakdown

Okay, today we are talking about Claude Code. This is the first video on the channel that is going to be like a really, really solid deep dive. Listen, I know you're a dopamine gremlin and I know you're going to be like, "Oh, this is boring. It's drawn out. " This is the difference between you being poor and you making a lot of money from AI. And now, I've been playing with Claude Code the last couple months. I've gotten really good at it. This is a ground level understanding because you're probably not technical as was I. I have no idea what any of this is and you need to know these things especially how cloud code works because other tools will be coming out like it in the future and it's quite important. So in this video I'm going to cover everything for you. It is quite quite comprehensive. So without further ado, let's jump in and start talking about the coolest thing ever. So what is vibe coding guys? Vibe coding is building software by describing what I want in plain English. No syntax, no debugging, no stack issues. Obviously, you get a little bit complex as you go. Uh this term was first coined by Andre Karpathy who is open AI co-founder and um it's kind of taken the world by storm as you know. So the old way is you're learning Python, JavaScript, whatever language you're learning like the backend, all these different complicated things. Now, and I will show you proof of this, you can start building it in one day. Like you can build internal tools, whatever's in your brain, you can make reality. And if you don't know how to do something, you just say, "Hey Claude, how do I do that? " And it tells you. It's the coolest thing ever. This doesn't mean that the code doesn't exist. Okay? So this is not no code. No code is a thing from the past. This is real code, but the AI is running that code. Okay? And so basically, you are the project manager. You're the one in charge and saying, "Hey, let's build this. Here's the end goal and what we want to achieve, and then it does the code. So, you're not really the dev. You're more the manager. You're like the senior product engineer that's kind of telling it what's going on. " I want to breeze through all this and get really into the good stuff for you guys. So, there is a loop that you will get into. And trust me, like I've literally been doing this all weekend. Uh, as you can see here, you got to click the damn button every freaking day. Um, but for example, I'm saying, hey, why are there no enriched leads in this thing I'm making? It's going and doing the thing. So, you are going to get into this loop of you describe what you want to build. It writes all the code files. You test it. If it doesn't work, you just tell it doesn't work. If it does work, ship it. And then we go, we continue. So, you get in this loop of reiteration. Now, what can you build with this? Really, it's pretty limitless, guys. I've seen people even do hardware. Um, I've seen people do like robotic stuff that the code runs on a chip and like talks to the robot. You can do whatever you want. Obviously, if you're watching this video, it's probably going to be web apps like dashboards, you know, internal systems, prototypes, really good for prototypes, automation, business tools. Now, the most important thing here, and this is what the point of this video is, is you got to know really what you want. Okay, you as the project manager have to give it a clear outcome, a clear goal, a clear desire, and a plan. like you need a plan of enactment of hey we're going to build this I want to build it needs to be like this and have these features but again it's only AI and so it's only as good as your prompts and we keep saying this on this channel because uh the biggest area of it I see even across our like 50 plus students in our mastermind it's a lack of prompt engineering and a lack of patience okay so quality prompt engineering quality communication patience for iteration so you're going to have this loop describe test refine test done, redo, test, redo, test. Like it's going to be the loop you're in. And then you got to have some basic uh computer control. So like if you're on a Mac, you got to understand how your files work on Finder. I really had never used them before. Vibe coding. So Finder, you got to understand how it works. You got to kind of understand how to open terminal, which is just this thing down here. You open it one time, then you download the Cloud Code um app anyway, and you're a piece of cake. But once you do that, the rest is the same as what you've been doing with AI for the last couple months. Now, there are a lot of vibe coding tools. So, we have like lovable, we have bolt, we have um like replet. Those are all I would say the beginner tools. Then you get into the more advanced things. Okay. So, you have cursor, wind surf, cloud code, um Gemini's anti-gravity or from Google. Um you have codeex 5. 3. I haven't used either of those yet. I've just been focusing on cloud code because it's it's pretty solid. And then you have things like GitHub copilot, etc. Now, for our educational purposes, we're just going to focus on cloud code, but everything here is applicable across all the other tools. Okay? So, um we're

going to skip all this and now we're going to get into the good stuff. So, cloud code is basically a LLM built to do code. Think of it like that. It lives on your computer. So, it has access to your files. It can create files. It can read files. You can literally build an entire software locally on your device. Um, which is really, really cool. And it reads your whole project. So, these are the differences between this and the web. Okay? Because I see people that are like, "Oh, Cloud Code's not that good. " And they're using it on the website like up here. You can't do that. You have to download the app. Why? Because if it's on your computer, it reads your whole project. Now, this is where you guys got to understand context windows. and we've talked about this a bit in the past. So, let's say this is all the available context that I have. Uh 4. 6 is a million tokens. Okay? So, this If I use this on the website, it's going to eat up like most of my tokens just reading the codebase. You know, if I use it on my computer, I have like pretty much all of it free because it's only using a little bit to read all of the memory, the working memory. Then I can give it big files like a PRD which I'll get into in a minute and it will read the whole thing because I got a million tokens to use which otherwise you don't have. Okay. Now number two is it's going to work across all your files. So what's going to happen and I'm going to try to show you this without um giving any sensitive data here. Okay, this should be fine. These are all different files. Now do I know what all this means? Absolutely not. Okay, this is my MD file. Um these are I think these packages for I I'm not going to explain that to you. Anyway, within these folders are different things. You have like the schema, you have the backend, you have the structure, you have the API keys because this new project I'm using, project overlord, which is top secret internal tool by the way, has a lot of API keys that it connects to. And so Claude is able to go through all of those rather than me have to upload on the browser. It just doesn't work. Okay. And it also can connect to GitHub and Versel automatically. Now just a little crash course for you. So you're going to have your let's say it's your laptop. Oh my lord, this is bad. It's your laptop. So your code lives here. You're using cloud code on here. Now you can do this locally. You can build locally. You can deploy locally. It'll still exist. But let's say I want to like share it with somebody or add a team member. I got to have it live on the internet. So, how do you do that? Well, there's two ways. You have what's called uh GitHub or you'll see like git for short. So, GitHub is basically think of it like a video game. It's the save state. So, it saves and organizes all your code. So, your code lives on GitHub, but it's not deployed on GitHub in a real sense of like production. So, then you got to connect your GitHub to Versel. Okay, we use Versell for Kindo as well. So, Ver CEL. Now, Versel is the hosting. So, it's kind of like AWS. You you've heard of AWS, but it's really easy to use. Now, here's the great part of Cloud Code. You just tell it to do this, and it'll do it for you. Okay? So, you're going to make a good account. free Versel account, both free. You're going to give the links to Claude Code in your terminal and say, "Hey, connect to these. " And then every time you make a change or an update, you're just going to say commit. And then it exists on the web like it now lives on the internet. Congratulations. It's that easy. Okay. So, regular claude, I told you claude code, just listen to me. Just use it. Now, here's how you install it because this is a bit confusing if you're not technical at all. So, we're going to go through Mac. Um, number one, you're going to take this command. Okay, this line. You're going to copy it. You're going to go here to your terminal if you have to like open up all your apps, whatever, and you're just going to paste this and hit enter. That's it. Okay. Then it's going to download cloud code. Make sure you have the cloud code um or the cloud desktop app installed where you get codework and everything with codework is awesome as well. Um install that. Now it's going to open up. It's going to do an authentication window in your browser. Congratulations, it's installed. Piece of cake. It's not that hard. Literally, just do this or just Google like Claude's website and they're going to show you how to do it. Now, once you have that downloaded, here's how to prompt it. Okay, this is the most important part. Number one rule is describe outcomes, not instructions. So, a lot of you guys are going to start and be like, edit this line, you know, do this. Like, no, no. You should say what you want to happen. So, basically, um, outcome and then work your way backwards from the outcome. So, hey, users should be able to see their dashboard if they're logged in. If they're not logged in, redirect them to the login page, right? Like really cool

like outcome. So, and I know this might sound simple, but this genuinely saves you a lot of time. So, if this is the end goal, okay, we just work our way backwards. We So, oh, I want a production grade beautiful app that does XYZ. Okay. Well, let's work our way backwards and go step by step. Okay. Now, prompt template for beginners. So, what I want describe it in plain English. Context. So, anything that it needs to know uh like details and then deliverable. What do you want cloud to give you? So, add a database. It's not very clear. You would rather say I want to save user information. So then instead of add a database where it's just going to connect to database, it's going to build the proper schema or whatever you call this of like users authentication, you know, backend. You've got to explain what you want in pretty good plain detail, but then it nails it and it does really well. Now, another trick here is tell it your end goal and then say, "Ask me questions to help give you context of exactly what we want to build. " and it will basically interview you and say hey do you want it to do this or this and then you can tell it which is really cool. Um feel free to screenshot these as well. These are pretty useful. Now prompting for improvements. Hey something works but looks like it could be improved. So blank feature works but it's not doing this. So I do this consistently like I said and I showed you guys when I opened up my cloud I said hey why are the leads not enriching? It's going to immediately go through the codebase. It's going to open a browser. It's going to test it. It's going to figure out why, deliver the error code back to me, tell me why it doesn't work, and it'll usually fix it on its own. If not, I just say, "Hey, fix it. This should happen. Here's the end goal of this feature. " You know, um, now prompting for bugs. So, let's say you get a crash. Hey, I'm getting this error. Now, this is a big hack. Get really used to screenshotting. And at least on Mac, when you screenshot, you get this thing in your bottom right, um, like your clipboard, and you can drag it. I'm And another hack, keep your window open like this. So, if this is where your deployed app is, keep cloud code open like this. That way, because if you have it full screen, you have to like switch between tabs. I want to be able to see what's going on. And so, what I'll do is, let's say there's a problem. I'll screenshot. I'll drag that little thing right into here, and I don't even really got to say much, and it'll know, oh, it's broke because I can see it, you know. Um, visual works really, really well. And then prompting for new features. Hey, I want to add feature. Here's how it should work. Again, end goal from user perspective. Make sure it also does this or has any restraints or whatever. It's like the same prompt engineering as when we write copy. Okay. Now, here's some commands. When you hit slash, you're going to get commands that pop up. Okay. So, you got multiple things to go through here. Um, one also a hack for you. You got to learn how to use the context window. the million tokens that you get does get compacted if I have like just a long chain of like conversation history over a week. Instead, what I should be doing is every time I'm building something new like a big feature or uh if it's in the same project, obviously think of it like here's my projects folder. Okay, so I have my folder. Every time I want to start something, I'm starting a new chat plus new chat. And then it saves obviously the memory. It writes the memory into your folder. If you keep it going, you're going to run out of window. It's going to compact it. And then it's going to get like It's not going to know what it's doing. Okay. Then you have uh things like rewind or you can undo things uh if it breaks something, which this why you should be using GitHub, by the way. You can roll back to a safe state. Um you can switch your model. Use Opus. Opus is pretty good. Um, reference files, etc. Okay, use the clear constantly. Like, I'm really telling you, you have to do that or you're going to run into issues. Number one, things that you can do with this. It's not just code, by the way. This is where the real hack becomes is like you can kind of use it like an open claw. So, you can do landing pages. And again, I'm not going to read all these. Feel free to screenshot all these. Um, these are all really good quality. Landing pages, it can do. Client dashboard. It can do. uh automate repetitive tasks. It can do it's basically going to set up a cron which is like dot co n it's going to do something at a certain time. Number four add AI to an existing app uh which is really cool and it can actually fix codebase. So if you have a codebase once you have another software let's say you can drag and drop it into cloud code be like hey something is broken here like will you fix this and it will do that as well. It's quite amazing. Um, now here's some advanced features in your claw. md. So your project's memory file like I showed you that MD file you basically have a brain. So this is the brain of the project because again it's locally on your computer. So it's in files. So

you can say so but it doesn't have to reference every time that you restart a session. You can basically say all of this in that cloud MD file. And so all you're going to do is go to finder, open the file, text, save, close file, close folder, and then you have it saved. So basically, you got to think, I only got a million tokens every time I'm trying to give this a go. And you should be on the max plane anyway. I need to make the most out of those tokens because it does get eaten up quickly. So I need to give it as much context as possible in the safe state so it doesn't have to like rego through this every freaking time. Um, that's a great hack that I figured out. Number two, the safety net. So use GitHub, but you can also roll back that state. So um instead of being cautious, you can say refactor the entire uh authentication system and let it run. Worst case, you just roll it back. So you don't need to be scared of like letting it have all your code. Like I see people nervous about this. Use GitHub and use the roll back feature and you're pretty fine. It's like saving in a video game before you go fight a boss. Um and then you can actually run multiple tasks. Now Claude Code does multi- aent. So it'll actually spin up different agents for you. You have to go I'll make another video about this. You have to enable it in the settings, but you can basically have different agents do different things and it does save on token window because then all of these agents would report to one agent. Now, you're not even setting this up. It kind of does it automatically, which is super cool. Um, now here's the bottom line for this, at least on the base level. This is legit, guys. This is like the coolest thing ever. Um, I'm actually going to show you a couple things that I have been building. So, for example, I'm going to blur out all of uh like sensitive data here so nobody can log into my stuff, but I am building a basically an SDR lead enrichment system for Kindo. Um, I'm a couple hours into this. And so basically I can go define my ICP and use a bunch of APIs for like Apollo uh Serper the Anthropic key and browser and some other things and I now can just enrich leads and pull leads straight from the internet sequence them send them to our CRM. I can enrich them and it's actually going to give me like here's a lead. It's going to enrich these and give me a score of uh how well it fits our ICP and then it gives us all this. And so basically, I've just created a full-blown SDR team where all I'm paying, and it actually tracks the cost. All I'm paying is um credits. Like, this is insane that I built this. I've also rebuilt Kendo as an MVP staging area for me to basically have an idea, build it, make sure I like the functionality, and then give it to my dev team. So, we're shipping a lot faster than we've ever Obviously, they got to go put it into real production code and everything, but I can MVP. I can build internal tools. I can do things so much faster than I could in the past. Um, I really think this is one of the best uses of your time right now. Now, obviously, you got to build things that are applicable and going to actually make you money. Um, and I wanted this video to be kind of like a base level understanding. We're going to make more advanced videos uh shortly. However, you got to understand the basics. And once you do, and once you start playing with this and you start like kind of using it every day and you're like, "Okay, I know what's going on here. " You know, like look how much I've been using this like and I keep these chats going, but I've been building a lot of crazy stuff. So, for example, I said, "Hey, the enrichment's not working. They're stuck at discovered. They were found by Apollo, but never scored or enriched. It stopped. It's painfully slow. It's sequential. " So, instead of sequential, we need to make it multi-agent. So, I've already cleared. Want me to fix B? Yeah. Concurrent processing. Yes. Let's make it concurrent so we can enrich thousands a day. Again, plain language. I'm just saying the end goal and it already has my whole codebase here that it's referencing and so it understands what's going on. Okay, so we're going to call that for a video. Uh let me know what you want help with specifically the next couple. We're going to get more advanced. We're going to actually build some stuff and show you like what I'm building. Um, but yeah, this is a great grassroots sort of base understanding of cloud code. Hope you enjoyed. I'll see you guys on the next one.