# Saer Create and saer create

Source: https://saer.app/docs/create
Updated: 2026-11-12

**Short answer.** Saer Create builds a design system in your browser: colour scales in OKLCH, semantic tokens for light and dark with every text pair checked to WCAG AA, type, shape, density and seven components. Open [Saer Create](https://saer.app/create), download `saer-system.json`, then run `saer create --from saer-system.json` in your project: it writes the theme for your stack, the tokens and, if you want them, the components, asking before it changes a file you already have.

## Build the system

Open [Saer Create](https://saer.app/create). It needs no account and runs in your browser; the system you build is not sent to Saer. Your choices are kept in the page address, so you can bookmark or share a system as a link.

- Colour: any number of scales (primary, secondary, accent, neutral and your own), eleven steps each, generated in OKLCH and kept inside sRGB.
- Semantic tokens for light and dark: background, surfaces, text, borders, primary and accent. The solids, the text on them, primary-coloured text and muted text each pick the step that reads at 4.5:1 or better.
- Type, shape and density: heading and body fonts from Google Fonts, a modular type scale, radius, elevation and control density.
- Components: Button, Input, Switch, Badge, Card, Tabs and Select as React and Tailwind source on the tokens, keyboard accessible.

## Export it

- Tailwind v4: `saer-theme.css`, with `@theme` scales and light and dark semantic colours.
- shadcn/ui: `shadcn-theme.css`, the `:root` and `.dark` variables shadcn/ui expects.
- Plain CSS: `saer-tokens.css`.
- W3C design tokens: `saer.tokens.json`, for a Figma variables importer or Tokens Studio.
- Style Dictionary and resolved JSON.
- `saer-system.json`: the whole system, for `saer create` and for reopening it in Saer Create.

## Write it into a project

See what it would write, then write it:

```
$ saer create --from saer-system.json --dry-run
$ saer create --from saer-system.json
```

`saer create` detects Tailwind v4, shadcn/ui or plain CSS (or use `--theme tailwind`, `shadcn` or `css`), writes the theme and `saer.tokens.json`, and offers the components (`--components` or `--no-components`). It adds the Saer agent section to `AGENTS.md` and a `saer.config.json` unless you pass `--no-agent`; an existing `saer.config.json` is kept.

It never overwrites a file without a yes or `--force`, and it changes your main stylesheet (one import after Tailwind) only after a yes. Run without `--from` in a terminal for a short interactive flow instead.

## Then keep agents on it

Run `saer init` to connect your coding agents and add the pull-request check ([saer init](https://saer.app/docs/init)). From then on the system you created is the system Saer checks against: raw values equal to a token and hand-built UI where your components exist show up in the scan and on pull requests.
