Claude Code Workflow for Design Teams

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

Source video:
- Title: Claude Code Workflow for Design Teams
- URL: https://www.youtube.com/watch?v=revAqLgO5VY
- Topic: Codex + Claude Workflows
- My current learning frame: Recreate Becky's approach by building a Claude Code sandbox of one flow you design, wiring real components plus a dropdown to switch between two or three iteration states, and routing a teammate to a single state for version-scoped feedback.
- Why this matters: New playlist item from Sneak Peek; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:50 / Evidence 1: "designers are going to need to start thinking and caring about as AI becomes more prominent. It's not just some recording or things that she added in. This is pulling in the code. This is what someone would..."
- 21:19 / Evidence 2: "experience that we had already solved. So what do you do in this scenario? We're building with code. We're product builders now. Just go and make something, right? And build an add on top of it. Like I..."
- 25:17 / Evidence 3: "something she just built and did. She can make this 20 times bigger, add a thousand options like whatever she wants. She's building with code now, right? >> So it's not it's not limited to the function of..."
- 28:24 / Evidence 4: "memorable. And this was also when I was starting to build out the sandbox. So that's why there's like very limited pages here, right? You'll see it's like very sparse and uh there isn't much here yet. >>..."
- 39:47 / Evidence 5: "craft as much as possible. I highly encourage design leaders to take that step a little bit deeper than just people managing and be in the tools and actually work with them. I am building stuff in cloud..."
- 44:21 / Evidence 6: "everything really manually. But as I mentioned over here, if you look at my Figma file, I went into cloud and this is what I recommend doing is if you don't know how to do this is Ashclaude,..."
- 46:00 / Evidence 7: "core foundation of that design system is what was built over here. So this is how I did it originally and you know I think it's something that people should do right from the start but I think..."

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 "Claude Code Workflow for Design Teams", 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.