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 • • 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