Foundations
Voice & Tone
The system reads as precise, calm, and engineered. It never oversells, never fakes progress, and never dresses a machine signal as prose. Three habits carry the voice: the mono labels, the case rules, and an insistence on telling the truth about state.
Mono-label tells
Two small marks make anything read as part of the system.
About
Slash eyebrow
/// + spaced uppercase mono above every section. Names the block; never a sentence.01
Bracket index
Padded
[ 01 ] enumerators on cards and rows — the system counting itself.Microcopy case
Case is not decoration — it signals whether a thing acts or merely reports. Match the control to the case, never the reverse.
UPPERCASE actions
Buttons, chips, tabs: short verb phrases, no trailing punctuation — “Deploy service”, “Export ledger”.
Deployed
Sentence-case status
Badges, callouts, banners describe a state in plain sentence case — “Deployed”, “Payment pending”.
2026-07-03 · 42ms
As-typed metadata
Ids, regions, and timestamps appear exactly as the machine emits them.
Honest states
Loading, empty, error, and pending are first-class — never faked, never hidden behind a spinner that lies. A button in flight says so and disables itself; an empty result says it is empty and offers the next step; an error names what failed.
Payment pendingQueued
No services
Nothing deployed yet
This project has no running services. Deploy one to see it here.
Do
- Say what is happening: “Deploying…”, not a bare spinner.
- Give empty states a next action, not just a shrug.
- Name the failure and how to recover in error states.
- Keep status sentence-case and honest — no exclamation marks.
Don’t
- Don’t show fake progress or optimistic success before it is real.
- Don’t hide errors to keep the UI looking tidy.
- Don’t UPPERCASE a status or sentence-case an action label.
- Don’t pad microcopy with marketing adjectives.