All products

Build a design system with AI

Inventory existing styles, decide which values have the same job and document how shared components behave.

To build a design system with AI, start with a question your team can answer from the files. Why does the save button use three different blues across two forms? Give taste-design-system the styles for those forms. Its first deliverables are an inventory, a count of inconsistencies and an order for fixing them.

A shared colour does not always mean a shared purpose. A link and a warning might happen to have the same value today and still need different names. The guide separates raw values from meanings and from the names used by individual components, so a later change can affect exactly the controls its designer intended.

What it does

  • Find colours and spacing values that sit outside the existing scale.
  • Document deliberate exceptions, such as an optical adjustment to an icon.
  • Map button and input styles to names that describe their function.
  • Record focus, disabled, loading and error states for a component.
  • Plan an orderly replacement for a token that other screens still use.

Install and use

  1. Provide the Design Taste core guide, the skill and the style files for one part of your product. No external design account is required.
  2. Ask for an inventory before authorising edits. For example, compare the buttons and validation states in two checkout forms.
  3. Agree on the token map, then try one component change. Record the old name and its replacement if the change affects other screens.

FAQ

Source

Made by Mustafa. Original skill: taste-design-system, published on GitHub under the MIT licence.

View on GitHub