PO PJ Onori A design systems practitioner whose work centers on the mechanics of running one: adoption, governance, design tokens, and how teams train and organize around a...

“If you want to have a designer that is literally working in code and understands it, I think that goes back to having approachable technologies for them. Because the route we're heading towards is just pure vibe coding, which is going to be madness. Because what does collaboration look like when the artifact is not something that the person that's there to answer questions really understands?”

Design System Office Hours · User Experience · November 2026

“If you want to have a designer that is literally working in code and understands it, I think that goes back to having approachable technologies for them. Because the route we're heading towards is just pure vibe coding, which is going to be madness. Because what does collaboration look like when the artifact is not something that the person that's there to answer questions really understands?” — PJ Onori, Design System Office Hours

Context

Davy Fung had said designers sometimes tell Claude to recreate a component from a screenshot and get something subtly wrong, such as the navigation. Onori replied that designers who can't explain the code they shipped is a coming collaboration problem.

Transcript

Design System Office Hours Around 18:13 into the episode
PJ Onori

It's easy to forget these things, man. That's that's the thing that's hard. There's just a lot, there's a lot of variables at this point, no pun intended. So, trying to keep all this stuff at the top of your mind while we're also just, we got things we got to do. That's what's hard. No,

Davy Fung

…very good knowledge on. They might take a shortcut and say, Hey, Claude, why don't you just recreate this off the screen? And it gets it a percent there, but you'll see, oh, they recreated the navigation. Yeah, it's incorrect. So, that we do need some better skills for that sort of investigation.

PJ Onori

I was going to say, I think that goes back to developers. If you want designers working in code and actually working in code, not just saying, Hey, Claude, go do this, and then spitting out gibberish, or hey, maybe it's fine, maybe the code's fine, but the designer doesn't fully understand it. So, when you go to ask a question, they're like, I don't know, Claude did it. If we want, if you want to have a designer that is literally working in code and understands it, I think that goes back to having approachable technologies for them to actually work into it. Because what the route we're heading towards is just pure vibe coding, which is going to be madness. Because what does collaboration look like when the artifact is not something that the person that's there to answer questions really understands? I think that's a real not crisis, but it's a big pain in the ass, impending pain in the ass, if we don't address this.

Davy Fung

So, we're back at the source of truth question, right? Yeah. So, obviously, this, the code is a source of truth. There's no debate. Correct. The Figma was a reference, right? The Figma was a reference in a very specific point in time. These prototypes are also of reference, but the prototypes are…

PJ Onori

The one monkey wrench that that comes in to play is we say code is the source of truth, but if you're handling multiple platforms in your design system, then you theoretically have three sources of truth that could, you know, the work that is starting to be done within contracts. So, the things…

Davy Fung

Can you help explain the difference between contracts and schema and where they relate to each other?

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

More from Design System Office Hours