The bait, then the rug-pull.
A bar chart opens the lesson: Manual Coding towers over n8n, which towers over Claude Code — Time to build compressed to nearly nothing. Nate Herk then lays out a six-point agenda and promises to build a full deployed automation before the video ends. It is the two-part tutorial hook done right: visceral visual claim, then structured curriculum contract.
What the video promised.
stated at 01:30“After this video, you will have everything you need to go build your first automation in Claude Code.”delivered at 36:00
Where the time goes.
01 · Interface
VS Code + Claude Code extension install. Left pane = files, right pane = agent. Must open a project folder. Bypass permissions mode toggle. Pricing: $17/mo Pro includes Claude Code.
02 · WAT Framework
Introduces claude.md as system prompt. Walks the WAT three-layer architecture: Workflows (markdown SOPs), Agent (Claude), Tools (Python scripts). Self-improvement loop. File structure: tmp/, tools/, workflows/, .env, .gitignore.
03 · Planning in Plan Mode
Brain-dump prompt triggers plan mode. Claude web-searches, asks 4 clarifying questions, scaffolds 7 Python tools before writing code. Key lesson: plan mode prevents rework.
04 · Superpowers — MCPs and Skills
MCPs as universal USB port. Skills as dynamic instruction bundles. Installs Canvas Design skill from claudecodetemplates.com via npx. Distinguishes Projects vs Skills vs MCPs.
05 · Testing and Optimization
Full pipeline run: 30 channels, 187 videos, 6 charts, 9-slide branded PDF, Sheets export, Gmail send. Swaps PowerPoint for PDF with AIS+ logo. Self-healing loop: 2-page PDF fixed to 9-page in one feedback message.
06 · Deploy to Modal
Two Modal deploy patterns: scheduled cron (YouTube analytics every Monday 6AM) and webhook trigger (lead notification on POST). Security review before push. Modal secrets for all credentials.
Visual structure at a glance.
Named ideas worth stealing.
WAT Framework
- Workflows
- Agents
- Tools
Three-layer agentic architecture: Workflows are markdown SOPs, Agents are Claude orchestrating execution, Tools are deterministic Python scripts. Separates probabilistic reasoning from deterministic execution.
Self-Improvement Loop
- Hit error
- Read full error + trace
- Research fix
- Refactor tool
- Verify fix
- Update workflow to prevent recurrence
When Claude Code hits an error it should document the failure pattern and update the workflow file so the error never recurs.
Plan Mode Protocol
- Switch to Plan mode
- Brain-dump goal + features
- Let Claude ask clarifying questions
- Review plan
- Auto-accept or give feedback
- Execute
Using plan mode before any new automation forces Claude to think through edge cases and ask questions before writing code. Prevents the rework cycle.
Lines you could clip.
“You're not deploying the agent. You're deploying the workflow connected to tools.”
“The only way it's truly gonna click is if you get in here and do it yourself.”
“Think of an MCP server as an app store. It's like a universal micro USB port.”
“If each step is 98% accurate, you're down to 59% success after just five steps.”
How they spent the runtime.
Things they pointed at.
How they asked for the click.
“If you are looking to dive deeper into this kind of stuff and connect with over 3,000 members who are also all in on AI and building businesses with AI, definitely check out my plus community.”
Double CTA: free claude.md in School community (lower commitment) + paid AI Automation Society membership. Free asset drives email capture; paid community is the upsell.
Steal the WAT framework.
The WAT architecture is the missing scaffolding for every Claude Code project Joe already runs — name it, teach it, sell it.
- Use the WAT claude.md as the default starting point for every JoeFlow Chef batch — Workflows folder = session templates, Tools folder = MCP call wrappers.
- The bar chart open (Manual vs n8n vs Claude Code, Time to build) is a template for a JoeFlow demo: Manual typing vs JoeFlow dictation speed.
- Plan mode + clarifying questions before any new automation is the protocol to teach in the LFB Line — it is the difference between one-shot builds and rework loops.
- Modal webhook deploy maps directly to JoeFlow Chef triggers: one POST to a Modal endpoint = spin up a Claude Code agent batch.
- The self-improvement loop is a teachable mental model for MCN+ members building their first agentic stack.
- The six-point agenda slide drives 37-minute watch time — use it for the next JoeFlow demo video.
How to actually start using Claude Code.
You do not need to understand code to ship a working automation — you need a clear goal, a brain-dump prompt, and a folder structure.
- Start with VS Code and the Claude Code extension. Open a project folder. That is the whole environment.
- Write a claude.md file first — tell Claude what your project does, what tools it has, and where files live. Without it Claude is generic.
- Use plan mode for anything new. Let Claude ask questions before it builds. The questions are the most valuable part.
- Put API keys in a .env file, never in the code. Claude knows to look there.
- When something breaks, paste the full error log back and say nothing else. It will find the fix.
- Modal gives you $30 free credit — enough to run a weekly automation for months without spending a dollar.
