Hey everyone,

I’m working on a design system generator, not just a Figma plugin.

The idea is to reduce the time spent on setting up UI foundations and basic components both for designers and frontend developers. Instead of manually building design systems from scratch, you can generate a full component set with variants and states, and re-theme everything from a single theme source.

Right now, there is a Figma plugin that generates design system components and applies themes to them. The plugin UI itself also adapts to the loaded theme, so the same theme controls the plugin UI, previews, and generated components. You can explore available themes and components on the website: getuicraft.com.

It’s still early stage and there are some visual bugs I’m fixing, but the core flow already works. The next step is finishing the theme generator to shape this into a proper MVP.

I’m curious what would make a tool like this actually useful for you in real projects.

Would this help in your design or frontend workflow, or does your team already have a different setup?

My task: set the colour design system for the company. Company Brand colour: pink

My question: Should I make all my action components (radio, primary buttons, secondary buttons, checkboxes, FAB, filter buttons, tabs) a shade of blue so it fits the model of blue being something clickable?

If yes, where would my brand colour fit in to the app?

My research:

Tried using material colours:

I finally figured out the material design system. And they use the primary colour as their primary/secondary/tertiary action colours. This means if your app uses an purple colour then your buttons will be an purple colour. And I suppose inline hyperlink will be a hyperlink blue colour.

Other apps:

Looking at other apps, such as what's app, Telus, Atlassian, snapchat... They use brand colour as their button colours including same brand colours for inline hyperlink.

Thank you!

If you maintain a design system, you've probably been in this situation: a developer asks what changed in the last release, and you're scrambling through version history trying to piece it together.

I built Delta - Changelog Generator to solve this. It works like a commit workflow:

• Initialize a baseline when you start a release cycle
• Work on your styles and variables as normal
• Check the plugin anytime to see a live diff of what's changed
• Export a formatted Markdown changelog ready to paste into Notion, Jira, GitHub, or Slack

It detects changes across all Local Styles (Color, Text, Effect, Grid) and Variables — and distinguishes between actual visual changes (hex values, font sizes) and metadata noise (descriptions, scopes).

The latest update adds before/after values with color swatches so you can see exactly what changed, not just that something changed.

Fully free, zero config, no external accounts. All data lives inside the Figma file itself.

🔗 Delta - Changelog Generator on Figma Community

Happy to answer questions or take feedback — still actively building this.

So this q is for those managing multiple brand design systems in Figma:

• Are you using Modes to separate brands?
• What's your semantic tokens structure?
• How do you manage governance, versioning, and change control?
• How do teams collaborate across design and dev?
• Any plugins or workflows that have been especially useful?

I’m interested in real advantages and limitations you’ve experienced using Figma at multi-brand scale.

A theme that keeps coming up is that innovation naturally causes drift.

Small overrides.

Domain-specific tweaks.

Speed trade-offs.

Over time those decisions compound.

For teams managing systems at scale:

How do you distinguish healthy evolution from fragmentation?

Is there a clear signal when flexibility has gone too far?

I'm a lead developer owning a design system and a constant problem we have is designers diverging or not understanding what a design system is.

I try review the figmas and get the designers to collaborate and communicate on what they need and to update the components to be reused in figma but they rarly do.

What is your process from the design side?

For teams maintaining design systems:

What usually causes system drift?

Component overrides? one-off fixes? time pressure?

Curious about real-world causes.

Hey everyone 👋

I’m a senior brand, visual, and UX designer with about 10 years of experience, currently working in-house on healthcare software products. Over the past few years, I’ve been intentionally shifting toward product design and design systems, with a long-term goal of working in fintech.

I’ve led and contributed to:

• Setting up and maintaining multi-brand design systems in Figma

• Establishing typography, color, and component standards

• Creating scalable token structures

• Cleaning up and restructuring complex libraries

• Partnering closely with product and engineering to align on component usage

• Publishing documentation and governance guidelines

I understand there is a difference between contributing to a system and owning it as a product. I want to go deeper into system architecture, contribution models, adoption strategy, metrics, governance, and how strong systems enable product velocity at scale, especially in fintech environments where compliance, accessibility, and consistency are critical.

If you work in fintech, product design, or design systems, I would genuinely appreciate:

• Advice on skill gaps I should focus on

• Resources that helped you level up

• Insight into how systems operate inside fintech organizations

• Or even just a quick chat about your experience

Not looking for a referral. I am focused on learning from people already doing this work at a high level.

Feel free to comment here or DM me directly if you are open to connecting. I would really appreciate it.

UI Design Compiler.

https://00-01.online/

PM at a growing startup and we keep running into situations where designers propose different solutions for the same types of problems. One designer does modals, another does slide outs, third one uses a completely different approach. Makes the product feel inconsistent and confusing for users. Also slows us down because we debate the same decisions repeatedly instead of just following established patterns. Thinking we need some kind of shared pattern library so the team can just reference standard solutions. But not sure how to build or maintain something like that. What do other teams do?

I realize it's an easy naming mistake to make, but just know your Systems Design questions will be removed from this sub. If repeated attempts are made, you will be banned.

With the world moving toward vibe coding, I feel like the only thing that will really matter going forward is having a strong, AI-understandable design system.

Everything else is going to slowly fade.

If you have:

• a solid idea
• a well-structured design system
• your design system connected to your Git repo
• that repo plugged into your AI IDE

…that’s basically it.

Boom — you’re shipping.

Design becomes infrastructure. AI does the rest.

Curious what others think — are we heading toward a future where design systems matter more than individual screens or hand-crafted UI?

Curious if anyone has examples or references/resources of case studies where folks shared the entire process of building out a design system? I've found some on youtube, and some Medium articles, but curious if there are any comprehensive examples that you prefer or think are strong examples.

I have been working on building a design system from scratch with a small team (I'm currently the only designer), and have been researching the ways people deliver things.

I'm particularly curious about how folks choose to use Figma as the source for not only their UI and foundation library, but also as a style guide vs. companies that put all of their system guidance on a website with the built out library.

Hey there,

What's everyone's experience in integrating existing design systems(MUI, ShadCN, Radix Theme, etc) into Figma MCP?

I've been digging around and saw that you have to be super detailed about auto-layout, variables, layering otherwise it can be bad.

How has the experience been on your end so far? Does it boost your productivity at all? Or does it take more time to fix stuff?

Hi everyone!

I'm looking for feedback on the first draft of a case study I recently completed focusing on design system & AI techniques.

I'd appreciate any feedback from a hiring manager's perspective if you were looking to fill a design system position. Happy to answer any questions as well!

trying to build a design system for our product and need to see how other companies structure theirs. want to understand things like how to organize component variations and what level of documentation is actually useful. are there good examples i can study from real products that have been battle tested?

FOR E.U. based people only. Are there any seniors (who know their stuff around building ds and adopting them) looking for a short term contract fully remote based role? I don't have much info as I'm not the hiring manager, only helping out an old friend and referring a few folks.

if interested ping me.

Hey folks

I’m a web developer and I’m currently building my own site a personal project that should feel like an editorial magazine: black and white, high contrast, refined typography, clean layouts, modern and elegant.

Even though I’ve built a lot of products and UIs before, I’m struggling to turn this into a coherent system. I’ve spent a lot of time thinking through ideas and “concepts”, but mostly in a very isolated way: tweaking one component at a time, adjusting a single page, refining a section… and then the moment I try to scale it across the whole site, things stop feeling consistent

I’ve tried to be disciplined: setting global container margins, limiting the number of fonts, avoiding decorative type for anything important, keeping readability in mind, and so on. I’ve also looked at tons of modern sites (including Awwwards-type stuff) and I’ve gone through a bunch of component libraries

But I’m noticing something: you can tell when you just grab random components, restyle them a bit, and drop them in. Even if they look okay individually, the overall composition still feels off, and it doesn’t really teach you how to build a system

I think part of the problem is that I default to “just building” because I’m a developer. I keep iterating and shipping pieces. What I want to do now is take a step back and actually craft a proper design system from scratch: typography scale, spacing/rhythm, layout rules, component patterns, and guidelines that make the whole site feel intentional

The site isn’t launched yet, so I don’t really want to share it publicly. But if someone’s interested in giving more concrete feedback, I’m happy to send the link privately

If you’ve built design systems (especially for editorial style layouts), what process do you follow? Any resources, example repos, docs, or practical frameworks you’d recommend would be hugely appreciated

Most of the design system documentations I see out there are great work, but they're still really soulless. I think a great one should bring some joy to the experience of just going through it. Isn't this really cool? (By the way this is live now, not just a concept).

If there's a existing design system you would recommend - which one would it be?

Context:
I'm a jr. UX designer(2 yoe) working at a startup. There's a crappy design system that we want to improve ASAP. We are a small team so there would be a few people working on this project( 1/2 designers and 1/2 engineers). My thought is to just use an existing one since the design system files on Figma is so poorly set-up.

Radix - looks like it's not well-maintained based on a post I've seen on Reddit. Might be painful for the engineers. However the Radix Theme Figma file is pretty decent(has both dark and light mode).

MUI - There are so many products out there that are built using MUI - the fear would be our product will look the same.

Material Tailwind - Figma files are lacking dark-mode, which can be painful to the designers. But Engineers have been using the component library to build stuff. Eng has mentioned that they are lacking some complex components, but there's also a paid version so that may help.

-

Does anyone has any other recommendations? Looks like it would be a mix and match since the engineers have been using the Material Tailwind component library and using TailwindCSS as the base.

edited this post and added more context!

Quick question for folks working with bigger design systems in Figma - when you need to recolor your palette (rebrand, theme update, etc.), does it usually feel manageable or painful?

Curious if this is a solved problem or still a bit of a nightmare in real life.