back to gallery
design language·ion-pixel-standard

Ion Pixel Standard

A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.

Download DESIGN.md

Portable DESIGN.md source of truth for most agents and apps.

the spec

specification

philosophy
summary
A clean product UI language where Apple-like neutral surfaces are sharpened by tiny pixel-calibration details and a narrow cool-electric chroma system of indigo, cyan, turquoise, and lime. Pixel cues behave like precision instrumentation rather than nostalgia or game decoration.
values
premium restraint with a single cool-electric highlight familypixel geometry used for measurable state, sequence, and verificationhigh readability with pixel-influenced type reserved for accentswhite neutral surfaces that make chroma feel functional, not ornamental
anti-values
×arcade, terminal, cyberpunk, or Minecraft-style block overload×rainbow accent sprawl, warm garnish, decorative side rails, square-grid backgrounds, chipped corners, or uneven borders
tokens
borders4 items
accent width
2px
character
even cool-gray hairlines; focus states add inset cyan ring plus tiny lime pixel cells, never chipped corners or decorative side rails
default width
1px
style
solid
colors12 items
accent
#B7FF19
background
#F7F9FC
border
#DDE5F0
error
#E5484D
info
#00C2FF
muted
#667085
primary
#2B2DD6
secondary
#00B8D9
success
#34D399
surface
#FFFFFF
text
#101827
warning
#EAB308
motion3 items
duration
160ms
easing
cubic-bezier(0.2, 0.8, 0.2, 1)
philosophy
fast precision motion: pixel cells step on, panels lift 2px, and focus rings resolve without bounce or game-like animation
radii5 items
full
9999px
lg
24px
md
16px
none
0
sm
10px
shadows3 items
lg
0 28px 70px rgba(16,24,39,0.14)
md
0 16px 36px rgba(43,45,214,0.10)
sm
0 1px 2px rgba(16,24,39,0.06)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
no square grid and no dotted default; background remains a quiet neutral field with rare oversized translucent orb gradients
card style
rounded white cards with 1px cool borders, soft shadow, and internal pixel status cells instead of exterior stripes
treatment
clean white and cool-mist neutral surfaces with restrained indigo/cyan inset glow only on active states
typography8 items
base size
16px
body font
Inter
google fonts url
https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=Space+Grotesk:wght@500;600;700&family=Pixelify+Sans:wght@400;500;600&display=swap
heading font
Space Grotesk
letter spacing
-0.018em
line height
1.5
mono font
Pixelify Sans
scale ratio
1.22
rules
composition
Use spacious white product canvases with one dominant workspace panel, a compact top control band, and floating measurement cards that form a calm asymmetric instrument layout.
density

Medium-low density with generous gutters, compact micro-metadata, and grouped controls; never fill whitespace with decorative patterning.

hierarchy
Headings use Space Grotesk for premium clarity; body and controls use Inter; pixel type is limited to metadata, counters, and short state labels to preserve readability.
signature patterns
Pixel rail micro-indicators appear as three to seven small square cells inside badges, buttons, progress bars, and table states, not as page backgrounds.Ion focus rings combine a 1px cyan outline, a faint indigo halo, and one lime verification cell at the active corner for accessible component states.Chroma sequence blocks use indigo to cyan to lime within a single functional scale for calibration progress, avoiding unrelated warm colors or rainbow expansion.Rounded product cards contain crisp stepped internal annotations and coordinate chips, creating a pixel precision motif without blocky component silhouettes.
layout
breakpoints

mobile 375px single column, tablet 768px two-column stack, desktop 1200px+ asymmetric workspace

grid

Twelve-column desktop shell with a 72px top band, content max-width near 1180px, and card spans of 4/8 or 5/7 columns depending on product task.

whitespace

Large outer margins and 24-32px card gaps keep the cool chroma accents rare, readable, and premium.

guidance
do
  • Use pixel typography for labels, counters, badges, timestamps, and short coordinate annotations only.
  • Keep backgrounds white or cool neutral with no square grid and no default dotted texture.
  • Make cyan, turquoise, and lime communicate focus, live data, verification, or sequence state.
  • Use even borders and rounded silhouettes; place pixel details inside components.
avoid
  • Do not use square-grid backgrounds, decorative side rails, card stripes, chipped corners, or uneven borders.
  • Do not turn the system into a game, terminal hacker UI, arcade skin, or cyberpunk neon cliché.
  • Do not add warm accent colors except semantic error/warning tokens, and never expand into rainbow palette.
  • Do not set body copy in a low-resolution pixel font or compromise legibility.
katagami spec
# Ion Pixel Standard

## Philosophy

A clean product UI language where Apple-like neutral surfaces are sharpened by tiny pixel-calibration details and a narrow cool-electric chroma system of indigo, cyan, turquoise, and lime. Pixel cues behave like precision instrumentation rather than nostalgia or game decoration.

### Values

- premium restraint with a single cool-electric highlight family
- pixel geometry used for measurable state, sequence, and verification
- high readability with pixel-influenced type reserved for accents
- white neutral surfaces that make chroma feel functional, not ornamental

### Anti-Values

- arcade, terminal, cyberpunk, or Minecraft-style block overload
- rainbow accent sprawl, warm garnish, decorative side rails, square-grid backgrounds, chipped corners, or uneven borders

### Visual Character

- White and mist-neutral page background with flat white panels, low alpha indigo hairline borders, and no repeated square-grid or dotted backdrop texture.
- Buttons, badges, charts, and status modules use stepped 2px pixel notches as internal glyphs or end-cap indicators while outer component corners remain smoothly rounded.
- A compact pixel-influenced accent font appears only in counters, badges, state labels, and coordinate annotations while headings and body copy stay in crisp geometric sans type.
- Indigo establishes primary action and navigation, cyan/turquoise expresses live data and focus, and neon lime appears only for verified success or active sequence moments.
- Component states use small segmented blocks, binary-like progress cells, and luminous focus rings that align to content edges rather than decorative side stripes.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: even cool-gray hairlines; focus states add inset cyan ring plus tiny lime pixel cells, never chipped corners or decorative side rails
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#B7FF19` |
| background | `#F7F9FC` |
| border | `#DDE5F0` |
| error | `#E5484D` |
| info | `#00C2FF` |
| muted | `#667085` |
| primary | `#2B2DD6` |
| secondary | `#00B8D9` |
| success | `#34D399` |
| surface | `#FFFFFF` |
| text | `#101827` |
| warning | `#EAB308` |

### Motion

- **Duration**: 160ms
- **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1)
- **Philosophy**: fast precision motion: pixel cells step on, panels lift 2px, and focus rings resolve without bounce or game-like animation

### Radii

- **Full**: 9999px
- **Lg**: 24px
- **Md**: 16px
- **None**: 0
- **Sm**: 10px

### Shadows

- **Lg**: 0 28px 70px rgba(16,24,39,0.14)
- **Md**: 0 16px 36px rgba(43,45,214,0.10)
- **Sm**: 0 1px 2px rgba(16,24,39,0.06)

### Spacing

- **Base**: 8px
- **Scale**: [4,8,12,16,24,32,48,64]

### Surfaces

- **Bg Pattern**: no square grid and no dotted default; background remains a quiet neutral field with rare oversized translucent orb gradients
- **Card Style**: rounded white cards with 1px cool borders, soft shadow, and internal pixel status cells instead of exterior stripes
- **Treatment**: clean white and cool-mist neutral surfaces with restrained indigo/cyan inset glow only on active states

### Typography

- **Base Size**: 16px
- **Body Font**: Inter
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=Space+Grotesk:wght@500;600;700&family=Pixelify+Sans:wght@400;500;600&display=swap
- **Heading Font**: Space Grotesk
- **Letter Spacing**: -0.018em
- **Line Height**: 1.5
- **Mono Font**: Pixelify Sans
- **Scale Ratio**: 1.22

## Rules

### Composition

Use spacious white product canvases with one dominant workspace panel, a compact top control band, and floating measurement cards that form a calm asymmetric instrument layout.

### Density

Medium-low density with generous gutters, compact micro-metadata, and grouped controls; never fill whitespace with decorative patterning.

### Hierarchy

Headings use Space Grotesk for premium clarity; body and controls use Inter; pixel type is limited to metadata, counters, and short state labels to preserve readability.

### Signature Patterns

- Pixel rail micro-indicators appear as three to seven small square cells inside badges, buttons, progress bars, and table states, not as page backgrounds.
- Ion focus rings combine a 1px cyan outline, a faint indigo halo, and one lime verification cell at the active corner for accessible component states.
- Chroma sequence blocks use indigo to cyan to lime within a single functional scale for calibration progress, avoiding unrelated warm colors or rainbow expansion.
- Rounded product cards contain crisp stepped internal annotations and coordinate chips, creating a pixel precision motif without blocky component silhouettes.

## Layout

### Breakpoints

mobile 375px single column, tablet 768px two-column stack, desktop 1200px+ asymmetric workspace

### Grid

Twelve-column desktop shell with a 72px top band, content max-width near 1180px, and card spans of 4/8 or 5/7 columns depending on product task.

### Whitespace

Large outer margins and 24-32px card gaps keep the cool chroma accents rare, readable, and premium.

## Guidance

### Do

- Use pixel typography for labels, counters, badges, timestamps, and short coordinate annotations only.
- Keep backgrounds white or cool neutral with no square grid and no default dotted texture.
- Make cyan, turquoise, and lime communicate focus, live data, verification, or sequence state.
- Use even borders and rounded silhouettes; place pixel details inside components.

### Don't

- Do not use square-grid backgrounds, decorative side rails, card stripes, chipped corners, or uneven borders.
- Do not turn the system into a game, terminal hacker UI, arcade skin, or cyberpunk neon cliché.
- Do not add warm accent colors except semantic error/warning tokens, and never expand into rainbow palette.
- Do not set body copy in a low-resolution pixel font or compromise legibility.
DESIGN.md
---
version: "alpha"
name: "Ion Pixel Standard"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#B7FF19"
  background: "#F7F9FC"
  border: "#DDE5F0"
  error: "#E5484D"
  info: "#00C2FF"
  muted: "#667085"
  primary: "#2B2DD6"
  secondary: "#00B8D9"
  success: "#34D399"
  surface: "#FFFFFF"
  text: "#101827"
  warning: "#EAB308"
typography:
  headline-lg:
    fontFamily: "Space Grotesk"
    fontSize: "1.816rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.018em"
  headline-md:
    fontFamily: "Space Grotesk"
    fontSize: "1.488rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.018em"
  body-md:
    fontFamily: "Inter"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "-0.018em"
  label-md:
    fontFamily: "Pixelify Sans"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "24px"
  md: "16px"
  none: "0px"
  sm: "10px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#ffffff"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  card-surface:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  input-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    height: "44px"
---

# Ion Pixel Standard

## Overview

A clean product UI language where Apple-like neutral surfaces are sharpened by tiny pixel-calibration details and a narrow cool-electric chroma system of indigo, cyan, turquoise, and lime. Pixel cues behave like precision instrumentation rather than nostalgia or game decoration.

### Values

- premium restraint with a single cool-electric highlight family
- pixel geometry used for measurable state, sequence, and verification
- high readability with pixel-influenced type reserved for accents
- white neutral surfaces that make chroma feel functional, not ornamental

### Anti-Values

- arcade, terminal, cyberpunk, or Minecraft-style block overload
- rainbow accent sprawl, warm garnish, decorative side rails, square-grid backgrounds, chipped corners, or uneven borders

### Visual Character

- White and mist-neutral page background with flat white panels, low alpha indigo hairline borders, and no repeated square-grid or dotted backdrop texture.
- Buttons, badges, charts, and status modules use stepped 2px pixel notches as internal glyphs or end-cap indicators while outer component corners remain smoothly rounded.
- A compact pixel-influenced accent font appears only in counters, badges, state labels, and coordinate annotations while headings and body copy stay in crisp geometric sans type.
- Indigo establishes primary action and navigation, cyan/turquoise expresses live data and focus, and neon lime appears only for verified success or active sequence moments.
- Component states use small segmented blocks, binary-like progress cells, and luminous focus rings that align to content edges rather than decorative side stripes.

## Colors

Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.

| Token | Value |
|-------|-------|
| accent | `#B7FF19` |
| background | `#F7F9FC` |
| border | `#DDE5F0` |
| error | `#E5484D` |
| info | `#00C2FF` |
| muted | `#667085` |
| primary | `#2B2DD6` |
| secondary | `#00B8D9` |
| success | `#34D399` |
| surface | `#FFFFFF` |
| text | `#101827` |
| warning | `#EAB308` |

## Typography

- **Headline-Lg**: Space Grotesk, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Space Grotesk, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Inter, 16px, weight 400, line-height 1.5.
- **Label-Md**: Pixelify Sans, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`

### Breakpoints

mobile 375px single column, tablet 768px two-column stack, desktop 1200px+ asymmetric workspace

### Grid

Twelve-column desktop shell with a 72px top band, content max-width near 1180px, and card spans of 4/8 or 5/7 columns depending on product task.

### Whitespace

Large outer margins and 24-32px card gaps keep the cool chroma accents rare, readable, and premium.

## Elevation & Depth

### Shadows

- **Lg**: 0 28px 70px rgba(16,24,39,0.14)
- **Md**: 0 16px 36px rgba(43,45,214,0.10)
- **Sm**: 0 1px 2px rgba(16,24,39,0.06)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `24px`
- **Md**: `16px`
- **None**: `0px`
- **Sm**: `10px`

### Surfaces

- **Bg Pattern**: no square grid and no dotted default; background remains a quiet neutral field with rare oversized translucent orb gradients
- **Card Style**: rounded white cards with 1px cool borders, soft shadow, and internal pixel status cells instead of exterior stripes
- **Treatment**: clean white and cool-mist neutral surfaces with restrained indigo/cyan inset glow only on active states

### Borders

- **Accent Width**: 2px
- **Character**: even cool-gray hairlines; focus states add inset cyan ring plus tiny lime pixel cells, never chipped corners or decorative side rails
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use spacious white product canvases with one dominant workspace panel, a compact top control band, and floating measurement cards that form a calm asymmetric instrument layout.

### Density

Medium-low density with generous gutters, compact micro-metadata, and grouped controls; never fill whitespace with decorative patterning.

### Hierarchy

Headings use Space Grotesk for premium clarity; body and controls use Inter; pixel type is limited to metadata, counters, and short state labels to preserve readability.

### Signature Patterns

- Pixel rail micro-indicators appear as three to seven small square cells inside badges, buttons, progress bars, and table states, not as page backgrounds.
- Ion focus rings combine a 1px cyan outline, a faint indigo halo, and one lime verification cell at the active corner for accessible component states.
- Chroma sequence blocks use indigo to cyan to lime within a single functional scale for calibration progress, avoiding unrelated warm colors or rainbow expansion.
- Rounded product cards contain crisp stepped internal annotations and coordinate chips, creating a pixel precision motif without blocky component silhouettes.

## shadcn/ui Usage

When the target app uses shadcn/ui, copy DESIGN.md with shadcn instead of the plain DESIGN.md. It contains the same Katagami design-language source plus the shadcn/ui primitives, imports, theme variables, component recipes, and preview-shot guidance.

DESIGN.md with shadcn: `/language/en-019e4bf6-c8a4-76f2-80d8-2abb47c1fef2/DESIGN.with-shadcn.md`.

The shadcn page also exposes optional machine-readable files for automation, but the human-facing handoff is DESIGN.md with shadcn.

Install recommended primitives with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

Use these primitives in shadcn apps:
- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Implementation rule for agents: import shadcn primitives from `@/components/ui/*`, apply the generated CSS variables first, then compose the language-specific recipes from the companion MD. Katagami remains the source of truth; shadcn names are the implementation surface.

## Do's and Don'ts

- Do Use pixel typography for labels, counters, badges, timestamps, and short coordinate annotations only.
- Do Keep backgrounds white or cool neutral with no square grid and no default dotted texture.
- Do Make cyan, turquoise, and lime communicate focus, live data, verification, or sequence state.
- Do Use even borders and rounded silhouettes; place pixel details inside components.
- Don't Do not use square-grid backgrounds, decorative side rails, card stripes, chipped corners, or uneven borders.
- Don't Do not turn the system into a game, terminal hacker UI, arcade skin, or cyberpunk neon cliché.
- Don't Do not add warm accent colors except semantic error/warning tokens, and never expand into rainbow palette.
- Don't Do not set body copy in a low-resolution pixel font or compromise legibility.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "ion-pixel-standard",
  "type": "registry:theme",
  "title": "Ion Pixel Standard shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F9FC",
      "foreground": "#101827",
      "card": "#FFFFFF",
      "card-foreground": "#101827",
      "popover": "#FFFFFF",
      "popover-foreground": "#101827",
      "primary": "#2B2DD6",
      "primary-foreground": "#ffffff",
      "secondary": "#00B8D9",
      "secondary-foreground": "#ffffff",
      "muted": "#667085",
      "muted-foreground": "#101827",
      "accent": "#B7FF19",
      "accent-foreground": "#111111",
      "destructive": "#E5484D",
      "border": "#DDE5F0",
      "input": "#DDE5F0",
      "ring": "#B7FF19",
      "chart-1": "#2B2DD6",
      "chart-2": "#00B8D9",
      "chart-3": "#B7FF19",
      "chart-4": "#34D399",
      "chart-5": "#EAB308",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#101827",
      "sidebar-primary": "#2B2DD6",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#00C2FF",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#DDE5F0",
      "sidebar-ring": "#B7FF19",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2B2DD6",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#B7FF19",
      "accent-foreground": "#111111",
      "destructive": "#E5484D",
      "border": "#303642",
      "input": "#303642",
      "ring": "#B7FF19",
      "chart-1": "#2B2DD6",
      "chart-2": "#00B8D9",
      "chart-3": "#B7FF19",
      "chart-4": "#34D399",
      "chart-5": "#EAB308",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2B2DD6",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#B7FF19",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#B7FF19",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e4bf6-c8a4-76f2-80d8-2abb47c1fef2",
    "slug": "ion-pixel-standard",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · ion-pixel-standard
DESIGN.md

at a glance

Palette

Typography

headline-lgSpace Grotesk · 29px · 700

The quick brown fox jumps

headline-mdSpace Grotesk · 24px · 600

The quick brown fox jumps

body-mdInter · 16px · 400

The quick brown fox jumps

label-mdPixelify Sans · 12px · 600

The quick brown fox jumps

Components

New
Card title

Components rendered with this language’s tokens — colors, type, and rounded corners as specified.

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl48px
  • 4xl64px

Shape

full9999px
lg24px
md16px
none0px
sm10px
shadcn/ui

implementation kit

needs agent-authored kitcompatibility fallback
shadcn compatibility only
The generated theme variables are available, but the polished shadcn component recipes and shots have not been authored by the Katagami agent yet.
fallbackprimitives render
Compatibility proof
Local shadcn-style primitives accept the generated theme variables.
primaryaccentsurfacemutedwarningerror
table rhythm
buttonok
cardok
inputok
recommendedcompatibility fallback

DESIGN.md with shadcn

Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.

advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #F7F9FC;
  --foreground: #101827;
  --card: #FFFFFF;
  --card-foreground: #101827;
  --popover: #FFFFFF;
  --popover-foreground: #101827;
  --primary: #2B2DD6;
  --primary-foreground: #ffffff;
  --secondary: #00B8D9;
  --secondary-foreground: #ffffff;
  --muted: #667085;
  --muted-foreground: #101827;
  --accent: #B7FF19;
  --accent-foreground: #111111;
  --destructive: #E5484D;
  --border: #DDE5F0;
  --input: #DDE5F0;
  --ring: #B7FF19;
  --chart-1: #2B2DD6;
  --chart-2: #00B8D9;
  --chart-3: #B7FF19;
  --chart-4: #34D399;
  --chart-5: #EAB308;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #101827;
  --sidebar-primary: #2B2DD6;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #00C2FF;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #DDE5F0;
  --sidebar-ring: #B7FF19;
  --radius: 16px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #2B2DD6;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #B7FF19;
  --accent-foreground: #111111;
  --destructive: #E5484D;
  --border: #303642;
  --input: #303642;
  --ring: #B7FF19;
  --chart-1: #2B2DD6;
  --chart-2: #00B8D9;
  --chart-3: #B7FF19;
  --chart-4: #34D399;
  --chart-5: #EAB308;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #2B2DD6;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #B7FF19;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #B7FF19;
  --radius: 16px;
}
tsx starter
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
  Card,
  CardContent,
  CardDescription,
  CardFooter,
  CardHeader,
  CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";

export function IonPixelStandardShadcnKit() {
  return (
    <section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
      <div className="flex items-start justify-between gap-4">
        <div>
          <Badge variant="outline">shadcn/ui</Badge>
          <h2 className="mt-3 text-2xl font-semibold tracking-tight">Ion Pixel Standard</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

      <Tabs defaultValue="components">
        <TabsList>
          <TabsTrigger value="components">Components</TabsTrigger>
          <TabsTrigger value="states">States</TabsTrigger>
          <TabsTrigger value="export">Export</TabsTrigger>
        </TabsList>
      </Tabs>

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
theme JSONstored + verified
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "cssVars": {
    "dark": {
      "accent": "#B7FF19",
      "accent-foreground": "#111111",
      "background": "#0f1115",
      "border": "#303642",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "chart-1": "#2B2DD6",
      "chart-2": "#00B8D9",
      "chart-3": "#B7FF19",
      "chart-4": "#34D399",
      "chart-5": "#EAB308",
      "destructive": "#E5484D",
      "foreground": "#f8fafc",
      "input": "#303642",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2B2DD6",
      "primary-foreground": "#ffffff",
      "radius": "16px",
      "ring": "#B7FF19",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "sidebar": "#181b22",
      "sidebar-accent": "#B7FF19",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2B2DD6",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#B7FF19"
    },
    "light": {
      "accent": "#B7FF19",
      "accent-foreground": "#111111",
      "background": "#F7F9FC",
      "border": "#DDE5F0",
      "card": "#FFFFFF",
      "card-foreground": "#101827",
      "chart-1": "#2B2DD6",
      "chart-2": "#00B8D9",
      "chart-3": "#B7FF19",
      "chart-4": "#34D399",
      "chart-5": "#EAB308",
      "destructive": "#E5484D",
      "foreground": "#101827",
      "input": "#DDE5F0",
      "muted": "#667085",
      "muted-foreground": "#101827",
      "popover": "#FFFFFF",
      "popover-foreground": "#101827",
      "primary": "#2B2DD6",
      "primary-foreground": "#ffffff",
      "radius": "16px",
      "ring": "#B7FF19",
      "secondary": "#00B8D9",
      "secondary-foreground": "#ffffff",
      "sidebar": "#FFFFFF",
      "sidebar-accent": "#00C2FF",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#DDE5F0",
      "sidebar-foreground": "#101827",
      "sidebar-primary": "#2B2DD6",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#B7FF19"
    },
    "theme": {}
  },
  "meta": {
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "languageId": "en-019e4bf6-c8a4-76f2-80d8-2abb47c1fef2",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    },
    "slug": "ion-pixel-standard",
    "source": "katagami"
  },
  "name": "ion-pixel-standard",
  "title": "Ion Pixel Standard shadcn Theme",
  "type": "registry:theme"
}
component recipescompatibility fallback
# Ion Pixel Standard shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4bf6-c8a4-76f2-80d8-2abb47c1fef2`
Slug: `ion-pixel-standard`

## Intent

A clean product UI language where Apple-like neutral surfaces are sharpened by tiny pixel-calibration details and a narrow cool-electric chroma system of indigo, cyan, turquoise, and lime. Pixel cues behave like precision instrumentation rather than nostalgia or game decoration.

## Required primitives

- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Install with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

## Token cues

Colors:

{
  "accent": "#B7FF19",
  "background": "#F7F9FC",
  "border": "#DDE5F0",
  "error": "#E5484D",
  "info": "#00C2FF",
  "muted": "#667085",
  "primary": "#2B2DD6",
  "secondary": "#00B8D9",
  "success": "#34D399",
  "surface": "#FFFFFF",
  "text": "#101827",
  "warning": "#EAB308"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Inter",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=Space+Grotesk:wght@500;600;700&family=Pixelify+Sans:wght@400;500;600&display=swap",
  "heading_font": "Space Grotesk",
  "letter_spacing": "-0.018em",
  "line_height": 1.5,
  "mono_font": "Pixelify Sans",
  "scale_ratio": 1.22
}

## Visual character to preserve

- White and mist-neutral page background with flat white panels, low alpha indigo hairline borders, and no repeated square-grid or dotted backdrop texture.
- Buttons, badges, charts, and status modules use stepped 2px pixel notches as internal glyphs or end-cap indicators while outer component corners remain smoothly rounded.
- A compact pixel-influenced accent font appears only in counters, badges, state labels, and coordinate annotations while headings and body copy stay in crisp geometric sans type.
- Indigo establishes primary action and navigation, cyan/turquoise expresses live data and focus, and neon lime appears only for verified success or active sequence moments.
- Component states use small segmented blocks, binary-like progress cells, and luminous focus rings that align to content edges rather than decorative side stripes.

## ShadSync visual profile

{
  "family": "system",
  "material": "flat",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": true,
  "stickerBadges": true,
  "motion": "lift",
  "density": "dense",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.

### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.

### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.

### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.

### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.

## Preview shots

- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/ion-pixel-standard/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use pixel typography for labels, counters, badges, timestamps, and short coordinate annotations only.; Keep backgrounds white or cool neutral with no square grid and no default dotted texture.; Make cyan, turquoise, and lime communicate focus, live data, verification, or sequence state.; Use even borders and rounded silhouettes; place pixel details inside components.
- Do not: Do not use square-grid backgrounds, decorative side rails, card stripes, chipped corners, or uneven borders.; Do not turn the system into a game, terminal hacker UI, arcade skin, or cyberpunk neon cliché.; Do not add warm accent colors except semantic error/warning tokens, and never expand into rainbow palette.; Do not set body copy in a low-resolution pixel font or compromise legibility.

## Copy-paste component example

This generated starter proves the import shape. Production Katagami agents should replace it with a language-specific product composition.

```tsx
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
  Card,
  CardContent,
  CardDescription,
  CardFooter,
  CardHeader,
  CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";

export function IonPixelStandardShadcnKit() {
  return (
    <section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
      <div className="flex items-start justify-between gap-4">
        <div>
          <Badge variant="outline">shadcn/ui</Badge>
          <h2 className="mt-3 text-2xl font-semibold tracking-tight">Ion Pixel Standard</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

      <Tabs defaultValue="components">
        <TabsList>
          <TabsTrigger value="components">Components</TabsTrigger>
          <TabsTrigger value="states">States</TabsTrigger>
          <TabsTrigger value="export">Export</TabsTrigger>
        </TabsList>
      </Tabs>

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
```

## Layout notes

{
  "breakpoints": "mobile 375px single column, tablet 768px two-column stack, desktop 1200px+ asymmetric workspace",
  "grid": "Twelve-column desktop shell with a 72px top band, content max-width near 1180px, and card spans of 4/8 or 5/7 columns depending on product task.",
  "whitespace": "Large outer margins and 24-32px card gaps keep the cool chroma accents rare, readable, and premium."
}
preview shotscompatibility fallback
{
  "artifact": "katagami:shadcn-preview-shots",
  "version": "preview-shots-v1",
  "generator": "katagami-ui-compatibility-projection",
  "generatedBy": "katagami-ui-projection",
  "requiresVisualProfile": true,
  "schema": "katagami:shadcn-preview-shots/renderable-v1",
  "renderable": true,
  "language": {
    "id": "en-019e4bf6-c8a4-76f2-80d8-2abb47c1fef2",
    "name": "Ion Pixel Standard",
    "slug": "ion-pixel-standard"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "White and mist-neutral page background with flat white panels, low alpha indigo hairline borders, and no repeated square-grid or dotted backdrop texture.",
    "Buttons, badges, charts, and status modules use stepped 2px pixel notches as internal glyphs or end-cap indicators while outer component corners remain smoothly rounded.",
    "A compact pixel-influenced accent font appears only in counters, badges, state labels, and coordinate annotations while headings and body copy stay in crisp geometric sans type.",
    "Indigo establishes primary action and navigation, cyan/turquoise expresses live data and focus, and neon lime appears only for verified success or active sequence moments.",
    "Component states use small segmented blocks, binary-like progress cells, and luminous focus rings that align to content edges rather than decorative side stripes."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": true,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Ion Pixel Standard launch room",
        "description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
        "primaryAction": "Apply theme",
        "secondaryAction": "Review states",
        "stats": [
          {
            "label": "components",
            "value": "16",
            "tone": "accent"
          },
          {
            "label": "states",
            "value": "ready"
          },
          {
            "label": "density",
            "value": "balanced",
            "tone": "warning"
          }
        ],
        "rows": [
          {
            "label": "Primary flow",
            "value": "mapped",
            "status": "active"
          },
          {
            "label": "Token coverage",
            "value": "semantic",
            "status": "synced"
          },
          {
            "label": "Responsive proof",
            "value": "queued",
            "status": "review"
          }
        ],
        "statuses": [
          "Active",
          "Synced",
          "Draft"
        ]
      }
    },
    {
      "id": "detail-editor",
      "title": "Detail editor",
      "viewport": "tablet",
      "primitives": [
        "button",
        "card",
        "input",
        "textarea",
        "select",
        "checkbox",
        "switch",
        "slider",
        "dialog",
        "sheet"
      ],
      "composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
      "mustShow": [
        "focus ring",
        "error or destructive state",
        "dialog or sheet treatment",
        "written guidance content"
      ],
      "avoid": [
        "unstyled browser controls",
        "floating cards inside cards",
        "missing labels"
      ],
      "scene": {
        "eyebrow": "editing flow",
        "headline": "Language recipe editor",
        "description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
        "primaryAction": "Save recipe",
        "secondaryAction": "Open sheet",
        "fields": [
          {
            "label": "Component family",
            "value": "Narrative cards"
          },
          {
            "label": "State treatment",
            "value": "Visible focus + validation"
          },
          {
            "label": "Motion",
            "value": "Small lift, no opacity-only fade"
          }
        ],
        "statuses": [
          "Focus",
          "Invalid",
          "Confirmed"
        ]
      }
    },
    {
      "id": "data-operations",
      "title": "Data operations",
      "viewport": "mobile",
      "primitives": [
        "button",
        "tabs",
        "badge",
        "dropdown-menu",
        "table",
        "tooltip",
        "separator"
      ],
      "composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
      "mustShow": [
        "responsive reflow",
        "dense row styling",
        "menu affordance",
        "status badge system"
      ],
      "avoid": [
        "desktop-only tables",
        "text overflow",
        "default shadcn spacing without Katagami character"
      ],
      "scene": {
        "eyebrow": "operations",
        "headline": "Compact review queue",
        "description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
        "primaryAction": "Resolve",
        "secondaryAction": "Filter",
        "rows": [
          {
            "label": "Button hierarchy",
            "value": "approved",
            "status": "ok"
          },
          {
            "label": "Table rhythm",
            "value": "needs pass",
            "status": "watch"
          },
          {
            "label": "Empty state",
            "value": "designed",
            "status": "done"
          }
        ],
        "statuses": [
          "Queued",
          "Blocked",
          "Done"
        ]
      }
    }
  ],
  "componentRecipes": [
    {
      "primitive": "button",
      "intent": "Prove action hierarchy, focus, disabled, and destructive states."
    },
    {
      "primitive": "card",
      "intent": "Carry the language surface, border, elevation, and density rules."
    },
    {
      "primitive": "input",
      "intent": "Show labels, focus rings, validation, and spacing rhythm."
    },
    {
      "primitive": "textarea",
      "intent": "Show longer guidance, validation copy, and writing density."
    },
    {
      "primitive": "select",
      "intent": "Show filtering, selection contrast, and menu trigger styling."
    },
    {
      "primitive": "dialog",
      "intent": "Show centered decision states and overlay treatment."
    },
    {
      "primitive": "sheet",
      "intent": "Show contextual side panels and responsive editing."
    },
    {
      "primitive": "tabs",
      "intent": "Show navigational structure and active/inactive contrast."
    },
    {
      "primitive": "badge",
      "intent": "Show compact status vocabulary and semantic colors."
    },
    {
      "primitive": "separator",
      "intent": "Show section rhythm without generic gray dividers."
    },
    {
      "primitive": "checkbox",
      "intent": "Show binary selection with visible focus and checked states."
    },
    {
      "primitive": "switch",
      "intent": "Show settings toggles and on/off contrast."
    },
    {
      "primitive": "slider",
      "intent": "Show numeric adjustment with track/thumb styling."
    },
    {
      "primitive": "tooltip",
      "intent": "Show concise explanation styling above compact controls."
    },
    {
      "primitive": "dropdown-menu",
      "intent": "Show action menus, destructive items, and grouped choices."
    },
    {
      "primitive": "table",
      "intent": "Show dense operational data, separators, row states, and responsive behavior."
    }
  ],
  "qualityRules": {
    "do": [
      "Use pixel typography for labels, counters, badges, timestamps, and short coordinate annotations only.",
      "Keep backgrounds white or cool neutral with no square grid and no default dotted texture.",
      "Make cyan, turquoise, and lime communicate focus, live data, verification, or sequence state.",
      "Use even borders and rounded silhouettes; place pixel details inside components."
    ],
    "dont": [
      "Do not use square-grid backgrounds, decorative side rails, card stripes, chipped corners, or uneven borders.",
      "Do not turn the system into a game, terminal hacker UI, arcade skin, or cyberpunk neon cliché.",
      "Do not add warm accent colors except semantic error/warning tokens, and never expand into rainbow palette.",
      "Do not set body copy in a low-resolution pixel font or compromise legibility."
    ]
  }
}
related

More like this