Colours
An orange brand over a beige page, with white cards and fields, orange borders, and neutral grey text.
Colour comes in two layers. The palette layer is Tailwind’s OKLCH palette: greys from neutral (chroma 0), the brand from orange, destructive and error from red, success from green, warning from amber. The functional layer gives each job a token that points at one palette step, as --primary: var(--color-orange-600). Components use the functional tokens and never the palette steps behind them, so a change of step happens in one place.
Every colour is a palette step. There is no colour alpha anywhere, so no /50 modifiers and no color-mix. A hover or press shade steps along the ramp, as orange-200 to orange-300. Opacity on a whole element, for a disabled state or a fade, is fine because it fades the element and does not define a colour. The system is light only.
Tokens
Surfaces
Surfaces separate by background step and solid border, never by shadow.
| Sample | Token | Value | Job |
|---|---|---|---|
| --background | orange-50 | The page. Everything else sits on it. | |
| --card | white | Cards, alerts, and field boxes: input, textarea, select, combobox, date picker, number field. | |
| --popover | white | Floating surfaces: menus, select lists, the date picker panel, dialogs, drawers. | |
| --muted | orange-100 | A quiet background step: a read-only field, the number field spin button, the empty state icon tile. | |
| --secondary | orange-100 | The secondary button and badge, an unpressed toggle group chip, the avatar group overflow count. | |
| --accent | orange-200 | Hover and highlight: a ghost button under the pointer, the highlighted menu row, a calendar day under the pointer. |
Text
Text is neutral grey on every surface.
| Sample | Token | Value | Job |
|---|---|---|---|
| --foreground | neutral-950 | Body text, headings, values, and the tooltip fill. --card-foreground and --popover-foreground take the same step. | |
| --muted-foreground | neutral-600 | Descriptions, placeholders, helper text, and field icons. | |
| --secondary-foreground | neutral-900 | Text on --secondary. | |
| --accent-foreground | neutral-900 | Text on --accent. | |
| --primary-text | orange-700 | Orange as text: the date picker focused segment, the notice subject on hover. |
Orange
Orange has three jobs. --primary is a fill under text, --indicator is a mark on a surface (a fill, a bar, a ring, an underline), and --primary-text is orange as text. The first two share orange-600 but name different jobs, so a mark and a fill can move apart without touching each other’s consumers.
| Sample | Token | Value | Job |
|---|---|---|---|
| --primary | orange-600 | An orange fill under text: the default button, the default badge, the pressed toggle group chip. | |
| --primary-foreground | white | Text on --primary. | |
| --indicator | orange-600 | Every orange mark on a surface: checked fills, active bars, field focus rings, the text link underline, the progress fill. | |
| --indicator-foreground | white | A glyph on --indicator: the checkbox tick, the radio dot, the switch thumb, the selected calendar numeral. |
Borders and rings
Borders are decorative. Rings are how focus shows, so a ring has to stand out against the page.
| Sample | Token | Value | Job |
|---|---|---|---|
| --border | orange-200 | Every surface border and divider. | |
| --input | orange-200 | Field box borders at rest. They step to orange-300 on hover. | |
| --ring | neutral-950 | The default focus ring, for anything that does not ring in its own hue. |
Status
Each status ships as a fill and a text colour that reads on it. Error does not reuse --destructive, because a tint cannot come from a solid without alpha.
| Sample | Token | Value | Job |
|---|---|---|---|
| --success | green-100, text green-800 | A success fill, with --success-foreground on it. | |
| --warning | amber-400, text amber-900 | A solid warning fill, with --warning-foreground on it. | |
| --error | red-100, text red-700 | An error fill, with --error-foreground on it. The destructive button fills with this. | |
| --destructive | red-600 | An invalid field: error text, the required asterisk, borders, focus rings, and a checked invalid checkbox or radio. Also the destructive menu item text. |
Loading
Placeholders and tracks sit two steps above the page on the orange ramp.
| Sample | Token | Value | Job |
|---|---|---|---|
| --skeleton | orange-200 | Skeleton blocks. | |
| --progress-track | orange-200 | The progress and stepper track. | |
| --progress-fill | orange-600 | The progress and stepper fill, an alias of --indicator. |
Charts
The brand leads, then four pale hues. A chart that needs a status colour takes --success directly.
| Sample | Token | Value | Job |
|---|---|---|---|
| --chart-1 | orange-500 | The first series. The brand leads. | |
| --chart-2 | sky-300 | The second series. | |
| --chart-3 | violet-300 | The third series. | |
| --chart-4 | teal-300 | The fourth series. | |
| --chart-5 | pink-300 | The fifth series. |
Group colours
Six hues tell items in a set apart: the stays of a trip, avatar fallbacks, labels. Each hue has six tokens. --group-<hue> is the solid fill with -foreground text, -soft is a tint with -soft-foreground text, and -border steps to -border-hover.
Assign hues by index in this order: cyan sits close to sky and fuchsia close to pink, and this order keeps each lookalike pair three places apart.
Usage rules
- DoChoose a colour by its job: orange for the main action, red for loss, grey for supporting text.A colour then means the same thing on every screen, so a reader learns it once.
- DoPut white on every orange fill.Dark text on orange reads muddy. White is the one pairing that keeps the brand vivid.
- DoDeepen a colour one step for hover and another for press.The control stays recognisably the same colour, and each state reads as a little more pressed.
- Don’tMake a colour see-through to get a lighter tint.A see-through colour takes on whatever is behind it, so the same tint looks different on each surface.
- Don’tLet a group colour work alone.The set leaves out every hue near the brand or a status, so a group never reads as an action or a result. Always pair the colour with a text label.
- Don’tDesign a dark version of a screen.The system is light only: orange on a warm beige page is its identity, and there is no dark theme for a screen to join.