* ui: generate DESIGN.md's token sections from the CSS Add scripts/design-md.js in ui/apps/chat (npm run design:tokens, and npm run check:design in CI), which writes the colors, typography and rounded sections of DESIGN.md's front matter from llama-brand's colors.css and Llama UI's primitives, semantic tokens and font stacks. The front matter had drifted: it gave Matte's surfaces as the light base and system-ui for every text role. Twins are now written wherever a token resolves differently in dark mode (-dark) or in Matte (-matte). Describe the floating panel's rim as the CSS draws it, on the border, and say which parts of DESIGN.md are generated and which are kept by hand. Assisted-by: Claude (Opus 5.5 Medium) * ui: say the Storybooks show accessibility findings without enforcing them Both Storybooks keep a11y test 'todo': under 'error' 98 of the stories fail, most on colour contrast of the muted foreground and on nested interactive controls, which need design changes. Reword the Uses tile and record the reason next to the setting. Assisted-by: Claude (Opus 5.5 Medium) * ui: list every Llama Chat group in the Introduction's Sections figure The figure said it was in sidebar order but left out Forms, Actions, Badges, Misc, Servers and PWA. Its list moves to sections.ts, and a unit test checks it against storySort in .storybook/preview.ts, which has to stay inline there because Storybook parses it as written. Assisted-by: Claude (Opus 5.5 Medium) * ui: load the package's Llama Mono in both Storybooks The library's Storybook declared Llama Mono a second time from tests/stories/brand/fonts, a 72276-byte file that differs from the 76896-byte one the package ships, so its pages showed a Llama Mono that does not ship. Drop both Storybooks' copies: theme.css already loads the package's font. Assisted-by: Claude (Opus 5.5 Medium) * ui: take Llama Chat's shared Storybook helpers from Llama UI Llama Chat kept copies of the Editorial, Chapters, StateGallery, StateGalleryItem, svx.d.ts and docs.css that live with the library's stories. Its stories now import them as $llama-ui-stories/..., an alias its Storybook config and tsconfig.json map onto ui/lib/ui/tests/stories, the way it already compiles the library from source; docs.css and svx.d.ts are referenced by path. The library's Editorial takes Llama Chat's newer list numbering. An empty svelte.config.js next to the stories keeps Llama Chat's svelte-check from loading the library's vite.config.ts, as src/svelte.config.js does for the sources. Assisted-by: Claude (Opus 5.5 Medium) * ui: pin the library's Storybook to Llama Chat's versions ui/lib/ui used ^10.6.2 with @storybook/addon-mcp at 10.6.2, while ui/apps/chat pins 10.6.6, so one tree had two Storybooks. Pin the library's Storybook packages exactly to Llama Chat's: 10.6.6, addon-svelte-csf 5.1.6 and @chromatic-com/storybook 5.5.1. Assisted-by: Claude (Opus 5.5 Medium)
58 KiB
version, name, description, colors, typography, rounded, spacing, components
| version | name | description | colors | typography | rounded | spacing | components | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| alpha | Llama UI - Matte Glass | Llama UI, the design system and components of Llama Chat, the chat client llama-server bundles. Neutral and quiet: frosted matte surfaces with faint blue-grey hairlines, near-flat fills, and status colours for success, warning, error and info. Tokens come in three tiers: primitives, semantic tokens (with a "-dark" twin where dark mode differs and a "-matte" twin where the Matte light theme does) and components. The colors, typography and rounded sections are generated from ui/lib/ui/src/lib/styles by `npm run design:tokens` in ui/apps/chat; spacing, components and the prose are kept in sync with the CSS by hand. |
|
|
|
|
|
Overview
Llama UI is the design system and component library this file describes. Llama Chat, built from it, is the local, private chat client that llama-server bundles, and the native Llama apps (Llama for Mac, Llama for Windows) open it in their own window. It should feel calm and tool-like: neutral greys, plenty of space, and surfaces that read as frosted matte glass rather than shiny plastic. Depth comes from blur, a faint hairline edge and soft shadows, never from strong gradients. Colour is reserved for meaning: the status colours (success, warning, error and info), destructive actions, and the content itself.
There are three layers between a person and a model: the model (the weights, a GGUF
file), the service (the server that runs inference: llama.cpp and llama-server) and the
application (the harness, the UI and UX). The harness, the agentic loop, is its own headless
package, Llama Harness (@ggml-org/llama-harness), next to Llama UI (@ggml-org/llama-ui). Llama UI and Llama Chat are the application
layer. Running all three locally is the point: people choose their model and keep their
conversations and traces, so the UI never assumes a cloud account or hides which model runs.
The service need not be on the same machine: a server can be run by one person and shared by
many (a family, a team, a community), so the UI should make clear which server a model runs on.
This file is the how, written for agents first. Its principles, as rules to apply here:
- Function first. Every element has a job and takes its measurements from a shared role (control heights, corners, icon sizes, type roles); never give one component its own.
- Simple by default, deep on request. The first screen offers a suggested model and sensible defaults; advanced settings (sampling, penalties, system prompts, recipes) sit one step away behind a disclosure, never on the default path. Prefer plain words to terms like GGUF, quantization or speculative decoding, and explain a term where it must appear.
- The content is the loudest thing. The conversation carries the weight and the colour; the interface around it stays neutral and quiet.
- Colour has one job. Greys build everything; status colours show status and nothing else; art colours and cinder are for artwork and the odd brand detail, never for the UI's controls.
- Recognisable, easy to change. Keep the character in the icon, the type and one accent, so an app built on Llama UI can restyle it through component tokens alone.
- Design lives in code. The CSS is the source of truth; prefer what is generated or
derived over hand-tuned values, and record the reason next to the value. Content pages are
Markdown with Svelte components in them, as
.svx(seeAGENTS.md). - Reuse before adding. An existing role before a new token, an existing component before a new one.
Design tokens come in three tiers, each in its own file under ui/lib/ui/src/lib/styles/tokens/:
- Primitives (
primitives.css): raw values named by what they are, such asneutral-900,cool-gray-200,red-500,white-a30,font-size-14orlength-24. Only semantic tokens point at them. - Semantic tokens (
semantic.css): named by purpose, such assurface-glass,fg-muted,line-field,edge-focus-side,action-primaryorstatus-warning. They point at primitives and are the only tier that changes between light and dark. The type, corner, icon size and control height roles live here too and are Tailwind utilities:text-label,rounded-control,size-icon-md,h-control-md. - Component tokens (
components.css): one group per component, named[component]-[variant]-[property]-[state], such aschat-form-edge-side-focusorbutton-secondary-background-hover. They point at semantic tokens, and components read them asbg-(--button-primary-background)and similar.
The front matter's colors, typography and rounded are generated from the primitives, the
semantic tokens and the font stacks by npm run design:tokens in ui/apps/chat, and CI fails
when they are out of date (npm run check:design): change the CSS and run it, never edit them
here. The spacing and components sections and the prose are written by hand; when they
disagree with the CSS, the CSS wins and this file is updated to match. Storybook shows every
tier under Llama UI › Foundations › Colors.
Paper light mode is the base. A semantic token that resolves differently in dark mode has a
-dark twin here, and one that resolves differently in Matte a -matte twin; components list
a -dark entry wherever their colours change. Translucent component
fills are given as they render over the page, so contrast checks see the real colour.
Colors
The palette is achromatic. Hue appears only in the hairline edges (a cool grey at hue 250,
kept almost neutral) and in the status colours, which serve function only: green for success,
amber for warning, red for errors and blue for information, saturated enough to read at a
glance and tuned to text contrast in both modes. Each status has one root colour, its fill (fill-*),
and everything in that status derives from it: the soft surface and line of alerts and badges,
the border of an invalid field, the lamp. Red keeps to the same rule, so there is one red: the
danger button and the solid danger badge are the fill itself (action-danger), solid in light
mode and frosted, translucent matte glass in dark (58% of the fill over the page). Never style a
danger control with its own red (bg-destructive, bg-red-500 …): use the destructive
variant, which AlertDialog.Action takes too, or the status tokens. Cinder (art-cinder, oklch(0.68 0.18 46), #ee6c1e) is the brand's one accent orange: the .cpp of the llama.cpp
logotype, the mark on a detail in the brand pages and the warm pop in artwork. It is not part of the UI palette. Sand (sand-50 to sand-900) is the warm neutral for communications
(posters, boards, the site); the UI itself stays on the greys.
Backgrounds stay neutral as a rule, in the UI and in communications alike: greys and sand
behind, colour only where it serves a purpose, functional (status, a selection, focus) or
creative (a shape, a numeral, an illustration). Artwork takes its colours from the greys, sand and
the art-* primitives: the day sky and the night sky (llama.app's light and dark hero grounds) and
cinder, the accent orange; never from the status colours, and never red.
Light mode has two surface themes, which share everything else (the palette, buttons, fields,
badges, shadows and dark mode): Paper, the default, sets white panels, fields and keys on a
faint grey page (neutral-25); Matte sets grey glass on a white page. Matte is the
theme-matte class on <html>, chosen with the Light surfaces setting (Settings → General) or
the Surface switch in Storybook's toolbar, and only its surface tokens differ: surface-page,
surface-glass, surface-code, field-background and float-panel-background-modal.
- Surfaces:
surface-pagefor the page,surface-mutedfor quiet panels,surface-emphasisandsurface-selectedfor stronger fills and hover or selected rows,surface-raisedfor menus and dialogs,surface-liftedfor a selection raised on a recessed track,surface-pressedfor a key pressed in,surface-glassfor the translucent matte fill,surface-codefor code andsurface-overlaybehind dialogs. - Foreground:
fg-defaultandfg-mutedfor text and icons,fg-on-actionandfg-on-dangeron filled buttons,fg-codefor code,fg-dangerfor errors,fg-successfor confirmations such as a copied check,fg-warningfor cautions andfg-infofor neutral notices. - Lines:
line-defaultfor dividers,line-controlfor outlined controls (soft in dark mode),line-fieldfor inputs,line-focusfor focus andline-dangerfor invalid fields. - Edges: the hairlines of matte surfaces, darker at the sides than in the middle.
edge-rest-*at rest,edge-focus-*when focus is inside,edge-ambient-*for large quiet containers whose edge never changes,edge-faintfor the user bubble andedge-raisedfor floating panels. - Actions:
action-primary(near black in light mode, near white in dark mode) and its hover,action-dangerand its hover, andaction-ghost-hover. - Status fills:
fill-success,fill-warning,fill-dangerandfill-infoare each status colour at its brightest, for dots, lamps and other small solid marks. They are brighter than the matchingfg-*text colour, which keeps to a readable lightness (4.5:1 on the soft surfaces), and are a little lighter again in dark mode. - Status surfaces:
surface-success,surface-warning,surface-dangerandsurface-infoare soft tints of each status fill for alerts and soft badges, withline-*-softhairlines to match. They are mixed in oklab so the hue holds over the page. Soft status badges are pills with a small dot in the status fill before the label. - Status:
status-danger,status-warning,status-successandstatus-infoare the lamp fills for error or stopped, loading or warning, ready or connected, and informational. They take the status fills, and each has a lighter-rimand a darker-glyph. Known gap: the glyph on the red lamp reaches only about 2:1 and on the green lamp about 3.2:1, below WCAG AA, so the lamp colour must never be the only signal; pair it with a label or tooltip.
Typography
The UI uses Llama Sans for all text, headings included (with the system sans-serif stack as its
fallback), and Llama Mono for code (with the system monospace stack as its fallback). Llama Sans
is one variable font with an optical size axis: the browser sets it from the font-size, so text at
16px gets the UI spacing and kerning, 36px and up the tighter Display setting and text under 16px a
looser Small one, with a blend in between. Nothing needs choosing per element; pin a point only to
show it, with font-variation-settings: 'opsz' 16 or 36. Its line box is 1.25 at every size, centred on the
cap height; large headings set line-height: 1.15 themselves. Llama Mono keeps every character,
its coding ligatures included, in one cell, so code and numbers line up in columns. Type is set through roles that fix size, line height and weight together:
body(16/24, 400): chat messages and the chat input.body-sm(14/20, 400): most text, fields and lists.label(14/20, 500): buttons and field labels.label-sm(12/16, 500): badges and compact labels.caption(12/16, 400): tooltips, hints and metadata.title(18/28, 600) andheading(24/32, 600): rare headings; there is no display size.
When a component lets callers override the size, keep an explicit weight class next to the
role (text-label font-medium) so a size override does not drop the weight. Placeholders
in the chat form are engraved: muted text with a 1px highlight below it in light mode and a
1px shadow above it in dark mode (the engraved utility).
Layout
Spacing follows a 4px grid. Gaps of 4 to 12px (xs to md) dominate inside controls and
lists; 16 to 32px (lg to 2xl) separate sections. Controls are 32, 36 or 40px tall
(h-control-sm, h-control-md, h-control-lg) and icons are 12, 14, 16 or 20px
(size-icon-xs to size-icon-lg). Square boxes use size-N, never a matching h-N w-N
pair, and icons use the size-icon-* roles. Inside buttons, toggles and menu items an icon is
16px (size-icon-md) unless a smaller control calls for less. The chat column is centred with
a generous bottom offset so the floating chat form never covers the last message. The desktop
sidebar is 18rem wide by default, can be resized, and collapses to a 3rem strip.
Safe areas
The page runs under the status bar and over the home indicator (viewport-fit=cover), which
an installed iPhone app always shows and a browser tab mostly does not. The insets are
--safe-area-top and --safe-area-bottom (0 where there is none). Anything pinned to a screen
edge keeps clear of them with the safe-area utilities from src/lib/styles/safe-area.css,
never a hand-written calc():
pt-safe,pb-safe: padding of just the inset, e.g. a sheet that fills the screen.pt-safe-N,pb-safe-N: a spacing step plus the inset, e.g.pt-safe-12for the chat, whose messages start 3rem below the top on a phone.pt-(--page-top): where a page with a title, like Models, Projects or Library, starts on a phone: a row below the corner controls, so the title clears both the menu key and the fade under the status bar.top-safe-N,bottom-safe-N: the same for absolutely or fixedly placed controls, e.g.top-safe-2.5for the expanded chat form's collapse button.top-(--corner-control-top),bottom-(--corner-control-bottom),right-(--corner-control-side): the phone's corner controls, like the menu key and a page's floating key. They follow the insets differently in the installed app (see Corners below).
Corners in the installed app. The status bar and the home indicator set the screen's top
and bottom apart on their own, so a corner control does not add its usual gap on top of their
insets there. At the top it sits just below the status bar (--corner-control-top, the inset
plus 0.25rem). At the bottom the home indicator is a short bar in the middle and the corners
beside it are free, so a bottom corner action ignores its inset instead of stacking above the
indicator. Its gaps from the bottom and the side are always equal, 1.75rem
(--corner-control-bottom is defined from --corner-control-side), which keeps a 56px key
about concentric with an iPhone's rounded screen corner. Only what spans the bottom edge's
middle, like a sheet's last row, clears the inset with pb-safe or bottom-safe-N. In a
browser tab the top keeps 1rem and the bottom its 1.75rem beyond the insets.
A control placed inside a padded box still needs its own top-safe-N: absolute positions
ignore the padding. Dialogs keep clear of the insets on their own (see Dialogs on phones under
Components). At the top, every route on a phone has the status-bar-fade from the root
layout: solid behind the status bar and the row of corner controls under it, fading out down to
--page-top, like the fade under the desktop tab bar, so content scrolls away under them
instead of colliding with the clock or the chat's header. A route needs no fade of its own;
what covers the whole screen, like the expanded chat form, hides it, and it fades out as the
page slides aside for the sidebar. Check
pinned content with the insets simulated (the Safe areas page in
Storybook does this), since they are 0 in a desktop browser.
Elevation & Depth
Depth is built from the matte utilities in ui/lib/ui/src/lib/styles/surfaces.css. Pick the one that
matches the role of the surface instead of combining raw shadows.
matte-glass: large resting surfaces. A translucent fill with a backdrop blur, an inner highlight, a soft drop shadow and a 1px hairline whose sides are slightly darker than its middle. The hairline is drawn on a masked::beforeso it never tints the fill. Focus inside swaps the hairline to the focus edge; the shadow stays the same. Its colours come from slot variables, andchat-form-surface,card-surface,sidebar-surfaceandinset-group-surfacepoint those slots at one component's tokens, so each component needs a single class.matte-floatandmatte-float-modal: menus, popovers, select lists, hover cards and drawers, and dialogs over the page colour. An 86% opaque panel with blur, a faint edge, a rim and a deeper shadow. The edge is a hairline ring baked into the shadow as its last layer (float-panel-edge). The panel's 1px border is its rim, the inner highlight (float-panel-highlight) right inside the ring; an inset shadow for the rim would sit inside the border instead, and the 1px between the two would draw a double edge. In light mode dialogs are solid white instead: over the dimmed page a translucent white turns grey.matte-key: buttons, selects, toggles and tabs. The matte finish: on top of the button's own fill it adds a light blur, a fill barely lighter at the top (--key-sheen, 12% white in light mode, 2% in dark) and a small drop shadow. It never changes the button colour and draws no rim of its own: everymatte-keycontrol has a border, and a rim inside it would double the edge. Nothing marks the top edge alone, so the edge looks the same all round, with no gloss.matte-key-solid: primary and danger buttons. The same sheen, fainter (--key-sheen-solid), the same blur, and an even 1px hairline in a shade of the fill drawn inside the button (--key-edge), so the width does not change. The danger key stays matte glass rather than metal: its sheen is almost none (--button-danger-sheen), and in dark mode it is a frosted, translucent red (red-500at 58%) whose edge is a soft tint of the red, never a lighter rim.elevated-control,elevated-surfaceandelevated-raised: cards, floating bars and thumbnails. An elevation token with a hairline ring baked in as its last layer, so the edge melts into the shadow and the shadow deepens in dark mode. The ring is--elevation-ring(black 5%, white 18% in dark) at--elevation-ring-width(1px). They replace a border plus a shadow; never add a border to them.matte-well: inputs, textareas and checkboxes. A shallow inset shade so fields read as recessed.matte-sheenandmatte-sheen-solid: the user message bubble and badges. An almost invisible top-to-bottom sheen, fainter on solid fills.status-lampandmatte-orbwithorb-danger,orb-warningororb-success: small status dots and the recording button. A near-flat fill barely lighter at the top and an even hairline, with no glow.
The elevation tokens are elevation-surface, elevation-control, elevation-raised,
elevation-inset and elevation-tooltip. The drop shadows are smooth stacks: a few soft
layers instead of one hard one, the closest the darkest and smallest, each further layer about
twice the offset and blur and fainter, the far ones pulled in with a negative spread, so the
shadow fades out instead of ending in a visible edge. They stay as close as upstream's
Tailwind shadows: elevation-surface reaches about 20px, like shadow-lg, elevation-raised
about 38px, like shadow-xl, and elevation-control is three tight layers reaching no further
than 4px, so buttons and other controls sit close to the page. Two softer steps sit below them: elevation-soft for the chat form,
which floats only a little, and elevation-faint for the user message bubble, which barely
lifts. The keys inside the chat form, the add key and the model selector, take elevation-key
(--chat-form-key-shadow): a 0.5px hairline all round and a 1px drop, since the control elevation's soft
spread blends into the white form; in dark it is the control elevation. Dark mode deepens the same stacks. Tailwind's own shadow-xs to shadow-2xl are
built the same way (tokens/semantic.css), each reaching about as far as Tailwind's default for
it. Every
button carries elevation-control (--button-shadow); a ghost button only while hovered. Overlays behind dialogs are surface-overlay
with a 2px blur.
Shapes
Corners are soft and consistent, set through roles: control (8px) for buttons, fields and
badges, panel (10px) for menus and dialogs, card (14px) for cards, container (16px) for
the sidebar, and surface (24px) for the chat form and message bubbles, rising to
surface-lg (32px) for the chat form on small screens. Status lamps, avatars and the round
icon buttons in the chat form are fully round.
Brand
- Logo: the llama.cpp mark, one inline SVG (
Logo) filled with the current text colour, so it follows the theme with no light and dark copies. It is sized by--size, 1rem by default: 14px in model rows, 16px in the sidebar. Colour it with a text token such asfg-defaultorfg-muted, never a raw colour. - App icons: the mark in
#111111on white, or#fafafaon#111111in dark mode (FAVICON_COLORS,THEME_COLORS). The favicon keeps a 4% margin (FAVICON_PADDING), so the logo spans 96% of it. The maskable and Apple touch icons are white squares with the logo at 67% (the generator's 30% padding); its farthest point reaches 73%, inside the 80% maskable safe zone. The PWA icons are white circles with the logo at 57% (make-icons-circular.js, 85% of the square icon). - Splash screens: white, or
#111111in dark mode, with the logo centred at 24% of the screen's shorter side (SPLASH_PADDING). - The icons and splash screens in
static/are build output ofnpm run build-pwa-assets, drawn fromlogo.svg; change the source or the constants, never the generated files.
Components
-
Buttons: six variants.
default: the solid primary button, including the chat submit button.secondary: the matte glass button, the same fill as the chat form with a faint border, also used for the chat form's Stop and Skip reasoning buttons.tertiary: a faint grey tint with a soft muted border, quieter than secondary and still a visible button; kept for low-emphasis actions that need more presence than ghost.outline: the input fill with aline-controlborder, for secondary actions in dialogs and forms.ghost: no fill until hovered, for icon buttons and quiet actions.destructive: red, for deleting and other irreversible actions.
All except ghost carry
matte-key. Sizes are sm (32px), default (36px) and lg (40px), plus square icon sizes. -
Badges: four variants with the same names:
default,secondary(a light foreground tint),outlineanddestructive, plus the soft status badgessuccess,warning,dangerandinfo. Badges are a fill or a border with the faint matte sheen and no inner rim. -
Toggles: the same corners, type, heights, padding and icon size as buttons, with square
icon-sm,iconandicon-lgsizes for icon-only toggles.defaulthas no fill until hovered;outlineborrows the outline button. Pressed toggles taketoggle-background-on. -
Button groups: joined buttons share one shadow, drawn by the group, and one border at each seam. A group separator replaces the seam border. Filled buttons draw a seam in their own text colour (
button-primary-seam,button-danger-seam) instead. -
Selection on a track: a choice that moves along a track is a recessed track with the selection raised on it, never a row of outlined buttons. The track is
surface-mutedwith the inset shade (elevation-inset); the selection is asurface-liftedchip withelevation-control, and unselected options are softened text with no fill. Tabs use the same track for their list, with the active tab raised (tabs-*); alinevariant underlines the active tab instead. The chip or underline slides between tabs in 300ms on a plain ease-out, with a stretch of at most 5% along the move that is gone by the time it lands; with reduced motion it jumps instead. The switch is the same track with a raised thumb; switched on, the track takes the primary colour. The message statistics view switcher uses the tabs tokens. -
Toggle groups: a row of keys, like an old stereo's, not a track. At rest the group is a secondary button, the same glass fill, border and shadow as a select trigger, with a
line-controlseam between keys. A pressed key turns white (surface-pressed, the lightest fill in dark mode) and sinks in under a subtle inner shadow (elevation-pressed), its label a pixel lower. While any key is pressed, the others turn grey in light mode (surface-muted) and mute their labels, so the pressed one stands out. A group is as tall as a control of its size. -
Chat form: one
chat-form-surfaceholding the input, attachments and actions. Its fill is the muted grey at 60% in light mode and 75% in dark mode. -
User message bubble: the primary colour at 5% with
matte-sheenand the very faintedge-fainthairline, so it separates from the page without a visible border. -
Sidebar:
sidebar-surface, the muted fill at 60% with no inner highlight and the ambient edge. On small screens it keeps a plainshadow-mdinstead. -
Inset groups:
inset-group-surfacegathers rows inside a glass panel, like the sidebar footer's Models, MCP and Settings, instead of a rule between them and the rows above. In light mode it is a soft white (surface-raisedat 85%) on the grey glass; in dark mode a raised fill would be darker than the glass, so it is a 3% tint of the text colour. It takes the sidebar's ambient edge, no inner highlight and only a faint, wide shade under it (0 2px 8px -4px, 8% black in light, 40% in dark), with the card radius. It reads as part of the panel: no tight contact shadow and no solid border, which make a button, and no inset shade, which makes a field. Unlike the othermatte-glasssurfaces it does not blur: it already sits on glass, and a second backdrop blur re-paints the panel's fill behind it and turns the group visibly lighter, whatever its own fill. -
Selected rows:
selected-row-surfacemarks the row a sidebar list is on: a conversation, a project or a top action, on desktop and on a phone. It is a 5% tint of the text colour, under hover's 10%, with the inset group's edge and shade, so the selected row reads as picked out rather than hovered, in both modes. It keeps the row's own radius, and hover and press fills still paint over it. -
Fields:
matte-wellwith a 1pxline-fieldoutline and the standard 3px focus ring. -
Floating panels: every menu, popover, select list, hover card and drawer uses
matte-float; dialogs usematte-float-modal. -
Chat header on phones: a chat shows its title and, under it, its working directory centred between the menu key and the context gauge, on the top fade. The directory is the folder's name (the full path is its title) and tapping it opens the directory picker, which on a phone is a drawer. A new chat has no header yet: it offers "Set working directory" in the + menu instead, and no chip sits under the form on a phone. The header steps aside with the corner keys while the expanded chat form covers the screen.
-
Dialogs on phones: below
mdevery dialog is full screen, whatever size it takes on a desktop. The sharedDialog.Contentdoes this, so a dialog sets only its desktop size and never its own phone size. Its top and bottom borders take the height of the status bar and the home indicator, transparent, so the content keeps clear of both with no change to its padding (see Safe areas). A dialog that draws its own full-screen content instead, like the attachment preview, keeps clear withpt-safe,pb-safeandtop-safe-Nitself. Alerts (AlertDialog: confirmations, renames, errors) are the exception: a short question with a button or two, they stay small and centred on a phone too. A place the sidebar opens, like Settings, MCP Servers or Servers, is no dialog on a phone at all but a page at its own route (#/settings,#/mcp-servers,#/servers), with the menu key and a title like any phone page; a desktop or tablet keeps it a dialog over the page it was opened from. -
Glass keys: a round key that floats over the page and lets it show through, like the menu and context gauge keys at a phone's top corners and the key back to a chat's bottom, is a
GlassKey(GLASS_KEY_CLASS): white glass (surface-glass), a faintline-defaulthairline, andmatte-key's blur and saturation with its small shadow, so what scrolls under it softens instead of showing sharp behind the icon. 40px at the corners, 36px over the page; its icon is a 2px-stroke glyph infg-defaulton the 24px icon grid, the context gauge's dial drawn the same way. Don't rebuild one from a ghostButtonplus classes: the button's own blur overridesmatte-key's. -
A page's main action on phones: below
mdthe action that adds to a page, like New project or New prompt, leaves the page's header for aFloatingActionButton: a round 56pxdefault(primary) key with a large shadow and only a+icon, pinned in the bottom-right corner 1.75rem from both edges (--corner-control-side,--corner-control-bottom; in the installed app beside the home indicator rather than above it, see Safe areas), where the thumb rests. It is portalled to the body, so its place on screen never depends on the page's box, and slides with the page when the sidebar opens, by the same offset and ease (--sidebar-reveal-x), taking no taps while the page is aside. The page keeps room under its last row (max-md:pb-safe-24) so the key never covers it. One per page, only for its main action; frommdup the action stays a button in the header. -
Copy feedback: a copy action turns its icon into a
fg-successcheck for 1.5s (COPY_FEEDBACK_RESET_MS), only when the copy succeeded, then back. The icon pops in with a 150ms fade and scale, skipped on first render and with reduced motion. -
Tooltips: the inverse of the page, the primary colour with a faint inner rim.
-
Status: server, model and MCP connection states use the status lamps, never coloured text alone.
Do's and Don'ts
- Do keep fills flat. Gradients, if any, must be barely perceptible; a visible gradient makes the UI look like a 2000s interface.
- Do keep edges faint. At rest a hairline should blend in; on focus it should be noticeable but never strong.
- Do keep the shadow the same on focus. Focus is shown by the edge and the focus ring, not by lifting the surface.
- Do use the status colours only for status. Buttons keep their neutral colours, and the submit button stays black in light mode and white in dark mode.
- Do read component tokens in components, semantic tokens in shared styles, and primitives only in semantic tokens.
- Do add a new colour as a primitive first, then give it a semantic name before any component uses it.
- Do give motion a job: show where something went or what changed, like a selection sliding to its new place. A barely visible stretch along a move, or a settle past the target by a pixel or two, can make that feel physical; keep it under about 5% and 300ms, and drop it entirely with reduced motion. Never let a bounce carry something past the edge of its container, such as a tab indicator past its track; there, slide without one. If you notice the effect itself rather than the change it shows, it is too much.
- Do reach for the surface utility that matches the component instead of adding raw
shadow-*,border-*andbackdrop-blur-*combinations. - Don't use Tailwind's palette classes (
text-amber-500,bg-green-500/10) for meaning in new code; use the semantic tokens. Some older components still do and are being moved over. - Don't introduce new accent hues (such as a blue submit button) without a design decision.
- Don't put white rims or highlights on large ambient containers such as the sidebar.
- Don't animate for decoration: no motion on things that did not change, no bounces on entrances, and nothing that delays the user.
- Don't stack two glass surfaces with blur directly on top of each other.
- Don't give a dialog its own size on a phone: every dialog is full screen there. Only alerts stay small and centred.
- Don't put more than one floating key on a phone page, or use one for anything but the page's main action.
- Don't lift a bottom corner action above the home indicator's inset in the installed app,
or give it a different gap from the bottom than from the side: the corners beside the
indicator are free, and
--corner-control-bottomand--corner-control-sidekeep the two gaps equal.