How Claude Code’s lead designer builds with AI

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

Source video:
- Title: How Claude Code’s lead designer builds with AI
- URL: https://www.youtube.com/watch?v=hKeDfupbA4U
- Topic: Codex + Claude Workflows
- My current learning frame: On an open-source repo like Excalidraw, start a Claude work tree, have Claude build and run a /prototype skill to generate 5 options for a small feature, pick one, and let Claude verify and open a PR with a screenshot — practicing the full prompt-to-PR loop while you stay the design decision-maker.
- Why this matters: New playlist item from Dive Club 🤿; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 1:11 / Evidence 1: "does anyone know what this is? All right. So, work trees are pretty complicated and generally I don't think you need to know what they are. But all you need to know is that if you have a..."
- 3:10 / Evidence 2: "/prototype skill. I asked Claude to build this. You could build in like 2 seconds. All it does is get Claude to generate uh n number of options default to five of a different implementation of a feature."
- 5:43 / Evidence 3: "going to show all of you today. So the first is that Claude tragically and most LLMs are not good at design yet. So what this means is that you should still very much be in the loop..."
- 7:15 / Evidence 4: "Claude in the web. Does everyone have this internally at their teams or companies? Uh you might have it with your own internal infrastructure, but I have like claude in the cloud or cloud in the web as..."
- 8:52 / Evidence 5: "changes, it's just a really good way to like do a little bit of a hygiene check. uh simplify and code review are internal to our repository but I guarantee you if your engineering team is using AI..."
- 11:12 / Evidence 6: "like not just the first step but like the next step the next step the next step after that like you want to be pushing it so far that it's like building the actual end product and I..."

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 "How Claude Code’s lead designer builds with AI", 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.