Everything Claude Code: Building a YouTube Channel from Zero

You know Claude Code inside and out. You built production systems on it. You wrote skills, wired MCP servers, automated workflows, and shipped real software with it daily. That knowledge is worth something – most developers are still watching generic “AI coding assistant” videos that barely scratch the surface. A dedicated channel fills a gap that nobody else is filling well.

Here is how to build “Everything Claude Code” from setup to first upload to sustainable growth.

Step 1: Create the Channel

Go to studio.youtube.com and sign in with a Google account. If you want the channel separate from your personal Google identity, create a Brand Account:

  1. Click your profile icon -> Settings -> Add or manage your channels -> Create a channel
  2. Name it Everything Claude Code
  3. This creates a Brand Account that multiple people can manage without sharing passwords

Channel settings to configure immediately:

Step 2: Branding

You need three visual assets before your first upload.

Profile picture (800x800px) A clean logo or stylized icon. The Claude Code terminal prompt ($) or a minimal monogram works. Avoid photos – a logo reads better at thumbnail size.

Banner (2560x1440px) Keep it simple. Channel name on the left, a one-line tagline on the right: “Master Claude Code – from first install to production.” The safe area for mobile is the center 1546x423px – put all text there.

Thumbnail template Design one reusable template in Canva or Figma:

Canva (canva.com) is free and sufficient for all three. Create a brand kit with your colors and fonts so every asset stays consistent.

Step 3: Equipment

You do not need expensive gear. You need clear audio and readable screen content.

Minimum setup:

Audio matters more than video. Viewers tolerate average visuals but leave immediately on bad audio. Record in a quiet room. If your space echoes, hang a blanket behind your monitor – it works better than most acoustic foam.

Screen recording settings:

Step 4: Content Strategy

The channel name is the strategy: everything about Claude Code. Organize content into series that map to how people learn.

Series 1: Getting Started (Episodes 1-5)

Hook new viewers. These are evergreen and will drive discovery for months.

  1. “Claude Code in 10 Minutes – Install to First Project” – quick-start from npm install to completing a real task
  2. “Claude Code vs Cursor vs GitHub Copilot – What Actually Matters” – honest comparison, not clickbait. Focus on the workflow differences, not “which is better”
  3. “Your First MCP Server in Claude Code” – connect to a real external tool, show the permission model
  4. “Claude Code Settings That Actually Matter” – the config file, model selection, permission modes, memory
  5. “5 Things I Wish I Knew Before Using Claude Code” – mistakes you made, time you wasted, what you do differently now

Series 2: Deep Dives (Ongoing)

One feature per episode. Exhaustive coverage.

Series 3: Real Projects (Monthly)

Build something real on camera. Start to finish. No cuts during the Claude Code interaction so viewers see the actual workflow – the mistakes, the corrections, the iteration.

Ideas:

Series 4: Tips and Tricks (Short-form)

60-90 second YouTube Shorts. One tip per video. These drive discovery through the Shorts algorithm.

Step 5: Your First Video

Do not overthink it. Your first video will not be great. Ship it anyway.

Recommended first video: “Claude Code in 10 Minutes – Install to First Project”

Script structure:

  1. Hook (15 seconds): Show the end result – a working project built entirely with Claude Code. “I just built this in 10 minutes. Here is exactly how.”
  2. Install (2 minutes): Walk through installation. Show real terminal output.
  3. First task (5 minutes): Give Claude Code a real task. Show the interaction – the prompts, the tool calls, the file edits. Narrate your thinking: why you prompted it that way, what you expected, what surprised you.
  4. Key takeaway (2 minutes): One thing that makes Claude Code different from other tools. Be specific.
  5. Call to action (30 seconds): Subscribe, next video topic, ask a question in comments.

Recording workflow:

  1. Write bullet-point notes (not a word-for-word script – you will sound robotic)
  2. Do one practice run without recording
  3. Record the screen and audio in one pass
  4. Edit out long pauses and dead air, but leave the natural flow
  5. Add a simple intro card (channel name, 3 seconds) and end screen
  6. Export at 1080p, upload

Step 6: Optimization for Discovery

YouTube is a search engine. Treat it like one.

Title formula for dev content:

Description template:

[One sentence summary of what the viewer will learn]

Timestamps:
0:00 - Intro
1:30 - [Section 1]
4:00 - [Section 2]
...

Links mentioned:
- [relevant URLs]

Subscribe for weekly Claude Code deep dives.

Timestamps (chapters) are critical. They improve watch time metrics because viewers jump to the section they need instead of bouncing.

Tags: Use 5-10 relevant tags. “claude code”, “anthropic claude”, “mcp server”, “ai coding tool”, “claude cli”, plus the specific feature name.

Step 7: Upload Schedule

Consistency beats frequency. Pick a schedule you can sustain.

Recommended starting cadence:

Best upload times for developer audiences:

Batch-record when you can. Record 2-3 videos in one session, then edit and schedule them across the week.

Step 8: Growth Tactics

Cross-post strategically:

Engage with comments. Reply to every comment in your first 50 videos. YouTube’s algorithm rewards channels with high engagement rates. A reply from the creator doubles the chance the commenter comes back.

Collaborate. Find other Claude Code or AI tooling creators. Guest appearances, reaction videos, or “I tried their workflow” videos cross-pollinate audiences.

Build an email list. Put a link in every video description to a simple signup page. YouTube can change its algorithm overnight. An email list is yours.

Step 9: Monetization Path

YouTube Partner Program requires:

At 1 video per week with dev content, expect to hit this in 6-12 months if content is good and consistent.

Beyond ad revenue:

Step 10: Content Ideas for the First 20 Videos

  1. Claude Code in 10 Minutes – Install to First Project
  2. Claude Code vs Cursor vs Copilot – Honest Comparison
  3. Your First MCP Server in Claude Code
  4. Claude Code Settings Deep Dive
  5. 5 Mistakes Every New Claude Code User Makes
  6. Building a REST API from Scratch with Claude Code (real project)
  7. Claude Code Skills – Create Reusable AI Workflows
  8. Claude Code Hooks – Automate Everything
  9. Claude Code Memory – How CLAUDE.md Actually Works
  10. Connecting Claude Code to External APIs via MCP
  11. Claude Code Agent Mode – Parallel Subagents Explained
  12. Building a CLI Tool with Claude Code (real project)
  13. Claude Code for Code Review – Better Than You Think
  14. Advanced Prompting Techniques for Claude Code
  15. Claude Code Skills Evals – Test Your Skills Automatically
  16. Managing Large Codebases with Claude Code
  17. Claude Code Plans and Tasks – Complex Project Management
  18. Building an MCP Server from Scratch (real project)
  19. Claude Code in VS Code vs Terminal – Which Workflow Wins?
  20. Claude Code Permissions – Security Model Explained

What Makes This Channel Win

The developer YouTube space is crowded with surface-level AI content. “I used ChatGPT to build an app” videos get views but don’t retain audiences. What retains audiences is depth, consistency, and genuine expertise.

You have all three. You built production systems with Claude Code. You understand MCP at the protocol level. You know the permission model, the skill system, the hooks, the agent architecture. That depth is rare and it is what turns casual viewers into subscribers who watch every upload.

The channel name says it all: Everything Claude Code. Not “sometimes Claude Code mixed with other AI tools.” One tool, covered completely, by someone who actually uses it. That focus is the competitive advantage.