The argument in one line.
Claude Code's poor reputation stems from users treating it like a conventional IDE instead of leveraging advanced techniques like plan mode, surgical prompts, XML templates, background processing, and AI-reviewing-AI workflows that unlock its full potential.
Read if. Skip if.
READ IF YOU ARE…
- A developer who uses Claude Code but feels frustrated by its output and suspects the problem is their workflow, not the tool.
- Someone building with Claude Code who wants to move beyond basic prompting and unlock patterns like plan mode, surgical edits, and AI-reviewing-AI chains.
- A programmer familiar with CLI tools and prompt engineering who's curious how to combine them — slash commands, background runs, TDD templates, and custom workflows.
SKIP IF…
- You've never used Claude Code or don't have it installed — this assumes you already know the basic interface and can navigate the editor.
- You're looking for architectural advice on large systems or production deployment patterns — these are tactical coding shortcuts, not system design.
- You primarily work in languages or domains Claude Code doesn't handle well yet (embedded systems, CUDA, specialized DSLs) — most tips assume general-purpose web or backend development.
The full version, fast.
The love-hate split on Claude Code is a usage problem, not a tool problem, and fourteen specific habits close the gap. Treat the CLI like a teammate: shift-tab-tab into plan mode before destructive work, write surgical prompts that name files and behaviors, and wrap longer asks in XML tags like instructions, requirements, and testing that Claude is trained to follow. Run /init to seed a claude.md, resume with claude --continue, commit and push from inside the session, and fire claude -p to run unattended jobs while you step away. Add custom slash commands under .claude/commands, have Claude review Claude's output in a fresh context, drag screenshots in for UI bugs, prompt test-driven loops, invoke ultrathink with sub-agents for harder work, and throw away off-rails attempts instead of fighting them.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.
00:00 – 00:56
01 · Cold open: the love/hate split
Two real comments side by side. Adam frames the premise: maybe the haters just aren't using it right.
00:56 – 01:38
02 · Tip 1 — Plan Mode (Shift+Tab+Tab)
New built-in feature: hit Shift+Tab+Tab to switch Claude Code into plan mode. It drafts the plan, you approve, then it executes.
01:38 – 02:22
03 · Tip 2 — Talk to it like a teammate
Ask questions, don't issue commands. 'What API am I calling when onboarding starts?' or 'when this button is clicked I get a 500, here's the log.'
02:22 – 03:59
04 · Tip 3 — Be surgical
Scope tightly to a single file and a single question. 'In this file the calculated LTV is different from what shows on this file — work through the likely calls.'
03:59 – 05:26
05 · Tip 4 — XML prompts for big features
Use <instructions>, <requirements>, <testing> tags for long prompts. Adam keeps these in Windows Notepad, copies them in. Anthropic has confirmed Claude follows XML structure well.
05:26 – 05:45
06 · Tip 5 — /init for CLAUDE.md
Run /init to generate the project memory file, and tell Claude to keep it updated.
05:45 – 06:24
07 · Tip 6 — claude --continue
Resume your last Claude Code session instead of starting cold. There are deeper ways via logs/conversation IDs but --continue is the daily driver.
06:24 – 07:15
08 · Tip 7 — Commit from inside Claude
Type 'commit' in Claude Code to stage, commit (with a generated message), and even push. No need to drop to another terminal for git.
07:15 – 08:32
09 · Tip 8 — `claude -p` one-shot mode
Fire-and-forget background runs with no approval prompts. 'Local Codex.' Run a few in parallel across the codebase, come back after lunch.
08:32 – 09:48
10 · Tip 9 — Custom slash commands
Drop a markdown file at .claude/commands/<name>.md and /name appears. Adam demos /project:update_docs and the Anthropic-recommended /fix-github-issue.
09:48 – 10:41
11 · Tip 10 — Claude reviews Claude
Open a fresh-context window and ask it to review the code another Claude wrote. Then hand the critique back to the original session.
10:41 – 11:31
12 · Tip 11 — Use screenshots
Drag-and-drop images directly into the terminal. Game-changer for design feedback and UI bug reports.
11:31 – 12:22
13 · Tip 12 — TDD prompt
XML triple: <test>, <implementation>, <rules>. 'Implement my test, then implement the functionality to pass the test.'
12:22 – 13:45
14 · Tip 13 — UltraThink prompt
'Please ultra-think through this. Start by exploring the codebase and gathering the necessary context. Use sub-agents where it makes sense. Explore, plan, implement.' Triggers extended thinking visibly in the UI.
13:45 – 14:40
15 · Tip 14 — Throw it away
Git commit. Throw away work that goes off the rails. Start over. Code is cheap. The biggest mental shift for Claude Code haters.
14:40 – 15:46
16 · Close: why the disconnect persists
Adam speculates: maybe some people just aren't CLI-native. He still loves Roo Code too. Asks for more tips in comments. Peace out.
Lines worth screenshotting.
- Plan mode (Shift+Tab+Tab) lets you have Claude draft a full execution plan before writing a single line of code.
- The love/hate divide on Claude Code almost always traces back to usage patterns, not tool quality.
- Talking to Claude Code like a teammate — asking what an API does or what called a 500 error — consistently outperforms command-style prompting.
- XML tags (instructions, requirements, testing) dramatically improve Claude's ability to execute large, multi-step feature prompts.
- Running `claude -p` turns Claude Code into a local Codex: kick off background tasks, go to lunch, review results on return.
- Custom slash commands stored in .claude/commands/ let you automate entire review, commit, and PR workflows with a single typed shortcut.
- Having a second Claude instance review the first instance's output catches more issues than any single-pass code review.
- Dragging screenshots directly into the Claude Code terminal works in WSL and Linux and cuts UI bug diagnosis time dramatically.
- The `--continue` flag reloads your last conversation exactly where it ended — most developers don't know this exists.
- Test-driven development prompts that separate test, implementation, and rules into XML tags make Claude's output significantly more reliable.
- UltraThink prompting on Sonnet 4 produces sub-agent task planning and implementation quality most developers associate only with Opus.
- When Claude goes off the rails, the correct move is git commit, throw it away, and restart — fighting a derailed context wastes more time than regenerating.
- You can commit and push directly from within Claude Code without ever opening a second terminal.
- The gap between people who love and hate Claude Code is almost entirely explained by whether they treat it as a search box or a collaborator.
The swipe file is the format.
Steal the templates, ship the listicle
Adam Larson turned his prompt notepad into a YouTube tutorial — and the swipe file is what people actually came for.
- Lift the four template prompts (XML long-form, TDD triple, UltraThink, slash-command pattern) into Joe's own .claude/commands and Rewriter library — they're battle-tested and free.
- Steal the cold-open structure for any pro/anti tool video: two real comments side by side, then 'maybe it's just the way you're using it.' Works for JoeFlow, Mod Boss, MCN+.
- Ship the same format for Joe's stack — '15 things you aren't doing with Cursor / Supabase / Vercel' on a single Excalidraw scroll. The simplicity IS the production design.
- Add a custom slash command for every prompt Joe types more than twice — release checklist, deploy-joeflow, mod-watch trigger. Put them in Mod Boss as exportable templates so members get them too.
- Frame the 'throw it away' permission as its own short — it's the deepest tip in the video and it's a paradigm shift, not a trick. Massive evergreen potential.
Terms worth knowing.
- Plan mode
- A Claude Code mode (activated with Shift+Tab+Tab) where the agent outlines all the steps it plans to take before writing any code, letting the user review and approve the approach first.
- XML tags (prompting)
- HTML-style markers like <instructions> or <requirements> used in prompts to clearly separate different sections of context, which large language models parse with high accuracy.
- CLAUDE.md
- A markdown file placed at the root of a project that gives Claude Code persistent instructions — coding standards, architecture notes, or behavioral rules — that apply across every conversation in that repo.
- /init command
- A Claude Code slash command that analyzes the current project and auto-generates a CLAUDE.md file with relevant context about the codebase.
- --continue flag
- A command-line option for Claude Code (`claude --continue`) that resumes the most recent conversation session instead of starting a fresh one.
- -p flag (headless mode)
- A Claude Code flag that runs a prompt non-interactively in the background — the agent completes the task without waiting for approvals or user input.
- Custom slash commands
- User-defined commands stored as markdown files in the .claude/commands/ folder that appear as /command shortcuts inside Claude Code, letting users run saved prompt templates instantly.
- TDD (Test-Driven Development)
- A software development practice where tests are written before the implementation code; the developer writes a failing test first, then writes code to make it pass.
- UltraThink
- A Claude Code prompt keyword that instructs the model to spend significantly more compute on reasoning before responding, surfacing a deeper chain-of-thought process.
- Sub-agents
- Independent AI agent instances spawned by a primary agent to handle parallel or specialized subtasks, then report results back to the orchestrator.
- WSL
- Windows Subsystem for Linux — a compatibility layer built into Windows that lets users run a Linux environment directly without a virtual machine.
Things they pointed at.
01:30toolRoo Code (root/group code)
05:26tool/init Claude Code command
05:45toolclaude --continue flag
07:15toolclaude -p (one-shot/print mode)
08:44tool.claude/commands/ slash command dir
12:40toolUltraThink (extended thinking)
13:25toolSonnet 4 (Adam's daily driver)
13:28toolOpus (better for hard things, per others)
Lines you could clip.
00:50
“Maybe it's just the way I'm using it.”
04:07
“I have like a million notepad on my Windows. A billion notepads open.”
07:23
“You can just kinda kick off these tasks… think about this like a local codex.”
14:11
“Throw away things that mess up. Go back. Start over. Reword it. It is okay. Code is now pretty cheap to generate.”
14:37
“There may just be a nature that people are not CLI based users.”
15:57
“The control that I get on it is just absolutely incredible.”
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
metaphoranalogystory
00:00I'm honestly blown away by the huge disconnect between people like I have here on the left where they say, I tried Cloud Code on your recommendation, and I have a very different opinion than yours.
00:12It was horrible. Then you've got people over here on the right that say Cloud Code made programming fun again. As you may know, I fall more on the right side.
00:22And I've been thinking a lot, like, why do I see such a divide between people loving Cloud Code and then people absolutely hating Cloud Code?
00:34And I I got to thinking, like, maybe it's just the way I'm using it. So what I wanna do today is I wanna break down all the different things that I've learned. I've tried to actually capture everything I could, all the techniques that I use.
00:48And I'm gonna go through them one by one. I won't make this incredibly long, and I'll try to put time stamps below so you can kinda jump between them. So the first tip that I wanna talk about is something brand new, but I have loved it.
00:59Like, this is actually something that I didn't realize how much I missed, and it could be one of the reasons why a lot of people still really prefer root code. If you hit shift, tab, tab and let me pull over the terminal here.
01:12So shift, tab, tab, you can see over here on the bottom where it says plan mode on. What you can do is you can actually have a conversation with Claude, And, basically, it will generate a plan of all the things it's gonna do, and then you could just kick it off and run it.
01:27It's magical. Now I have someone in Discord to thank for this. This actually just released a few days ago.
01:33Definitely try it out. Shift tab tab is not an obvious, like, thing that I would actually normally hit, but it is there now in the latest latest version of Claude.
01:45Now the tip two that I would give you is talk to it like a teammate. There's a few different ways you can talk about talk to it.
01:53But you can you know, think about how you would talk to another engineer. Ask it questions about the code. What does this class do?
02:01Which API like, one of my favorite things is I I couldn't remember the name of an API. And I was like, you know, I was like, start and all this stuff.
02:11And I said, okay. Uh, when onboarding starts, what API am I calling?
02:16And in a few seconds, you know, it ended up having the answer for me, and it was correct. You can also do things like change the login button. You don't even need to point to the component name.
02:26Um, you don't even need to put to the file. It does help it speed things up if you do point to the file, which I'll talk about in a minute There's a button that says create campaign.
02:35When it's clicked, I get a 500 server error from the API. Here is the log. That is a that is one that I actually used yesterday because I was getting a weird 500 error for, uh, just a field that was missing.
02:48So then it ended up fixing that for me, and I didn't have to go in and actually do anything too crazy there. You can also do, like, explain this thing to me.
02:58It it just works really, really, really well. Here's another project that I've been working on. I say, can you tell me what the API is for logging in and the format?
03:08And it starts to answer that question for me. It does a great job on it.
03:12But I also recommend being more precise and surgical. In this file, I need you to add a function that validates x y z before letting the user click sign up. Here's an example of one that I did.
03:24In this file, the calculated LTV last 90 is different from what shows on this file. In this case, the number of customers is the same, but the LTV is different. Work through the likely calls and a proposed plan to fix it.
03:38Very surgical. Like, I don't want it to actually code anything.
03:43I actually wanted to go try to figure out what the problem is. I'll kick this off and I'll go work on something else. It ends up being a very minor change or it may be a little bit more in the weeds.
03:52I can kind of take control of it if I need to there. Now this is one of the prompts that the formats that I like to use for long prompts. So a lot of times I'll be working on a new feature or I want something a little bit bigger.
04:04You need to be even more precise. So I'll use XML tags that I actually I know this is crazy, but I have like a million notepad on my Windows. A billion notepads open.
04:15And this is the format that I'll use. I'll use things like instructions, requirements, testing.
04:19Great tags to use. Clog code seems to follow those really, really well. So I'll build something like this where I'll this is an exact example that I actually used.
04:30So I will say build a serverless user authentication system using AWS Cognito, Lambda, and CDK, and then I kind of fill in all the stuff. So I'll go through and tweak this.
04:39I actually will use AI to help generate this originally, uh, initially, and then I just go in and kinda manually change it. And this will help a ton with the way that the Cloud Code will actually pick up this feature and run it.
04:54I've, uh, Cloud Anthropic itself actually talk about how well Cloud has been trained on following XML based tags, and you can actually reference them in other parts of the prompt. For example, you can be make sure you refer back to this information area or make sure you do this particular thing.
05:12And I actually use that a lot in my production prompts as well. So this is a you know, this is an example of a prompt that I would build outside of Cloud. I wouldn't just type it in, and then I copy and paste it in, and we're good to go at that point.
05:26Make sure you use a net to create a Cloud dot m d file. Talked about that a little bit, but also make sure you keep it up. So tell it to update it once in a while.
05:33This is something I've talked about in previous videos quite a bit, so make sure you just are aware of the slash init command. That's a very, very, very powerful one. Now this is one that I know a lot of people don't know about.
05:46But let's say for some reason you end the day, you close out the conversation, cloud exit, you can simply hit claw dash dash continue to load up your previous conversation. You're good to go. It's super helpful.
05:57There's also ways to go look at your clawed logs and grab the idea of a conversation, and then you can load that in as well. But claud dash dash continue is the one I probably use the most.
06:06Because most of my conversations, my old ones, I don't really want to resume them very well. For the longest time, I was actually exiting claud or opening up another terminal to actually interact with GitHub.
06:16And I still do this quite a bit, but there's no reason to always do that. There are times that I just want to go ahead and commit.
06:24So you can literally just type in commit into ClogCode, and it'll actually go through. You could see here where I've actually been asked if I wanna git add that file and basically eventually do a git commit dash m.
06:35I do actually love the commit message it has here. Another thing that I'll typically do, though, is if I am if I wanna do the commit myself, I actually tell it to generate a commit message for me.
06:47I'll copy and paste it, and I use that. I typically don't use it, but you can actually use the push as well. Um, so you can say, uh, push branch or push to dev, and then you could actually get it to to to go ahead and do the push for you as well.
07:02Again, you do need to have git configured correctly to make this work, but it is a very useful thing if you just really wanna kinda have it do its thing in particular. Now this is one I freaking love. So now we're starting to get into some stuff that I probably would think that you guys probably haven't tried yet.
07:19So let's say that I'm in a, uh, I'm in a terminal, and I just have an idea for something I wanna go to lunch.
07:28So I will say something like claw dash p. So this is basically it's just gonna sit there and do the work behind the scenes. I don't have to interact with it.
07:36I don't have to approve anything. I'll say, I want you to make it so that I can attach a user avatar via an URL to my user record. I need an APN model update.
07:45Very basic. And this is what ends up happening. Like, I get back this once it's finished.
07:51All the work's done. I can then now go in and review it. This is great.
07:55You can kinda think about this like a . You can just kinda kick off these tasks.
08:00And sometimes I'll kick off couple of them at a time in different parts of the code, and then I'll come back to it and just see what it did. Now but you do end up losing the interactivity to it.
08:10So if it's something that, you know, you kinda wanna have a conversation with or be able to iterate on, you do want to not do the Dashpeak. But it's so freaking awesome if you just wanna get a start on it and treat it literally like codecs or some sort of remote aid agent.
08:28This is one I've started using a bit more. This is a new project I'm working on. But in general, what I wanna say is like Claude custom slash commands.
08:36You can actually create your own slash commands by going into your dot Claude folder, creating a folder called commands, and then making a markdown file. In this case, let's just say I wanna do an update docs one.
08:48So I'll say evaluate the current project, evaluate the current documentation, update cloud dot md with any new functionality, update other documentation as needed. And now you can see I do slash, and I have that command in there.
09:00This this is a brilliant, like, brilliant addition that I've actually started to play around with a lot more in my main repo that I work on a daily basis.
09:11I think I have two three, actually, that I've created, all very, very useful. This one is one that Anthropic kinda recommends where you can be like, please analyze and fix the GitHub issue. You can pass in a number for the GitHub issue, and it has the these commands here.
09:25Like, follow these steps. Use GitHub issue view to get the issue details, etcetera, etcetera, all the way down to push and create a PR to literally automate the entire thing without ever interacting with it.
09:37It's super, super sweet. This is one thing a workflow that I've used, and I use this with other AI too. But have Claude review work from Claude, and you can have one in Opus and one in Sonnet.
09:50Now I primarily use Sonnet just because I want as much usage as possible. But I will, a lot of times, basically, go through and I'll have something done.
10:00And then I'll be like, alright. This is a new file I created. Go review this in another window.
10:06So I basically bring a new context. Look for issues. You can make a prompt for this as well, by the way.
10:12You can do a prompt, uh, a custom prompt if you have, like, special review guidelines, and it gives me the reviews, I will typically go through and have a conversation about this, get it to the point I want, and I give it back to the one that actually built it, and I have it iterate on it.
10:26It's very, very handy to start thinking about AI, kind of iterating on things that AI has actually done for you. And Cloud Code is perfect, absolutely perfect at that.
10:36Yep. Use screenshots. Really use them.
10:38You can drag and paste or drag and copy them directly into the terminal. This is what it looks like for me when I do that. It works on WSL.
10:45It also works really well in Linux. So in my case, what I typically do is I'll just drag a file itself into the terminal. It really, really is handy, especially when you're doing design stuff or if there's a UI bug.
10:58Copy and paste it in there or just drag and and put it in there rather, and then have tell it what's going on with it, and it helps it so so much. So definitely use screenshots.
11:08Don't be afraid of them. I know a lot of people like the computer use and some of the other tools. This is one of the prompts that I've been using quite a bit.
11:15Again, I have what I do is I have, um, these little text files I save on my desktop. My desktop is a mess, by the way.
11:21I need to organize that. But I will do, like, a TDD type prompt, and notice that I'm using the XML format.
11:28I'll do three different tag types, so test, implementation, and rules. And then I'll say, we are doing test driven development. The implementation does not quite exist yet.
11:37Please implement my test, then implement the functionality to pass the test. Now you can actually go on and say, go ahead and commit and do a PR as well. I actually wanna review the code before that happens.
11:48So I do just usually stop it here. You can add any rules that you want in there. This is a very, very cool way because it actually makes ClogCode pretty powerful.
11:58If if you have something kinda isolated enough to where you can just have it iterate on to make the tests that it wrote pass, it's pretty pretty freaking powerful, to be honest with you. So definitely give this a try if you haven't already.
12:12You may even have a better prompt than what I have here, and I would love to hear that in the comments below. Now this is one that I think a lot of people were most surprised about, but it is so so helpful.
12:26So I use a combination of ultra think, but also a few other things in this prompt. This is the prompt that I save, and I just copy and paste it in, and I fill in what I wanna do.
12:36So I'll say, please ultra think through this. Start by exploring the code base and gathering the necessary context. You should use sub agents where it makes sense.
12:44I want you to explore, plan, and implement the following. So, basically, take a look at this example here.
12:51All of the stuff I just said, implement a new table for child profile. This should include name, birthday, and avatar name, avatar image. Child profile should reference a user as the owner.
13:00The users add them to their account. It's possible in the future that other users will have access to viewing child profiles owned by a different user.
13:08And it goes through and starts to do work. So you can kinda see some of the thinking that it did here.
13:14Then it builds a really great task list manager or a task list of things that it needs to go through and do. And this is spot on. And the implementation here was incredible.
13:26And you can see that we've now triggered this thinking dot dot dot because we've told it to think harder. This is all done with Sonnet four. This is not Opus.
13:35I've heard people could say they get even better results from Opus, but I have again, I have most of my testing has done been done with Sonnet.
13:43Now the last thing that I wanna do say is don't be afraid to throw away what it does. This is something that I feel a lot of people struggle with.
13:54And if I were was a betting person, I think a lot of people spend a lot of time fighting AI to try to get it to go back on the rails when it's already messed something up.
14:04Git commit. Git commit. Throw away things that mess up.
14:08Go back. Start over. Reword it.
14:11It is okay. Like, code is now pretty cheap to generate. So if it goes , go ahead and just wipe it away and start over.
14:20So my hope is that I'll start to gather even more information over time to try to understand why there is this, like, massive disconnect. And I see this.
14:30I'm talking tons of messages, uh, saying, I love Cloud Code or I hate Cloud Code.
14:38And there may just be a nature that people are not CLI based users. You know, it is a just a different experience. And I can't fault anyone for wanting to go back to a group code.
14:49I love group code. I still use it on a daily basis. But I also think CloudCode really does make programming very fun.
14:58I don't know another way to actually explain it other than I just have so much control of how I actually wanna get things done. And I can choose, like, I could choose to do a one shot and let it go.
15:11I can actually have it go really deep and build a task list. The control that I get on it is just absolutely incredible.
15:19So, anyway, I hope these tips have been helpful to all of you. If they have in some way, let me know in the comments below. If there's new ones that you actually know that I haven't included here, um, this is just my own personal, uh, way of using CloudCode.
15:31I'm sure there are ways that people use it that are beyond my, uh, beyond my knowledge at this point, which would be amazing to learn for myself.
15:40Anyway, I hope you guys all have a wonderful day. And until next time, everyone. Peace out.
The Hook
The bait, then the rug-pull.
Adam Larson opens with two real YouTube comments side by side — one calling Claude Code horrible, one calling it the thing that made programming fun again — and asks the obvious question: why the disconnect? His thesis is that it's a usage problem, not a tool problem. The rest of the video is the receipts.
Named ideas worth stealing.
04:14model
XML-tagged long-prompt template
- <instructions>
- <requirements>
- <testing>
Wrap long prompts in named XML tags. Claude was trained to follow this structure and you can reference tags from elsewhere in the prompt ('refer back to the requirements above').
Steal forany prompt longer than a paragraph — Joe's Rewriter, batch templates, JoeFlow Chef context blocks
11:40model
TDD prompt structure
- <test>
- <implementation>
- <rules>
Three-tag prompt that tells Claude: write the tests, then write the code to pass them, follow these rules. Pair with --no-approval for autonomous loops.
Steal forany agent that needs verifiable success criteria — Karpathy goal-driven execution lives here
12:40model
UltraThink prompt
'Please ultra-think through this. Start by exploring the codebase. Use sub-agents where it makes sense. Explore, plan, implement the following: [...]' — triggers Claude's extended thinking and parallel sub-agent dispatch.
Steal forany non-trivial feature spec — replace one-shot prompts with this for anything that touches >1 file
08:44concept
Custom slash command via .claude/commands/
A markdown file in .claude/commands/ becomes /filename in Claude Code. The file body is the prompt. $ARGUMENTS is the placeholder. Lets you ship reusable team prompts inside the repo.
Steal forevery repeated prompt Joe types — Mod Boss session-launch, JoeFlow release checklist, MCN migration patterns
09:50concept
Claude-reviews-Claude loop
Fresh-context window reads code another Claude wrote, returns a critique, hand it back to the original session to iterate. Catches the writer's blind spots.
Steal forany agent orchestrator with quality gates — Chef → Critic loop in JoeFlow Sessions
How they asked for the click.
VERBAL ASK
15:28subscribe
“Let me know in the comments below. If there's new ones that you actually know that I haven't included here…”
soft — no aggressive subscribe ask, just a comment prompt. The real CTA is implicit: try the prompts. No timestamp links to Scrimba in-video, only in description.
FROM THE DESCRIPTION
AFFILIATECommission earned if you click.
OTHER LINKSAlso linked in the description.
Visual structure at a glance.
