§ 01 · The Hook
The bait, then the rug-pull.
When the person who built Claude Code posts his actual personal workflow, you read it. Alex Finn did exactly that — pulled Boris Czerny's X thread, stripped it to seven steps, and proved each one live in the terminal.
What the video promised.
stated at 00:04 "In this video I'll go through all eight steps of his workflow, and it'll have you building apps 100 times faster with Claude Code." delivered at 09:01
Where the time goes.
00:00 – 00:23
01 · Hook + promise
Title hook, authority borrow (Boris Czerny), promise: beginner to Claude Code master.
00:23 – 02:12
02 · Step 1: 5 terminals in parallel
Ghostie terminal demo split-pane Claude left / npm run dev right. 5 windows, one per feature. Memory argument vs VSCode/Cursor.
02:12 – 03:43
03 · Step 2: 5-10 Claude web agents
claude.ai Claude Code section — spin up agents before bed. Alex runs 3-4 nightly, wakes up to reviewed code.
03:43 – 04:36
04 · Step 3: Opus 4.5 for everything
Dismiss Sonnet cost-savings argument. Opus uses fewer tokens per task, better results. Set via /model Default.
04:36 – 05:35
05 · Step 4: Consistent CLAUDE.md
Rules sent with every prompt. Alex shows 6-rule template: think first, check in before major changes, explain steps, keep simple, never speculate on unopened files.
05:35 – 07:31
06 · Step 5: Plan mode + multi-iteration
Shift+Tab twice = plan mode. Multiple back-and-forth iterations before finalizing. Boris: most apps one-shot from good planning.
07:31 – 09:01
07 · Step 6: Custom slash commands
Ask Claude to write slash commands for repetitive tasks. Live demo /git. Meta-trick: ask Claude what slash commands would save time right now.
09:01 – 10:50
08 · Step 7: End-of-session verification
Prompt Claude to verify all work, use best coding practices, maintain good security. Security catch for vibe coders.
10:50 – 10:59
09 · Outro + CTA
Subscribe, notifications, Vibe Coding Academy plug, like ask.
Visual structure at a glance.
Named ideas worth stealing.
00:23
list
Boris Czerny 7-Step Claude Code Workflow
- 5 Claude Code terminals in parallel
- 5-10 Claude web agents
- Claude Opus 4.5 for everything
- Maintain a consistent CLAUDE.md file
- Start in plan mode, go back and forth multiple times
- Use slash commands for common activities
- End every session: prompt Claude to verify its work
The actual personal workflow of the person who built Claude Code, posted on X and distilled into 7 steps.
Steal for Drop these 7 steps as a checklist slide in any Claude Code intro video or course module
04:36
list
Alex Finn CLAUDE.md Rules
- First think through the problem, read the codebase for relevant files
- Before you make any major changes, check in with me and I will verify the plan
- Every step: give me a high level explanation of what changes you made
- Make every task and code change as simple as possible
- Maintain a documentation file describing the architecture
- Never speculate about code you have not opened — MUST read the file before answering questions
Six rules for a CLAUDE.md that steer Claude toward minimal, explained, non-speculative changes.
Steal for Copy into CLAUDE.md for any new project — especially rule 6 (no speculation) and rule 2 (check-in before major changes)
Lines you could clip.
05:56
"Claude code's plan mode is, in my opinion, the best technology in the entire world. It is as close to AGI as it gets."
04:03
"You're not saving any money by using Sonnet at this point. Opus is so smart that you'll get way more out of fewer tokens."
10:07
"So many vibe coders introduce security issues into their app. But by using this verification prompt, you'll make sure every session you walk away using best security practices."
02:44
"Before I go to bed, I always spin up three to four agents, and by the time I wake up, I have code to review."
How they spent the runtime.
Hook length23s
Info densityhigh
Filler8%
Things they pointed at.
00:23linkBoris Czerny X thread
10:41productVibe Coding Academy
How they asked for the click.
10:50
subscribe
"If you learned anything at all, make sure to subscribe, turn on notifications."
Standard YouTube trifecta (subscribe + notifications + like). Delivered over the completed canvas doc showing all 7 steps.
Word for word.
HOOK opening / re-engagementCTA the pitch analogy story
00:00HOOKThe creator of Claude Code just revealed his entire Claude Code workflow, and honestly, it's amazing, and I just learned a ton. In this video, I'll go through all eight steps of his workflow, and it'll have you building apps 100 times faster with Claude Code even if you've never touched a line of code in your life. Whether you're a stone cold beginner or a seasoned vet, by the end of this video, you'll be a Claude Code master.
00:23Now lock in and let's get into it. So Boris Czerny, the creator of Claude Code, just revealed his entire workflow on x, and it's really long. But I pulled out the eight most important steps, and we're gonna go through all of them right now. So step one of his workflow for using Claude code, the product that he built and knows the best is he always has five Claude code terminals open in parallel. So that's why he doesn't use Visual Studio Code or cursor to house Claude code. He uses the straight up terminal. But here's how you should be doing it. I found this app named Ghostie. Ghostie is basically a terminal wrapper. So it looks exactly like your terminal, but it has a few extra features that makes it super easy to use for beginners. And what I'll do with Ghostie is I will actually split this in two. So you can split this in half. And what I'll do is after I split in half on the left hand side, I'll open up Claude. On the right hand side, I'll actually run the server. So I'll do NPM run dev.
01:19And now I have the server running on one side so I can keep an eye on the logs. And on the left hand side, I can keep working on my app. And now to match Boris' workflow, what we can do is we can open up five of these windows inside this project and have Claude running across all those sessions. The beauty of this workflow of just using Claude code in a terminal, not in cursor or not in Versus code, is the terminal uses significantly less memory
01:44than Versus code. So you can have five, ten, 20 these terminals open for your project working on your project without slowing down your computer at all. If you were to have five VSCodes or five cursors open working on your project, your computer would grind to a halt and probably be a thousand degrees. So step one of this workflow, I would download Ghostie, link down below, completely free. Just makes your terminal easier to use. And then you can open up Claude code in it, open five of these terminals,
02:12and have Claude working on your app on five different parts of your app all at once. You're gonna get so much more done. But this is only improved by the second step of this workflow. The second step that Boris uses in his workflow is five to 10 Claude web agents. This is where you bump everything up a notch. So if you go to claude.ai, then go to the Claude code section, you can see the Claude code for web, and what you can do in here is awesome. You can actually spin up agents in the web to do work on your app. So Boris goes in here, and he spins up five to 10 agents working on different tasks in his app at once. My favorite way to use this is when I'm either on the go or about to go to sleep. So anytime I come up with ideas at the gym, which is where most of my ideas come up with, or I'm about to go to bed, I make sure to spin up agents here. So before I go to bed, I always spin up three to four agents, give them different tasks to work on in my app, and by the time I wake up, I have code to review the moment I wake up. So my app is always improving.
03:13You need to be doing this as well. With your Claude code subscription, you get this Claude for web app. Go to claude.ai. Go to the Claude code section. Spin up agents right before you go to bed. Or if you're on the go, open up the Claude mobile app. You get this same interface as well. This ensures that, a, you're always building tasks on your computer, and, b, you have agents in the cloud building tasks for you on the go. This will multiply
03:37the amount of work you can get done with Claude code, which brings us to the third part of Boris' master workflow, which is Claude Opus four five for everything. So as you can see here, this is his third step. He uses it for everything. It's the best coding model he's ever used. I completely agree. I think it's the best model I've ever used. It's always faster than using any other smaller model because it's so smart. I personally use Opus four five for everything as well. It's smarter. It's better. It's more cost efficient. You're not saving any money by using SONNET at this point. Opus is so smart that you'll get way more out of fewer tokens.
04:13So you absolutely should use Opus four five everything. If you haven't yet, do slash model inside Claude code, hit enter, and make sure you have the default, which is recommended, which is Opus four five for absolutely everything. You're gonna get way better results. Which brings us to the fourth step in his master workflow, which is maintaining a consistent Claude dot m d file. So having really consistent Claude dot m d rules.
04:36For those who don't know, the these are the rules that get sent with every single prompt you send to Claude code, which makes Claude work so much better if you have the right rules. I have my own custom Claude dot m d rules I put in every single project. I'm always changing, always keeping it up to date. I will put my latest Claude dot m d rules down below in the description so you can just copy and paste them. But, basically, it just steers Claude to make sure it makes the least amount of mistakes possible. And ever since I implemented these claude.md rules, it has been spectacular at avoiding bugs and errors. So make sure you have a Claude dot m d file. All you need do is inside of your project, make a Claude dot m d file in your root directory,
05:20HOOKand then copy and paste what I have down below, and Claude will perform so much better for you. That is a big rule in his eight step workflow. Maintain a consistent Claude dot m d file. The next step in his workflow is start in plan mode and go back and forth multiple times. This is probably, out of all of them, the most important step in the workflow. The reason being is if you can nail the plan mode in Claude code, you can get absolutely incredible results in one single shot. Claude code's plan mode is, in my opinion, the best technology in the entire world. It is as close to AGI as it gets. What you need to make sure you do is when you're in Claude code, hit shift tab twice.
06:00That puts you in plan mode. And then when you are starting any new session with Claude code, you want to put in a good plan. So for instance, I'm starting this session. I'm building out this project management tool. If you wanna check it out, you can see it right here. It's this really cool looking project management tool to manage my vibe coded apps. I wanna come up with new features and functionality for this tool. So I went into plan mode, and I'm not just gonna implement the first plan they come up with. I'm going to go back and forth. Boris makes it really clear here. He always goes back and forth multiple times to Claude before finalizing a plan. One of my favorite things to do as I'm going back and forth with Claude is I ask it to ask me questions to find out more about what I'm looking for. So after I get this initial plan with Claude, I'm gonna ask it to, hey. Any other things I can answer for you to give you a more clear picture in what I'm looking for? By having multiple back and forths with Claude in this plan mode, the plan you're gonna get is gonna be so much better than just your one shot plan most people get. And the more detailed this first plan is, the better the results you're gonna get. As Boris says here,
07:07most of his apps, can one shot because his plan mode is so good. So always spend extra time in plan mode because it's gonna save you a tremendous amount of time in the long run. This plan mode step is as important as it gets. It saves you a ton of time, but not quite as much time as this next tip I'm gonna get you, which is use slash commands for common activity. Slash commands are one of the most underutilized
07:31features of Claude code. When used correctly, they can save you a ton of time. What you wanna be doing is you wanna be making your own custom slash commands for activities you do over and over. So for instance, if you are committing to GitHub a lot, which you should be doing, in one of my last videos, I recommend using GitHub as much as you can, you can say, make me a slash command that commits
07:56and pushes all our code to GitHub. And what Claude code will do here when I hit enter is it actually create a custom slash command for me that will push all our code to GitHub when we are done coding. And this will save a lot of time because typically you have to put in four or five different commands to commit and push your code to GitHub. Now we can do it in one single slash command. Then when all that's done, all I to do is do slash git, and that custom slash command it creates for us will then do all the actions we described, saving us from having to go in and type in 10 different commands to get all our code onto GitHub. Make custom slash commands. It will save you so much time. And you don't even have to write them yourself. Just tell Claude code to write them for you. And if you can't think any slash commands that save you time, just go in here and say, hey. What are some slash commands that can save me time right now? Hit enter. Claude will come up with slash commands that can write for you. Whenever you're at a loss for what to build or how to save time, just ask Claude to do it for you. And speaking of having Claude doing things for you, that brings us to the last part of Boris'
09:01massive workflow that he goes through. I'll also link the entire thread down below if you wanna read it in detail. I think I picked out all the important parts, though, which is when you are done a session, prompt Claude to verify its work. So if you're anything like me, you spend hours a day on Claude code. You have these huge sessions, these huge changes to your app. What you wanna do when you're done a session, when you've changed a lot of code is you just wanna have Claude go back and verify it did good work and verify that it has good security practices and all that. So you want to prompt Claude at the end of every session to review its work. This is the prompt I use. I'll put this down below as well, but I say, please go back and verify all your work so far. Make sure you use best coding practices where efficient and maintain good security. Now that I think about this, this makes a good slash command. So I'm gonna make that right after this. You hit enter. Claude then goes back, reviews all the work it did during the session, and make sure you use good security practice. This is probably the most critical part. So many Vibe coders introduce security issues into their app. But by using this verification prompt, you'll make sure every session,
10:05CTAyou walk away using best security practices, and your code is super efficient. I put this down below so you can copy and paste it for every single session. I completely changed my workflow because of this. Now I am using Claude exclusively in the terminal. My computer is running so much faster. I'm getting so much more done. I'm using those web agents, which is allowing me to get work done at night, and all these coding best practices just make my code so much higher quality and save me a ton of time. If you have any questions on this, feel free to put them down below. I also answer questions live inside my vibe coding community. If you wanna join that, hit the link down below for the vibe coding academy. Do live calls all there all the time if you wanna ask me questions directly. If you learned anything at all, make sure to subscribe, turn on notifications.
10:50CTAAll I do is make amazing videos about building with Claude code. Also, leave a like as well. It's the easiest and freest way to support this channel, and I'll see you in the next
— full transcript
§ 05 · For Joe
Steal the stack. Ship overnight.
JoeFlow playbook
The man who built Claude Code runs 5 terminals + 10 web agents + a tight CLAUDE.md — you can copy this setup in an afternoon.
- Install Ghostie free. Split every project: Claude left, server log right. Open 5 windows. This is your new default.
- Set up overnight agents. Before bed, queue 3-4 tasks on claude.ai. Wake up to code. This compounds daily.
- Lock in Opus 4.5 as default via /model. Stop second-guessing the cost — the token efficiency argument is real.
- Write a CLAUDE.md for every project using Alex's 6 rules as a base. Rule 6 (no speculation on unopened files) is the most important bug-preventer.
- Plan mode is Shift+Tab twice. Never accept the first plan. Ask Claude what it needs to know before letting it write a line.
- Ask Claude to write your slash commands. Start with /git and the verification prompt. Then ask Claude what else it would automate.
- End every session with the verification prompt. Make it a slash command so you never skip it.
