Vibe coding is changing when I use Figma
by•
I’m a product designer, and vibe coding has changed where Figma fits into my process.
I still use simple prototypes when I need to review the overall flow and context with the team.
But when I actually want to test an idea, I’m increasingly going straight to building it with AI instead.
A working version lets me test things that are hard to judge in a static design, especially interactions and how the whole flow feels when you actually use it.
So Figma hasn’t disappeared from my process, but its role is starting to feel different.
For other designers who vibe code, has Figma’s role changed for you too? What do you still prefer to figure out in Figma before you start building?
23 views
Replies
One thing I’d still prefer to work out in Figma is the information architecture. I find it easier to compare different structures visually before getting distracted by implementation details.
@federicoportela Do you still create detailed component designs in Figma before vibe coding , or are you mostly using it for early flows and team alignment now? I’m curious where you draw that line.
the intresting change for me is that prototyping no longer has to mean stopping at a simulated interface. Being able to test a real interaction earlier could make the design process much more iterative.
An agent generated what looked like a clean UI fix and a passing test. I reverted the patch to check it, and the test stayed green. The agent had written an assertion that only checked if the component mounted, completely bypassing the broken state.
I’ve found the same shift: once the working build is in hand, the key is testing states and transitions rather than polishing a static frame. I keep the design artifact as a reference, then make the desktop app’s real behavior the source of truth—especially on Linux, where native input and windowing details matter. Figma still helps me communicate intent; it just isn’t the finish line.