Skip to content

Rules

Straight answers to the questions teams ask first.

  • Do I have to use the system as it is?

    Use it as it is whenever you can. People learn the parts once and then trust them everywhere. Bend it only when a real need cannot be met by what is here.

  • Can I change a color, size or corner?

    Change the values in the tokens, not inside a part. That keeps light and dark mode, and every part that uses the value, in step. Do not use one-off colors.

  • Amber and lime: when can I use them?

    Amber means a person has to act. Use it for nothing else. Lime marks what the AI made or a main action, and it is only ever a fill, never text.

  • Can I add my own part?

    Yes, if no existing part does the job. First check Patterns and Components. Then build it from the tokens, give it a plain-language description, and test it with a keyboard and on a phone.

  • How do I ask for a new part?

    Open a request and describe what the person is trying to do, not the shape you want. We will tell you whether an existing part fits or whether it should be added.

  • Who owns the system?

    The design system team owns the tokens and parts. Product teams own how they use them. Anyone can suggest a change.

  • How do I know I used a part correctly?

    Compare your screen with its Do and Avoid lists, and with the matching pattern. Every part can be opened from the site and tried with a keyboard.

  • Something is broken or confusing. What do I do?

    Tell us with the feedback link. Include the page, what you expected, and what you saw. A screenshot helps.

Build your next AI screen with Tattva.

Free and open, with the code. Start in one line.

Get started