Home
DESIGN.mdStar on GitHub
// autonomous validation

Autonomous validation for the AI era

Ship at AI speed, confidently — the CI/CD platform trusted by 2M+ developers for production-ready software.

Colors
Brand
green#00DB74Passed, primary
blue#2152E5Running, links
blue-bright#0055FFHero links
green-tint#C4EDCFSuccess fills
Build status
success#00DB74Passed
running#2152E5In progress
on-hold#DD9F54Needs approval
failed#CC4242Failed
Surfaces
terminal#161616Page bg
midnight#1C273APanels
slate#2E3C52Raised / hover
fog#EDEDEDLight neutral
Typography — Space Grotesk · Inter · Roboto Mono · Silkscreen
display / mega
Space Grotesk · 700
97% faster test runs
52px700
heading
Inter · 600
Ship at AI speed, confidently
24px600
body
Inter · 400
Any app, deployed anywhere, at any scale.
15px400
mono
Roboto Mono
git@main · a1f9c02 · deploy-prod · 2:14
13pxmono
pixel / label
Silkscreen
// WORKFLOWS
11pxpixel
Components
Buttons
Status badges
passed running
on hold failed
Signature — Workflow graph
circleci/frontend main a1f9c02 · "chore: bump smart test splitting"
build-test-deploy 0:00
Click Rerun workflow to stream jobs through queued → running → passed. The deploy-prod job holds for manual approval — click Approve to release it.
Guardrails
DO
Use #00DB74 as the brand green — dull legacy greens are retired.
Keep status colors strictly semantic: green passed / red failed / blue running / bronze on-hold.
Put branch names, SHAs, job names, and durations in monospace.
Pulse running jobs; make failed jobs impossible to miss.
Use black text on the green button (green is too bright for white).
DON'T
Don't use the Morph pastel gradient inside product UI — hero only.
Don't put white text on #00DB74.
Don't repurpose build-status colors for decoration.
Don't hide duration on completed jobs.
Don't set body copy in the pixel face — short uppercase labels only.