# Noiz — Design System
> A high-performance, game-profile-inspired link-in-bio platform for creators, gamers, and artists featuring animated backgrounds, custom widgets, and a dark, high-contrast aesthetic.
- **Canonical:** https://uiuxskills.com/library/noiz
- **Source:** https://noiz.bio/
- **Category:** Productivity & SaaS
- **Compatible tools:** claude, cursor, lovable, figma-make
- **Coverage:** 81%
- **License:** MIT
- **Last updated:** 2026-11-08T03:39:56.395Z

---

---
version: alpha
name: Noiz
tagline: The link-in-bio that makes noise.
description: >-
  A high-performance, game-profile-inspired link-in-bio platform for creators, gamers, and artists
  featuring animated backgrounds, custom widgets, and a dark, high-contrast aesthetic.
tone: bold, modern, gaming-inspired, premium, high-contrast
color-scheme: dark
colors:
  primary: "#06B6D4"
  secondary: "#22C55E"
  accent: "#F97316"
  background: "#000000"
  surface: "#080808"
  surface-container: "#121212"
  surface-bright: "#1A1A1A"
  on-primary: "#000000"
  on-surface: "#F2F2F2"
  on-surface-variant: "#A3A3A3"
  outline: "#292929"
  error: "#EF4444"
typography:
  display-lg:
    fontFamily: Outfit
    fontSize: 4.75rem
    fontWeight: 700
    lineHeight: "0.8"
    letterSpacing: "-0.06em"
  display-md:
    fontFamily: Outfit
    fontSize: 3rem
    fontWeight: 700
    lineHeight: "0.9"
    letterSpacing: "-0.04em"
  headline-lg:
    fontFamily: Outfit
    fontSize: 2rem
    fontWeight: 600
    lineHeight: "1.1"
    letterSpacing: "-0.03em"
  headline-md:
    fontFamily: Outfit
    fontSize: 1.5rem
    fontWeight: 600
    lineHeight: "1.2"
    letterSpacing: "-0.02em"
  body-lg:
    fontFamily: Outfit
    fontSize: 1rem
    fontWeight: 400
    lineHeight: "1.5"
  body-md:
    fontFamily: Outfit
    fontSize: 0.8125rem
    fontWeight: 400
    lineHeight: "1.5"
  label-lg:
    fontFamily: Outfit
    fontSize: 0.9375rem
    fontWeight: 500
    lineHeight: "1.2"
  label-sm:
    fontFamily: Jet Brains Mono
    fontSize: 0.6875rem
    fontWeight: 500
    lineHeight: "1.0"
    letterSpacing: 0.05em
rounded:
  sm: 4px
  md: 8px
  lg: 12px
  xl: 16px
  full: 9999px
spacing:
  xs: 4px
  sm: 8px
  md: 16px
  lg: 24px
  xl: 32px
  2xl: 48px
components:
  button-primary:
    backgroundColor: "{colors.on-surface}"
    textColor: "{colors.background}"
    typography: "{typography.label-lg}"
    rounded: "{rounded.full}"
    padding: 12px 24px
    height: 48px
  button-primary-hover:
    backgroundColor: "#FFFFFF"
    textColor: "{colors.background}"
    typography: "{typography.label-lg}"
    rounded: "{rounded.full}"
    padding: 12px 24px
    height: 48px
  button-secondary:
    backgroundColor: "{colors.surface}"
    textColor: "#FFFFFF"
    typography: "{typography.label-lg}"
    rounded: "{rounded.full}"
    padding: 12px 24px
    height: 48px
    borderColor: "{colors.outline}"
  card:
    backgroundColor: "{colors.surface-container}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.xl}"
    padding: 24px
    borderColor: "{colors.outline}"
  card-elevated:
    backgroundColor: "{colors.surface-bright}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.xl}"
    padding: 24px
    borderColor: "{colors.outline}"
  input-field:
    backgroundColor: transparent
    textColor: "{colors.on-surface}"
    typography: "{typography.body-md}"
    rounded: "{rounded.md}"
    padding: 12px 16px
    height: 48px
    borderColor: "{colors.outline}"
  input-field-focus:
    backgroundColor: transparent
    textColor: "{colors.on-surface}"
    typography: "{typography.body-md}"
    rounded: "{rounded.md}"
    padding: 12px 16px
    height: 48px
    borderColor: "{colors.primary}"
  link:
    textColor: "{colors.accent}"
    typography: "{typography.body-md}"
  link-hover:
    textColor: "{colors.primary}"
    typography: "{typography.body-md}"
  badge:
    backgroundColor: "{colors.surface-bright}"
    textColor: "{colors.on-surface-variant}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.full}"
    padding: 4px 8px
    height: 24px
  badge-success:
    backgroundColor: "{colors.secondary}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.full}"
    padding: 4px 8px
    height: 24px
  badge-error:
    backgroundColor: "{colors.error}"
    textColor: "#FFFFFF"
    typography: "{typography.label-sm}"
    rounded: "{rounded.full}"
    padding: 4px 8px
    height: 24px
  divider:
    backgroundColor: "{colors.outline}"
    height: 1px
    width: 100%
motion:
  duration-short: 150ms
  duration-medium: 300ms
  duration-long: 500ms
  easing-standard: cubic-bezier(0.4, 0, 0.2, 1)
elevation:
  sm: 0 1px 3px rgba(0, 0, 0, 0.4)
  md: 0 4px 6px rgba(0, 0, 0, 0.5)
  lg: 0 10px 15px rgba(0, 0, 0, 0.6)
---

## Overview

Noiz delivers a bold, dark-mode-first visual identity inspired by gaming profiles and digital culture. It features high-contrast typography, sleek chrome accents, and vibrant semantic highlights against a pure black canvas, creating an immersive, premium feel for creators. The aesthetic balances high-performance utility with expressive, interactive elements tailored for gamers, artists, and developers.

## Colors

The color strategy relies on a pure black canvas to establish a gaming-profile aesthetic, using high-contrast off-white for text and vibrant neon accents for interactive states and highlights.

*   **Primary** (`{colors.primary}`) (#06B6D4): Vibrant cyan used for primary focus states, interactive highlights, and key brand accents.
*   **Secondary** (`{colors.secondary}`) (#22C55E): Vibrant green used for success states, online indicators, and positive metrics.
*   **Accent** (`{colors.accent}`) (#F97316): Energetic orange used for links, promotional badges, and secondary highlights.
*   **Background** (`{colors.background}`) (#000000): Pure black canvas that forms the foundation of the dark-mode interface.
*   **Surface** (`{colors.surface}`) (#080808): Very dark gray used for secondary button backgrounds and subtle container fills.
*   **Surface Container (inferred)** (`{colors.surface-container}`) (#121212): Dark gray container background to group content sections and cards.
*   **Surface Bright (inferred)** (`{colors.surface-bright}`) (#1A1A1A): Lighter dark gray used for elevated cards, badges, and interactive hover states.
*   **On Primary (inferred)** (`{colors.on-primary}`) (#000000): High-contrast black text used on top of primary cyan or light surfaces.
*   **On Surface** (`{colors.on-surface}`) (#F2F2F2): Off-white primary text color ensuring high readability against dark backgrounds.
*   **On Surface Variant (inferred)** (`{colors.on-surface-variant}`) (#A3A3A3): Muted gray text color used for secondary labels, descriptions, and metadata.
*   **Outline** (`{colors.outline}`) (#292929): Subtle dark border color used to define component boundaries without adding visual noise.
*   **Error** (`{colors.error}`) (#EF4444): Red color used for error states, destructive actions, and critical alerts.

## Typography

The typography system uses Outfit as the primary typeface to deliver a clean, geometric, and high-impact look, complemented by Jet Brains Mono for technical data and system labels.

*   **display-lg**: Massive, high-impact display size used for main hero headings in Outfit.
*   **display-md (inferred)**: Large display size used for secondary hero elements and section titles in Outfit.
*   **headline-lg (inferred)**: Standard headline size for major section headers in Outfit.
*   **headline-md (inferred)**: Sub-headline size for feature titles and card headers in Outfit.
*   **body-lg (inferred)**: Comfortable reading size for introductory paragraphs and feature descriptions in Outfit.
*   **body-md**: Standard body text size used for general copy and descriptions in Outfit.
*   **label-lg**: Medium label size used for navigation links and button text in Outfit.
*   **label-sm (inferred)**: Monospace label used for technical stats, UIDs, and system badges in Jet Brains Mono.

## Layout

Noiz utilizes a structured grid layout with a standard max-width container and generous padding to frame the central link-in-bio card. Spacing relies on a strict 4px base unit, scaling up to 48px for section margins to maintain a clean, scannable hierarchy. The observed section order top-to-bottom is: `nav`, `hero`, `features`, `dashboard-tour`, `comparison`, `feature-grid`, `use-cases`, `pricing`, `faq`, and `footer`. The hero composition pattern features a massive, centered 3D chrome logo dominating the hero section, flanked by a floating cookie banner and a clean, right-aligned list of key value propositions, leading into a centered primary CTA input. On mobile viewports, the layout is highly responsive, collapsing multi-column grids into single-column stacks, with the navigation bar adapting to a compact layout.

## Elevation & Depth

Depth is primarily conveyed through color contrast and subtle borders rather than heavy shadows, fitting its flat, gaming-inspired aesthetic. Where elevation is used (such as cards or overlays), deep, dark shadows are applied to stand out against the pure black background.

*   `elevation.sm` (inferred) — Applied to low-level interactive elements and small card lifts.
*   `elevation.md` (inferred) — Used for standard dropdowns, popovers, and floating containers.
*   `elevation.lg` (inferred) — Reserved for high-priority overlays, modals, and drawer components.

## Shapes

The brand employs a mix of sharp and fully rounded shapes to balance gaming aesthetics with structured layouts. Buttons and badges use pill-shaped fully rounded corners (`{rounded.full}`), while content cards and containers utilize a 12px (`{rounded.lg}`) to 16px (`{rounded.xl}`) border radius to soften the high-contrast layout. Smaller inputs use a 4px (`{rounded.sm}`) or 8px (`{rounded.md}`) radius to maintain alignment precision.

## 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 action button features a high-contrast background of `{colors.on-surface}` with `{colors.background}` text, utilizing `{typography.label-lg}` and a fully rounded shape (`{rounded.full}`). It is used for the main call-to-action on any screen or form.

### button-primary-hover
The hover state of the primary button shifts the background to solid white while keeping the text color as `{colors.background}`. This subtle brightness increase signals interactivity.

### button-secondary
A secondary action button with a dark background of `{colors.surface}` and white text, framed by a border of `{colors.outline}`. It uses `{typography.label-lg}` and `{rounded.full}` for secondary or alternative actions.

### card
The standard content container, styled with `{colors.surface-container}` background, `{colors.on-surface}` text, and `{rounded.xl}` corners. It features a subtle `{colors.outline}` border to define its boundaries.

### card-elevated
An elevated variation of the card component utilizing a lighter `{colors.surface-bright}` background to stand out against the pure black canvas, framed by `{colors.outline}`.

### input-field
A clean text input with a transparent background, `{colors.on-surface}` text, and `{rounded.md}` corners, outlined by `{colors.outline}`. Used for user inputs like claiming a profile name.

### input-field-focus
The active state of the input field, which transitions the border color to `{colors.primary}` to indicate focus and user interaction.

### link
Inline text links styled with `{colors.accent}` and `{typography.body-md}` to stand out within body copy.

### link-hover
The hover state for inline links, shifting the text color to `{colors.primary}` to provide clear visual feedback.

### badge
A small metadata tag using `{colors.surface-bright}` background, `{colors.on-surface-variant}` text, and `{typography.label-sm}`. Styled with `{rounded.full}` for a pill shape.

### badge-success
A semantic badge indicating positive status or metrics, using `{colors.secondary}` background and `{colors.on-primary}` text.

### badge-error
A semantic badge indicating alerts or errors, using `{colors.error}` background and white text.

### divider
A thin, 1px horizontal line styled with `{colors.outline}` to separate content sections without adding visual clutter.

## Do's and Don'ts

| Do | Don't |
| --- | --- |
| Use `{colors.background}` as the primary canvas color to maintain the dark-mode aesthetic. | Do not use light backgrounds; the interface must remain strictly dark-mode using `{colors.background}`. |
| Apply `{colors.primary}` and `{colors.accent}` selectively for interactive states and highlights. | Never apply `{colors.primary}` to large text blocks; reserve it for accents and `{components.input-field-focus}` borders. |
| Ensure all primary actions use `{components.button-primary}` with high-contrast text. | Avoid using sharp corners on interactive elements; always default to `{rounded.full}` or `{rounded.xl}`. |
| Use `{rounded.full}` for interactive buttons and badges to match the gaming-profile style. | Do not mix multiple font families; stick strictly to Outfit for headings and body, and Jet Brains Mono for `{typography.label-sm}`. |
| Separate content sections using `{components.divider}` with `{colors.outline}` color. | Never use high-opacity borders; keep dividers and borders subtle using `{colors.outline}`. |
| Set body text to `{typography.body-md}` using `{colors.on-surface}` for optimal readability. | Do not crowd elements; maintain breathing room using `{spacing.lg}` and `{spacing.xl}`. |
| Use `{colors.surface-container}` for standard cards to group content sections cleanly. | Do not use `{colors.surface-bright}` for all cards; reserve it for `{components.card-elevated}` states. |
| Use `{typography.label-sm}` with Jet Brains Mono for technical stats, UIDs, and system badges. | Do not use `{typography.body-md}` for technical metadata or system badges. |

## Content Style

CTA style is direct, action-oriented, and concise. Button labels use imperative verbs in title case or sentence case, such as "Claim it", "Create your profile", or "Get Premium" to drive immediate engagement.

Heading tone is punchy, confident, and slightly rebellious. Headlines are phrased as short, impactful statements that challenge standard conventions, such as "Short names are trophies" or "A control room, not a form", establishing an authoritative and gaming-inspired voice.

Copy density is low to medium. Information is broken down into short, highly scannable bullet points, feature lists, and bold callouts, leaving generous breathing room to avoid overwhelming the user and to maintain a clean visual hierarchy.

## Imagery & Icons

The visual treatment is mixed, combining high-fidelity 3D chrome lettering with clean, flat vector icons and dark, stylized dashboard screenshots. Icons are monochrome, stroke-based, and follow a clean, rounded aesthetic. Illustrations and screenshots are framed within containers that match the dark aesthetic, while the prominent 3D chrome logo acts as a central anchor in the hero layout.

---

## Companion prompt

## Role
You are an AI assistant generating UI components and layouts for Noiz, a bold, dark-mode-first link-in-bio platform with a gaming-inspired, premium tone. 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.display-lg}`, `{spacing.lg}` — never hardcode hex values, pixel sizes, or font names inline.
2. Render only the component variants listed under `components:` (`button-primary`, `card`, `badge-success`, etc.). Do not invent variants the spec doesn't define.
3. Follow the Shapes notes strictly: `{rounded.full}` on all buttons and badges; `{rounded.lg}` or `{rounded.xl}` on cards and containers. Never apply sharp corners to interactive elements.
4. Treat the Do's and Don'ts table as authoritative. If a user request conflicts with a rule (e.g., requesting a light background or multi-family font mixing), surface the conflict before proceeding.
5. Apply `{typography.label-sm}` (JetBrains Mono) only for stats, UIDs, and system badges. All other text uses Outfit via the appropriate type token.

## Output contract

**Must:**
- Use token names for every color, spacing, radius, and type decision.
- Implement hover, focus, and disabled states for any interactive component when the spec defines them (`button-primary-hover`, `input-field-focus`, `link-hover`).
- Maintain `{colors.background}` as the canvas on every surface; use `{colors.surface-container}` and `{colors.surface-bright}` for layered elevation.
- Keep body text in `{colors.on-surface}` and secondary labels in `{colors.on-surface-variant}`.
- Match CTA copy style — direct, imperative, concise — per the Voice & Content section.

**Must NOT:**
- Introduce colors, radii, or font families absent from the spec.
- Apply `{colors.primary}` to large text blocks; restrict it to accents, highlights, and focus borders.
- Use light or mid-tone backgrounds; the interface is strictly dark-mode.
- Add emoji, filler copy, or marketing language.
- Rewrite, replace, or restructure existing page copy, headings, navigation items, or routes as a side effect of applying tokens.

## When in doubt
- If a required token isn't defined in the spec, ask the user before inventing a value.
- For ambiguous backgrounds, default to `{colors.surface-container}`; for ambiguous text, default to `{colors.on-surface}`.
- Prefer composing existing components over introducing new tokens or variants.
- Tokens marked "(inferred)" in any spec prose are approximations; a verified theme file or Figma token source takes precedence.
- For unspecified breakpoints, apply mobile-first layout with a single breakpoint at 768px, respecting the max-width container and `{spacing.2xl}` section margins described in Layout notes.
