r/DesignSystems • u/Extreme-Protection74 • 13h ago
r/DesignSystems • u/General-Mulberry-526 • 1d ago
Need some input on my AI experiment
We recently built an automated video pipeline using AI agents to turn dense technical specs into visual explainer videos, and I’d love some community feedback on how to refine it.
How the pipeline works:
- Context Synthesis: Ingestion agents pull from our docs and specs to structure clean, grounded context (avoiding hallucinations).
- Storyboard Generation: A reasoning agent breaks that context into modular beats, pairing concise narration with specific visual cues.
- Programmatic Visuals & Audio: Instead of generative video, agents generate code-based diagrams/animations synced to TTS word timestamps, then stitch everything automatically.
We have one Ai agent, which is responsible to fetch some context. Then another AI agent to create the video. On top of that final review AI agent which reviews the frame.
Looking for your feedback:
- What do you think is missing from a workflow like this to make the output feel less "automated" and more cohesive?
- For those building multi-agent pipelines, how are you tweaking your prompts, handoffs, or evaluation loops to tune the agents for better visual pacing and consistency?
Here is the link to the video we created - https://www.youtube.com/watch?v=bxDOdSKzHIQ
Would love to hear your thoughts or critiques!
r/DesignSystems • u/Alarming-Position887 • 2d ago
How do you structure brand assets when one parent company runs several brands?
I do some freelance marketing and I have a client that might end up taking on a second brand next year. So I've been poking around to see how multi-brand companies split up their non-component stuff, the logos, product shots and packaging files that don't live in the library.
One I found interesting is AYR. They keep everything on one public page with a tile per brand, and some brands get a separate tile for each state, so kynd and Later Days each have Pennsylvania, New Jersey and Ohio versions. For a dispensary buyer that's probably easy to follow, but I wonder about the upkeep, and how much gets copied across every state version.
For those of you who've run a system across several brands: do you split it per brand, or keep one hub with sections? What do you do about the shared stuff? Here's the one I mean: https://www.lingoapp.com/118670/p/AYR-Wholesale-oEKE6L
r/DesignSystems • u/Resident_Style5928 • 2d ago
Shipped 4 frontends with AI agents this fall. The design system did more than any prompt.
reddit.comr/DesignSystems • u/Tarasenko_by • 2d ago
I updated Veritheme, my free design system generator: theme builder, slot-based Figma components, and an MCP server
I've been building Veritheme, a service that generates design systems, and I just shipped a big update. It's free.
New since my last post: the theme builder, slot-based Figma components, and the MCP server.
I know that today you can generate any design system with AI. The problem is that AI isn't deterministic: you get a different result every time, and you end up fixing its mistakes over and over. That's why I'm building a system that is deterministic and gives you a predictable design system every time.
Here's how it works now:
- Build a theme. The site has a new theme builder: pick your brand color, neutrals, typography, radius, and shadows, and see the result right away.
- Generate it in Figma. Download the theme, load it into the Figma plugin, and it generates the whole system in your file with your theme applied: buttons, inputs, selects, checkboxes, switches, tabs, tables, dialogs, toasts, navigation, and so on. 85 components in total, in light and dark.
- Components now use slots. This is the biggest change in Figma. Instead of a separate variant for every case, a component is a shell with slots you fill with whatever you need. That makes the components much more universal, and there are far fewer variants to dig through.
- Everything is built on tokens. Every component is bound to variables, so when the theme changes, the whole file changes with it. The system follows atomic design: complex components are built from simpler ones, and on top of the base components there are ready-made blocks. Every component has its specs documented on the site.
- An MCP server with design contracts. You generate a theme, generate the Figma components, and then the MCP server gives your AI tool a design contract that ties the components in Figma to the components in code. The code comes out cleaner and closer to the design. Or you can skip Figma and generate pages right away from the components I've already built, with the theme you made in the builder.
I've posted about this project here before, and I keep improving it, in part based on your feedback. So if you try it and have ideas or suggestions, tell me, and I'll do my best to build them in.
Links:
- Site and theme builder: https://veritheme.com
- Figma plugin: https://www.figma.com/community/plugin/1610343587499165100
- Example of a generated design system in Figma: https://www.figma.com/community/file/1700399582961383799
r/DesignSystems • u/Ok_Buy8550 • 3d ago
I built a local-first design system editor that writes the prompt for your coding agent (open source)
i.redd.itI kept running into the same problem: the design system looks right in one place, then colors, type, radii, and motion drift between the canvas, the stylesheet, and the codebase. The prompt I give my coding agent is usually a screenshot and a guess.
So I built SaaS-UI: a local-first editor for design systems.
- Edit the real tokens — palette, type, layout, components, effects, motion.
- Preview the same system on real page types.
- Export CSS, Tailwind, TypeScript, JSON, Markdown, or one agent-ready prompt.
- Generate a brand book, audit an existing stylesheet, or import tokens.
- The editor is MIT and works without an account. Cloud sync and collaboration are optional.
The demo is the real product, captured live — no mockups.
Open source: https://github.com/BlackBenAI/saas-ui
Hosted version: https://saasui.cloud
Community: https://discord.gg/GMtNYDevE
I would especially appreciate feedback on:
- the token model and export formats;
- the agent prompt structure;
- accessibility gaps or missing editor workflows;
- what would make you contribute or use it in a real project.
If you want to contribute, the repo has the setup, architecture, local-first data model, and contributing guide. Issues and small PRs are welcome.
r/DesignSystems • u/helorebyron • 3d ago
I updated my OKLCH based palette generator to keep chroma consistent across different hues
I built a palette generator that lets you create palettes with shared chroma settings and different hues, then compare the minimum, average, and maximum chroma at each brightness step.
I’ve recently added a few features:
1. Editable brightness steps
Previously, the brightness steps were fixed. You can now customize the steps and their names, or use presets(Material color system or Tailwind). You can enter brightness using CIELAB L*, OKLCH L, HSB brightness, or grayscale HEX values. The alternative input formats are converted using neutral gray values to define each step’s target CIELAB L* (D65).
2. Display P3 support
You can now generate palettes in either sRGB or Display P3. All palettes share the selected color space.
3. More copy formats
Colors can now be copied as HEX, OKLCH, or RGB. Display P3 RGB values use CSS color(display-p3 ...) syntax. For Display P3 colors outside the sRGB gamut, copying HEX provides a gamut-mapped sRGB fallback.
4. WCAG 2.1 contrast matrices
You can inspect contrast ratios between brightness steps in Basis and between the final colors in each palette’s details, with AA and AAA filters. CIELAB L* (D65) is derived from relative luminance, which is what WCAG 2.1 uses to calculate contrast.
Keeping each step’s L* fixed therefore preserves contrast between the same pair of steps across different hues and chroma levels. Final color conversion and rounding can still affect AA/AAA results near contrast thresholds, so please check each palette’s contrast matrix before using the colors.
For a basic guide to using the palette generator like Controls parameters, check out my previous Reddit post.
https://www.reddit.com/r/DesignSystems/comments/1wownnq/i_built_an_oklch_palette_generator_to_balance/
If you try it, I’d appreciate any feedback or suggestions!
r/DesignSystems • u/Relative-Chemical-32 • 3d ago
Our design system got a third user: the agent
With my team, we’re building a design system to be used with agents, we named it: Whisk/UI. It uses the same tokens in Figma and in code: brand palettes, 45 semantic color roles, then component tokens.
A lint runs with every check and fails when the UI uses a raw HTML element instead of a Whisk/UI component, a hardcoded color, an inline style, or text without a text style. A real exception goes in a config file, with the exact file and a written reason. So the agent gets an error it can fix, not just a guideline it can skip, and doesn’t have to guess.
Whisk/UI is part of a bigger project, the Smoothie Framework, which also adds generative UI. It lets AI build screens at runtime, while someone is using the app. You give the model a catalog, the list of components it may use. It replies with a JSON description of the screen, the app validates it, and anything outside the catalog or its limits isn’t rendered.
We built a small demo to show it. Dump a note and the AI files it. Anything that isn’t a task or an expense gets a new space, with a layout generated on the spot. Try “books to read: Dune, Piranesi”, then change the UI of a space, for example "Do not show me tasks as a kanban but use a list instead". You get 3 tries a day, so pick good ones.
We used the same setup with a client. Iteration was much faster, and we mirrored the codebase on Lovable so they could try variants on their own in a safe place. Everything followed the design system, and the code was easy to pick up by hand afterwards.
We’re still working on Whisk/UI, and the next release we have in mind is making it cross-platform. So basically you write a screen once in Whisk markup (it looks like TSX but it’s pure data), and it compiles to a Whisk document that each platform draws with its own native toolkit: GPUI on desktop (Rust), SwiftUI on iOS, Compose on Android (Kotlin), so no webview. If you only ship on one platform, you can also use Whisk/UI directly in Rust, Swift or Kotlin.
Sorry for the long post, this project is hard to explain in a few words. 👉🏻👈🏻
If you want to take a look, here are some links:
- Docs, public but still a work in progress: here
- Figma preview: here
- We opened Founding access a few weeks ago: here ; we are still figuring out the business model.
I am really curious to hear your feedback.
r/DesignSystems • u/sabarishsanjay • 3d ago
How are you handling AI agents in your Figma workflow? I built a local bridge and want honest feedback
r/DesignSystems • u/No_Draw4901 • 3d ago
We rebuilt our design system so our team and AI agents follow the same rules and get the same UI
Our team (one designer, one engineer) spent 3 weeks rebuilding our design system, MBSW, around one question: can a human and an AI agent start from the same source and end up with the same UI?
When we asked AI to follow our old system, it kept rebuilding components we already had and picking colors that were only close. The rules it needed lived only in someone's head, not anywhere it could read.
What we changed:
- Two layers per component. An intent doc (MD) written by the team explains when and why to use it. The values (JSON) are generated by a script from a Figma version the design team has approved.
- No AI summarizing Figma. We first had AI read Figma through MCP and turn it into JSON, but the same component came out slightly different every run. Pinning the Figma version and using the REST API made the output identical, whoever runs it.
- Tokens mapped by intent, not by value. Different tokens can share the same color, so the value alone can't tell you which token it is. We map values through Figma variables and keep each confirmed mapping.
- No filling gaps by guessing. If we've agreed on a behavior that isn't drawn in Figma, it goes in the intent doc. If a token mapping is missing or ambiguous, the AI doesn't pick one just because the name or color looks close; it waits until we confirm.
It's public (React 19, MIT) if you want to see how the docs and tokens are structured: https://rdo.sh/G1SCiIV
Curious how other teams approach this. Do you write documentation with AI as a reader in mind, and what has worked or not?
r/DesignSystems • u/design-for-good • 3d ago
Are others using more than one design system for their company?
Is it overkill to create an entirely separate design system for my marketing site and ad content?
My SaaS app is one thing but the marketing site is starting to take a very different turn and making one design system was starting to get more complicated to accommodate both.
I'm on the track that I'm about to create a second one but now I'm going to have a lot of duplicate tokens such as colors for example.
Has anyone else faced this issue and do you have any suggestions?
r/DesignSystems • u/otc_playDraft • 4d ago
A design-system gate caught 46 color violations, then exposed the palette I did not have
I added a deterministic “steel curtain” to my portfolio repo. It checks only the lines a pull request adds and blocks things it can prove are wrong: raw colors that already have tokens, classes with no stylesheet, images without alt text, and a few other mechanical rules.
On my homepage redesign it finished in 38 seconds and stopped the merge on 46 findings. Every blocker was a color I had already named. Twenty-nine were exact token values typed by hand, and 14 of those were inside one sticker component.
The report-only findings were more interesting. Thirteen colors were too far from any token to block. Ten of the twelve unique colors were drawing materials: sticker release paper, aluminum, glass, a bezel, and a lens.
My system has a brand palette. It does not have a material palette.
The gate also writes proposed components and patterns into a registry for me to review. It has proposed 18 additions so far. I have promoted none. The script can spot drift and collect evidence; deciding what the system should keep is still manual.
I am trying to decide what the correct layer is for those material colors. Would you:
- promote them into the main token system;
- create a separate material palette with its own rules;
- keep them local to the illustrated objects;
- or treat this as evidence that the gate is checking at the wrong level?
Full write-up with the receipt and swatches:
https://www.rdeboerdesigns.com/notes/the-gate-stopped-my-redesign/
r/DesignSystems • u/Jaapuchkeaa • 4d ago
Share some new exciting design systems that you recently discovered
r/DesignSystems • u/Minimum_Hour519 • 5d ago
Introducing spatial CSS: A developer preview
r/DesignSystems • u/design-for-good • 5d ago
What actually belongs in a design system for a small to mid size company?
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 • u/ved_NT • 5d ago
Building design stack which curates AI slop gracefully.
reddit.comr/DesignSystems • u/roundabout-design • 6d ago
How are you delivering "use this, not that..." logic via your MCP servers?
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 • u/DirtyOught • 6d ago
How often are Design Systems matured beyond “component library”?
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 • u/jcchengjh • 6d ago
How do you prep your design guideline for LLM-agent?
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 • u/ephemerald-0000 • 7d ago
Design Handoff to Devs: What's your process?
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 • u/designersbr • 7d ago
How do you structure your Design System? Recipes, Sections, Templates, and Chassis
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 • u/DirtyOught • 8d ago
Need advice on where to invest time after design system has already been built out
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 • u/rjescobar_design • 8d ago
Walk me through your workflow
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.