# Sparsity Research — Design System
> Onchain data, a daily holder strength index and a bottoming test for Robinhood Chain, Solana, Ethereum, Base and BNB Chain memecoins.
- **Canonical:** https://uiuxskills.com/library/sparsity-research
- **Source:** https://sparsitydata.com/
- **Category:** Fintech & Crypto
- **Compatible tools:** claude, cursor, lovable, figma-make
- **Coverage:** 81%
- **License:** MIT
- **Last updated:** 2026-10-28T19:57:55.364Z

---

---
version: alpha
name: Sparsity Research
tagline: ONCHAIN RESEARCH
description: >-
  Onchain data, a daily holder strength index and a bottoming test for Robinhood Chain, Solana,
  Ethereum, Base and BNB Chain memecoins.
tone: modern-terminal
color-scheme: dark
colors:
  background: "#2B2B2B"
  surface: "#2B2B2B"
  surface-container: "#363636"
  primary: "#EFEEE9"
  on-primary: "#2B2B2B"
  on-surface: "#EFEEE9"
  accent-blue: "#0055FF"
  accent-orange: "#FF5E3A"
  accent-yellow: "#FFB000"
  outline: "#565655"
  error: "#FF5E3A"
  success: "#0055FF"
typography:
  display-lg:
    fontFamily: Space Grotesk
    fontSize: 184px
    fontWeight: 700
    lineHeight: "1.0"
    letterSpacing: "-0.04em"
  display-md:
    fontFamily: Space Grotesk
    fontSize: 96px
    fontWeight: 700
    lineHeight: "1.1"
    letterSpacing: "-0.03em"
  headline-lg:
    fontFamily: Space Grotesk
    fontSize: 32px
    fontWeight: 600
    lineHeight: "1.2"
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: Space Grotesk
    fontSize: 24px
    fontWeight: 600
    lineHeight: "1.3"
    letterSpacing: "-0.01em"
  headline-sm:
    fontFamily: Space Grotesk
    fontSize: 20px
    fontWeight: 500
    lineHeight: "1.4"
    letterSpacing: 0.0em
  body-lg:
    fontFamily: Geist
    fontSize: 18px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0.0em
  body-md:
    fontFamily: Geist
    fontSize: 16px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0.0em
  body-sm:
    fontFamily: Geist
    fontSize: 14px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0.01em
  label-md:
    fontFamily: Geist
    fontSize: 12px
    fontWeight: 500
    lineHeight: "1.0"
    letterSpacing: 0.05em
  label-sm:
    fontFamily: Geist
    fontSize: 10px
    fontWeight: 500
    lineHeight: "1.0"
    letterSpacing: 0.08em
rounded:
  sm: 4px
  md: 8px
  lg: 12px
  xl: 24px
  full: 9999px
spacing:
  xs: 4px
  sm: 8px
  md: 16px
  lg: 24px
  xl: 32px
  2xl: 48px
components:
  button-primary:
    backgroundColor: "{colors.background}"
    textColor: "{colors.on-surface}"
    typography: "{typography.body-md}"
    rounded: "{rounded.lg}"
    padding: 12px 24px
    borderColor: "{colors.outline}"
  button-primary-hover:
    backgroundColor: "{colors.surface-container}"
    textColor: "{colors.primary}"
    typography: "{typography.body-md}"
    rounded: "{rounded.lg}"
    padding: 12px 24px
    borderColor: "{colors.primary}"
  button-secondary:
    backgroundColor: transparent
    textColor: "{colors.on-surface}"
    typography: "{typography.body-md}"
    rounded: "{rounded.lg}"
    padding: 12px 24px
    borderColor: transparent
  card:
    backgroundColor: "{colors.background}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.lg}"
    padding: 16px 24px
    borderColor: "{colors.outline}"
  card-elevated:
    backgroundColor: "{colors.surface-container}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.lg}"
    padding: 16px 24px
    borderColor: "{colors.outline}"
  input-field:
    backgroundColor: "{colors.background}"
    textColor: "{colors.on-surface}"
    typography: "{typography.body-md}"
    rounded: "{rounded.md}"
    padding: 12px 16px
    borderColor: "{colors.outline}"
  input-field-focus:
    backgroundColor: "{colors.background}"
    textColor: "{colors.on-surface}"
    typography: "{typography.body-md}"
    rounded: "{rounded.md}"
    padding: 12px 16px
    borderColor: "{colors.primary}"
  link:
    textColor: "{colors.primary}"
    typography: "{typography.body-md}"
  link-hover:
    textColor: "{colors.accent-blue}"
    typography: "{typography.body-md}"
  badge:
    backgroundColor: "{colors.surface-container}"
    textColor: "{colors.on-surface}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.sm}"
    padding: 4px 8px
  badge-beta:
    backgroundColor: transparent
    textColor: "{colors.accent-orange}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.sm}"
    padding: 2px 6px
    borderColor: "{colors.accent-orange}"
  badge-error:
    backgroundColor: transparent
    textColor: "{colors.error}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.sm}"
    padding: 2px 6px
    borderColor: "{colors.error}"
  badge-success:
    backgroundColor: transparent
    textColor: "{colors.success}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.sm}"
    padding: 2px 6px
    borderColor: "{colors.success}"
  badge-warning:
    backgroundColor: transparent
    textColor: "{colors.accent-yellow}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.sm}"
    padding: 2px 6px
    borderColor: "{colors.accent-yellow}"
  divider:
    backgroundColor: "{colors.outline}"
    height: 1px
  card-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.md}"
    padding: 16px
  swatch-on-primary:
    backgroundColor: "{colors.on-primary}"
    rounded: "{rounded.sm}"
    size: 32px
motion:
  duration-short: 150ms
  duration-medium: 300ms
  easing-standard: cubic-bezier(0.25, 0.1, 0.25, 1)
elevation:
  sm: 0 1px 2px rgba(0,0,0,0.06)
  md: 0 2px 4px rgba(0,0,0,0.08)
  lg: 0 4px 8px rgba(0,0,0,0.10)
---

## Overview

Sparsity Research presents a highly technical, data-dense, and retro-futuristic visual identity tailored for onchain data analysts. The interface is dominated by a dark, low-contrast background paired with a massive, generative pixel-art scatter plot that visually represents data sparsity. High-contrast, clean typography and subtle outlined container cards establish a precise, scientific tone.

## Colors

The color palette is built on a low-contrast dark foundation that mimics a retro-terminal environment, punctuated by high-contrast off-white text and vibrant primary-colored accents. This strategy keeps visual noise low while drawing immediate focus to critical data points and system statuses.

*   `{colors.background}` (#2B2B2B): The primary dark background canvas establishing the terminal environment.
*   `{colors.surface}` (#2B2B2B): Matches the background color to maintain a flat, single-pane aesthetic.
*   `{colors.surface-container}` (inferred) (#363636): A slightly lighter dark gray used for container backgrounds and hover states.
*   `{colors.primary}` (#EFEEE9): Off-white ink color used for primary text, headings, and high-contrast elements.
*   `{colors.on-primary}` (inferred) (#2B2B2B): Dark text color used when overlaying bright primary elements.
*   `{colors.on-surface}` (#EFEEE9): Off-white text color used on top of dark surface containers.
*   `{colors.accent-blue}` (#0055FF): Vibrant blue used for accents, active links, and success states.
*   `{colors.accent-orange}` (#FF5E3A): Vibrant orange-red used for beta badges, errors, and highlighting experimental features.
*   `{colors.accent-yellow}` (#FFB000): Warm yellow used for warning states and secondary accents.
*   `{colors.outline}` (#565655): Medium gray used for card borders and dividers to structure the layout.
*   `{colors.error}` (inferred) (#FF5E3A): Mapped to the vibrant orange-red for semantic error and alert states.
*   `{colors.success}` (inferred) (#0055FF): Mapped to the vibrant blue for semantic success and positive trend states.

## Typography

The typography pairs Space Grotesk, a geometric sans-serif with quirky terminal-like details, for headings, with Geist, a highly legible monospaced-leaning sans-serif, for data displays and body copy. This combination reinforces the scientific, developer-focused aesthetic.

*   `{typography.display-lg}`: Space Grotesk. Used exclusively for the massive hero brand mark.
*   `{typography.display-md}` (inferred): Space Grotesk. Used for intermediate promotional headings.
*   `{typography.headline-lg}` (inferred): Space Grotesk. Used for prominent section headers and card titles.
*   `{typography.headline-md}` (inferred): Space Grotesk. Used for medium-sized headings and primary card labels.
*   `{typography.headline-sm}` (inferred): Space Grotesk. Used for smaller sub-headings and highlighted metrics.
*   `{typography.body-lg}` (inferred): Geist. Used for introductory body copy and descriptive text.
*   `{typography.body-md}`: Geist. The standard body text size for general reading and data tables.
*   `{typography.body-sm}` (inferred): Geist. Used for secondary metadata and helper text.
*   `{typography.label-md}` (inferred): Geist. Used for small badges, tags, and micro-labels.
*   `{typography.label-sm}` (inferred): Geist. Used for tiny uppercase labels and system status indicators.

## Layout

*   The layout relies on a structured, responsive grid that maximizes screen real estate for dense data visualization, utilizing a base spacing unit of `{spacing.sm}` (8px).
*   The observed section order flows top-to-bottom: `nav` → `hero` → `features` → `footer`.
*   The hero pattern features a massive centered brand title using `{typography.display-lg}` overlaid on a dense, generative pixel-art background, flanked by two prominent interactive metric cards.
*   Containers use generous padding like `{spacing.xl}` (32px) and `{spacing.2xl}` (48px) to balance the dense pixel-art background and prevent visual crowding.
*   Responsive behavior is fluid, with the pixel-art background scaling dynamically and the main metric cards stacking vertically on smaller viewports.

## Elevation & Depth

Depth is conveyed primarily through flat, outlined containers rather than traditional soft drop shadows, maintaining a retro-terminal aesthetic. The elevation scale is inferred to provide subtle layering when elements overlap:

*   `elevation.sm` (inferred): Used for subtle card lift or interactive hover states.
*   `elevation.md` (inferred): Used for dropdown menus, popovers, and floating tooltips.
*   `elevation.lg` (inferred): Used for modal overlays or drawer containers.

## Shapes

The brand employs a deliberate contrast between sharp, pixelated elements in its background graphics and moderately rounded corners for interactive components. This juxtaposition of sharp 1-pixel data points and smooth rounded cards creates a polished terminal feel.

Interactive modules and cards utilize `{rounded.lg}` (12px) to soften the interface, while smaller elements like badges and color swatches use `{rounded.sm}` (4px) to maintain a crisp, structured appearance. Buttons and input fields leverage `{rounded.md}` (8px) and `{rounded.lg}` (12px) to ensure touch targets feel defined and cohesive.

## 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
The primary button is an outlined container using `{colors.background}` and `{colors.outline}` with `{colors.on-surface}` text. On hover, it transitions to `{colors.surface-container}` with a `{colors.primary}` border. Use this for the main call to action within a card or section.

### Button Secondary
The secondary button features a transparent background with `{colors.on-surface}` text and no border. It uses `{typography.body-md}` and `{rounded.lg}`. Use this for low-priority actions or secondary options next to a primary button.

### Card & Card Elevated
Cards are the primary container elements, styled with `{colors.background}` and `{colors.outline}` borders. The elevated variant uses `{colors.surface-container}` to stand out against the background. Use these to group related metrics, charts, or interactive controls.

### Input Field
The input field is styled with `{colors.background}` and a `{colors.outline}` border, transitioning to a `{colors.primary}` border on focus. It uses `{typography.body-md}` and `{rounded.md}`. Use this for search queries, contract address inputs, or filter parameters.

### Link
Links are rendered in `{colors.primary}` and transition to `{colors.accent-blue}` on hover. They use `{typography.body-md}`. Use these for inline text navigation or external references to block explorers.

### Badges (Default, Beta, Error, Success, Warning)
Badges are small, status-indicating labels. The default badge uses `{colors.surface-container}` with `{colors.on-surface}` text, while semantic badges (beta, error, success, warning) use transparent backgrounds with colored borders matching their respective status colors like `{colors.accent-orange}` or `{colors.success}`. Use these to display system status, risk levels, or experimental features.

### Divider
A thin horizontal rule with a height of 1px, styled with `{colors.outline}`. Use this to separate distinct content blocks or list items within a card.

### Swatch On-Primary
A small square indicator styled with `{colors.on-primary}` and `{rounded.sm}`. Use this for color coding data series or representing active states in charts.

## Do's and Don'ts

| Do | Don't |
| --- | --- |
| Use `{colors.background}` for the main page canvas to maintain the dark, terminal-like aesthetic. | Do not use heavy drop shadows on `{components.card}` as it disrupts the flat, retro-terminal aesthetic. |
| Apply `{colors.outline}` for card borders to clearly separate interactive modules from the background. | Never apply `{colors.primary}` text directly onto bright accent backgrounds without checking contrast. |
| Use `{typography.display-lg}` exclusively for the main brand title 'Sparsity'. | Avoid using `{typography.display-lg}` for standard section headers; reserve it for the hero brand mark. |
| Render beta badges using `{colors.accent-orange}` to draw subtle attention to experimental features. | Never use vibrant background fills for `{components.badge-beta}`; keep them outlined to match the minimal style. |
| Ensure all body text uses `{typography.body-md}` with `{colors.on-surface}` for optimal readability. | Do not crowd the generative pixel background with dense text blocks; maintain generous spacing using `{spacing.2xl}`. |
| Use `{colors.accent-blue}` to highlight active links or primary interactive hover states. | Do not mix rounded corner scales; stick to `{rounded.lg}` for cards and buttons to maintain consistency. |
| Use `{colors.surface-container}` for hover states on primary buttons to provide subtle visual feedback. | Do not use `{colors.success}` or `{colors.error}` for non-semantic decorative elements. |
| Apply `{rounded.sm}` to small elements like `{components.badge}` to maintain a crisp, structured appearance. | Do not use `{typography.label-sm}` for long paragraphs of body copy. |

## Content Style

*   **CTA Style:** Call-to-action elements are direct, technical, and action-oriented. They utilize simple imperative verbs paired with arrow indicators to guide the user (e.g., "Holder strength index →").
*   **Heading Tone:** Headings are objective, scientific, and strictly data-driven. The tone focuses entirely on metrics, live status updates, and onchain parameters without marketing fluff or hyperbolic language.
*   **Copy Density:** The interface is extremely sparse and relies heavily on micro-copy, status tags, and real-time data points. Long paragraphs are avoided in favor of high-density data tables and structured metric cards separated by generous whitespace.

## Imagery & Icons

The visual system features a massive, generative pixel-art scatter plot representing raw data points, reinforcing the onchain analytics theme. Icons and logo marks are strictly grid-aligned, pixelated, and multi-colored—utilizing `{colors.accent-blue}`, `{colors.accent-orange}`, and `{colors.accent-yellow}`—to mimic raw terminal data feeds. Photographic elements are completely avoided in favor of abstract, code-driven graphic representations.

---

## Companion prompt

## Role
You are an AI assistant generating UI components and layouts for Sparsity Research, a modern-terminal onchain research brand with a retro-futuristic, data-dense aesthetic. Content, copy, and information architecture remain owned by the product team.

## How to use design.md
1. Reference every value by its token name — `{colors.background}`, `{typography.body-md}`, `{rounded.lg}` — never hardcode hex values, font sizes, or pixel radii.
2. Use only components listed under `components:` (`button-primary`, `card`, `badge-beta`, etc.). Do not invent variants the spec does not define.
3. Follow the Layout and Shapes notes: data-dense grids with generous `{spacing.2xl}` container padding; `{rounded.lg}` on cards and buttons consistently — do not mix radius scales.
4. Treat the Do's and Don'ts table as authoritative. If a user request conflicts (e.g., requesting drop shadows on cards or `{typography.display-lg}` for a section header), surface the conflict explicitly before proceeding.
5. Apply the Voice and Content rules: CTAs use direct imperative phrasing with arrow indicators; copy is micro-dense; headings are metric- and status-oriented, never promotional.

## Output contract

**Must:**
- Use all tokens by name on every generated element.
- Cover hover, focus, and disabled states for any interactive component the spec defines them for; use `{colors.accent-blue}` for active/hover states and `{colors.surface-container}` for hover backgrounds.
- Apply `{colors.outline}` to all card borders and dividers.
- Render `{typography.label-sm}` badges with outlined styles only — no vibrant fills.
- Use `{colors.on-surface}` for body text on dark surfaces; check contrast before placing `{colors.primary}` on any accent background.

**Must NOT:**
- Invent colors, fonts, or radii outside the spec.
- Apply heavy drop shadows or elevation effects to `{components.card}`.
- Use `{typography.display-lg}` for anything other than the hero brand mark.
- Add emoji, marketing copy, or filler text.
- Rewrite page copy, button labels, headings, or alter navigation structure as a side effect of applying tokens.

## When in doubt
- If the spec does not define a value, ask the user before introducing one.
- Prefer composing existing components over creating new tokens.
- Default ambiguous backgrounds to `{colors.surface-container}`; ambiguous text to `{colors.on-surface}`; headline actions to `{colors.primary}`.
- For unspecified breakpoints, use mobile-first layout with one breakpoint at 768px, respecting the horizontal-axis alignment described in Layout notes.
- Tokens marked "(inferred)" in prose are approximations; any authoritative token file takes precedence.
