taste:
id: terminal-bay-devtools
name: Terminal Bay — Dev tools
summary: >-
A technical, minimal development interface defined by flat-bordered surfaces, crisp typography,
and high-contrast vivid green accents.
app_type: WEB_APP
project_types:
- saas
styles:
- technical
- minimal
industry: software
aesthetics:
- technical
- minimal
tags:
- technical
- minimal
theme:
default_mode: LIGHT_MODE
palette_note: >-
Only the 500 anchor is provided per palette; the full 17-step ramp (100-900) is derived from
it by the system's heuristic shade tool.
palettes:
neutral:
'500': '#686D76'
description: Observed cool-tinted slate grey neutral scale
brand:
'500': '#00FFC0'
description: Vivid Terminal Bay cool-green brand color
danger:
'500': '#DC3545'
warning:
'500': '#FFC107'
success:
'500': '#00FFC0'
info:
'500': '#3E4C5C'
accent:
'500': '#6DFFDB'
colors:
background:
light: '#E0E6EB'
dark: '#0A0A0B'
foreground:
light: '#0A0A0B'
dark: '#ECEDEE'
card:
light: '#ECEDEE'
dark: '#212326'
card-foreground:
light: '#0A0A0B'
dark: '#ECEDEE'
popover:
light: '#ECEDEE'
dark: '#212326'
popover-foreground:
light: '#0A0A0B'
dark: '#ECEDEE'
primary:
light: '#00A980'
dark: '#00FFC0'
primary-foreground:
light: '#0A0A0B'
dark: '#0A0A0B'
secondary:
light: neutral/200
dark: neutral/700
secondary-foreground:
light: neutral/900
dark: neutral/100
muted:
light: neutral/200
dark: neutral/800
muted-foreground:
light: neutral/700
dark: neutral/400
accent:
light: brand/200
dark: brand/800
accent-foreground:
light: neutral/900
dark: brand/100
destructive:
light: '#A91D22'
dark: '#A91D22'
destructive-foreground:
light: '#FFFFFF'
dark: '#FFFFFF'
border:
light: '#3E4C5C'
dark: '#3E4C5C'
input:
light: '#3E4C5C'
dark: '#3E4C5C'
ring:
light: brand/500
dark: brand/500
chart-1:
light: brand/500
dark: brand/500
chart-2:
light: neutral/600
dark: neutral/400
chart-3:
light: warning/500
dark: warning/500
chart-4:
light: danger/500
dark: danger/500
chart-5:
light: info/500
dark: info/500
sidebar:
light: neutral/100
dark: neutral/900
sidebar-foreground:
light: neutral/900
dark: neutral/100
sidebar-primary:
light: brand/500
dark: brand/500
sidebar-primary-foreground:
light: neutral/900
dark: neutral/900
sidebar-accent:
light: neutral/200
dark: neutral/800
sidebar-accent-foreground:
light: neutral/900
dark: neutral/100
sidebar-border:
light: '#3E4C5C'
dark: '#3E4C5C'
sidebar-ring:
light: brand/500
dark: brand/500
radius:
base:
value: 12px
description: Matches measured lg corner radius (12px); sm renders at 4px.
shadows:
xs:
value: none
sm:
value: none
md:
value: none
lg:
value: none
xl:
value: none
gradients:
brand_wash:
value: 'linear-gradient(135deg, #00FFC0 0%, #00A980 100%)'
fonts:
sans:
family: Inter
description: UI body and controls
display:
family: Space Grotesk
description: Headings and metrics
mono:
family: JetBrains Mono
description: Code and telemetry data
typography:
hero:
font: display
size_px: 36
line_height_px: 44
weight: 700
letter_spacing_em: 0
transform: none
title:
font: display
size_px: 24
line_height_px: 28
weight: 700
letter_spacing_em: 0
transform: none
heading:
font: display
size_px: 20
line_height_px: 24
weight: 700
letter_spacing_em: 0
transform: none
body:
font: sans
size_px: 13
line_height_px: 20
weight: 400
letter_spacing_em: 0
transform: none
caption:
font: sans
size_px: 12
line_height_px: 18
weight: 400
letter_spacing_em: 0
transform: none
label:
font: sans
size_px: 14
line_height_px: 21
weight: 700
letter_spacing_em: 0
transform: none
overline:
font: sans
size_px: 12
line_height_px: 16
weight: 700
letter_spacing_em: 0.05
transform: uppercase
style_guidelines:
hierarchy:
title: Hierarchy
recommendations:
- >-
Utilize stark weight contrast between bold Space Grotesk headers and clean Inter body copy
to anchor user scanning.
- >-
Employ high-saturation brand green exclusively for active states and primary workflow
triggers.
layout:
title: Layout
recommendations:
- >-
Separate complex data views using solid thin borders rather than relying on depth shadows
or background shifts.
- >-
Align interactive elements to a strict horizontal grid to minimize eye fatigue during long
monitoring sessions.
components:
title: Components
recommendations:
- >-
Set primary buttons to an explicit 36px height with flat solid backgrounds to ensure
consistent targets.
- >-
Apply a sharp 4px radius to interactive inputs and a wider 12px radius to container cards
to frame content clearly.
typography:
title: Typography
recommendations:
- >-
Use Space Grotesk for metrics and section headers to inject technical character into the
interface.
- >-
Render all status labels and body text in highly legible Inter to maximize long-term
reading comfort.
color_and_effects:
title: Color & Effects
recommendations:
- >-
Avoid soft drop shadows entirely, opting instead for crisp 1px borders to define all
surfaces.
- >-
Reserve the vivid green accent for active indicators, using cool muted slates for default
states.
quality_bar:
title: Quality Bar
checks:
- id: contrast-compliance
label: Contrast Compliance
recommendation: >-
Confirm all primary text maintains at least a 4.5:1 contrast ratio against the cool grey
backgrounds.
- id: border-consistency
label: Border Consistency
recommendation: >-
Verify all container dividers and input borders utilize the exact 1px width with the slate
grey color.
- id: font-pairing
label: Font Pairing
recommendation: >-
Check that Space Grotesk is strictly reserved for display headings and Inter handles all
body text.
- id: radius-application
label: Radius Application
recommendation: >-
Ensure action buttons utilize the sharp 4px border radius while outer frames use the 12px
layout radius.
active_remix:
mode: light
brand: '#00FFC0'
display_font: Space Grotesk
shape: system
depth: system
spacing: system
spacing_value: null
craft: >
# Craft (universal core + conditional craft)
How to apply this design system well. These rules contain no brand look of their own — all
per-system character comes from the tokens and taste notes above; this section only governs
how they are composed. **Precedence:** the design system above is the authority on how things
look — where its own notes conflict with a rule here, the design system wins. And the user's
request is the authority on what the screen IS — notes above that describe the source
product's screens (workspaces, dashboards, panels) are its aesthetic heritage, not an
instruction to build that kind of screen.
## Universal — applies to every screen (screen-agnostic craft)
- **Surface definition.** Every container is visually separable from what it sits on — at least
one
honest edge cue: a hairline border, a ≥4% tonal step from its parent, or a real shadow. Never a card
whose fill matches its section with no border; never nested surfaces that dissolve together.
- **Accent discipline.** The brand/primary color is a scalpel, not paint: spend it on the primary
action, the active/selected/focused state, and at most **one** brand or data highlight per screen.
Everything else rides neutral background / card / muted / border tokens. A screen flooded with brand
color reads unfinished, not bold.
- **Restraint ledger.** Beauty is also what you don't do: at most one glow and two gradient
directions
screen-wide; decoration only where content doesn't reach; no ornament between a heading and its own
action. Every decorative element must answer "what does this make clearer or more felt?" — if the
answer is "nothing," remove it.
- **Type with intent.** The measured faces/scale are fixed; character comes from *usage*, and the
move
must fit the surface — a marketing page earns a dramatic display move; a working screen earns a
crisp, tight, legible hierarchy at UI scale (display-hero type on a dense tool is a smell). Chrome
and wayfinding are never display type; data numerals are tabular (mono or sans), never the
decorative face. Headings stay roman — italics live as emphasis inside running text, not as
display styling (unless the system's own type says otherwise).
- **Anti-default.** If the screen could pass for a generic template with the colors swapped, it is
not
done. Make the brand unmistakable through the accent's *use*, the type, the radius + density, and
**one** signature detail — never by importing another surface's clichés.
- **Honest content.** Never invent proof — no made-up adoption counts, growth percentages,
testimonials, client logos, or awards. Use the user's real content, a neutral placeholder, or
leave the element out and let the layout carry it. Never hand-draw fake browser bars, phone
frames, or editor chrome around content — show the content itself, or nothing.
- **Interaction integrity.** Buttons, links, tabs, and nav labels never wrap to two lines; display
headlines wrap cleanly, never clipping mid-word; nothing overflows horizontally at any width;
keyboard focus gets an instant, clearly visible ring.
- **Token fidelity.** Every design value comes from a token: colors, radii, shadows, and fonts
from
the system's variables — never a literal hex, a hand-picked shadow, or a substitute font. For a
translucent or composited value (a scrim, a glow, a hairline over a fill), derive it from a token
(an opacity modifier or color-mix), never a literal rgba. If the system specifies square corners and
a hard shadow, the screen shows square corners and that hard shadow — not a rounded, soft substitute.
## Conditional — apply ONLY the layer that matches the screen the user asked for
**First name the screen honestly from the user's prompt.** Then apply the matching guidance. Do
not
cross layers, and **do not add elements from a layer the screen doesn't call for** — a screen that
is
not a data view must not sprout KPI tiles, charts, filter bars, or data tables to satisfy a
template.
- **If it's a data / dashboard / admin / table view:** density done well (comfortable rows, tight
control clusters, one spacing rhythm); a populated working state (real rows/cards, not empty feature
boxes); tables with aligned tabular numerals, status as badges, row hover, one visible selected row,
and control states that agree with the data shown. KPI tiles, *if the screen has them*, are
value + label + delta. **At most one** chart, of a real metric for this domain, token-colored and
axis-labeled — never a decorative sine wave or filler sparkline. Exactly one unambiguous primary
action.
- **If it's a focused task / tool / player / capture / monitor / form / wizard (not a data
view):**
the screen's real job dominates the frame; chrome recedes. Honor the screen's own nature — a player
looks like a player, a monitor like a monitor, a form like a form — with the design system's color,
type, radius, and depth applied to *those* elements. **No dashboard furniture**: no KPI tiles, no
charts, no data tables, no filter chrome unless the task itself is about that data. Real-time or
safety-critical readouts get calm, unambiguous, high-legibility treatment over decoration.
- **If it's a marketing / landing surface:** editorial art direction belongs here — section rhythm
(modulate surface temperature, density, and scale; one oversized moment; at least one full-bleed
band) and considered visual treatments. Never put this on a working app screen.
- **Mobile:** follow the platform's native idioms for the screen's type (e.g. an app screen:
compact
top bar, one focused column, a bottom tab bar, ≥44px targets, safe areas) — the same conditional
rules above still decide what content belongs.
## Imagery (universal)
- **Imagery is content, not decoration** on working screens: images are data (covers, products,
avatars, places) in purposeful containers, one consistent treatment across siblings — never a lone
photo floating in a box, never marketing's decorative fades on a work screen. When a moment needs
atmosphere, build it from the token system (tinted panels, token gradients, geometry).
