The 5-Tool Fix for Claude Code's Worst Habits

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

Source video:
- Title: The 5-Tool Fix for Claude Code's Worst Habits
- URL: https://www.youtube.com/watch?v=hqcZZuvBUSY
- Topic: Creative Automation
- My current learning frame: On one real project, layer the five tools in sequence — generate Intent Layers navigation, run DeepSecure and the Vercel best-practices audit, wire up Agent Memory to persist the findings, then launch Claude with Chrome (claude --d-chrome) to make a visual change and let it iterate in the browser until it verifies the result looks right.
- Why this matters: New playlist item from Sean Kochel; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:25 / Evidence 1: "hierarchical agent.mmarkdown files so that agents can navigate your code bases more effectively. And so the way that this works is it creates a root index file called agents.mmarkdown or inside of your clawed markdown file. Now inside..."
- 1:55 / Evidence 2: "pointers to deeper documentation inside of our codebase. So, for example, if we're working on something that deals with our app routes and our APIs, instead of Claude having to read all of the files in chunks and..."
- 4:58 / Evidence 3: "of the conventions inside of your project. But the uncomfortable truth is that language models are still pattern followers. So what if in the course of all of this, we actually have a bad pattern in place? For..."
- 8:09 / Evidence 4: "of our app that we're working on in this project. It's possible that someone could try to prompt inject the system. So when we have this function that we call called build system prompt, it basically takes the..."
- 10:01 / Evidence 5: "you are building specifically from a performance perspective. So we're going to come through and we are going to run this command skills ad versel labs agent skills and then we can come down like I said and..."
- 12:53 / Evidence 6: "How do we make sure it actually gets carried across future sessions? Well, the answer to that is having a persistent memory system for your coding agent. And so, one tool that I found really valuable for this..."
- 16:29 / Evidence 7: "if you're not documenting those things after each session. And a tool like this keeps those findings 100% searchable over time. But here's a question nobody really asks. With some of these tools, we're writing better code. Maybe..."

Video-aware target:
- Prompt lane: Coding-agent workflow
- Mechanism to extract: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review.
- Artifact to produce: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
- Artifact must include: task class; agent/tool choice; context packet; verification step; handoff/recovery rule

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, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step
   - answers to these source questions: What workflow pain is being solved? | What exact coordination mechanism is shown? | What evidence proves it changes the work?
   - 3 concrete examples that apply the video idea to real agentic work, such as rate-limit routing; browser verification after a UI edit; long-running /goal session review
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: choosing tools by hype; losing context across agents; letting parallel sessions become invisible
   - a checklist for the next real workflow, focused on: routing decision, context portability, verification, handoff summary
   - one practical exercise with a clear done signal: Route three recent tasks across Codex, Claude, browser checks, and manual review with a reason for each.
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 "The 5-Tool Fix for Claude Code's Worst Habits", not a generic Creative Automation essay.
- Each workflow rule must point to a timestamped claim or demo moment, then state what remains unproven.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic Codex vs Claude comparison; feature lists without task routing; claims that ignore limits or recovery.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.