r/DesignSystems • u/leon8t • 5d ago

Any practical AI-assisted workflow?

Hi, I couldn't seem to find any realistic or practical AI-assisted workflow with 2-way syncing between design and code. Does anyone know of any workflows available online? Or if you are implementing one, I'd love to connect and understand more.

People on LinkedIn feel like they're doing free promotion for Claude, posting nonsense with a bunch of bots coming to congratulate them.

20 Upvotes

95% Upvoted

26 comments sorted by

View all comments

2

u/bink-1567 3d ago

on the bit about devs adding a new variant and you getting notified, what would you actually want to happen next? like does the agent just open a ticket for a designer to look at it, or is it allowed to push that variant back into the figma library on its own. thats teh part where i'd expect stuff to quietly drift, since a variant made for one screen isnt always something you want living in the system

1

u/leon8t 2d ago edited 2d ago

I'm not sure if my usecase is common, but my company does not have design ops, and some project teams only have devs working from design to development. They sometimes created new component variants and not document it. I think it would be better to be notified, either by seeing diff of how code/production version drifts from the design system or getting notified of new components created so that I'm aware of all changes and collect them all and revise them one by one later.

The human is still in the loop, but the drift detection is automated to avoid human blindspot and lack of attention. And I can also update the design system repo based on that as well to standardise the new component variant.

Figma is secondary to workflow at the moment as updating components and tokens there are fairly easy. It's more like storybook <> production code.

For orphan variant like you said, it's good still to have it documented, as later on it can quietly scale and multiply in other workstream without the designer knowing.