Your AI Agent Doesn't Understand Design Intent

20 Apr 2026 · 1 min

Watch on YouTube

0:52

In this segment, the speaker argues that designers should work directly from their original Figma files rather than relying on vague "vibe coding" or screenshots when using AI agents for UI development. He highlights practical issues such as zoom level, cropping, and which UI elements are visible in a captured frame, noting that current computer‑vision‑based AI models can accurately measure pixels and rounding but still fail to grasp the underlying design intent. The speaker warns that these limitations make AI‑driven UI generation unreliable unless the full design context is provided.

Chapters

if you have an actual design that you're working from and you're not just quote unquote vibe coding or saying, hey, build me this thing and just hoping that it's going to grab UI somewhere, you do also have to still be in Figma. I think the next level up from chatting and vibe coding is, you know, a lot of folks probably take screenshots of either a UI component that they see in a kit somewhere online or maybe of their Figma screen directly. And what zoom are you at in Figma? You know, what? Did you crop in or out? What particular button or element is visible in that frame or not in Figma? So it can get kind of dicey if you're relying on sort of that computer vision capability of the agents and the current Frontier models. They're good, right? They're really quite good. And they can even measure pixels and figure out the rounding and all of that, but they don't necessarily understand the intention.