
Tech • IA • Crypto
L’essor des outils d’IA permet désormais à des débutants complets de créer des applications en quelques jours, à condition d’adopter une méthode structurée et orientée problèmes.
Des utilisateurs novices parviennent à concevoir leur première application ou automatisation en seulement quelques jours. L’accessibilité des agents de code assistés par IA réduit drastiquement la barrière d’entrée, rendant ces outils utilisables bien au-delà du cercle des développeurs.
À l’horizon 2026, les compétences liées à l’IA devraient s’imposer dans de nombreux métiers. L’enjeu n’est plus seulement technique mais professionnel: ne pas maîtriser ces outils risque de devenir un handicap sur le marché du travail.
La méthode recommandée repose sur l’identification des tâches qui coûtent le plus de temps ou d’argent. L’IA est ensuite utilisée pour résoudre ce problème précis. Cette logique de levier maximal permet d’obtenir rapidement un retour sur investissement.
Deux usages se distinguent clairement. L’automatisation vise à déléguer des tâches répétitives, tandis que l’augmentation consiste à utiliser l’IA comme un conseiller capable d’analyser du contexte et d’améliorer la prise de décision. L’efficacité réelle vient de la combinaison des deux.
La mise en place passe par l’installation via terminal (Mac ou Windows) et l’utilisation d’un environnement comme Visual Studio Code. L’organisation des fichiers est essentielle: un espace de travail structuré améliore fortement les performances de l’IA.
Regrouper tous les projets dans un seul dossier central permet à l’IA d’accumuler du contexte. Cette approche facilite la cohérence, la réutilisation des éléments et accélère la construction de nouvelles applications.
L’IA devient nettement plus performante lorsqu’elle dispose d’instructions claires et d’un environnement structuré. Des fichiers de configuration dédiés permettent de définir les règles, préférences et logiques de travail, rendant l’outil jusqu’à “cent fois” plus pertinent selon les usages.
Des outils comme Seed (idéation) et Pull (construction) structurent le processus. Le premier aide à formaliser un projet, le second orchestre sa réalisation en phases, avec une organisation claire des tâches et des objectifs.
L’IA peut être connectée à des outils externes (CRM, gestion de projet, etc.) pour automatiser des processus complets. Exemple concret: qualification de prospects, rédaction d’emails personnalisés et mise à jour automatique des pipelines commerciaux.
La progression repose sur un cycle simple: résoudre un problème, maîtriser l’outil, puis recommencer. Chaque projet renforce les compétences et élargit les possibilités, transformant progressivement l’utilisateur en expert opérationnel.
L’accès simplifié aux agents de code transforme l’IA en levier immédiat de productivité, à condition de cibler des সমস্যes concrets et de structurer son usage autour du contexte et des priorités.
Is it possible for a complete AI beginner to hop into clawed code and build their first application or automation in the first couple of days? Yeah, it's completely possible. I've had clients who have just started using this product just a couple days ago and have already built out their first application. So, here's the game plan, fam. I'm going to go through some misconceptions and I'm going to give you some context about how I use this product, who it's really meant for, and then we're going to go into the setup. We'll go into how I'm currently using it, how I've set up my Clawude code, and then I'm going to leave you with some golden nuggets. First off, this product is for everybody. This product isn't just for business owners or coders. Even if you're working a regular job, this product can help you streamline so many of your processes. When we look at what's beyond 2026, we're going to start seeing jobs are going to require these AI skills. So, if you don't want to fall behind, continue watching this video because I'm going to give you guys the full scoop that you never knew you needed. And when it comes down to what is the right way to use these tools, there is no right or wrong way to use any AI tool, but there sure are better and worse ways to use them. And as you guys see me teach my personal setup, you'll see that it's all based around a simple framework that I've operated on for years. Find your dot problems, find out which one is costing you the most money and time, and then use a tool like Claude Code to solve that one problem. So, you're going to be targeting the highest lever action, solving that problem while simultaneously learning how to use this agent coding tool. That is one of the best ways to use AI. And you'll also learn a clear distinction between AI automation and AI augmentation. If you want AI to automate your entire life and do everything for you, you're in the wrong place. Can it solve micro problems, save you money, and make you better? Absolutely. And that's where AI augmentation comes into play. We want to use AI to automate tasks, yes, but the augmentation aspect is using AI like a counselor. Feeding it massive amounts of context to become the expert you need it to be and then having those consulting sessions to help you make better decisions in your life. TLDDR, that's exactly how I use these tools. And you'll see it in my setup and how I teach. Now, you are going to need some skin in the game. You're going to need a subscription. And I wouldn't recommend free. I also wouldn't even recommend going pro. If you're going to use pro and you want to get serious with this tool, you're going to hit limits very frequently. Okay, the number one recommendation I have for you, and I get this, I get asked this all the time, is you would need the max five times minimum. This is what I'm using. Okay, max 20. Once you start evolving, you can upgrade, but that's after maybe you've made a return and you see an ROI on your time or the money, right? So, five times this is what you would do. So once you have your subscription, you're going to want to visit code.claw.com. And this is going to be linked below. And you can read through some of this if you'd like, but most importantly, what we're going to be looking at is the native install commands here. So if you're Windows, you got it here. If you're Mac, you got it right there. And it's a very similar setup for both, but we're going to do it from Mac. And what I want you to do on your Mac or Windows is go to your search and type in terminal. Now, if you're on Windows, you're going to type in PowerShell. And now with the command that we referenced, we just paste that in here. Click enter. It'll go through an installation. And if it doesn't prompt you and ask you how you want to set up Claude yet, but it's fully installed as you can see. Then just exit out of the terminal, open up a brand new one, and just type in Claude and click enter. And now you have Claude code accessing your computer. But if you notice up here, there's a couple files that it's actually into right now. And what we want to do is create a new custom folder that Claude can work out of. So, you would set up a new folder right here on your desktop and you could just call it Charlie Workspace, whatever your name is. Open that file up, create a new folder, and you could just call it CharlieDev. And the reason we're doing this is because we want Claude to build context and to build things inside of one folder. I work off of a mono repo workspace, meaning everything that I build with Claude, I house in one folder. This one right here. And we're jumping a couple steps here because it's very important for you to understand how Claude can work effectively. And it's through proper file structure. This is my main folder. I showed you guys the main folder and then the secondary folder. This is my secondary folder. And inside of it, all the apps I build, all the different businesses I'm running, I have context on here and I run it. This is monor repo. Some people will have a different folder for every app they're working on and it's preference. But the way that I'm teaching is monor repo. And I want you guys to understand that AI is powerful. Yes, it is the product. But what is going to allow Claude to become even more powerful is the right context, meaning the right information. And how you scaffold it out here and teach Claude to read all of this is going to make Claude way more effective, if not a hundred times more effective to you personally. I've even personally taught my system how to speak just like me. And if you're new to this, what you were just looking at is called Visual Studio Code. It's essentially a shell. You can run clawed code inside of this to see your files. I can pull any of these files into my session. This is an integrated terminal. We have this a regular terminal on your computer. But this is integrated inside of this shell. So I could have different sessions that are all named accordingly. I can operate with claude here, opening it up the same way, preview different files and then I have all my files here. It's better than just using this by itself because we can have multiple sessions and we can see all of our files and preview whatever it's building. If you want to boot directly into this folder and build in here, grab the file, drag it in and ask it what command would I use to directly boot into this file. So now if I take this right here, I exit out of the current session and I open up a new window. When I paste this in and I click enter, Claude will activate, but now it's running in this particular folder where we're going to be adding all of our context. So, if you've gotten this far, congratulations. You have your system set up, but it's far from being complete or custom. This is what VS Code looks like by itself. This is phase two. Okay, this is very important. This is how we're going to work with it. We're not just going to work out of a raw terminal. And it might look super confusing, like what the heck is even going on here? And that's all right. So, what I want you guys to do is to visit code.vvisualstudio.com. visualstudio.com, also linked below, and download the version right for your computer. If it's Mac, just download it. Now, once you're done with the actual install, notice what pops up right here. You haven't opened a folder yet. So, this is going to be how we're going to actually get into the file that we just built. Instead of using the custom command, we're going to go to desktop where we just built that file. We're going to see this one here, and then we're going to see the secondary one, which we're going to open up. You just trust and continue. Yes, I trust the authors. So, now you have no files in here. Nothing yet. And we see that it's automatically booted inside of this folder. And I'm going to show you some of the appearance settings that I have here. You I'm not going to narrate. You guys can just copy them. Okay. I have move I moved the primary sidebar the primary sidebar to the right. Um I have this as bottom. You can leave the panel position to bottom. You align the panel to the left. So your terminal pops open on the left like you see here. Tab bar. You see this? Turn this off. This off. You guys got this set up. If your explorer, like your files aren't showing up, file explorer. That'll pop open here. This is the primary sidebar. And if the terminal is not showing up or you can't even type in claude, just click new terminal. That'll pop open here. And you can actually drag the terminal to appear in any which of these places. I typically just keep it where it is here. Okay. And then you just type in claude. And now we have Claude operating inside of our workspace. So now you've gotten Claude code on your computer. You've started your file structure. And you have the shell VS Code setup. And now your setup looks like mine, but without all the context and craziness going on. The main files I'm just going to start you off with is a cloud folder. You want an admin folder, apps, websites, workflows. So over here, just type in.claude, type in admin, type in apps, websites, workflows. And you could add your business here and just do example business. Now, you're not going to have a lot of the fancy stuff that I have on mine yet. I have a status line here. I have all sorts of custom commands that I built out. But what I am going to do is show you two frameworks that you can download right now so that you can start building and take a access to. This is seed. This is going to help you actually ideulate, create ideas, and then feed it into something called pull, which is actually going to give you structured building processes. It'll build things for you. In this video, I'm not going to teach you the basics, the granulars about using seed and pole, but on my channel, I have this video right here. You guys can check it out. And if you guys want in-depth trainings of the entire setup, all the frameworks I'm using, my skills, consider joining my school. I'm just wrapping up the final module here, but everything from A to Z, all the frameworks I'm using, and it comes with a template vault. So, if you want to join the school, this is available for you. It's going to be the quickest way to get you dangerous with this tool. And if you guys want to skip the entire setup process, consider grabbing a copy of Charlie OS. It's my entire setup, all my frameworks, skills, everything pre-installed. So you guys can skip the headache and go right to building. And if you guys want to grab a copy of this, just go ahead and click the booking link below in the description. And if you guys want to take it a step further and work with me more personally, you don't want just education from the school, you don't want just the setup, and you want some one-on-one time with me, that's why I've developed the reserve program. We get Charlie OS installed within an hour and I'll work with you to diagnose your biggest revenue bottleneck and we'll solve that with a system on Charlie OS within 30 days and you guys get an hour of my time every single month with this system but you'll also get a private Slack channel with me where you can ask any questions anytime. So if you guys want access to that just book a call with me and we could chat. Now the installation process for seed and poll are very similar. So there's a command here and then there's another one here for poll. Both of these repos are also going to be linked below. So grab each one of those commands one by one. Open up a new terminal without claude. Paste that in and click enter. Mine's already downloaded, but then it's going to ask you for you one or two if you want it global or local or user. Just type in global. Same thing for poll. You could open up a new terminal or in the same one if it lets you paste the command. Click enter. And then here it's going to be the same process as we saw for seed uh global or local. I already have uh poll set up, but you would just do global for each. And what I do want to note, it got kind of ugly here for a second, but basically I ran slashinit. Okay, that's going to help you set up something called a claw.md file. And there's no information here, so it has nothing to reference, but it's okay. We still want the file to at least be configured. We can update it. This is tople instructions for claude.claude adds a claude.md markdown file instructions. And as we grow with claude, we teach it how we've scaffold out see the intended layout. It understands how this is laid out. And we can tell it what goes in each. And then as we have custom preferences, we tell Claude, "Hey, can you update the MD to remember this or do that?" But here, what we're going to do is yes. So, I just wanted Claude to place the MD file here. You can ask it. It's right here. And if you guys want instructions on how to set up your MD file, I got a lot of that in school, but we're not going to go too deep on the MD file. And if we consider what it looks like to have a base and a couple frameworks to help you build, you guys are set. If you guys type in slash, you guys can gain access to custom commands. And the first one I want to show you guys is seed. Seed is going to help you ideulate. So the second you watch this video and get your setup, you guys can run seed and you can IDate. So we'll talk to Claude. It's going to ask us some questions about the kind of project that we want to build. And notice this, it's called a bash command. It's always going to ask, do you want to proceed? I have a custom alias that you guys can gain access to that allows you to just type in instead of clawed to boot open a new new terminal, right? I have claude. It boots it open. But I also have CDD and it's going to boot open to into a completely different file that I have my other workspace. So it's actually pulling into this one. But it's going to actually bypass permissions. So it's not going to constantly ask me all this yes or no. I don't have CDD in here, but I do have other really good resources for you. So you guys can check that out if you want to check out the blog. Get clear on some of the videos that I have. It's all connected to YouTube. And if I had to lay out some custom resources for you, I would say this is a really good one. Claw design to build websites. You could use this with Paul and I actually have that on my YouTube channel right here. So, you could either check my YouTube or come to my website, but navigate this yourself. Pull what you like. Forget about it. We're going over here. We're using the CDD alias. We're going to have bypass permissions on. And I'm going to run seed again. Okay. We're going to idate. Notice how it's not asking me any of the yes or no anymore. And the goal is to get it to give us a full idea about a project. So, we would feed it massive amounts of context in order for it to package the idea. And then what we're going to do is actually launch it with Paul. So if seed is going to help you structure the idea and help you ideulate, you would actually launch it into Paul in order to start the building process. It's an entire building framework. If we look at my personal workspace and I open up one of the websites that I just built, the one that I referenced actually, it scaffoldled out a poll folder and I started with seed. I had the idea and then it launched poll with everything after it discussed many ideas with me and it built out different phases. But for this website, I didn't actually use the phases. If I show you another one, for example, this workflow that I built, this one actually had different phases that we went through. And we built this entire workflow phase by phase. I had to activate a plan and then I had to execute a plan. There's separate commands with Paul. And I have to apologize if my audio is going back and forth because I'm moving the mic. But as you can see here, it asks us what we want to build. And let's say I went through the entire building process and I was like, I just want to start building now. I think the idea is great. you helped me package it up. Maybe it was an application. It went through an entire interview process. You guys can see that in the video that I gave you below. But we can actually launch the project and it runs Paul initi similar to the initial init I ran above up here for the claude MD file, but it's going to scaffold out an entire folder system specifically for the new app that we're looking to build. And we could just reference, hey, put it in the app section. Or if it's a website we're building, put it here. Workflows, same idea. And it's going to run Paul initi by itself. and it's going to scaffold out that project. And the cool part is it keeps you organized. It keeps project state so you know exactly where the project build is, the road map, like where you're going with the project and the whole idea of the project itself. So with just those two plugins alone, see it as a plugin and pull as a framework, you can now ideate and build. If you guys want to check out some of the custom skills and other plugins that I have available on my website, you're more than welcome to search through those. So what we've went through together is the context rules. The beginning we kind of skipped up because I wanted you guys to be able to start building immediately with your setup. But in between the beginning and end toend orchestration, end to end orchestration is just you using seed to IDate and Paul to build with the framework so you can build an application. Jumping from here to here is going to essentially force you to learn these different things. If you want to learn about hooks, ask Claude. And the custom skills and commands, you guys can explore a lot of those that I have available here. I have a few that I use every single day like my humanizer skill. I have a custom SOP building skill. So, if I want to build out processes and share them with a teammate or an employee. So, there was a slight error and sometimes that happens with Claude. And the best part is you could tell Claude to fix those problems. Um, but essentially it loaded my SOP skill. So, it's operating now as a COO and it's going to ask me which business do I want to build some SOPs for? And notice the file structure, right? I taught Claude at the Claude MD level like we talked about before. different structure of the different businesses and the SOPs that I would place in each. So this is what you guys can aspire to do. I'm using it as a personal command center, but I'm also using it to build out websites and applications. And that's the whole benefit of using it as a monor repo workspace. I also have built out an entire workflow for bottleneck pipeline. If I run this, it'll actually look through my go high level pipeline and help me triage all the new reports that came in and help me figure out where they'd be placed. Low ticket, high ticket leads, and then tell me how to respond to them. I don't think I have any new leads in here right now, but we'll see. It's actually bottleneck pipeline. That'll actually pull the spreadsheet. This is actually going to pull the CRM. And for example, I have a new report. I just did a quick test. And if I click new report, this command, it's a workflow. It's tied together a bunch of different processes, right? Okay, so now it's looking through the new report and it connected via an MCP which is just toolbox and that's a whole other level that you guys can aspire to with claude code. Coolest part is a lot of the MCPs that allow you to connect to different softwares. For example, I have an MCP that connects claude code to my CRM, right? And if I show you here SLMCP, I have them all available right here. I've connected to school my community Trello and other CRM go high level also Higfield for AI image and video generation and I can do it all from cloud code directly here pull in that information send information back and forth just wanted to give you guys a quick segue to see that and have an understanding of how I have this um this actual workflow set up here which was the bottleneck pipeline. Okay, in the beginning we talked about a foundation a lot of what I've discussed here with you. We discussed how to build a seed and pull. Okay, customizing claude with skills and commands. We did that more in depth inside the school and we discussed MCPs and CLIs and then systemizing stacking the commands, the skills, the MCPs. CLI and MCP tools are very similar and it's okay. I'm not even the most technical guy. You call a spade a spade. They're connectors to different softwares. We stacked all this together in order to create these custom workflows. And I have a lot of available MCPS in the free resource section of my website. I wanted to run an analysis even though it's a test. So, it's going to look at the contact and inside of this, I've actually had Claude help me set up a system. So, when people fill out my form, it'll auto connect the form details that they filled out. So, Claude can access this and then have a really good idea of what kind of prospect they are, low ticket, high ticket. Then, it'll actually draft custom responses to this person. And see, it pulled in all that information. And it's saying skip it. Move it to dead because it's shitty. And notice now I'm just going to tell it to draft a response. It knows where to put it. I'm forcing it to avoid my rules. But notice, it's actually going to pull up some custom skills that I've added part of this workflow. So, it's activating email subject lines. It's going to activate my copywriting skill and my humanizer skill. So, it's going to figure out exactly how to write the copy of the email, how to write the subject lines, and how to speak like me. So, it picked the subject. It's going through the copywriting process now. And then it's actually going to humanize it to speak like me. And then after it's done, I'm not even going to look at the email. I'm going to ask it to send it and add to contact stage. It'll add it here. and it'll also attach my booking link. So, I'm creating custom responses to all the all of the leads that are filling out my forms and the forms and all of the sales process and lead intake processes. I've actually used Claude to build and a lot of it I use seed and Paul for just those two basic plugins and frameworks. And why am I showing you this workflow over all others? Because my biggest bottleneck, my biggest pain point is the fact that I have people filling out my forms and I can't write custom emails to all of these people. RIP to those who've gotten email from me from this, but it is taught how to speak like me. And when you do opt in or you do hop on a call, it is me. Of course, I'm not an AI avatar. But the whole point is I needed help with this. This is my biggest pain point. So that's where I started with all of the knowledge I have about business, marketing, and sales. Just give it to Claude. Help me facilitate this process. Save me time. And that's where I started among other projects that I built out. So you can see I was updated in the pipeline and it sent myself an email with my own booking link. So we're using Claude to create applications, processes, increase my sales, reduce the friction on the sales process. But this is all you guys need to get started. If you guys have any questions, just comment below. But that's what I got for you guys today. The best perspective I can give you guys when using this tool is whatever you don't know, ask Claude. Open up the terminal. say, "Hey, this is what I'm trying to do, but I can't quite figure it out." You can even give it the link to my resource page and say, "Hey, what kind of resources would work best for X, Y, and Z?" There's so many possibilities with this tool. But always remember this. Start with your bottlenecks. Find the one that's costing you the most time and money. Solve that problem with one tool. Fix the problem. Get good with the tool. Rinse, wash, and repeat. That's how you become an expert, a little bit every single day. It was fun. I hope you guys got value out of this. And if you did, like the video and consider subscribing with notifications turned on because I do about one to two videos like this every single week on this channel. And if you guys want to go deeper, we got all the links below. I did enough pitching. So, one way or another, I will see you guys on the next one. Thanks for watching.