Claude's New /design Skill Just Killed Figma! (Tutorial)

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

Source video:
- Title: Claude's New /design Skill Just Killed Figma! (Tutorial)
- URL: https://www.youtube.com/watch?v=IHPcOvVU4PM
- Topic: Interfaces + Open Design
- My current learning frame: Generate several artboards for a small web page, branch the strongest concept, refine its properties by hand, save it, and launch the named design locally to verify both visuals and interactions.
- Why this matters: New playlist item from Brendan Jowett; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:16 / Evidence 1: "to easily view and iterate on the design of anything we are building inside Clod code. So instead of telling Clod code to make changes, waiting for it to write that code, then viewing it in your browser,..."
- 1:57 / Evidence 2: "here. I can even go into it and click these buttons and it's all very interactive. But one of the big downsides of this is how we can actually take one of these designs and get it working..."
- 3:39 / Evidence 3: "built in a folder and you are just starting from scratch, you can just go ahead, type {slash} design, and then tell it to design you a website or a web app, and it's obviously going to get..."
- 6:07 / Evidence 4: "with the sort of blue styling instead. And then we've got this styling right here which is sort of just slightly modified the location of the buttons below it. But really just trying to prove the point that..."
- 7:52 / Evidence 5: "through and manually do any of this ourselves?" It's because I do think that the design process is still quicker if we just quickly update things ourselves. For example, I can now scroll down, click onto this blue..."
- 10:51 / Evidence 6: "Claude design. We'd have to be uploading it into our instance of Claude code here. It would have to then understand exactly what this design is and only then would it be able to then locally host it."

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 "Claude's New /design Skill Just Killed Figma! (Tutorial)", 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.