Turn Claude Code into a Design GENIUS

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

Source video:
- Title: Turn Claude Code into a Design GENIUS
- URL: https://www.youtube.com/watch?v=fVPCbCH_c1c
- Topic: Interfaces + Open Design
- My current learning frame: Connect the Mobbin and Figma MCPs to Claude Code, build a sign-up mood board for a chosen app category, then export your own draft screen and have Claude critique it against Mobbin references and decide which feedback you actually accept.
- Why this matters: New playlist item from Kyle Skelly; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "In today's video, I'm going to show you guys how to turn Claude code into a master designer and a strategist. To do this, we're going to be connecting Mobbin using an MCP. And honestly, this workflow is..."
- 1:49 / Evidence 2: "show you guys how to connect it. So, if we head to mobbin.com/mcp, now installing it is quite easy. So, you can see here the setup. So, first you need a paid plan to Mobbin, and then you..."
- 3:59 / Evidence 3: "what seems to work best between all of these and why? We're going to get Claude code to think like a designer here. Are there any other non-fitness apps on Mobbin that could be additional source of inspiration..."
- 5:55 / Evidence 4: "feedback of what we've gathered here from Mobbin. Now, obviously, we haven't given it any specific info about our fitness app, what makes it different, what it's supposed to do, who the demographic is, but just as a..."
- 7:27 / Evidence 5: "the premium designs that are on Mobbin. All right, so here's when Claude Code tells me that my design sucks. So, it's pulled together some reference images from Mobbin and here's its detailed critique. The color system is..."

Video-aware target:
- Prompt lane: Design system
- Mechanism to extract: Extract how the video turns visual references or component systems into usable constraints for agents.
- Artifact to produce: A design-system adoption brief with source references, tokens/components, agent handoff rules, and visual QA checks.
- Artifact must include: references; tokens/components; handoff artifact; implementation rule; visual QA

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: Extract how the video turns visual references or component systems into usable constraints for agents. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A design-system adoption brief with source references, tokens/components, agent handoff rules, and visual QA checks.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Reference -> Tokens -> Components -> Usage rules -> Agent prompt context -> Implementation -> Visual QA
   - answers to these source questions: What design source is reused? | How is it translated into agent context? | What review catches generic output?
   - 3 concrete examples that apply the video idea to real agentic work, such as Figma-to-shadcn workflow; design.md brief; UI reference library remix
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: copying visuals without rules; generic generated UI; no visual QA screenshot pass
   - a checklist for the next real workflow, focused on: references, tokens, components, handoff, QA
   - one practical exercise with a clear done signal: Turn one screen reference into five constraints a coding agent must follow.
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 "Turn Claude Code into a Design GENIUS", not a generic Interfaces + Open Design essay.
- Cite transcript anchors for every claim about design context, UI generation, preview, critique, or handoff.
- 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 design inspiration; component lists without usage rules; no screenshot review.
- 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.