design · brand at the interface

Make AI worth using.

Software is for humans, even when it's AI. Brand is the difference between using it and choosing it. The interface decides which one yours is, every time someone opens it. You deserve a team that actually cares.

We're the product, brand, and system partner for AI teams turning working AI into a product worth choosing and scaling.

Everything below is live. This page, this site, every component and interaction you see — it's all running on FixBroken OS, the same design system methodology we'd build for you. Not a mockup. Not a case study. The actual system, in production.

01 / stance

Brand isn't a logo. It's the product opening.

Every screen, flow, word, and component is a decision about who you are. We make those decisions intentional, coherent, and unmistakably yours.

02 / approach

From brand strategy to shipped pixels.

Design systems, component libraries, interaction rules, motion, UX engineering. The taste calibrates to the brand. The system survives your engineers.

03 / range

Calibrated to your brand. Not copied from someone else's.

Founder-mode gets edge. Enterprise gets gravity. Consumer gets velocity. The aesthetic flexes. The discipline stays.

04 / system

One CSS file. Entire product covered.

Tokens, components, responsive breakpoints, accessibility. One import. No Figma handoff that rots. Living code your team ships with on day one.

05 / intelligence

Your LLM ships on-brand without being told twice.

Agent instructions, voice rules, banned behaviors, component inventory. The AI doesn't guess your brand — it knows it.

06 / scale

One OS, many faces. No forks.

Sub-brands, product lines, client surfaces — they all load the base system and swap tokens. Multi-tenant by architecture, not by accident.

07 / toolchain

The system enforces itself.

Voice linter, design audit, manifest validator, pre-commit hooks. Brand compliance isn't a meeting — it's a build step.

08 / proof

This site runs on it.

Everything you're looking at — every page, component, interaction — is FixBroken OS in production. Not a demo. The real thing.

The system · live

Tokens, type, components — running right now.

Palette · 7 signal colors

Black canvas. Controlled neon. Every color is a CSS custom property - override one token and the whole system shifts.

Type · two families, no compromise
sans Inter - human copy
mono JetBrains Mono - system
scale 10 · 11 · 12 · 13 · 14 · 15 · 16 · 18 · 20 · 24 · 32 · 48 · 64 · 88
Components · live from the system
signal flagship alive default
system online
fixbroken-os / design / proof
npm run build:system
compiling 95 tokens → fixbroken-os.css
29 components registered
115 classes exported
build · complete
ready to ship
Panels · four variants
.fb-panel · default

Subtle border, slight lift. The workhorse.

.fb-panel--signal

Signal-tinted border for emphasis.

.fb-panel--matrix

Matrix-tinted. Alive, runtime, active.

Spacing · 4px base grid
--fb-s-14px
--fb-s-28px
--fb-s-312px
--fb-s-416px
--fb-s-624px
--fb-s-832px
--fb-s-1664px · section
--fb-s-2496px · hero
Forms · inputs feel like terminal fields
Effects · MCP cone

Signal in. Clarity out.

tokenz · claude runtime · light cycles awaiting signal…
8s
- -
42s
- -
80s
- -
800s
- -
8000s
- -
80ks
- -
800ks
- -
lifetime - proj/day - rate -
Voice · how the system talks
USE
  • Run the signal
  • Open the console
  • Trace the pattern
  • Send the signal
  • See what broke
AVOID
  • Get started today
  • Supercharge your workflow
  • Unlock AI-powered insights
  • Revolutionize your [anything]
  • Next-gen / cutting-edge

Take ours apart.

The system running this page — tokens, brand rules, agent instructions — packaged as a zip. See how a real design system ships before we build yours.

fixbroken-os-kit.zip · system.css + brand.md + manifest.json + CLAUDE.md · 21 KB

Download kit
Deliverables · what you walk away with

Files, not theater.

The work ships as a real system: tokens, components, rules, and production-ready patterns your team imports on day one. Delivery isn't the pitch. It's the proof the design survives contact with engineering.

01 system.css

Complete design system — tokens, components, responsive breakpoints, accessibility — as a single CSS file.

02 brand.md

Voice, palette, principles, and an explicit avoid list — readable by humans and machines.

03 manifest.json

Machine-readable map of every token, component, and rule — structured for toolchains, CI, and LLMs.

04 CLAUDE.md

Agent instructions so your LLM ships on-brand every session without being told twice.

05 style-guide/

Living reference page generated from the CSS — auto-updates when the system changes.

06 overrides.css

Multi-tenant override architecture — one OS, many faces, no forks.

07 toolchain/

Voice linter, design audit, manifest validator, and pre-commit hooks — the system enforces itself.

08 governance/

SDLC rules, architecture decisions, QA checklists, and agent instructions — operational docs that run the shop.

Every file in this list exists in the repo you're looking at right now. We ship what we use.

How we work

Four rules. Everything else follows.

01
Signal over spectacle
Every pixel earns its place. If it doesn't help the user understand state, hierarchy, or next action - it gets cut.
02
Systems, not pages
We design the tokens, components, and rules that generate screens. Your third page should take ten minutes, not ten days.
03
Brand becomes UI
Tokens carry the brand. Components carry the voice. No translation layer between strategy and what users see.
04
Human-readable intelligence
Executive, engineer, operator, customer - they all need to feel at home. Information-dense without being intimidating.
Signal · start here

Bring something broken.

A brand that doesn't scale. A product that looks like five teams built it. A design system that exists in theory but not in code. We've seen it. We fix it.