Case study · IPLM · AI workflow design
Human checkpoint: a designer reads, corrects and approves before anything moves on.
IPLM is a set of connected Perforce products, so three of us design across it, and I’m the lead designer on IPLM. When we moved to AI-assisted design-to-code with VS Code and Claude, the AI kept ignoring our design system.
So, with our engineers, we built a design-to-code orchestrator. It turns a product manager’s user story into a spec, wireframes and a working design sandbox, using only our real components, with designers and product managers approving along the way.
Even when we told it not to, it created new components and new wrappers instead of using what already existed in our Storybook.
+ <ButtonV2 />new component+ <TableWrapper>new wrapper <DataTable />already in Storybook+ .custom-chip { … }new stylesAn illustration, not our real code.
The environment was new, so at first we couldn’t even name the problem. We corrected the output, rewrote the spec again and again, and tried different methods to see what worked.
Connecting Figma through MCP didn’t fix it: the AI still reached for different components. It did better when we described what we wanted in writing than when we gave it visuals.
An illustration of what we saw.
I brought the problems we kept hitting. Our engineers proposed a design-to-code orchestrator, and we designed its workflow together. It combines several agents, with our rules, do’s and don’ts and the design system built in, so nobody has to write them again each time.
/design-to-codeAs an admin, I want to filter IPs by owner and status, so I can find what needs review.
An illustration: one command, then the user story.
Our rules, do’s and don’ts and “use our Storybook” live inside the orchestrator, so nobody has to repeat them in every prompt, and nobody forgets them.
An illustration.
We spent most of our time reading and approving the spec. That’s where the human in the loop sits: once the spec is right, the build needs far less rework.
Plan well, read the spec, approve it. Then build.
Once the spec is approved, it lists the components and UI it will use for the sandbox, all from Storybook, and flags anything new so a designer decides before it exists.
DataTableStorybookFilterChipStorybookDropdownStorybookOwnerBadgeNew: needs a designerAn illustration.
Before any code, it sketches wireframes. We decide the flow and behaviour there, and make corrections right in the chat, while changes are still cheap.
Move the filters into the table header.
Done. Filters now sit in the column headers.
An illustration.
If I change the spec, my product manager has to approve it, because his user stories need to match. The agent notifies him. We work in different time zones, so I log the pending approval and keep going; he reviews and comments when he’s online, and we follow up.
An illustration of how an approval moves.
When the orchestrator offers options or asks a question, we don’t just click the recommended one. We pick what’s best for the product and for what we want to achieve.
How should filters appear on this table?
An illustration of the kind of choice we make.
Rules and components are built in, and anything new is flagged, so we stopped correcting the same things.
We weren’t vibe coding anymore. A written, approved spec replaced trial-and-error prompting, so we spent far fewer tokens.
From a user story to a working sandbox, with changes made in the chat as we go.
Sandboxes use the product’s own Storybook components and behaviour.
Part of our move to AI-assisted design-to-code, which took feature delivery from 4–5 weeks to 2–2.5 weeks.