Karpathy's Skill Just Fixed Claude Code's Biggest Problem

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

Source video:
- Title: Karpathy's Skill Just Fixed Claude Code's Biggest Problem
- URL: https://www.youtube.com/watch?v=EsgUfrwsV5A
- Topic: Codex + Claude Workflows
- My current learning frame: Install the Karpathy guardrails into an existing project's CLAUDE.md, merge any conflicts with the agent's help, then augment each principle with an explicit skill-trigger path and verify the agent both honors the constraints and calls the correct skill on a sample feature and bug.
- Why this matters: New playlist item from Eric Tech; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:52 / Evidence 1: "that we have used in the past. So, with that being said, if you're interested, let's get into the video. Now, before we continue, I recently launched our school community where help you to master AI agents, automations,..."
- 2:54 / Evidence 2: "make sure that large language model here never hallucinates when writing code. Now, to put this into practice, here you can see it tells exactly how to install this. First of all, what we can do here is..."
- 4:24 / Evidence 3: "file. Like try to merge the conflicts that you have. And you can see here that this is what it recommends. After it pasted from the original car party skills repository, here's some problem that I found. For..."
- 6:06 / Evidence 4: "these four constraints every time we do something. When it asks to do I do anything, like maybe helping us to writing a blog post or helping us to generate images or helping us to writing code. It's..."
- 7:41 / Evidence 5: "but it doesn't build into the brain. But most of them are very similar, right? The same rule, the same concept is very similar between the two. But that's why my recommendation, my workflow is combining the all..."
- 9:40 / Evidence 6: "developments here. If it's like executing a written plan, well, let's do the executing plan, right? So, there's actually a lot of skills that does that. For example, if we want to do a security review, there's also..."

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 routing matrix for when to use Codex, Claude, browser checks, or manual review.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Inspect -> Plan -> Edit -> Verify -> Review -> Route
   - 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 "Karpathy's Skill Just Fixed Claude Code's Biggest Problem", not a generic Codex + Claude Workflows 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.