# Dune — Design System
> Normalized blockchain datasets across stablecoins, tokenized assets, payments, trading, and lending. Delivered anywhere you work — warehouse, MCP, Data Hub, API, and connectors.
- **Canonical:** https://uiuxskills.com/library/dune
- **Source:** https://dune.com/
- **Category:** Fintech & Crypto
- **Compatible tools:** claude, cursor, lovable, figma-make
- **Coverage:** 80%
- **License:** MIT
- **Last updated:** 2026-10-28T19:58:06.788Z

---

---
version: alpha
name: Dune
tagline: The industry standard for onchain data
description: >-
  Normalized blockchain datasets across stablecoins, tokenized assets, payments, trading, and
  lending. Delivered anywhere you work — warehouse, MCP, Data Hub, API, and connectors.
tone: professional
color-scheme: light
colors:
  primary: "#216BA5"
  secondary: "#1BA374"
  accent: "#446BCE"
  background: "#FAFAF9"
  surface: "#FAFAF9"
  surface-dim: "#F0F0EF"
  surface-bright: "#FFFFFF"
  on-primary: "#FFFFFF"
  on-surface: "#0F0F0E"
  outline: "#D7D7D6"
  error: "#C72C28"
typography:
  display-lg:
    fontFamily: tiemposHeadlineLight, serif
    fontSize: 82px
    fontWeight: 300
    lineHeight: "1.1"
    letterSpacing: "-0.02em"
  display-md:
    fontFamily: tiemposHeadlineLight, serif
    fontSize: 60px
    fontWeight: 300
    lineHeight: "1.15"
    letterSpacing: "-0.01em"
  headline-lg:
    fontFamily: Neue Haas Grotesk Text, sans-serif
    fontSize: 36px
    fontWeight: 600
    lineHeight: "1.2"
    letterSpacing: "-0.01em"
  headline-md:
    fontFamily: Neue Haas Grotesk Text, sans-serif
    fontSize: 24px
    fontWeight: 600
    lineHeight: "1.3"
    letterSpacing: 0em
  headline-sm:
    fontFamily: Neue Haas Grotesk Text, sans-serif
    fontSize: 20px
    fontWeight: 600
    lineHeight: "1.4"
    letterSpacing: 0em
  body-lg:
    fontFamily: Geist, sans-serif
    fontSize: 18px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0em
  body-md:
    fontFamily: Geist, sans-serif
    fontSize: 14px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0em
  body-sm:
    fontFamily: Geist, sans-serif
    fontSize: 12px
    fontWeight: 400
    lineHeight: "1.4"
    letterSpacing: 0em
  label-md:
    fontFamily: Neue Haas Grotesk Text Mono, monospace
    fontSize: 14px
    fontWeight: 500
    lineHeight: "1.2"
    letterSpacing: 0.05em
  label-sm:
    fontFamily: Neue Haas Grotesk Text Mono, monospace
    fontSize: 12px
    fontWeight: 500
    lineHeight: "1.2"
    letterSpacing: 0.05em
rounded:
  sm: 4px
  md: 8px
  lg: 16px
  xl: 24px
  full: 9999px
spacing:
  xs: 4px
  sm: 8px
  md: 16px
  lg: 24px
  xl: 32px
  2xl: 48px
components:
  button-primary:
    backgroundColor: "{colors.surface-bright}"
    textColor: "{colors.on-surface}"
    typography: "{typography.label-md}"
    rounded: "{rounded.full}"
    padding: 12px 24px
    borderColor: "{colors.surface-bright}"
  button-primary-hover:
    backgroundColor: "{colors.surface-dim}"
    textColor: "{colors.on-surface}"
    typography: "{typography.label-md}"
    rounded: "{rounded.full}"
    padding: 12px 24px
    borderColor: "{colors.surface-dim}"
  button-secondary:
    backgroundColor: transparent
    textColor: "{colors.on-surface}"
    typography: "{typography.label-md}"
    rounded: "{rounded.full}"
    padding: 12px 24px
    borderColor: "{colors.outline}"
  button-dark:
    backgroundColor: "{colors.on-surface}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.full}"
    padding: 8px 16px
    borderColor: "{colors.on-surface}"
  card:
    backgroundColor: "{colors.surface}"
    rounded: "{rounded.lg}"
    borderColor: "{colors.outline}"
  card-elevated:
    backgroundColor: "{colors.surface-bright}"
    rounded: "{rounded.lg}"
    borderColor: transparent
  input-field:
    backgroundColor: "{colors.surface-bright}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.md}"
    padding: 12px 16px
    borderColor: "{colors.outline}"
  input-field-focus:
    backgroundColor: "{colors.surface-bright}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.md}"
    padding: 12px 16px
    borderColor: "{colors.primary}"
  link:
    textColor: "{colors.primary}"
    typography: "{typography.body-md}"
  link-hover:
    textColor: "{colors.accent}"
    typography: "{typography.body-md}"
  badge-success:
    backgroundColor: "{colors.secondary}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.sm}"
    padding: 4px 8px
  badge-error:
    backgroundColor: "{colors.error}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.sm}"
    padding: 4px 8px
  divider:
    backgroundColor: "{colors.outline}"
    height: 1px
  swatch-background:
    backgroundColor: "{colors.background}"
    rounded: "{rounded.sm}"
    size: 32px
motion:
  duration-short: 200ms
  duration-medium: 300ms
  easing-standard: cubic-bezier(0.2, 0, 0.3, 1)
elevation:
  sm: 0 1px 3px rgba(0,0,0,0.1)
  md: 0 4px 6px rgba(0,0,0,0.1)
  lg: 0 10px 15px rgba(0,0,0,0.1)
---

## Overview

Dune's visual identity balances institutional credibility with modern crypto-native energy. It pairs a clean, highly structured light-mode interface with vibrant, fluid blue-to-green gradient backdrops in high-impact areas like the hero section. The typography combines elegant, editorial serif headings with highly legible, technical sans-serif and monospace body faces to establish a trustworthy yet cutting-edge platform.

## Colors

The color strategy relies on a clean, light-mode base to project clarity and professional authority, accented by vibrant, data-inspired hues. High-contrast dark charcoal is used for text, while a structured system of off-whites and light greys organizes content without visual clutter.

* **primary** (`#216BA5`): The core brand blue, used for primary links, active navigation states, and brand accents.
* **secondary** (`#1BA374`): A vibrant green representing growth, positive metrics, and success states.
* **accent** (`#446BCE`): A bright indigo-blue used in gradients and hover states to add depth.
* **background** (`#FAFAF9`): The primary off-white background color used across the light-mode interface.
* **surface** (`#FAFAF9`): The default surface color for containers and cards.
* **surface-dim** (inferred) (`#F0F0EF`): A slightly darker grey surface variant used for hover states and subtle backgrounds.
* **surface-bright** (`#FFFFFF`): Pure white used for high-contrast elements like primary buttons and elevated cards.
* **on-primary** (`#FFFFFF`): White text used on primary colored backgrounds.
* **on-surface** (`#0F0F0E`): The primary dark charcoal text color, ensuring high contrast and readability.
* **outline** (`#D7D7D6`): A light grey border color used to define boundaries without adding visual noise.
* **error** (`#C72C28`): A strong red used for error states, destructive actions, and negative alerts.

## Typography

Dune uses a sophisticated typographic hierarchy that pairs the editorial elegance of Tiempos Headline with the clean, technical precision of Neue Haas Grotesk and Geist. This contrast reinforces the brand's position as both an analytical authority and a developer-friendly platform.

* **display-lg** (`tiemposHeadlineLight, serif`): Used for high-impact hero headlines to establish an elegant, editorial tone.
* **display-md** (`tiemposHeadlineLight, serif`): Used for secondary display headings and section titles.
* **headline-lg** (inferred) (`Neue Haas Grotesk Text, sans-serif`): Used for major section headers.
* **headline-md** (inferred) (`Neue Haas Grotesk Text, sans-serif`): Used for card titles and mid-sized headers.
* **headline-sm** (inferred) (`Neue Haas Grotesk Text, sans-serif`): Used for small group headers and feature titles.
* **body-lg** (inferred) (`Geist, sans-serif`): Used for hero subheaders and introductory paragraphs.
* **body-md** (`Geist, sans-serif`): The standard body text size for paragraphs and descriptions.
* **body-sm** (inferred) (`Geist, sans-serif`): Used for secondary metadata, captions, and footer links.
* **label-md** (`Neue Haas Grotesk Text Mono, monospace`): Used for technical labels, buttons, and uppercase navigation items.
* **label-sm** (`Neue Haas Grotesk Text Mono, monospace`): Used for small technical badges and micro-labels.

## Layout

* The layout is built on a clean, responsive grid system with a maximum container width of 1200px, utilizing container padding of 16px (`spacing.md`) on mobile, scaling up to 32px (`spacing.xl`) or 48px (`spacing.2xl`) on desktop.
* Section spacing relies heavily on large vertical margins of 64px to 96px to create breathing room between dense data tables and feature grids.
* The standard page flow top-to-bottom follows the sequence: `nav`, `hero`, `social-proof`, `features`, `solutions`, `testimonials`, `press`, and `footer`.
* The hero composition features a centered serif headline and sans-serif subhead over a vibrant blue-to-green gradient background, anchored by a prominent white pill CTA button and secondary text link.
* On smaller viewports, the layout transitions to a mobile-friendly navigation bar that collapses into a hamburger menu, and grid systems stack vertically.

## Elevation & Depth

Depth is primarily conveyed through flat design principles, relying on subtle borders and background color shifts, with a soft, multi-layered shadow scale used to lift elements gently off the background.

* **elevation.sm**: Used for subtle card lift and hover states on interactive elements.
* **elevation.md**: Used for dropdown menus, popovers, and floating UI elements.
* **elevation.lg**: Used for high-impact modal overlays and drawer components.

## Shapes

Dune utilizes a hybrid shape language that balances friendly interactivity with structured, institutional trustworthiness. Interactive elements like buttons use a fully rounded pill shape (`rounded.full`) to feel modern, approachable, and distinct.

Content containers, cards, and input fields use a structured corner radius (`rounded.md` or `rounded.lg`) to maintain a professional, clean appearance. Small badges and technical swatches use a sharp `rounded.sm` to align with the technical, data-dense nature of the platform.

## Components

> **Note:** This spec was generated from a website scrape and contains visual approximations.
> For production use, add a deep reference to each component pointing to its authoritative
> source (Storybook story, metadata file, or component spec):
> `→ Deep reference: src/components/Button/metadata.ts`

### button-primary
A high-contrast pill-shaped button using `{colors.surface-bright}` background and `{colors.on-surface}` text. It uses `{rounded.full}` and `{typography.label-md}` for a clean, technical appearance. Use as the primary call to action, especially over dark gradient backgrounds.

### button-primary-hover
The active hover state for the primary button, transitioning the background and border to `{colors.surface-dim}`. This provides a subtle, tactile response without disrupting the overall color balance.

### button-secondary
A transparent button with a `{colors.outline}` border and `{colors.on-surface}` text. It maintains the `{rounded.full}` shape and `{typography.label-md}` style. Use for secondary actions alongside primary buttons.

### button-dark
A solid dark button utilizing `{colors.on-surface}` background and `{colors.on-primary}` text. It uses a tighter padding and `{typography.label-sm}`. Use for secondary technical actions or inline toolbar buttons.

### card
A structured content container with `{colors.surface}` background and a `{colors.outline}` border. It features a `{rounded.lg}` corner radius to group related metrics, features, or data points cleanly.

### card-elevated
A high-contrast card variant using `{colors.surface-bright}` background with a transparent border. It relies on `{elevation.sm}` to lift it off the background. Use to highlight featured content or interactive items.

### input-field
A text input container with `{colors.surface-bright}` background, `{colors.on-surface}` text, and a `{colors.outline}` border. It uses `{rounded.md}` and standard padding to ensure high legibility.

### input-field-focus
The active focus state for input fields, shifting the border color to `{colors.primary}` to provide clear interactive feedback.

### link
An inline text link using `{colors.primary}` and `{typography.body-md}`. Use for inline navigation and text-based actions.

### link-hover
The hover state for text links, transitioning the text color to `{colors.accent}` to indicate interactivity.

### badge-success
A small status indicator using `{colors.secondary}` background and `{colors.on-primary}` text. It uses `{rounded.sm}` and `{typography.label-sm}`. Use strictly for positive metrics, growth indicators, and success states.

### badge-error
A small status indicator using `{colors.error}` background and `{colors.on-primary}` text. It uses `{rounded.sm}` and `{typography.label-sm}`. Use strictly for negative metrics, alerts, and error states.

### divider
A thin, 1px horizontal rule using `{colors.outline}` background. Use to separate distinct content sections and maintain layout structure.

### swatch-background
A small visual block using `{colors.background}` and `{rounded.sm}`. Use for color previewing or technical swatches.

## Do's and Don'ts

| Do | Don't |
| --- | --- |
| Use `{colors.primary}` for all primary text links and active navigation states. | Never use `{colors.secondary}` for body text; reserve it strictly for success badges and accents. |
| Apply `{typography.display-lg}` exclusively for high-impact hero headlines. | Avoid applying `{typography.display-md}` on small mobile viewports without responsive scaling. |
| Ensure `{components.button-primary}` uses `{colors.surface-bright}` background when placed over dark gradient sections. | Never overlay `{colors.on-surface}` text directly onto dark gradient backgrounds without a high-contrast container. |
| Use `{colors.outline}` for subtle borders on `{components.card}` elements to maintain a clean layout. | Do not use sharp corners on buttons; always apply `{rounded.full}` to interactive elements. |
| Maintain a `{rounded.full}` radius on all interactive button components like `{components.button-primary}`. | Do not exceed `{spacing.xl}` for standard grid gutters to maintain layout density. |
| Apply `{colors.secondary}` for positive metrics, success badges, or growth indicators. | Avoid using `{colors.error}` for non-destructive actions or neutral badges. |
| Use `{spacing.md}` for standard padding inside `{components.input-field}` elements. | Do not apply `{elevation.lg}` to standard content blocks, reserving it only for modal overlays. |
| Apply `{elevation.sm}` to hover states on `{components.card}` elements to provide soft depth. | Do not use `{colors.primary}` for background fills; reserve it for interactive accents and active states. |

## Content Style

Dune's copy style is imperative, direct, and action-oriented. Button labels and primary actions use clear, commanding verbs such as "Explore data", "Book demo", "Subscribe", and "Talk to an expert" to drive engagement.

Headlines are authoritative, institutional, and clear. They emphasize industry standards, reliability, and scale, positioning the platform as the definitive source of truth for onchain data.

The copy density is scannable and highly structured. It utilizes short paragraphs, bulleted lists, and prominent metrics (e.g., "130+ Chains", "1M+ Users") to establish credibility quickly and make complex technical information easily digestible.

## Imagery & Icons

Dune's imagery combines vibrant, smooth abstract gradients in the hero background with clean, minimal vector logos of integrations (such as Snowflake, BigQuery, and Databricks). Editorial-style report covers are featured with high-contrast typography and structured layouts. Icons use a clean, minimal, and consistent line weight that aligns with the technical nature of the platform.

---

## Companion prompt

## Role
You are an AI assistant generating UI components and layouts for Dune, a professional onchain data platform with a minimal, institutionally credible aesthetic. Content, copy, and information architecture remain owned by the product team.

## How to use design.md
1. Reference every visual value by its token name — `{colors.primary}`, `{typography.body-md}`, `{spacing.lg}` — never hardcode hex values, font names, or pixel sizes.
2. Use only the components listed under `components:` (`{components.button-primary}`, `{components.card}`, etc.). Do not invent variants the spec does not define.
3. Apply the shape rules from Shapes: `{rounded.full}` on all interactive buttons, `{rounded.md}` or `{rounded.lg}` on cards and inputs. Never use sharp corners on buttons.
4. Treat the Do's and Don'ts as authoritative. If a user request conflicts — for example, using `{colors.secondary}` for body text or `{colors.error}` on a neutral badge — surface the conflict before proceeding.
5. Follow the Layout notes for container width (max 1200px), page margins (`{spacing.md}` mobile, `{spacing.2xl}` desktop), and section vertical rhythm (64px–96px between major sections).

## Output contract

**Must:**
- Use all tokens by name; cover hover, focus, and disabled states for every interactive component the spec defines.
- Apply `{rounded.full}` to all button components and `{rounded.md}`/`{rounded.lg}` to all content containers.
- Use `{typography.display-lg}` only for hero headlines; `{typography.label-md}` for buttons and navigation labels.
- Match CTA copy style — imperative, direct verbs — per the Voice and Content section.
- Maintain text contrast ≥ 4.5:1; never place `{colors.on-surface}` text directly on dark gradient backgrounds.

**Must NOT:**
- Invent colors, radii, or type scales absent from the spec.
- Use generic utility defaults when a brand token exists.
- Add emoji, filler copy, or marketing language.
- Rewrite page headings, button labels, navigation items, or any existing copy.
- Alter page structure or information architecture as a side effect of applying tokens.

## When in doubt
- If a value is not specified, ask before inventing one.
- Prefer composing existing components over introducing new tokens.
- For ambiguous backgrounds, default to `{colors.surface}`; for text on those surfaces, use `{colors.on-surface}`.
- If breakpoints are unspecified, default to mobile-first with one breakpoint at 768px.
- Tokens marked "(inferred)" in the spec are approximations; authoritative theme files take precedence.
