My design-to-code workflow just became a native Figma feature. A few weeks ago I wrote about moving between Figma and code as one connected loop instead of a handoff. Then I watched Config 2026, and Figma basically built that loop into the canvas itself. Code, motion, and AI, all living in the same file as the design. My first reaction was excitement. My second was something quieter. Because here's the thing these announcements don't say out loud: putting code and design in one place doesn't automatically make anything clearer. The tools got more powerful. The hard part didn't move. You can now generate a working component in seconds. But someone still has to decide if it's the right component. You can run real code on the canvas. But someone still has to know which version to keep and which to quietly delete. The canvas isn't the thing that creates clarity. The thinking is. What I love about where this is heading is that it finally puts design and build in the same conversation. What I'd gently remind everyone is that a shared file still needs a clear head behind it. Better tools raise the ceiling. They don't replace the judgment that gets you there. What's the skill you think matters more now, not less, because of all this?