# Slate Design System

> Slate is the visual language of the Everruns UI. Tokens, components, page layouts and writing rules, rendered with the app's own CSS.

Source: <https://everruns.com/docs/design-system/>

Slate is the design system of the Everruns management UI. It is sharp-cornered, grayscale, dense, and calm: a navy primary for actions, one gold accent for the moments that matter, and color otherwise reserved for status.

Slate at a glance: a create action, a commit action, a secondary action, status, and a card.

## What is here

* [Foundations](https://everruns.com/docs/design-system/foundations/): color tokens, type, spacing, shape, elevation, the dot grid, and motion.
* [Components](https://everruns.com/docs/design-system/components/): buttons, badges and status, inputs, tabs, cards, navigation, notices.
* [Page layouts](https://everruns.com/docs/design-system/layouts/): the five page zones, list, detail, edit, and chat.
* [Icons and brand](https://everruns.com/docs/design-system/icons/): the Facet domain icons, action icons, and logo use.
* [Writing](https://everruns.com/docs/design-system/writing/): voice, casing, vocabulary, and punctuation for UI copy.

## How this site stays current

The examples are not screenshots. Every example renders with the tokens, dot grid and motion of the app’s [`apps/ui/src/app/design-system.css`](https://github.com/everruns/everruns/blob/main/apps/ui/src/app/design-system.css), read at build time, and every domain icon comes from the app’s Facet vector masters. A token change in the app changes this site in the same build.

The example markup is a hand-written reproduction of the production components in [`apps/ui/src/components/`](https://github.com/everruns/everruns/tree/main/apps/ui/src/components). Those components stay canonical. A pull request that changes a pattern in the app updates its page here in the same change.

## Redesigning with Slate

A redesign starts on this site, not in the app:

1. Read the page for the area you are changing and the rules on [Writing](https://everruns.com/docs/design-system/writing/).
2. Mock the change with the classes and examples from these pages. Keep tokens as they are unless the redesign is about the tokens.
3. Get the design approved, then build it in [`apps/ui`](https://github.com/everruns/everruns/tree/main/apps/ui) from the production components.
4. In the same pull request, update the pages here so the next redesign starts from what shipped.

## Sources of truth

When two sources disagree, use this order:

1. [`apps/ui/src/app/design-system.css`](https://github.com/everruns/everruns/blob/main/apps/ui/src/app/design-system.css): runtime tokens, utilities, and motion.
2. [`apps/ui/DESIGN.md`](https://github.com/everruns/everruns/blob/main/apps/ui/DESIGN.md): the token file in DESIGN.md format, plus composition rules.
3. Production components in [`apps/ui/src/components/`](https://github.com/everruns/everruns/tree/main/apps/ui/src/components): exact behavior and APIs.
4. These pages: how the parts fit together, and the starting point for new designs.

Product decisions behind individual screens, such as the agent page or chat, live in the repository’s `knowledge/ui/` folder. These pages link to them where it helps.