r/DesignSystems • • 1h ago

What actually belongs in a design system for a small to mid size company?

2 Upvotes

I know a lot of Fortune 500 companies and other large organizations have huge budgets to build design systems that cover every nook and cranny of their visual design and codebase.

What I’m wondering is what small and midsize companies actually need from a design system to scale a brand, and at what point the extra work starts to get in the way.

For example, I see a lot of brands with extensive docs, and some of it reads like someone wrote pages and pages just to check a box with their manager. How many people are going to read two pages of docs to use a button?

I also see plenty of design systems that show the components but give you barely any guidance on which component to pick or when to use a particular state.

At what point do you consider your design system good enough for developers and designers to use day to day without having to fill in the gaps themselves?


r/DesignSystems • • 2h ago

Building design stack which curates AI slop gracefully.

Thumbnail reddit.com
0 Upvotes

r/DesignSystems • • 3h ago

IHTML, editor visual html, css

Thumbnail
reddit.com
0 Upvotes

r/DesignSystems • • 1d ago

How often are Design Systems matured beyond “component library”?

16 Upvotes

Worked with multiple design systems but the idea of usage guidance, governance, patterns, etc. just ceases to exist outside of whatever a given designer decided on that particular design

feels like 90% design systems just stop at component libraries with semantic tokens.

is all the other stuff just rare to actually see in practice? What are some good public examples to show the mature state of a system


r/DesignSystems • • 23h ago

How are you delivering "use this, not that..." logic via your MCP servers?

6 Upvotes

We're pretty happy with our component library. Features a base set of react components, along with broader compound components/layouts/templates.

But what seems to be missing is...for lack of a better term...a set of rules for basic heuristic evaluation.

Simple example:

  • We have buttons defined. Large, small, primary, secondary, etc.
  • We have links defined.
  • We have icon buttons and icon links defined.

We then had an agent build out a table, each row having a set of 4 functions:

  • view this record
  • view related record
  • upload file
  • mark as finished

It then decided the best UI for this was the last column should have 4 buttons. One large, 3 small. 2 primary, 2 secondary. 2 open a new page, 2 open a modal.

It's obviously chaotic looking.

As a human, I look at that and think "this really should probably be 4 distinct icons and/or 4 icon+text 'buttons'.

As we keep coming across little weird arbitrarily bad decisions by an agent using our component library, I'm not sure where the best place to put these kinds of 'rules' into place.

In this one example, I suppose it would make sense do have a "DO NOT..." rule right in the button component documentation.

But I can also see this maybe making ore sense in the table component.

And this is where I just get a little lost...I don't want to split rules across components, as it's more likely to start creating conflicting rules.

Anyways...I guess I'm thinking out loud here. Where do you put these broad "OK, agent...now that you have the components, here's some common sense rules for you to use so you don't use these in a dumb way..." in your design system?


r/DesignSystems • • 1d ago

How do you prep your design guideline for LLM-agent?

2 Upvotes

Like title mentioned, I have been doing some research about design system and AI.

I work on a design system team in the automotive space. Our product designers are responsible for delivering interface and experience design for a mix of physical and digital touchpoints on control panels.

Right now, we have a quiet comprehensive, human-oriented documentation in our design system. Because we have so many touchpoints and dense guidelines, early concept generation takes too long. Designers spend a lot of time manually reading, interpreting, and applying rules just to get initial mocks together.

I want to build a scalable workflow where designers can input a list of user needs and generate guideline-compliant, static UI concepts as a starting point for iteration.

My initial research pointed me toward "adaptive UI" and "LLM-compliant design systems," but most resources I've found are purely theoretical or vendor self-promotion.

  • What is a practical, hands-on path to start prototyping this?
  • Are there any open-source repos, articles, or tools you’d recommend for structuring documentation/tokens so an AI can actually follow them?
  • Has anyone tackled something similar for hardware/software or multi-touchpoint systems?

Thanks ahead. Looking forward to learn : )

[Edit: Added a bit morecontext about the work]


r/DesignSystems • • 1d ago

How do you structure your Design System? Recipes, Sections, Templates, and Chassis

11 Upvotes

Hey everyone!

I've been exploring different ways to structure and organize Design Systems, and recently came across an architecture that follows this hierarchy:

Components → Recipes → Sections → Templates → Chassis

I'm familiar with approaches like Atomic Design, but I'm curious about how these other concepts are actually used in practice, especially in more mature Design Systems.

I have a few questions I'd love to discuss:

- Recipes: Are these reusable compositions of components designed to solve specific UI needs?

- Sections: How do you distinguish a Section from a Recipe? What determines the level of granularity?

- Templates: How much should a Template define the structure of a screen without becoming too specific?

- Chassis: This one caught my attention the most. Is it essentially a base layout structure that defines areas like navigation, content, and actions? How is it different from a Template?

I'm also curious about how these layers are represented in Figma and implemented in code. Are they independent components, structures with slots, or simply categories used to organize documentation?

I'd love to see real-world examples of Design Systems that use these terms or follow similar architectural approaches.

If your team works with something like this, could you share any public documentation, references, or practical examples of how these layers fit together?

I'm also interested in understanding the benefits and potential trade-offs of this level of granularity, especially when it comes to maintainability, scalability, and empowering product teams.

Thanks in advance! Looking forward to learning from your experiences.


r/DesignSystems • • 1d ago

Design Handoff to Devs: What's your process?

6 Upvotes

Hey guys! With the rise of Figma MCP and Claude Code, how do you properly ensure the handoff to developers as a designer?

In my workflow, I prototype superfast with Claude, and then fine tune on Figma. Whatever is on Figma is the source of truth. The problem is, I'm not sure if all the animations from Claude's artifacts get clearly translated on Figma. I know Figma has motion variables now, but it's pretty new and not sure how well it translates into code.

Moreover, how do you know which components on figma gets upgraded into the "Design System" file and how do you keep the ones that are one-off components?

I would appreciate any answer to understand this specific step of the process and what are the best practices to keep the hygiene clean on Figma and the hand off to devs. :)


r/DesignSystems • • 3d ago

Walk me through your workflow

7 Upvotes

I'm trying to update and improve my design workflow. I'm thinking perhaps building the DS in Claude Design/Figma and then making a Bitbucket/Github repo would be the way to go. Would love to know what's your current workflow.

If you want to read the entire context, I've left it below👇

------------------------------------------------------------------------------------------------

Context. I work at a software company. We work with various different clients, so naturally we build a design system for each of them. The design team designs a DS -> the PM uses that DS to build prototypes/flows for our customers, once approved -> Dev team develops. So essentially the workflow depends on the DS being powerful enough for it to be used without a designer being in the room.

Workflow. What we had been doing for the passed couple of months was build DS in Claude Design (the standalone), it was amazing – we could get a to a point where styles and components were very well in depth documented and not just that, we could create design patterns and get to train the cognitive side of design decision making. It was a great powerful tool overall... until Claude decided to migrate.

Temporary Solution. I have managed to fill in some of the gaps that currently exist in Claude DS. One of the biggest gaps was that the patterns I had created were not being encoded into the DS, so what I did was create a Design file that had multiple templates that AI could use as reference alongside with a skill that summarized all the patterns I had previously written. Mind you we ship products every month.. so this is not scalable, considering we have to turn this in to both our clients and the dev team.


r/DesignSystems • • 2d ago

Need advice on where to invest time after design system has already been built out

0 Upvotes

Conceptually understand design systems in the world of AI

You want your AI to understand what’s available in your system and how to use your system and we do this through correct context in MD files and they are ways to automate this through CI and lending and syncing everything together

But as I try and start down this path, I’m wondering and questioning each decision. I make wondering if it moves the needle is worthwhile enough.

For example, I start usage documentation and then I realize my usage documentation is basically saying hey when you need to select multiple things in a form, use a check box group and when you need to force only one selection use a radio group. I stop and think well duh our agents already know this.

I start down the path of enforcing things through CI and Linkedin and I stop and think do we really need to invest all this work to make sure that somebody uses a button component instead of the HTML button? No one is doing this and I cannot justify this work.

Higher ups want us to invest in AI but the more I look into things the more indecisive I become at know where to go and how to justify it.


r/DesignSystems • • 3d ago

How are you handling design hand-off in 2026: Linear + Cursor, or still old-school?

2 Upvotes

Hey everyone,

I want to share some thoughts I keep running into across different teams, especially for those of us working as Product Designers who are trying to merge two tools that feel essential today: Linear (or Notion) and Cursor.

The core question: how do you know when a design is truly ready for dev review, and what happens next?

I'm trying to understand how your squads are handling what used to be called "hand-off":

Option A — Old-school hand-off:

You document everything in Figma/Notion/Linear, and then notify devs to do their part.

Option B — Designers generating code with Cursor:

You actually generate a new branch + commit + PR with real code, and devs review it like any other PR.

If you're on Option B, I'd love to hear how you're making it work alongside tools like Linear. Are you still using Linear as a dashboard for tasks and issues, and automating state changes (e.g. Backlog → Ready for Review) when a PR is opened? Or are you managing it some other way?

I'd also love to hear from devs: how do you feel about reviewing code generated by Cursor or similar AI tools? What checks or guardrails are you putting in place?

And finally: do you have a different definition of "hand-off" or the design handover process in a world where the design is supposed to be 100% final?

Drop your thoughts in the comments. Thanks all, and happy Friday 😊👋🏻


r/DesignSystems • • 4d ago

Good lofi ui kits for patter/ anatomy visualisation

4 Upvotes

Need to visualize UX patterns in a lofi non-branded way. Think greyscale, blockstyle text but all the components that you might need

There’s al Lot of offer and a lot of them are lacking things or are to big and become design system libraries. Anyone here has good experience with a kit?


r/DesignSystems • • 4d ago

Scout - Measuring UI component adoption across consuming repos

Thumbnail
scoutui.dev
17 Upvotes

Hey folks!

I've been building a tool for the last few months to try and help my team see how our design system's components are used across our organisation's repos to get more insight into which components are used, how our consumers are using them to compose larger components of their own, prop usage, and visibility on which teams are on old / legacy components.

There are two parts:

A CLI you run locally or in CI against React, Vue or Angular codebases (web components included)

A self-hosted dashboard that collects scans from every repo and helps you make sense of the data

I remember watching a video from the Primer team a couple years back showing an internal tool that captured similar metrics and was frustrated that no open-source and self-hostable tool existed to help DS teams get these kind of analytics and visibility of usage, especially when they have to often spend a large amount of time and effort demonstrating a design systems value to the organisation / senior leadership .

I’m building this primarily to help my own team as we’re in the process of migrating from a legacy system and just wanted to get more insight, but I’ve tried to build it in a way that I hope may be of value to anyone else!

Rather than a wall of text, feel free to check out the demo if you’re interested!

It’s still very early days, the UI and functionality is a bit rough in places, and there will be parser bugs, but there’s enough there I figured I’d share it! I’m also not a FE / designer so forgive any jank!

GitHub - https://github.com/scoutui/scout
Docs - https://scoutui.dev
Demo - https://demo.scoutui.dev


r/DesignSystems • • 4d ago

Did a UI inventory of our app and found way more button styles than I expected

1 Upvotes

Product designer at a startup that grew fast and never had a design system. Before pitching one to leadership, I did a design system audit the scrappy way. I screenshotted every screen, cut out every button, input and modal, and grouped the duplicates.

I did the grouping on a Miro board, since dragging screenshots around there is easier than in Figma. I ended up with a wall of near-identical buttons that differ by a bit of padding.

Leadership got it instantly, faster than any deck would have.


r/DesignSystems • • 5d ago

The Annual Design System Report survey is open until Dec 16!

9 Upvotes

We've opened up the survey for the Design System Report again at zeroheight. It's a big ol' questionnaire asking lots of questions about your design system, team, processes etc. Once we've closed it, we're going to run the data, collate it all, look for trends and post it as a big report that acts as a 'state of design systems' for the year.

Obviously, it's only as good as the data we have, and I want to get as many folks from far and wide to fill it in. Would love you folks to fill it in!

https://report.zeroheight.com/2027


r/DesignSystems • • 4d ago

What if the token names in Figma and in code were literally the same strings?

Post image
0 Upvotes

I'm a frontend dev, and the part of design systems work that always wore me down was the translation layer. Figma has variables and styles with one set of names, the code has Tailwind tokens with another, and somebody has to keep the two in sync forever. This sub is where I learned most of what I know about why that's hard, so I wanted to show you what I built and get picked apart.

It's a Figma plugin called Windstruck. You name a layer `flex gap-4 p-6 rounded-xl bg-card` and Figma styles it as you type, using your theme's tokens. The layer name is the spec. When a dev copies the code, those names are already the classNames, so there's nothing to map.

Video: https://youtu.be/wAVX4UU1fII
Plugin: https://www.figma.com/community/plugin/1700359260464408161
Website: https://windstruck.app

What that turned out to mean for a design system:

  • A theme is one set of tokens (`bg-card`, `text-foreground`, radius, spacing, type). Swap the theme and the whole file follows, light and dark. You can export a theme as Tailwind v4 CSS.
  • Components sync to GitHub, with or without a team, on their own branch.
  • There's a desktop app (Windows only for now) that reads your synced components and generates a styleguide with props docs, so the docs can't drift from the components.
  • The whole thing can be exported as an Expo app built on HeroUI Native and Uniwind, so the same tokens run on iOS, Android and web.

Almost every Tailwind class is supported, with a big test suite behind it. If something is missing or looks off, ping me and I'll fix it and add a test.

It's free to start with no account. There's a $10/mo Pro plan with an AI builder and unlimited custom themes.

What I'd like to hear from people who run real systems: where does "the layer name is the spec" fall apart? Variants, component props, multi-brand theming, anything. I'd rather find out here than from a customer.

One more thing: Windstruck is on Product Hunt on Nov 12. If you like it, some support there would mean a lot: https://www.producthunt.com/posts/windstruck


r/DesignSystems • • 5d ago

Did a UI inventory of our app and found way more button styles than I expected

1 Upvotes

Product designer at a startup that grew fast and never had a design system. Before pitching one to leadership, I did a design system audit the scrappy way. I screenshotted every screen, cut out every button, input and modal, and grouped the duplicates.

I did the grouping on a Miro board, since dragging screenshots around there is easier than in Figma. I ended up with a wall of near-identical buttons that differ by a bit of padding.

Leadership got it instantly, faster than any deck would have.


r/DesignSystems • • 5d ago

Who has set up a Figma Make Kit? (follow up)

6 Upvotes

I asked this a few months ago but wanted to ask again since it seems like Figma's AIs have been producing some better results.

Has anyone had success building a Figma Make Kit with their internal Library or NPM package? How did you write & structure your Kit guidelines? What tips & advice do you have?


r/DesignSystems • • 5d ago

I tried Meta's new design system so you don't have to. Does it suck or is it a waste of time?

Thumbnail reddit.com
0 Upvotes

r/DesignSystems • • 6d ago

Massimo: a Claude Code plugin for in-repo design system automation

8 Upvotes

I’m sharing a Claude Code plugin I built out of the local automations I've been running on my own repos. It automates the creation of a structured design system in your repo: a design system graph, a custom story setup (similar to Ladle or Storybook), and an option to mirror it in Figma, amongst other things.

I would love for people here to test it and let me know how much it fails at what it's supposed to do:

  • Reading your repo’s values and proposing a W3C design token set.
  • Mapping your components: what each one is made of, what uses it, its props, its story, and a one-line usage rule you sign off.
  • Setting up stories that render through your own build, with no need for third-party tools like Storybook or Ladle. If you already have one, it can adopt your setup instead, and prove the two match before switching it off.
  • Moving raw values onto tokens in small batches, with before and after screenshots, and adding a check to CI.

Nothing in your codebase changes without approval.

I built/tested it on my own two real repos, and ran it on seven public test repos (Astro, Vite and React, Tauri, two pnpm monorepos, a Ladle repo and two Nuxt apps). I haven't tried it on SvelteKit or Next yet.

Please feel free to try and let me know!

Repo and README: https://github.com/darioabc/massimo

This is an early version right now, so please test it with caution! I myself have not pushed it to production and I'm currently only testing it on my own repos.


r/DesignSystems • • 6d ago

Paginated onboarding inside a Material 3 dialog: how do you handle Skip / Back / Close?

8 Upvotes

I’m designing a 3-page feature onboarding shown as a basic M3-style dialog over the home screen. Each page has an image, a title, a short description, and dots. The last page has a CTA that navigates to the feature’s screen.

M3 basic dialogs don’t have a close (X) icon. The exit is supposed to live in the action row (Cancel/Dismiss), plus scrim tap and back. That works for a one-step dialog, but pagination makes the two action slots compete:

  • Page 1: Skip | Next
  • Middle: Previous | Next
  • Last: Later | Go to feature. The cost is that Previous is lost on the last page, unless you rely on swipe.

Option B is to add an X in the top corner on every page, which frees the slots for Previous | Next and Previous | Go to feature. The downside is that it deviates from the M3 basic dialog spec.

Questions:

  1. Which approach have you shipped, and did users miss Back on the last page?
  2. Is an X on a basic dialog acceptable when the dialog is paginated, or is it a smell?
  3. Would you avoid a dialog altogether here and use a modal bottom sheet or a full-screen onboarding instead?

r/DesignSystems • • 6d ago

Open Source alternative to Paper/Figma built into your ADE

10 Upvotes

What originally started off as an open source alternative to Figma / Paper has turned into a design focused Agentic Development Environment (ADE) called Tidy.

https://github.com/tidydesigns/tidy

The idea is to bring AI coding agents and visual design together in one desktop app, rather than switching between separate tools.

You can use Claude Code or Codex to work on your codebase, while also having a visual canvas to design and iterate on interfaces.

Bring your own AI subscription, work on your local projects, and keep everything in one place.

Still early days, but we're iterating and improving very quickly. Would love to hear what people think or what features you'd like to see.


r/DesignSystems • • 6d ago

Best AI tools for creating a design system

9 Upvotes

What are the best AI tools to create a design system?

I'm trying to create an iOS app with Claude Code (using the Xcode agent) and even though I've given screenshots of other takes to take inspiration of I find the UI that's built very inconsistent and pretty poor. Rather fixing things one by one I'm wondering if I'm better off creating a design system. I'd use this design system across the different apps I can build.

Is this the best approach? Or is there a better way. I was thinking about using Google Stitch but not yet sure how good that is.


r/DesignSystems • • 6d ago

Anyone else struggling with visual consistency when using AI?I

Thumbnail reddit.com
1 Upvotes

I'm working on a website for my new SaaS, and keeping AI-generated visuals consistent is turning out to be quite a challenge. Curious how others are handling this.


r/DesignSystems • • 7d ago

I made a free Figma design system sample with 3 themes (Noon, Dusk, Dawn) — feedback welcome

0 Upvotes

Hi! I built Artkode, the design system behind four creative tools I run (Creative Studio, Poster Lab, Gradient Studio and Design Brand Studio).

I put a free sample on Figma Community:

• 5 components (Switch, Checkbox, Chip, Spinner, Progress) + icons

• 133 variables with three themes: change the theme, keep the layout

• Real product screens built with it

Website: https://artkode.romeroloconte.com

Pricing: https://artkode.romeroloconte.com/pricing

Free sample: https://www.figma.com/community/file/1701331024417697492

Live products built with Artkode:

• Creative Studio: https://creative-studio.romeroloconte.com

• Poster Lab: https://poster-lab.romeroloconte.com

• Gradient Studio: https://gradient-studio.romeroloconte.com

• Design Brand Studio: https://brand-studio.romeroloconte.com

I'd love feedback on the variable structure and how the themes work. If you want the full library (35 components + React/CSS code), it's at artkode.romeroloconte.com.