# Phantom — Design System
> The self-custodial wallet for trading predictions, perps, and tokens across Solana, Ethereum, Bitcoin, Robinhood, HyperEVM, and more.
- **Canonical:** https://uiuxskills.com/library/phantom
- **Source:** https://phantom.com/
- **Category:** Fintech & Crypto
- **Compatible tools:** claude, cursor, lovable, figma-make
- **Coverage:** 84%
- **License:** MIT
- **Last updated:** 2026-10-28T20:02:54.615Z

---

---
version: alpha
name: Phantom
tagline: Your home for trading crypto, predictions, perps, and more
description: >-
  The self-custodial wallet for trading predictions, perps, and tokens across Solana, Ethereum,
  Bitcoin, Robinhood, HyperEVM, and more.
tone: friendly, modern, trustworthy, accessible
color-scheme: light
colors:
  primary: "#AB9FF2"
  secondary: "#E2DFFE"
  tertiary: "#3C315B"
  background: "#F5F2FF"
  surface: "#FFFFFF"
  surface-dim: "#14121F"
  on-primary: "#3C315B"
  on-secondary: "#3C315B"
  on-surface: "#3C315B"
  outline: "#E2DFFE"
  error: "#FF5A5A"
  success: "#22C55E"
typography:
  display-lg:
    fontFamily: Phantom, sans-serif
    fontSize: 80px
    fontWeight: 700
    lineHeight: "1.1"
    letterSpacing: "-0.02em"
  display-md:
    fontFamily: Phantom, sans-serif
    fontSize: 56px
    fontWeight: 700
    lineHeight: "1.15"
    letterSpacing: "-0.01em"
  headline-lg:
    fontFamily: Phantom, sans-serif
    fontSize: 40px
    fontWeight: 700
    lineHeight: "1.2"
    letterSpacing: 0em
  headline-md:
    fontFamily: Phantom, sans-serif
    fontSize: 32px
    fontWeight: 700
    lineHeight: "1.25"
    letterSpacing: 0em
  headline-sm:
    fontFamily: Phantom, sans-serif
    fontSize: 24px
    fontWeight: 600
    lineHeight: "1.3"
    letterSpacing: 0em
  body-lg:
    fontFamily: Phantom, sans-serif
    fontSize: 20px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0em
  body-md:
    fontFamily: Phantom, sans-serif
    fontSize: 16px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0em
  body-sm:
    fontFamily: Phantom, sans-serif
    fontSize: 14px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0em
  label-lg:
    fontFamily: Phantom, sans-serif
    fontSize: 16px
    fontWeight: 600
    lineHeight: "1.2"
    letterSpacing: 0.02em
  label-md:
    fontFamily: Phantom, sans-serif
    fontSize: 14px
    fontWeight: 600
    lineHeight: "1.2"
    letterSpacing: 0.01em
  label-sm:
    fontFamily: Phantom, sans-serif
    fontSize: 12px
    fontWeight: 600
    lineHeight: "1.2"
    letterSpacing: 0.05em
rounded:
  sm: 4px
  md: 8px
  lg: 16px
  xl: 24px
  2xl: 32px
  full: 9999px
spacing:
  xs: 4px
  sm: 8px
  md: 16px
  lg: 24px
  xl: 32px
  2xl: 48px
  3xl: 64px
components:
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-lg}"
    rounded: "{rounded.2xl}"
    padding: 12px 24px
  button-primary-hover:
    textColor: "{colors.on-primary}"
    typography: "{typography.label-lg}"
    rounded: "{rounded.2xl}"
  button-secondary:
    backgroundColor: "{colors.secondary}"
    textColor: "{colors.on-secondary}"
    typography: "{typography.label-lg}"
    rounded: "{rounded.2xl}"
    padding: 12px 24px
  card:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.xl}"
    padding: 24px
  card-dark:
    backgroundColor: "{colors.surface-dim}"
    textColor: "#FFFFFF"
    rounded: "{rounded.xl}"
    padding: 48px 24px
  input-field:
    backgroundColor: transparent
    textColor: "{colors.on-surface}"
    borderColor: "{colors.outline}"
  input-field-focus:
    borderColor: "{colors.primary}"
  link:
    textColor: "{colors.primary}"
    typography: "{typography.label-md}"
  badge:
    backgroundColor: "{colors.secondary}"
    textColor: "{colors.tertiary}"
    rounded: "{rounded.full}"
    padding: 4px 12px
  badge-error:
    backgroundColor: "{colors.error}"
    textColor: "#FFFFFF"
    rounded: "{rounded.full}"
    padding: 4px 12px
  badge-success:
    backgroundColor: "{colors.success}"
    textColor: "#FFFFFF"
    rounded: "{rounded.full}"
    padding: 4px 12px
  divider:
    backgroundColor: "{colors.outline}"
    height: 1px
  page-container:
    backgroundColor: "{colors.background}"
motion:
  duration-short: 200ms
  duration-medium: 500ms
  easing-standard: cubic-bezier(0.4, 0, 0.2, 1)
elevation:
  sm: 0 1px 2px rgba(60, 49, 91, 0.05)
  md: 0 4px 12px rgba(60, 49, 91, 0.08)
  lg: 0 12px 24px rgba(60, 49, 91, 0.12)
---

## Overview

Phantom presents a friendly, highly polished, and accessible gateway to the crypto ecosystem. Departing from the typical high-contrast dark mode of developer-centric Web3 tools, the interface utilizes a soft, lavender-tinted light mode paired with deep purple typography and organic, rounded shapes. This combination establishes immediate trust, clarity, and ease of use for both novice and experienced traders.

## Colors

The color strategy centers around a soft, inviting lavender palette that softens the technical nature of Web3. Deep purple-indigo serves as the primary high-contrast anchor for typography and structural elements, while vibrant pastel accents guide the user's eye to primary actions.

*   `colors.primary` (#AB9FF2): Signature medium purple accent color used for primary actions and brand highlights.
*   `colors.secondary` (#E2DFFE): Light lavender purple used for secondary buttons, hover states, and subtle container backgrounds.
*   `colors.tertiary` (#3C315B): Deep purple-indigo color used for primary text, headings, and high-contrast brand elements.
*   `colors.background` (#F5F2FF): Signature light lavender-white background color that defines the overall soft aesthetic of the site.
*   `colors.surface` (#FFFFFF): Pure white used for floating navigation bars, content cards, and input fields.
*   `colors.surface-dim` (inferred) (#14121F): Dark purple-black used for high-impact dark mode containers like the hero card.
*   `colors.on-primary` (#3C315B): Deep purple text color used on primary light purple buttons for optimal contrast.
*   `colors.on-secondary` (#3C315B): Deep purple text color used on secondary lavender buttons.
*   `colors.on-surface` (#3C315B): Deep purple text color used on white surface containers.
*   `colors.outline` (inferred) (#E2DFFE): Light lavender border color used to subtly separate content without harsh lines.
*   `colors.error` (inferred) (#FF5A5A): Soft red color used for warning badges, error states, and transaction alerts.
*   `colors.success` (inferred) (#22C55E): Vibrant green color used for success badges and positive transaction states.

## Typography

The typography relies on the custom "Phantom" sans-serif typeface, which balances geometric clarity with friendly, approachable curves. This single-family system maintains a cohesive hierarchy across marketing copy and dense transactional interfaces.

*   `typography.display-lg`: Bold, high-impact typeface used for the main hero headline to create an inviting entry point.
*   `typography.display-md` (inferred): Large section headers and prominent callouts.
*   `typography.headline-lg` (inferred): Secondary section headings and major feature titles.
*   `typography.headline-md` (inferred): Mid-sized headings and card titles.
*   `typography.headline-sm`: Small card headers and feature group titles.
*   `typography.body-lg` (inferred): Introductory body copy and prominent feature descriptions.
*   `typography.body-md` (inferred): Standard body copy size used for descriptions, lists, and general text.
*   `typography.body-sm` (inferred): Secondary text, captions, and legal disclaimers.
*   `typography.label-lg` (inferred): Primary button text and main navigation links.
*   `typography.label-md` (inferred): Secondary button labels and interactive controls.
*   `typography.label-sm` (inferred): Badges, micro-copy, and small interactive labels.

## Layout

*   **Grid & Spacing:** Layouts are structured on a clean, centered grid utilizing a base-8 spacing scale (from `spacing.xs` to `spacing.3xl`) with generous padding to ensure readability and breathing room.
*   **Section Order:** The page follows a logical top-to-bottom flow: `nav` → `hero` → `features` → `product-showcase` → `security` → `social-proof` → `footer`.
*   **Hero Pattern:** The hero section features a high-impact, dark-themed container (`components.card-dark`) containing a centered headline, subhead, and a prominent pill-shaped CTA button, set against the light lavender `components.page-container`.
*   **Responsive Behavior:** The layout transitions smoothly across viewports; the floating navigation bar collapses into a mobile menu, and multi-column grids stack vertically using `spacing.xl` and `spacing.2xl` margins.

## Elevation & Depth

Depth is established through extremely soft, low-contrast shadows tinted with the deep purple brand color to prevent the interface from feeling harsh.

*   `elevation.sm` (inferred): Subtle card lift and interactive elements in default states.
*   `elevation.md` (inferred): Floating navigation bars and hovered interactive cards, making them appear to hover gently above the light background.
*   `elevation.lg` (inferred): Modals, dropdowns, and high-priority overlay containers.

## Shapes

The brand's shape language is defined by extremely soft, organic, pill-like corners that reinforce the friendly and approachable aesthetic. Sharp corners are intentionally avoided to maintain a welcoming, consumer-grade feel.

Interactive components like buttons utilize a fully rounded `rounded.full` or `rounded.2xl` radius to create a distinct pill shape. Major structural containers, content cards, and the floating navigation bar utilize `rounded.xl` to establish a cohesive, soft framing system across the entire interface.

## 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 call-to-action button is styled with a solid background of `{colors.primary}`, text in `{colors.on-primary}`, and a pill-shaped `{rounded.2xl}` border radius. It uses `{typography.label-lg}` for clear readability and is reserved for the single most important action on a page, such as downloading the application.

### button-secondary

Designed for secondary actions, this button utilizes a `{colors.secondary}` background with `{colors.on-secondary}` text and a `{rounded.2xl}` radius. Use this component to offer alternative paths that do not compete with the primary call-to-action.

### card

The standard content container features a `{colors.surface}` background, `{colors.on-surface}` text, and a soft `{rounded.xl}` corner radius. It is used to group related feature descriptions, list items, or secondary informational blocks.

### card-dark

A high-contrast container utilizing `{colors.surface-dim}` background with white text and a `{rounded.xl}` radius. Use this component exclusively for high-impact sections, such as the hero block, to create a dramatic visual focal point.

### input-field

An interactive text input styled with a transparent background, `{colors.on-surface}` text, and a subtle `{colors.outline}` border. Upon receiving focus, the border transitions to `{colors.primary}` (`components.input-field-focus`) to indicate active user engagement.

### link

A simple inline text link styled with `{colors.primary}` and `{typography.label-md}`. Use this component for inline navigation, "See more" actions, or linking to external documentation.

### badge

A compact status indicator featuring a `{colors.secondary}` background, `{colors.tertiary}` text, and a `{rounded.full}` radius. It is used to highlight categories, new features, or status states like `{components.badge-success}` (using `{colors.success}`) and `{components.badge-error}` (using `{colors.error}`).

### divider

A subtle structural line with a height of 1px and a background of `{colors.outline}`. Use this component to separate content blocks vertically without introducing harsh visual boundaries.

### page-container

The top-level layout wrapper that applies `{colors.background}` to the entire viewport, establishing the signature soft lavender canvas for all nested components.

## Do's and Don'ts

| Do | Don't |
| --- | --- |
| Apply `{colors.background}` as the default page background to maintain the soft, lavender brand identity. | Use pure white or saturated primary colors for the main page background. |
| Set heading text to `{colors.tertiary}` to ensure strong contrast and readability against light surfaces. | Never use pure black (#000000) for text; always use `{colors.tertiary}` to keep typography soft and on-brand. |
| Use `{colors.primary}` for primary call-to-action buttons like `{components.button-primary}` to ensure high visibility. | Place `{colors.primary}` text directly on `{colors.secondary}` backgrounds due to insufficient contrast. |
| Use `{rounded.xl}` for major container cards like `{components.card}` to preserve the friendly, organic shape language. | Apply sharp corners (`rounded.sm` or 0px) to structural containers, which violates the soft aesthetic. |
| Ensure all interactive buttons maintain a `{rounded.2xl}` radius for a consistent pill-shaped appearance. | Mix different border-radius styles like `{rounded.sm}` and `{rounded.2xl}` within the same button group. |
| Utilize `{colors.outline}` for subtle borders and dividers like `{components.divider}` to structure content without harsh lines. | Use high-contrast, harsh borders or dark dividers that break the soft, lavender-tinted visual flow. |
| Apply `{elevation.md}` to floating elements like navigation bars and hovered cards to create a subtle sense of depth. | Avoid using high-contrast, harsh drop shadows; stick to the soft, purple-tinted `{elevation.md}` scale. |
| Style status alerts and success states with `{components.badge-success}` using `{colors.success}` for positive reinforcement. | Use generic or unstyled text for transaction states; always wrap them in `{components.badge}` variants. |

## Content Style

*   **CTA Style:** Call-to-action labels must be direct, action-oriented, and simple. Use clear, high-intent verbs in title case (e.g., "Download Phantom" or "See more") to guide users seamlessly through conversion funnels.
*   **Heading Tone:** Headlines should be welcoming, benefit-driven, and clear. Avoid overly technical jargon in main headers; instead, focus on simplicity, ease of use, and user empowerment (e.g., "Your home for trading crypto").
*   **Copy Density:** Maintain a highly scannable layout with short, punchy bulleted lists and minimal paragraph blocks. Use generous whitespace to let the copy breathe, ensuring that complex financial or technical concepts are easily digestible.

## Imagery & Icons

The visual style employs a mixed treatment that combines abstract, colorful 3D-like ribbons in the hero section with clean, minimal vector icons and actual product screenshots. Icons must feature soft, rounded geometries that mirror the brand's shape language. Product screenshots should be framed within `{rounded.xl}` containers and set against the `{colors.background}` canvas to maintain a cohesive, integrated aesthetic.

---

## Companion prompt

## Role
You are an AI assistant generating UI components and layouts for Phantom, a friendly, minimal, and playfully accessible crypto wallet brand. Match its soft lavender aesthetic — approachable and polished, never developer-dark or austere. Content, copy, and information architecture remain owned by the product team.

## How to use design.md
1. Reference every visual value by token name — `{colors.primary}`, `{typography.body-md}`, `{rounded.xl}` — never hardcode hex values, pixel sizes, or raw font names.
2. Render only the components listed under `components:` (`button-primary`, `card`, `badge`, etc.). Do not invent variants the spec doesn't define.
3. Follow the shape mandate: buttons always use `{rounded.2xl}`, major cards and the floating nav use `{rounded.xl}`. Never mix radius styles within the same component group.
4. Treat the Do's and Don'ts as authoritative. If a user request conflicts (e.g., sharp-cornered buttons, black text, primary-on-secondary color pairings), surface the conflict before proceeding.
5. Apply layout notes when composing pages: centered grid, generous `{spacing.2xl}`–`{spacing.3xl}` vertical section gaps, floating nav island with `{rounded.xl}`.

## Output contract

**Must:**
- Use all tokens by name on every generated component.
- Cover hover, focus, and disabled states whenever the spec defines them (e.g., `button-primary-hover`, `input-field-focus`, `link-hover`).
- Use `{colors.background}` as the default page background and `{colors.tertiary}` for all heading and body text on light surfaces.
- Match CTA copy style: direct, verb-first, scannable — per the Voice & Content section.
- Maintain `{colors.outline}` for all borders and dividers; never use black or full-opacity shadows.

**Must NOT:**
- Invent colors, radii, or font scales outside the spec.
- Use pure black (`#000000`) for any text or border.
- Apply `{colors.primary}` text on `{colors.secondary}` backgrounds.
- Add emoji, filler copy, or unsolicited marketing language.
- Rewrite, replace, or restructure existing page copy, button labels, or navigation items.
- Alter information architecture as a side effect of applying tokens.

## When in doubt
- If the spec doesn't define a value, ask the product team before inventing one.
- For ambiguous backgrounds, default to `{colors.surface}` for cards and `{colors.background}` for page-level fills.
- For unspecified breakpoints, use mobile-first layout with one breakpoint at 768px, following the centered-grid layout notes.
- Tokens noted as inferred from a visual render yield to any authoritative Figma token file or theme config the team provides.
- Prefer composing existing spec components over introducing new tokens or radius values.
