Hasura — decoded design system
Hasura's design system, decoded live by Mozaika: measured color roles, type scale, buttons with real hover/focus states, motion and the brand's own tokens.
This is a static, crawlable rendering for search & AI engines. The interactive version — filters, live decode console, copy & export — is at https://mozaika.design/decode/hasura.io.
Decoded design system
Hasura's decoded design system: background #FFFFFF, text #0A0A0A, accent #1863DC, link #1863DC, primary #1863DC; type scale h1 40px / h2 28px / body 12px; 4px spacing base; 8px base radius. The single interactive/action color is #3B5CA0 — used only on interactive or must-notice elements (buttons, links, key highlights), never on large fills.
Color roles
| Role | Value |
|---|---|
| bg | #FFFFFF |
| surface | #F0F0F0 |
| border | #DADADA |
| text | #0A0A0A |
| text_muted | #676767 |
| primary | #1863DC |
| accent | #1863DC |
| link | #1863DC |
| secondary | #000615 |
| button_bg | #3B5CA0 |
| button_text | #FFFFFF |
Using these colors
- Action color
#3B5CA0— the single interactive color; only on things you click or must notice, never large fills. primary,accent,linkare all#1863DC— one role, not several (the action color).- accent
#1863DC— accent for emphasis — keep it rare on the page. - secondary
#000615— optional secondary accent — LOW decode confidence; use rarely (a status color or a single decorative moment) or omit it entirely. Prefer one accent unless the reference clearly shows two.
Typography
- Heading: Inter
- Body: Inter
- Mono: __JetBrains_Mono_3c557b
- h1: 40px
- h2: 28px
- body: 12px
Spacing
- base unit: 4px
- scale: 6px, 8px, 12px, 14px, 16px, 17px, 18px, 24px, 27px, 40px
Radii
- base: 8px
- button: 2px
Shadows (elevation)
- card:
rgba(0, 0, 0, 0.08) 0px 2px 6px 0px
Motion
Micro-interactions run at 150ms (dominant) with linear.
- durations: 150ms · 300ms
- easings:
linear·ease-in-out
Native design tokens
| Token | Value |
|---|---|
--radius | 0.5rem |
Button states (measured)
- primary focus: outline
2px solid rgb(24, 99, 220)
Layout (measured)
- nav: 60px
Overlay recipe (measured)
dialog panel: #FFFFFF · radius 6px
Input (measured)
height 48px · radius 8px · focus ring 2px solid rgba(0, 0, 0, 0)
Responsive (measured)
- breakpoints: 352px · 400px · 425px · 576px · 600px · 768px
- mobile (390px): hero 32px · nav inline
Install it
Drop this measured system into any shadcn/Tailwind project in one command:
npx shadcn add mozaika.design/r/decode/hasura.io
registry item · or query it over MCP: get_design_system("Hasura")
Export: DESIGN.md
# Hasura — Design System > light, modern, medium, tailwind — deep decode (measured live) ## Colors | Role | Value | |------|-------| | bg | `#FFFFFF` | | surface | `#F0F0F0` | | border | `#DADADA` | | text | `#0A0A0A` | | text_muted | `#676767` | | primary | `#1863DC` | | accent | `#1863DC` | | link | `#1863DC` | | secondary | `#000615` | | button_bg | `#3B5CA0` | | button_text | `#FFFFFF` | **Using these colors** - **Action color** `#3B5CA0` — the single interactive color; it appears only on things you click or must notice (buttons, key highlights), never on large fills or backgrounds. - `primary`, `accent`, `link` are all `#1863DC` — one role, not several. - **accent** `#1863DC` — accent for emphasis — keep it rare on the page. - **secondary** `#000615` — optional secondary accent — LOW decode confidence; use rarely (a status color or a single decorative moment) or omit it entirely. Prefer one accent unless the reference clearly shows two. - **Page coverage** (full-page screenshot pixels): `#F5F5F5` 63.1% · `#ACB7D4` 20.9% · `#C7E4D7` 6.6% · `#A4E3B0` 5.7% ## Typography - Heading: **Inter** - Body: **Inter** - Mono: **__JetBrains_Mono_3c557b** _(measured)_ | Role | Size / weight · line-height · tracking | |------|------------------------------------------| | hero | 40px / 300 · lh 44px · tracking -1.92px | | h2 | 28px / 600 · lh 42px · tracking -0.84px | | h3 | 24px / 400 · lh 36px · tracking -0.84px | | body | 12px / 400 · lh 16px | - Weight ladder: 300 · 400 · 500 · 600 — use these exact measured weights, not the 400/600 defaults. > **Fonts —** Inter — free, on Google. ## Spacing - base unit: 4px (inferred from the measured scale) - measured scale: 6px, 8px, 12px, 14px, 16px, 17px, 18px, 24px, 27px, 40px — snap all gaps/padding to these ## Radius - base: 8px - button: 2px - card: 6px - sharp: 2px ## Buttons | Button | Fill / text | Border | Radius | Padding | Font | Shadow | |--------|-------------|--------|--------|---------|------|--------| | primary | `#3B5CA0` / `#FFFFFF` | 2px solid rgb(59, 92, 160) | 2px | 8px 27px 8px 27px | 500 14px | none | | secondary | `rgba(0, 0, 0, 0)` / `#030712` | 1px solid rgb(3, 7, 18) | 40px | 6px 14px 6px 14px | 400 14px / -0.28px | none | **States (measured, not guessed)** - primary focus: outline `2px solid rgb(24, 99, 220)` - secondary hover: background `#030712` · color `#FFFFFF` ## Shadows (elevation) - card: `rgba(0, 0, 0, 0.08) 0px 2px 6px 0px` ## Motion - durations: 150ms (dominant) · 300ms - easings: `linear` (dominant) · `ease-in-out` Micro-interactions use the dominant duration + easing; nothing on the page animates slower than the longest duration above — don't invent springier motion. ## Their own tokens (verbatim from :root) | Token | Value | |-------|-------| | `--radius` | `0.5rem` | Prefer these names when extending their system — it's the brand's actual vocabulary. ## Layout (measured) - nav: 60px ## Motion choreography (measured) - overlay dialog (auto-opened): panel #FFFFFF · r 6px Rebuild the timeline, not just the durations — order, delays and staggers above are the choreography. ## Components (measured) - input: h 48px · r 8px · border 1px solid rgba(222, 222, 222, 0.2) · bg rgba(0, 0, 0, 0) · placeholder #6B7280 - focus ring: `2px solid rgba(0, 0, 0, 0)` — this exact construction, don't invent your own - link: #1863DC · underline ## Responsive (measured) - breakpoints: 352px · 400px · 425px · 576px · 600px · 768px - mobile (390px): hero 32px · body 16px · nav: inline ## How to apply Paste the Tailwind `@theme` (or CSS variables) as your base, then build each section to its spec — verify every color, radius, and font against these tokens. Hover/focus states, shadows and motion timings above are measured from the live page — match them exactly, don't re-guess them.
An automated reading of Hasura's publicly-visible CSS (colors, fonts, spacing, motion) — not affiliated with hasura.io. No screenshots stored. Removal requests: hello@mozaika.design.