I Stopped Using Figma MCP

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

Source video:
- Title: I Stopped Using Figma MCP
- URL: https://www.youtube.com/watch?v=0dj3_i849a4
- Topic: Interfaces + Open Design
- My current learning frame: Set up the HTML.to.design custom connector in Claude, generate a dashboard from a design.md spec, transfer it into a shared Figma file via the MCP prompt, and confirm the result actually contains working variables, styles, and auto layouts.
- Why this matters: New playlist item from Sergei Chyrkov; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 1:09 / Evidence 1: "design open already so you can go to claude.ai/design to launch it. You need to launch it in your browser. And here I will use the prototype tab and for my project name I'll just call it design..."
- 4:07 / Evidence 2: "super popular and but now they released a new feature which is the MCP uh, and it allows you to connect your agents um, with the plugin and with Figma. Uh, basically um, uh, will connect the Claude..."
- 5:52 / Evidence 3: "now because we're in Claude Design, so that's why it's easier for me to do it from the browser. But, you can use the app, of course. Again, so it's it's it is the same thing. So, we..."
- 7:38 / Evidence 4: "use the plugin. For example, we can um, use the web extension, or we can use the web clipper. For example, we can just paste in the URL and get the designs into our Figma file straight from..."
- 9:51 / Evidence 5: "use hyperlinks and HTML layers names. Let's use this as well because it's going to be easier for us later on. Uh if we want to transfer it to call back to call, for example, so it will..."
- 12:09 / Evidence 6: "and the layout is 1440 for the desktop. Of course, you can create another one for mobile version. All right. So, for this part, I think it's really good. Uh we got the designs transferred from the code..."
- 15:10 / Evidence 7: "project, we didn't do that. Um the next thing is what you can do, you can use AI to create variables from these designs if you need them. Uh and after this, you can, you know, like play..."

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 UI critique sheet for judging whether an AI interface improves control.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Canvas -> Artifact -> Preview -> Feedback -> Iteration
   - 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 "I Stopped Using Figma MCP", not a generic Interfaces + Open Design 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.