A practical watch order for beginners who want to stop feeling lost and start building with Claude Code.
By @lifeofarjav
What this page is for
Claude Code can feel intimidating at first because everyone online makes it look like you need to be a senior engineer before you can use it.
You do not.
You need three things:
- A clear starting point
- A few beginner friendly walkthroughs
- One tiny real project to build immediately
This page gives you the exact order I would recommend if you are starting from zero.
Do not binge everything at once. Watch the first two videos, build one small thing, then come back for the deeper material.
The best 4 videos to watch first
1. Start here: Nate Herk, Master 95% of Claude Code in 36 Mins
Best for: absolute beginners
Length: about 36 minutes
Watch: Master 95% of Claude Code in 36 Mins
Start with this because it is the least intimidating entry point.
This is the video I would send someone who has never properly used a terminal before. It gets you past the biggest blocker: opening Claude Code and doing your first useful thing without overthinking it.
What you should pay attention to:
- How Claude Code is opened and used
- How simple prompts become real file changes
- How to stay calm when the terminal looks unfamiliar
- How to think of Claude Code as a working partner, not just another chatbot
Your action after watching:
Create a new folder and ask Claude Code to build one tiny thing.
Example:
Build me a simple habit tracker as a single HTML file. Keep it clean, mobile friendly, and easy to edit.
2. Then watch the official one: Anthropic, Boris Cherny, Mastering Claude Code in 30 Minutes
Best for: understanding how Claude Code is meant to be used
Length: about 30 minutes
Watch: Mastering Claude Code in 30 Minutes
This is the official video from Anthropic featuring Boris Cherny, one of the key people behind Claude Code.
The value here is not just learning commands. It shows how serious builders actually use Claude Code inside real workflows.
What you should pay attention to:
- Asking Claude Code questions before asking it to change code
- Letting it understand the project first
- Using it for exploration, debugging, refactoring, and implementation
- Thinking in workflows instead of one prompt at a time
Your action after watching:
Open an existing folder or project and ask:
Before changing anything, explain how this project is structured. Tell me the main files, what each part does, and where I should start if I want to improve it.
This one habit saves you from making random changes before Claude understands the project.
3. Go deeper: Nick Saraev, Claude Code Full Course 4 Hours, Build and Sell
Best for: people ready to spend a weekend learning seriously
Length: about 4 hours
Watch: CLAUDE CODE FULL COURSE 4 HOURS: Build and Sell
Watch this once you have already used Claude Code at least once.
This is not the first video to watch because it is long. But it is useful when you are ready to move from playing around to building something you could actually deploy, package, or sell.
What it is useful for:
- Full setup
- Building real projects
- Working with agent style workflows
- Git worktrees
- Cloud deployment
- MCP servers
- Productizing what you build
Your action after watching:
Pick one small idea and turn it into a real mini product.
Example:
Build a simple lead magnet delivery page with an email capture form, a thank you page, and a clean mobile responsive layout.
4. Level up: Nate Herk, How to Use Claude Code Better Than 98% of People
Best for: improving your workflow after you have started
Length: about 30 minutes
Watch: How to Use Claude Code Better Than 98% of People
This is the video to watch when Claude Code no longer feels scary, but you still feel slow.
It helps you move from basic usage to better systems, better workflows, and better results.
What you should pay attention to:
- Repeatable workflows
- Better instruction design
- Cleaner project context
- Using Claude Code for more than simple coding tasks
Your action after watching:
Create or improve your CLAUDE.md file.
Example:
# Project Context
This project is a simple landing page for my personal brand.
## Goals
-Keep the design clean and premium
-Make it mobile first
-Use simple HTML, CSS, and JavaScript unless I ask otherwise
## Preferences
-Explain changes clearly
-Ask before deleting files
-Keep copy concise
-Prioritize readability and speed
The quick 15 minute start
Before watching everything, do this.
Step 1: Install Claude Code
You need Node.js and a Claude account.
Run:
npm install -g @anthropic-ai/claude-code
You can also use Claude Code in the browser at:
Sign in with your Claude account.
Step 2: Open a project folder
In your terminal, go to any folder.
Example:
mkdir claude-code-test
cd claude-code-test
Then start Claude Code:
claude
Step 3: Give it one small real job
Do not start with a giant app.
Start with something tiny.
Example prompts:
Build me a single page habit tracker in HTML, CSS, and JavaScript.
Create a simple personal website with a hero section, about section, and contact section.
Organize the files in this folder and explain what you changed before making changes.
The goal is not to build something perfect. The goal is to experience the loop: ask, review, improve.
Step 4: Add a CLAUDE.md file
A CLAUDE.md file gives Claude Code context about how you want the project handled.
Create a file named:
CLAUDE.md
Add something like this:
# Working Instructions
You are helping me build and improve this project.
## Rules
-Explain your plan before making large changes.
-Do not delete important files without asking.
-Keep the code simple and readable.
-Prefer practical solutions over clever ones.
-After every change, summarize what changed and what I should test.
## Style
-Clean
-Minimal
-Fast
-Easy to understand
Step 5: Try voice mode
Inside Claude Code, try:
/voice
Talking to it can make the workflow feel more natural, especially when you are planning or debugging.
The beginner watch plan
Use this order if you want the simplest path.
Day 1: Remove fear
Watch:
- Nate Herk beginner video
- Anthropic official Boris Cherny video
Then build one tiny project.
Do not watch more until you have built something.
Day 2: Build something real
Watch the first hour of the Nick Saraev full course.
Then build something you could actually use.
Examples:
- Personal landing page
- Lead magnet page
- Simple CRM
- Basic calculator
- Blog template
- AI tool directory
- Client onboarding checklist
Day 3: Improve your workflow
Watch Nate Herk’s advanced workflow video.
Then add:
CLAUDE.md- Better project structure
- Clear instructions
- A repeatable build checklist
10 more Claude Code videos to go deeper
These are optional. Do not use them as an excuse to avoid building.
1. Fireship, Claude 3.7 goes hard for programmers
Watch: Claude 3.7 goes hard for programmers
Good for seeing why developers got excited about Claude Code and Claude’s coding ability.
2. Tech With Tim, Claude Code: Full Tutorial for Beginners
Watch: Claude Code: Full Tutorial for Beginners
Good for a more traditional beginner walkthrough from setup to first app.
3. ThePrimeagen, Claude Code got leaked
Watch: Claude Code got leaked
Good for seeing how an experienced engineer thinks about the tool.
4. Anthropic, Introducing Claude Code
Watch: Introducing Claude Code
Good for the original product demo and the official framing.
5. Alberta Tech, Why devs are OBSESSED with Claude Code
Watch: Why devs are OBSESSED with Claude Code
Good for understanding the larger shift behind why Claude Code is getting attention.
6. John Kim, How I use Claude Code, Meta Staff Engineer Tips
Watch: How I use Claude Code
Good for practical daily usage patterns from a senior engineering perspective.
7. Anthropic, Claude Code best practices
Watch: Claude Code best practices
Good for official best practices around project context, permissions, and workflows.
8. Greg Isenberg, Claude Code Clearly Explained
Watch: Claude Code Clearly Explained
Good for a high level, beginner friendly explanation.
9. Alex Ziskind, I Ran Claude Code for FREE
Watch: I Ran Claude Code for FREE
Good if you want to understand local model experiments and cheaper workflows.
10. NetworkChuck, Claude Code on your Phone is OFFICIAL
Watch: Claude Code on your Phone is OFFICIAL
Good for seeing how mobile driven coding workflows can work.
What beginners get wrong
Mistake 1: Watching too much before doing anything
The fastest way to learn Claude Code is not to watch ten videos.
It is to watch one video, build one thing, then fix what breaks.
Mistake 2: Asking Claude Code to build a giant app first
Bad first prompt:
Build me a full SaaS with payments, dashboard, auth, database, admin panel, and AI features.
Better first prompt:
Build a clean single page landing page for a SaaS idea. Use placeholder copy and keep the code simple.
Start small. Then expand.
Mistake 3: Not giving project context
Claude Code is powerful, but it is not magic. If your project has rules, tell it.
Use CLAUDE.md.
Tell it:
- What the project is
- What stack you use
- What files matter
- What not to touch
- How you want changes explained
Mistake 4: Letting it edit before it understands
Before asking for changes, ask it to inspect the project.
Use:
Read the project first. Do not make changes yet. Explain the structure, the main files, and the safest way to make the next change.
Mistake 5: Treating Claude Code like ChatGPT
Claude Code is not just a chat window.
Think of it like a junior technical operator sitting inside your project folder.
It can:
- Read files
- Edit files
- Explain code
- Debug errors
- Refactor messy sections
- Build features
- Create docs
- Help you understand unfamiliar codebases
Your job is to give it clear direction and review the work.
The best first projects to build
Pick one.
Option 1: Personal landing page
Prompt:
Create a clean personal landing page for me as an AI creator. Use HTML, CSS, and JavaScript only. Include a hero section, about section, featured posts section, and contact section.
Option 2: Lead magnet page
Prompt:
Build a simple lead magnet landing page where users can enter their email to get a free Claude Code starter kit. Use a clean premium design and keep it mobile friendly.
Option 3: Content idea tracker
Prompt:
Build a simple content idea tracker as a single HTML file. It should let me add ideas, mark them as scripted, recorded, edited, or posted, and save data in local storage.
Option 4: Client onboarding checklist
Prompt:
Build a client onboarding checklist for an AI automation agency. Include sections for access, goals, deliverables, timelines, and launch checklist.
Option 5: File organizer script
Prompt:
Create a script that organizes files in this folder by file type. Before writing the script, explain the plan and ask for confirmation.
The simple Claude Code workflow
Use this every time.
1. Ask it to inspect
Read this project. Do not change anything yet. Explain the structure and what each major file does.
2. Ask it to plan
I want to add [feature]. Give me a simple implementation plan first. Do not edit files yet.
3. Ask it to build
Now implement the plan. Keep the changes minimal and explain what you changed.
4. Ask it to test
Review your own changes. Look for bugs, broken assumptions, missing edge cases, and anything I should test manually.
5. Ask it to improve
Clean this up without changing the behavior. Make the code simpler, easier to read, and easier to maintain.
This is where Claude Code becomes useful: not one perfect prompt, but a tight working loop.
My recommendation
Do this in order:
- Watch the Nate Herk beginner video
- Watch the Anthropic Boris Cherny video
- Install Claude Code
- Build one tiny thing
- Add
CLAUDE.md - Build a second tiny thing
- Watch the longer full course only after you have momentum
The trap is trying to become an expert before starting.
Start ugly. Start small. Start today.
Copy and paste starter prompts
Prompt 1: Understand my project
Read this project carefully. Do not make any changes yet. Explain what the project does, how the files are organized, and what I should understand before editing it.
Prompt 2: Build a simple feature
I want to add this feature: [describe feature]. First give me a simple plan. Then wait for my approval before editing files.
Prompt 3: Clean up messy code
Review this code and identify what is messy, duplicated, confusing, or risky. Do not edit yet. Give me a prioritized cleanup plan.
Prompt 4: Debug an error
I am getting this error: [paste error]. Find the likely cause, explain it in simple language, and suggest the safest fix before changing anything.
Prompt 5: Build from scratch
Create a simple [project type] using [stack]. Keep it clean, minimal, mobile friendly, and easy to understand. Explain the file structure when done.
Prompt 6: Create project rules
Create a CLAUDE.md file for this project. Include project context, coding preferences, safety rules, and instructions for how you should explain changes.
Final note
Claude Code is not hard because the tool is complicated.
It feels hard because most people start in the wrong place.
Start with one small build. Then repeat.
That is how it clicks.
Follow @lifeofarjav for practical AI workflows, creator systems, and useful tools that actually help you build.