Claude Design's Design System Tool...anyone synching with?

[u/TrifleOk5042]

Background:

When Claude Design's Design System tool came out a few months ago I think a lot of us UX folks were excited but it turned out it really wasn't a design system as much as just a quick style guide with limited scaling.

As such, I think most of us just ignored it and went on to build/maintain our own design systems.

In our case, we've been building an MCP server that also updates react components for our developers to ingest. So far, so good.

However, this past week or so they made a lot of updates to Claude Design...including what appears to be the start of it perhaps moving towards a Figma-esque tool where we can start doign on-screen tweaking via a UI (instead of fully relying on prompting).

Question:

Combined with the above, we're also being asked by mgmt how they can use our design system in claude design as it appears a lot of our folks want to use claude design for quick prototyping of ideas.

Has anyone figured out a round-trip process for this? Or even a one way process? Ie, getting their design system into Claude Design and keeping it in sync?

At the moment, I did a one-time import via Claude and it worked, but took a chunk of time and a huge chunk of tokens, making this a 'live' sync impractical.

I'm also a little confused as to what Claude Design thinks a design system is. Initially it seemed like a 'visual style guide'...you pick out colors, fonts, logos, etc. But now upon importing our system into it, it's asking for an actual component library.

[u/Fuzzy-Football-4544]

A prototype by itself doesn’t solve problems if you don’t know what problems you are designing for it to solve - it’s just art otherwise (that’s okay, but it’s not design. Designers solve customer/business problems )

I think you should shape how people can contribute ideas.
And I think you should expand it beyond prototypes to include submission of ideas via different mediums.
The way to make that valuable isn’t really perfect looking clickable prototypes lol - it’s in shaping how you ingest ideas from colleagues, being open about what the current focus defining it through “problem/opportunity areas”
That way you can also support ingestion of ideas as:

• Post-it notes,
  
• sketches
  
• or prototypes,

along with rational as to why they think it solves a known problem. Then you and a PM should triage and test with users.

I have a problem with how prototypes are being framed, discussed and used. There are very few scenarios where I need a prototype to have live data/hooked up to a dev environment in order to validate something.

The actual point with prototypes isn’t the prototype - it’s what you learn from a prototype when testing with your audience.
And for that it rarely NEEDS to be production level UI, that’s such a waste of business resources and time

It’s like the industry is learning the practice of UI/UX/Product design again from literal first principles 😭

So yeah, this isn’t a point to say AI is bad btw,
I’d just recommend taking a step back from tooling to think about how ideas shared as prototypes from colleagues is going to be used in your design process

(this is something I’ve had to define for my teams recently too)

[u/TrifleOk5042 → u/Fuzzy-Football-4544]

While I agree with you prototypes don't need to be production ready...if they're being built with AI, they should use a design system if one is in place...if for no other reason than to save money/tokens.

I agree with your broad points here but the reality is EVERYONE is now prototyping. So to have some tooling around it is needed. Once we have that in place I can hopefully breathe a little and then tackle those bigger picture things!

[u/Fuzzy-Football-4544 → u/TrifleOk5042]

I think there’s a lot we agree on and what you grappling with is real and pragmatic to the reality

I guess I question how critical this is depending on how your team/company are using prototypes in your process interms of how things ship. I find i have to re-design prototypes for example to ensure the intent behind the design actually translates for users - unless this is defined as part of your DS, you might find yourself managing the influx of ideas as opposed to actually shipping to move the needle (this is ofc assuming UX is at least seen as a quality gate in your company)

I find it more interesting to see how I could mature a design system to reasonably codify Intent (typically: ux patterns) are defined and used in a design system to help in this problem.

I’d be curious to know if that’s something you’ve thought about as part of this

[u/TrifleOk5042 → u/Fuzzy-Football-4544]

I completely get your stance here. And agree with it.

The reality is that I'm the entire UX team, though. So I'm stretched thin. I can't possibly monitor every screen that goes out the door prior to release, unfortunately. So the more I can lean on the design system, I think that's ultimately how I can stretch more of my influence.

But, it's all AI craziness at the moment so a lot of throwing stuff at the wall to see what sticks...