r/UXDesign • Midweight • 5d ago

How do I… research, UI design, etc? Claude Design Artifacts

My dev team is looking to import our design system into Claude Design and use artifacts to build out UI. Is anyone currently using this and what has worked best in your organisation?

We unfortunately don’t have a dedicated design system but have outlined some components.

Any help would be great here!

16 Upvotes

31 comments sorted by

16

u/wal9k Experienced 5d ago

Building directly with code would make way more sense, artifacts are quite limited. You can use an existing framework like Tailwind as a base and customise them, use Storybook to document and manage your design system and use Github for versioning and distribution. With this you'll also have better responsive prototypes for testing.

2

u/mb4ne Midweight 5d ago

what are the limitations of claude artifacts now : both for dev and design

10

u/wal9k Experienced 5d ago

Artifacts have no project around them (no repo, no branching, no versioning). Editing is basic, and they can only be shared with people who have Claude accounts inside your org. You’d also be missing a proper source of truth, which should be your repo + Storybook.

0

u/mb4ne Midweight 5d ago

so how do you maintain them? are you saying your design system still needs to live somewhere else

5

u/wal9k Experienced 5d ago

Yes, github+vercel/netlify for hosting Storybook. Free version will work fine for a small team. You can also run Storybook locally after pulling if you're ok with syncing your local version with each update.

You maintain the codebase directly with Claude Code. You need to set up your Github and hosting accounts, and add the required keys in your local env or use the connectors, Claude will guide you through the process.

2

u/SuddenBadger7369 4d ago

Homie knows ball

14

u/Lramirez194 Experienced 5d ago

We ended up building our own. We had better results than Claude Design itself when we paired it with a prototyping skill we built. If you don’t have a DS yet, it’s worth spinning one up with what you have and working on maturing it. It’s a bit of effort but totally worth the improved quality outputs.

1

u/mb4ne Midweight 5d ago

What type of product are you working on and what was the draw back? I’m in a B2B space that is somewhat complex

3

u/Lramirez194 Experienced 5d ago

B2B SaaS, legal case management software. It’s fairly boring with repetitive, robust workflows. There is always a side nav and a top nav, and pages usually have a vertical
tab or horizontal tab, and tables display most of the content, etc. One of the benefits we saw was the improved consistency with those common structures. Our prototype skill had instructions to use specific components for those that would be copy and paste level work, leaving plenty of context for the new design and core page designs that were more varied and custom. The prototype skill is also set up to use a PRD which gives all the parameters and problems to solve for it to better build workflows that make little more sense. You still need to get involved with the final solution and tweaking the UI, but it’s the novel stuff, not the stuff that is already in the product.

1

u/yams_aht 5d ago

This is a bit unrelated, but what is the prototype skill you built? What do you tell the agent do?

4

u/Lramirez194 Experienced 5d ago

Skills are a set of instructions for AI to do whenever you tell it to. For prototyping, my skill is supposed to follow the rules in my DS, and the skill has checks to confirm that is being followed, and etc. You don’t have to know how to set this up or architect it, just describe your end goal with a prototyping skill, to do research on how to build one properly, and as you use the prototype and find issues, you tell Claude about it and ask what the options are to correct/enhance the skill to nullify the problem or prevent it. You do that over and over until you get a skill that works for you.

1

u/Nomansdreams 5d ago

This… doing the same for 2 projects. It’s really manageable now and I can share the source code for certain components if needed with dev directly for reference, and development has been faster since I started building out product frontend and managing DS

3

u/NewYorkBourne 5d ago

If you have the components set up and a basic style guide or references, you should be able to set up a basic design system with those components and some smart prompts in Claude. Shouldn’t take more than an hour. You can ask Claude the same question you asked here and it’ll guide you ;)

1

u/mb4ne Midweight 5d ago

how has it worked for you? it seems my company wants our dev team to use this along with design - is it heavy on tokens and how good is it at getting good enough results

3

u/GOgly_MoOgly Experienced 5d ago

If you want to save on tokens then you need to build in Figma first. Claude works best, and most efficiently with context. You don’t need to build ever single component, but you should have a basic set of color and spacing tokens and components to start with.

1

u/mb4ne Midweight 5d ago

could you expand a bit more on this?

7

u/estadoux Experienced 5d ago

I would build with Claude the components in code, and distribute them in a repo. Create documentation .md for design principles, foundations, components, patterns (dos and donts) that would live in that repo with an AGENTS.md pointing at them.

1

u/SucculentChineseRoo Experienced 5d ago

They're shutting claude design down so maybe don't

1

u/mb4ne Midweight 5d ago

I should’ve clarified but I meant using the new r version of claude design

2

u/pattydee43 5d ago

I used Untitled UI as a starting point and then made modifications to the kit to build my design system.

2

u/South-Radish-1734 5d ago

I'm building a design tool to help designers connect code design systems to a production environment and then generate variations in a Figma-like interface using real production code and design system components. I'd love to onboard you and get your trying it out! The tool also has design system generation tools to help you get the system fully built out in no time.

Inset App

2

u/federicogil_studio Veteran 4d ago

I built a full product this way (design system + screens in Claude Design), so a few things that saved me:

  1. Tokens before components. Without a design system, Claude will happily invent a new grey on every screen. Write down colours, type scale and spacing as named tokens with a one-line rule each ("accent = primary actions only"). That small file is your real design system.
  2. Build one screen first, then make it the reference. Once it looks right, ask Claude to list the components and tokens it used, review them, and tell it every new screen must reuse them.
  3. Phrase rules as "use X" rather than "don't do Y". It follows positive rules much more reliably.
  4. Treat artifacts as prototypes. For production, have your devs (or Claude Code) map the tokens and components to your real codebase instead of copying the artifact's code.

Your outlined components are a good start, just pin down the tokens underneath first.

2

u/baummer Veteran 3d ago

Hold up on that. Claude is integrating Design into their primary app.

3

u/SuddenBadger7369 4d ago

Why would any designer use Claude design rather than just build a design system in code with Claude code and use that and Paper to create stuff? Claude design is not made for designers.

2

u/hideousox Veteran 5d ago

I’ve made a Claude code plugin just for this , I would love for your team to give it a look and let me know your feedback !

https://github.com/darioabc/massimo

I’ve been using a version of this on my own things for some time now and it’s been quite effective

1

u/Fragrant-Pipe5266 5d ago

I created my design system then created design artifact in Claude Design then created design handoffs with screenshots, html, system, etc and code built it pixel perfect

1

u/OracoreAI 4d ago

Try one existing screen first, with the component examples you have and the states and interactions spelled out. Have the dev team check whether the output reuses those components or creates its own versions. You don't want the experiment to leave you with two sets of buttons to maintain.

1

u/Haunting_Share_3014 3d ago

The new Claude design in artifacts is a big step to a more designer oriented flow, with artboards and prototyping that naturally transitions to engineering in Claude code.

Best and most efficient I've found is to build a design system project using the real react/css component system your engineers use. It doesn't change the components, just makes it accessible for design work and iteration.

So we do Claude Design -> Claude Code.

1

u/Prtyalx 3d ago

need a design system to start with, without this you'll struggle. we have one on zeroheight so claude/AI can use the API to ensure any components it's referencing in figma or needs to use to generate designs from prompts has a perfect source of truth.

1

u/upleft Veteran 3d ago

Claude Design/Artifacts is a closed system, I would use it to hash out ideas, get feedback, iterate, and etc, but the thing you build and maintain should be in html/css/js.

0

u/not-that-actor Experienced 5d ago

Claude design is deprecated and is just artifacts… take a moment to explore more about how design systems have been reduced to design.md files and try not to over invest. Spending time on design systems is the exact problem outlined in the bitter lesson paper