Docs navigation
Design

Interface theme template

Designs is rolling out gradually
The Design tab appears on an agent's page as it is enabled for your workspace. If you do not see it yet, email help@brainbaselabs.com to ask for it.

A design is a spec an agent follows when it builds something people look at: an interface, a slide deck or a document. Give an agent a design and the dashboards it builds match your organization's site, or any site you point it at, instead of the plain Brainbase look. This page explains designs briefly and gives you a template to paste in when you write one by hand for an interface.

What a design is

An agent's designs are listed in the Design tab on the agent's page. Each one has a name and a spec, and the agent picks the one that fits the work it is doing. A design comes from one of two places.

  • From a website: enter a public page's address and Taste Labs reads the site and pulls out its brand: colours, type, components and tone. The design is named after the site and takes a few minutes to extract. You can then edit the brand name, signature, tone, colours and fonts it found.
  • Written by hand: describe the colours, type, components and tone in markdown. It is ready the moment you save it. The template below is for this.

Either way, the people who use the dashboard see only the result. A design is part of how the agent builds, not something a viewer can see or change.

Create a design

  1. Open the agent's page and choose the Design tab, then New design.
  2. Choose a source. From a website asks for the site's address, such as northwind.example; Write by hand opens a markdown editor with Edit, Split and Preview panes, the same as the Instructions tab.
  3. For a hand-written design, give it a name people will recognise in a request, such as Northwind Main, paste the template below, and change the values to yours.
  4. Choose Create design (or Extract design for a website). The design opens on its own page. An extracted one shows its progress there and updates when it is done.
Limits and cost
An agent holds up to 50 designs. A name is up to 200 characters and a hand-written spec up to 200,000, far past any real style guide. Extracting a design from a website uses credits and reads public pages only: not localhost, a private network, or a page behind a login. Writing one by hand uses nothing. You need permission to edit the agent to add, change or delete its designs.

The theme template

Every interface is styled through a set of CSS variables, the theme tokens, in its app/globals.css: surfaces, borders, text, one accent, status colours, type, spacing and corners. The agent restyles a dashboard by pointing those tokens at your values, so the template names the token beside each colour. That is what makes it an interface theme rather than a general brand guide: the agent knows exactly where each value goes. Copy it into Write by hand and replace the Northwind values with your own. Delete any section you do not have an opinion on; the theme's defaults fill the gap.

Northwind interface thememarkdown
# Northwind interface theme

Use this design for interfaces (dashboards). Keep the house rules: plain,
readable at a glance, summary before detail, every control visible. Apply
the values below and nothing from the site's marketing pages.

## Brand

- Name: Northwind
- Match this site: https://northwind.example
- Signature: warm paper surfaces, hairline borders, one deep blue accent,
  no decoration.

## Colors

Set every colour as a token in `app/globals.css`, light then dark. Do not
write a colour anywhere else; name the token.

| Role | Token | Light | Dark |
| --- | --- | --- | --- |
| Page background | `--bb-surface-sunken` | #F5F5F4 | #14120B |
| Panel and card | `--bb-surface`, `--bb-surface-raised` | #FFFFFF | #1A1810 |
| Hover | `--bb-surface-hover` | #EFEEEA | #201E15 |
| Selected | `--bb-surface-selected` | #E7E5E0 | #2C291F |
| Border | `--bb-border` | #E2E0D8 | #2C291F |
| Strong border | `--bb-border-strong` | #D4D1C9 | #45413A |
| Text | `--bb-text` | #1C1917 | #F4F3EC |
| Muted text | `--bb-text-muted` | #635F54 | #A9A596 |
| Text on accent | `--bb-text-inverted` | #FFFFFF | #14120B |
| Accent: links, focus, primary button | `--bb-accent` | #1E3A8A | #93B4FF |
| Accent hover | `--bb-accent-hover` | #172E6E | #B4CBFF |
| Accent tint | `--bb-accent-quiet` | #E8EDF8 | #1E2740 |
| Chart series 1 to 4 | `--bb-viz-1` to `--bb-viz-4` | #1E3A8A, #F97316, #38BDF8, #7A5EA8 | #93B4FF, #FB923C, #7DD3FC, #A78BFA |

Status colours (idle, running, success, warning, danger) keep the theme's
values and mean a conversation's state and nothing else. Every text colour
must reach 4.5:1 contrast on its surface in both themes, and every chart
series at least 3:1: lighten any series that disappears on the dark
surface rather than keeping the light value.

## Typography

- Headings: Georgia, 600, sentence case, letter-spacing -0.02em
- Body and controls: Inter, 400, 14px / 1.5 (`--bb-text-base`)
- Data (ids, numbers, timestamps): JetBrains Mono, tabular numerals
  (`--bb-font-mono`)
- Load a web font only if the site does; otherwise keep the system stack.

## Shape and spacing

- Corners: 6px on panels, inputs and buttons (`--bb-radius-md`); the
  primary button is a pill (`--bb-radius-pill`)
- Borders: 1px hairlines. No shadows, no gradients.
- Spacing on a 4px step. Page column up to 62rem wide.

## Components

- Primary button: solid accent with inverted text. At most one per screen.
- Secondary button: hairline outline, transparent, border darkens on hover.
- Links: text colour, underlined in the border colour, accent on hover.
- Tables: small muted sentence-case headers, hairline rows, no stripes,
  numbers right-aligned in mono.
- Status: a dot in the status colour beside the word.
- Empty state: one muted sentence, no illustration.

## Light and dark

Light is the default and dark follows the viewer's system. Both must
read; check each in Preview before publishing.

## Tone

- Short, plain, sentence case. No exclamation marks, no emoji.
- Labels are nouns ("Open conversations"); buttons are a verb and its
  object ("Publish", "Ask the agent").

## Do not

- Bring over the site's hero images, illustrations or animation.
- Use a colour that is not a token above.
- Hide a control behind hover or a gesture.

Fill it in from your site

Most of the values come straight off the site you want to match. Open it beside the editor and work down the template.

  • Surfaces and borders: the page background, the card colour, and the line between them. Pick the dark set from the site's dark mode if it has one; otherwise darken the same hues and keep the same relationships.
  • Text: the body text colour and the quieter colour used for captions and metadata.
  • Accent: the one colour the site uses for links and its main button. A dashboard uses it for focus, links and the primary action, so pick the one that stands out, not a decorative one.
  • Chart colours: up to four. The first is the one that matters; the rest are used in order and never cycle.
  • Type: the heading and body families and weights, and whether the site loads a web font. Numbers and ids are always monospace on a dashboard, so name a mono family only if the site has one.
  • Corners and shadows: how rounded the site's buttons and cards are, and whether it uses shadows. The template keeps hairlines and no shadows; change that line if the site is softer.
Start from an extraction instead
If you would rather not read the values off the site yourself, create the design From a website. Once it is ready, its page shows the brand, colours and type Taste Labs found, each editable in place, and the agent maps them onto the same tokens when it builds. You can keep both: an extracted design for the brand and a hand-written one for the rules a dashboard should follow.

How the agent uses it

While an agent with at least one ready design builds an interface, it can read the agent's designs and follows the one that fits. If the agent has several, name the one you want in the build conversation: "Build this in the Northwind Main design." Ask for the theme in the same message as the dashboard, or afterwards as a change; either way the agent writes the tokens into app/globals.css, commits a version, and the build shows in Preview as usual. Look at it in both light and dark before you publish.

Designs reach the agent on the same harnesses that can build interfaces: Kafka (kafka_cloud), Claude Code, Codex, Qwen Code and OpenCode. An agent on any other harness cannot build dashboards, with or without a design.

Edit or remove a design

Open a design from the Design tab. A hand-written design is edited in the same panes it was written in; an extracted one can be renamed, and its brand name, signature, tone, colours and fonts changed in place. Choose Save changes when you are done, or Discard to drop the edit. A changed design applies to the next thing the agent builds; what is already published stays as it is until you ask for a new build.

Delete removes the design and the agent stops using it. Published dashboards keep the styles already written into their source.