Stop Watching Tutorials - Build These 4 Claude Projects to 10x Output

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: Stop Watching Tutorials - Build These 4 Claude Projects to 10x Output
- URL: https://www.youtube.com/watch?v=IiZ5HRaeX4s
- Topic: Creative Automation
- My current learning frame: Build the project-four internal operating system: create knowledge/skills/projects folders with a root claude.md, then implement and test a /improve system skill by refining one email draft and confirming the next draft inherits the feedback.
- Why this matters: New playlist item from Austin Marchese; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:12 / Evidence 1: "know your goals and where you want to go with your career. The key phrase here is the interview me part which tells Claude to pull context from you instead of guessing or making assumptions. And the pro..."
- 2:08 / Evidence 2: "stress how valuable this one project is, but that's just the first of four Claude Code projects you need to do, whether you're technical or not. And I promise if you do all four of these, you will..."
- 4:48 / Evidence 3: "want to plan before you build anything complex. So step back, breathe, and think about what you need Claude to build before it actually builds it. The key here is a planning prompt. This is similar to project..."
- 7:11 / Evidence 4: "these websites and they have a bunch of inspirations already pre-curated so that you could just find something that you love. Step three is create a NodeJS app with Claude code. So what you want to do is..."
- 8:45 / Evidence 5: "to awesome case.te. Then in your Claude code session, you can send this prompt and that's that. Claude handles the deploy and it's really that simple. And if anything fails, Hostinger's AI troubleshooter will scan the logs and..."
- 11:01 / Evidence 6: "to use the folders, so you don't have to reexplain every time you open a new session. It's like teaching Claude how to use the system. Step two is you want to build a slashimprove system skill. This..."
- 13:00 / Evidence 7: "anybody can start using this system. Here's a prompt you can use to help you get started with this. The key with this internal operating system is that you create a foundation that can build up over time."

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A creative workflow board with critique criteria and review checkpoints.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Brief -> Source -> Generation -> Selection -> Edit -> Taste Review
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "Stop Watching Tutorials - Build These 4 Claude Projects to 10x Output", not a generic Creative Automation essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.