back to gallery
design language·phosphor-command-grid

Phosphor Command Grid

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
Phosphor Command Grid translates historical green-screen terminal constraints into a disciplined modern product interface: dense monospace information, black glass surfaces, square technical panels, and just enough CRT artifacting to make the system feel alive without becoming decorative nostalgia.
values
Operational clarity before ornamentAuthentic terminal rhythm from monospaced rows and command promptsHigh contrast status communication with restrained accent colorEnterprise-grade hierarchy anchored by grid discipline and repeatable components
anti-values
×Rounded lifestyle-app softness that breaks the machine-console character×Rainbow cyberpunk excess or decorative glitch effects that obscure content×Skeuomorphic monitor bezels, fake hardware chrome, or novelty terminal jokes
tokens
borders4 items
accent width
3px
character
Thin phosphor grid lines define every region, with amber/cyan state strokes used sparingly for alerts and selected modules.
default width
1px
style
solid
colors12 items
accent
#ffb454
background
#050706
border
#1d6b4c
error
#ff4d6d
info
#3fd7ff
muted
#6fae8b
primary
#00ff66
secondary
#0b2f26
success
#00ff66
surface
#0b1110
text
#d7ffe5
warning
#ffb454
motion3 items
duration
140ms
easing
steps(2, jump-none)
philosophy
snappy
radii5 items
full
0
lg
0
md
0
none
0
sm
0
shadows3 items
lg
0 0 60px rgba(0,255,102,0.22), inset 0 0 30px rgba(63,215,255,0.04)
md
0 0 24px rgba(0,255,102,0.18), inset 0 0 18px rgba(0,255,102,0.04)
sm
0 0 10px rgba(0,255,102,0.16)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
lines
card style
Flat black-green panels with subtle CRT grain, inner phosphor glow, square edges, and command-line header strips.
treatment
noise
typography8 items
base size
16px
body font
IBM Plex Mono
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600;700&display=swap
heading font
IBM Plex Mono
letter spacing
0.01em
line height
1.55
mono font
IBM Plex Mono
scale ratio
1.2
rules
composition

Use a system-console layout: fixed header, narrow command rail, large terminal workspace, and right-side telemetry panel aligned to an 8px grid.

density

Dense by default with compact rows and narrow gutters, but preserve enough line height for readable operational dashboards on small screens.

hierarchy
Primary hierarchy comes from phosphor brightness, uppercase prompt labels, bordered modules, and tabular rows; the largest type is still monospaced and technical.
signature patterns
Apply a global CRT overlay using repeating-linear-gradient scanlines plus a faint animated opacity shimmer on the body pseudo-layer.Prefix section titles and buttons with terminal syntax marks ($, >, ::, [01]) generated in markup or CSS before content.Draw amber corner ticks on panels with absolutely positioned ::before/::after pseudo-elements instead of border radius or drop-shadow decoration.Use block-cursor interactions: focused fields, selected navigation, and live status labels include a blinking rectangular caret or solid phosphor left bar.Render data as fixed-width command output rows with dotted grid separators and color-coded status tokens rather than pictorial cards.
layout
breakpoints

Desktop >= 1100px uses three columns; tablet 700-1099px collapses to two columns with telemetry below; mobile < 700px becomes a single stacked console.

grid

Desktop uses a 240px command rail, flexible central terminal, and 320px telemetry column; internal panels follow repeatable 8px grid increments.

whitespace

Whitespace is compact and mechanical: 8px row gaps, 16-24px panel padding, and large empty areas only inside terminal output panes to imply screen depth.

guidance
do
  • Use IBM Plex Mono or a comparable technical monospace for all text, including numbers and form controls.
  • Keep components square with explicit 1px borders, clear focus rings, and phosphor text-shadow only on high-value labels.
  • Express navigation, filters, alerts, and actions through command-line language and bracketed status tokens.
  • Balance CRT effects with legibility by keeping scanlines subtle and never placing heavy glow behind long paragraphs.
avoid
  • Do not use rounded cards, pill chips, soft gradients, or consumer-app shadows.
  • Do not turn the palette into neon cyberpunk; green is primary, amber and cyan are scarce operational accents.
  • Do not use decorative glitch animation that moves text or disrupts reading.
  • Do not replace structured dashboard content with nostalgic ASCII art unless it serves an actual interface purpose.
katagami spec
# Phosphor Command Grid

## Philosophy

Phosphor Command Grid translates historical green-screen terminal constraints into a disciplined modern product interface: dense monospace information, black glass surfaces, square technical panels, and just enough CRT artifacting to make the system feel alive without becoming decorative nostalgia.

### Values

- Operational clarity before ornament
- Authentic terminal rhythm from monospaced rows and command prompts
- High contrast status communication with restrained accent color
- Enterprise-grade hierarchy anchored by grid discipline and repeatable components

### Anti-Values

- Rounded lifestyle-app softness that breaks the machine-console character
- Rainbow cyberpunk excess or decorative glitch effects that obscure content
- Skeuomorphic monitor bezels, fake hardware chrome, or novelty terminal jokes

### Visual Character

- Every major container uses zero-radius 1px phosphor borders with amber corner ticks drawn by pseudo-elements for a calibrated instrument-panel edge.
- The entire interface sits on a deep charcoal base with layered repeating-linear-gradient scanlines and a radial green glow centered behind the working terminal.
- Headers, labels, and controls use uppercase IBM Plex Mono with command-prefix glyphs such as $, >, ::, and bracketed numeric indices.
- Information hierarchy is built from terminal rows, tabular metric cells, and fixed-width prompt blocks rather than soft cards or image-led marketing sections.
- Interactive elements expose a block cursor motif: focused inputs and active tabs show a rectangular phosphor caret or filled left marker instead of rounded highlights.

## Tokens

### Borders

- **Accent Width**: 3px
- **Character**: Thin phosphor grid lines define every region, with amber/cyan state strokes used sparingly for alerts and selected modules.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#ffb454` |
| background | `#050706` |
| border | `#1d6b4c` |
| error | `#ff4d6d` |
| info | `#3fd7ff` |
| muted | `#6fae8b` |
| primary | `#00ff66` |
| secondary | `#0b2f26` |
| success | `#00ff66` |
| surface | `#0b1110` |
| text | `#d7ffe5` |
| warning | `#ffb454` |

### Motion

- **Duration**: 140ms
- **Easing**: steps(2, jump-none)
- **Philosophy**: snappy

### Radii

- **Full**: 0
- **Lg**: 0
- **Md**: 0
- **None**: 0
- **Sm**: 0

### Shadows

- **Lg**: 0 0 60px rgba(0,255,102,0.22), inset 0 0 30px rgba(63,215,255,0.04)
- **Md**: 0 0 24px rgba(0,255,102,0.18), inset 0 0 18px rgba(0,255,102,0.04)
- **Sm**: 0 0 10px rgba(0,255,102,0.16)

### Spacing

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

### Surfaces

- **Bg Pattern**: lines
- **Card Style**: Flat black-green panels with subtle CRT grain, inner phosphor glow, square edges, and command-line header strips.
- **Treatment**: noise

### Typography

- **Base Size**: 16px
- **Body Font**: IBM Plex Mono
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600;700&display=swap
- **Heading Font**: IBM Plex Mono
- **Letter Spacing**: 0.01em
- **Line Height**: 1.55
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.2

## Rules

### Composition

Use a system-console layout: fixed header, narrow command rail, large terminal workspace, and right-side telemetry panel aligned to an 8px grid.

### Density

Dense by default with compact rows and narrow gutters, but preserve enough line height for readable operational dashboards on small screens.

### Hierarchy

Primary hierarchy comes from phosphor brightness, uppercase prompt labels, bordered modules, and tabular rows; the largest type is still monospaced and technical.

### Signature Patterns

- Apply a global CRT overlay using repeating-linear-gradient scanlines plus a faint animated opacity shimmer on the body pseudo-layer.
- Prefix section titles and buttons with terminal syntax marks ($, >, ::, [01]) generated in markup or CSS before content.
- Draw amber corner ticks on panels with absolutely positioned ::before/::after pseudo-elements instead of border radius or drop-shadow decoration.
- Use block-cursor interactions: focused fields, selected navigation, and live status labels include a blinking rectangular caret or solid phosphor left bar.
- Render data as fixed-width command output rows with dotted grid separators and color-coded status tokens rather than pictorial cards.

## Layout

### Breakpoints

Desktop >= 1100px uses three columns; tablet 700-1099px collapses to two columns with telemetry below; mobile < 700px becomes a single stacked console.

### Grid

Desktop uses a 240px command rail, flexible central terminal, and 320px telemetry column; internal panels follow repeatable 8px grid increments.

### Whitespace

Whitespace is compact and mechanical: 8px row gaps, 16-24px panel padding, and large empty areas only inside terminal output panes to imply screen depth.

## Guidance

### Do

- Use IBM Plex Mono or a comparable technical monospace for all text, including numbers and form controls.
- Keep components square with explicit 1px borders, clear focus rings, and phosphor text-shadow only on high-value labels.
- Express navigation, filters, alerts, and actions through command-line language and bracketed status tokens.
- Balance CRT effects with legibility by keeping scanlines subtle and never placing heavy glow behind long paragraphs.

### Don't

- Do not use rounded cards, pill chips, soft gradients, or consumer-app shadows.
- Do not turn the palette into neon cyberpunk; green is primary, amber and cyan are scarce operational accents.
- Do not use decorative glitch animation that moves text or disrupts reading.
- Do not replace structured dashboard content with nostalgic ASCII art unless it serves an actual interface purpose.
DESIGN.md
---
version: "alpha"
name: "Phosphor Command Grid"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#ffb454"
  background: "#050706"
  border: "#1d6b4c"
  error: "#ff4d6d"
  info: "#3fd7ff"
  muted: "#6fae8b"
  primary: "#00ff66"
  secondary: "#0b2f26"
  success: "#00ff66"
  surface: "#0b1110"
  text: "#d7ffe5"
  warning: "#ffb454"
typography:
  headline-lg:
    fontFamily: "IBM Plex Mono"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "0.01em"
  headline-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "0.01em"
  body-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.55
    letterSpacing: "0.01em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "0px"
  lg: "0px"
  md: "0px"
  none: "0px"
  sm: "0px"
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: "#000000"
    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"
---

# Phosphor Command Grid

## Overview

Phosphor Command Grid translates historical green-screen terminal constraints into a disciplined modern product interface: dense monospace information, black glass surfaces, square technical panels, and just enough CRT artifacting to make the system feel alive without becoming decorative nostalgia.

### Values

- Operational clarity before ornament
- Authentic terminal rhythm from monospaced rows and command prompts
- High contrast status communication with restrained accent color
- Enterprise-grade hierarchy anchored by grid discipline and repeatable components

### Anti-Values

- Rounded lifestyle-app softness that breaks the machine-console character
- Rainbow cyberpunk excess or decorative glitch effects that obscure content
- Skeuomorphic monitor bezels, fake hardware chrome, or novelty terminal jokes

### Visual Character

- Every major container uses zero-radius 1px phosphor borders with amber corner ticks drawn by pseudo-elements for a calibrated instrument-panel edge.
- The entire interface sits on a deep charcoal base with layered repeating-linear-gradient scanlines and a radial green glow centered behind the working terminal.
- Headers, labels, and controls use uppercase IBM Plex Mono with command-prefix glyphs such as $, >, ::, and bracketed numeric indices.
- Information hierarchy is built from terminal rows, tabular metric cells, and fixed-width prompt blocks rather than soft cards or image-led marketing sections.
- Interactive elements expose a block cursor motif: focused inputs and active tabs show a rectangular phosphor caret or filled left marker instead of rounded highlights.

## 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 | `#ffb454` |
| background | `#050706` |
| border | `#1d6b4c` |
| error | `#ff4d6d` |
| info | `#3fd7ff` |
| muted | `#6fae8b` |
| primary | `#00ff66` |
| secondary | `#0b2f26` |
| success | `#00ff66` |
| surface | `#0b1110` |
| text | `#d7ffe5` |
| warning | `#ffb454` |

## Typography

- **Headline-Lg**: IBM Plex Mono, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: IBM Plex Mono, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Mono, 16px, weight 400, line-height 1.55.
- **Label-Md**: IBM Plex Mono, 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

Desktop >= 1100px uses three columns; tablet 700-1099px collapses to two columns with telemetry below; mobile < 700px becomes a single stacked console.

### Grid

Desktop uses a 240px command rail, flexible central terminal, and 320px telemetry column; internal panels follow repeatable 8px grid increments.

### Whitespace

Whitespace is compact and mechanical: 8px row gaps, 16-24px panel padding, and large empty areas only inside terminal output panes to imply screen depth.

## Elevation & Depth

### Shadows

- **Lg**: 0 0 60px rgba(0,255,102,0.22), inset 0 0 30px rgba(63,215,255,0.04)
- **Md**: 0 0 24px rgba(0,255,102,0.18), inset 0 0 18px rgba(0,255,102,0.04)
- **Sm**: 0 0 10px rgba(0,255,102,0.16)

## Shapes

### Rounded

- **Full**: `0px`
- **Lg**: `0px`
- **Md**: `0px`
- **None**: `0px`
- **Sm**: `0px`

### Surfaces

- **Bg Pattern**: lines
- **Card Style**: Flat black-green panels with subtle CRT grain, inner phosphor glow, square edges, and command-line header strips.
- **Treatment**: noise

### Borders

- **Accent Width**: 3px
- **Character**: Thin phosphor grid lines define every region, with amber/cyan state strokes used sparingly for alerts and selected modules.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use a system-console layout: fixed header, narrow command rail, large terminal workspace, and right-side telemetry panel aligned to an 8px grid.

### Density

Dense by default with compact rows and narrow gutters, but preserve enough line height for readable operational dashboards on small screens.

### Hierarchy

Primary hierarchy comes from phosphor brightness, uppercase prompt labels, bordered modules, and tabular rows; the largest type is still monospaced and technical.

### Signature Patterns

- Apply a global CRT overlay using repeating-linear-gradient scanlines plus a faint animated opacity shimmer on the body pseudo-layer.
- Prefix section titles and buttons with terminal syntax marks ($, >, ::, [01]) generated in markup or CSS before content.
- Draw amber corner ticks on panels with absolutely positioned ::before/::after pseudo-elements instead of border radius or drop-shadow decoration.
- Use block-cursor interactions: focused fields, selected navigation, and live status labels include a blinking rectangular caret or solid phosphor left bar.
- Render data as fixed-width command output rows with dotted grid separators and color-coded status tokens rather than pictorial cards.

## 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/phosphor-command-grid/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 IBM Plex Mono or a comparable technical monospace for all text, including numbers and form controls.
- Do Keep components square with explicit 1px borders, clear focus rings, and phosphor text-shadow only on high-value labels.
- Do Express navigation, filters, alerts, and actions through command-line language and bracketed status tokens.
- Do Balance CRT effects with legibility by keeping scanlines subtle and never placing heavy glow behind long paragraphs.
- Don't Do not use rounded cards, pill chips, soft gradients, or consumer-app shadows.
- Don't Do not turn the palette into neon cyberpunk; green is primary, amber and cyan are scarce operational accents.
- Don't Do not use decorative glitch animation that moves text or disrupts reading.
- Don't Do not replace structured dashboard content with nostalgic ASCII art unless it serves an actual interface purpose.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "phosphor-command-grid",
  "type": "registry:theme",
  "title": "Phosphor Command Grid shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#050706",
      "foreground": "#d7ffe5",
      "card": "#0b1110",
      "card-foreground": "#d7ffe5",
      "popover": "#0b1110",
      "popover-foreground": "#d7ffe5",
      "primary": "#00ff66",
      "primary-foreground": "#111111",
      "secondary": "#0b2f26",
      "secondary-foreground": "#ffffff",
      "muted": "#6fae8b",
      "muted-foreground": "#d7ffe5",
      "accent": "#ffb454",
      "accent-foreground": "#111111",
      "destructive": "#ff4d6d",
      "border": "#1d6b4c",
      "input": "#1d6b4c",
      "ring": "#ffb454",
      "chart-1": "#00ff66",
      "chart-2": "#0b2f26",
      "chart-3": "#ffb454",
      "chart-4": "#00ff66",
      "chart-5": "#ffb454",
      "sidebar": "#0b1110",
      "sidebar-foreground": "#d7ffe5",
      "sidebar-primary": "#00ff66",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#3fd7ff",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#1d6b4c",
      "sidebar-ring": "#ffb454",
      "radius": "0"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#00ff66",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#ffb454",
      "accent-foreground": "#111111",
      "destructive": "#ff4d6d",
      "border": "#303642",
      "input": "#303642",
      "ring": "#ffb454",
      "chart-1": "#00ff66",
      "chart-2": "#0b2f26",
      "chart-3": "#ffb454",
      "chart-4": "#00ff66",
      "chart-5": "#ffb454",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#00ff66",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#ffb454",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#ffb454",
      "radius": "0"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "phosphor-command-grid",
    "slug": "phosphor-command-grid",
    "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 · phosphor-command-grid
DESIGN.md

at a glance

Palette

Typography

headline-lgIBM Plex Mono · 28px · 700

The quick brown fox jumps

headline-mdIBM Plex Mono · 23px · 600

The quick brown fox jumps

body-mdIBM Plex Mono · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 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

full0px
lg0px
md0px
none0px
sm0px
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.
primaryaccentsurfacemutederror
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: #050706;
  --foreground: #d7ffe5;
  --card: #0b1110;
  --card-foreground: #d7ffe5;
  --popover: #0b1110;
  --popover-foreground: #d7ffe5;
  --primary: #00ff66;
  --primary-foreground: #111111;
  --secondary: #0b2f26;
  --secondary-foreground: #ffffff;
  --muted: #6fae8b;
  --muted-foreground: #d7ffe5;
  --accent: #ffb454;
  --accent-foreground: #111111;
  --destructive: #ff4d6d;
  --border: #1d6b4c;
  --input: #1d6b4c;
  --ring: #ffb454;
  --chart-1: #00ff66;
  --chart-2: #0b2f26;
  --chart-3: #ffb454;
  --chart-4: #00ff66;
  --chart-5: #ffb454;
  --sidebar: #0b1110;
  --sidebar-foreground: #d7ffe5;
  --sidebar-primary: #00ff66;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #3fd7ff;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #1d6b4c;
  --sidebar-ring: #ffb454;
  --radius: 0;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #00ff66;
  --primary-foreground: #111111;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #ffb454;
  --accent-foreground: #111111;
  --destructive: #ff4d6d;
  --border: #303642;
  --input: #303642;
  --ring: #ffb454;
  --chart-1: #00ff66;
  --chart-2: #0b2f26;
  --chart-3: #ffb454;
  --chart-4: #00ff66;
  --chart-5: #ffb454;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #00ff66;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #ffb454;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #ffb454;
  --radius: 0;
}
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 PhosphorCommandGridShadcnKit() {
  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">Phosphor Command Grid</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 JSONcompatibility fallback
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "phosphor-command-grid",
  "type": "registry:theme",
  "title": "Phosphor Command Grid shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#050706",
      "foreground": "#d7ffe5",
      "card": "#0b1110",
      "card-foreground": "#d7ffe5",
      "popover": "#0b1110",
      "popover-foreground": "#d7ffe5",
      "primary": "#00ff66",
      "primary-foreground": "#111111",
      "secondary": "#0b2f26",
      "secondary-foreground": "#ffffff",
      "muted": "#6fae8b",
      "muted-foreground": "#d7ffe5",
      "accent": "#ffb454",
      "accent-foreground": "#111111",
      "destructive": "#ff4d6d",
      "border": "#1d6b4c",
      "input": "#1d6b4c",
      "ring": "#ffb454",
      "chart-1": "#00ff66",
      "chart-2": "#0b2f26",
      "chart-3": "#ffb454",
      "chart-4": "#00ff66",
      "chart-5": "#ffb454",
      "sidebar": "#0b1110",
      "sidebar-foreground": "#d7ffe5",
      "sidebar-primary": "#00ff66",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#3fd7ff",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#1d6b4c",
      "sidebar-ring": "#ffb454",
      "radius": "0"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#00ff66",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#ffb454",
      "accent-foreground": "#111111",
      "destructive": "#ff4d6d",
      "border": "#303642",
      "input": "#303642",
      "ring": "#ffb454",
      "chart-1": "#00ff66",
      "chart-2": "#0b2f26",
      "chart-3": "#ffb454",
      "chart-4": "#00ff66",
      "chart-5": "#ffb454",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#00ff66",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#ffb454",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#ffb454",
      "radius": "0"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "phosphor-command-grid",
    "slug": "phosphor-command-grid",
    "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"
      ]
    }
  }
}
component recipescompatibility fallback
# Phosphor Command Grid shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `phosphor-command-grid`
Slug: `phosphor-command-grid`

## Intent

Phosphor Command Grid translates historical green-screen terminal constraints into a disciplined modern product interface: dense monospace information, black glass surfaces, square technical panels, and just enough CRT artifacting to make the system feel alive without becoming decorative nostalgia.

## 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": "#ffb454",
  "background": "#050706",
  "border": "#1d6b4c",
  "error": "#ff4d6d",
  "info": "#3fd7ff",
  "muted": "#6fae8b",
  "primary": "#00ff66",
  "secondary": "#0b2f26",
  "success": "#00ff66",
  "surface": "#0b1110",
  "text": "#d7ffe5",
  "warning": "#ffb454"
}

Typography:

{
  "base_size": "16px",
  "body_font": "IBM Plex Mono",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600;700&display=swap",
  "heading_font": "IBM Plex Mono",
  "letter_spacing": "0.01em",
  "line_height": 1.55,
  "mono_font": "IBM Plex Mono",
  "scale_ratio": 1.2
}

## Visual character to preserve

- Every major container uses zero-radius 1px phosphor borders with amber corner ticks drawn by pseudo-elements for a calibrated instrument-panel edge.
- The entire interface sits on a deep charcoal base with layered repeating-linear-gradient scanlines and a radial green glow centered behind the working terminal.
- Headers, labels, and controls use uppercase IBM Plex Mono with command-prefix glyphs such as $, >, ::, and bracketed numeric indices.
- Information hierarchy is built from terminal rows, tabular metric cells, and fixed-width prompt blocks rather than soft cards or image-led marketing sections.
- Interactive elements expose a block cursor motif: focused inputs and active tabs show a rectangular phosphor caret or filled left marker instead of rounded highlights.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "stickerBadges": false,
  "motion": "still",
  "density": "balanced",
  "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/phosphor-command-grid/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 IBM Plex Mono or a comparable technical monospace for all text, including numbers and form controls.; Keep components square with explicit 1px borders, clear focus rings, and phosphor text-shadow only on high-value labels.; Express navigation, filters, alerts, and actions through command-line language and bracketed status tokens.; Balance CRT effects with legibility by keeping scanlines subtle and never placing heavy glow behind long paragraphs.
- Do not: Do not use rounded cards, pill chips, soft gradients, or consumer-app shadows.; Do not turn the palette into neon cyberpunk; green is primary, amber and cyan are scarce operational accents.; Do not use decorative glitch animation that moves text or disrupts reading.; Do not replace structured dashboard content with nostalgic ASCII art unless it serves an actual interface purpose.

## 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 PhosphorCommandGridShadcnKit() {
  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">Phosphor Command Grid</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": "Desktop >= 1100px uses three columns; tablet 700-1099px collapses to two columns with telemetry below; mobile < 700px becomes a single stacked console.",
  "grid": "Desktop uses a 240px command rail, flexible central terminal, and 320px telemetry column; internal panels follow repeatable 8px grid increments.",
  "whitespace": "Whitespace is compact and mechanical: 8px row gaps, 16-24px panel padding, and large empty areas only inside terminal output panes to imply screen depth."
}
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": "phosphor-command-grid",
    "name": "Phosphor Command Grid",
    "slug": "phosphor-command-grid"
  },
  "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": [
    "Every major container uses zero-radius 1px phosphor borders with amber corner ticks drawn by pseudo-elements for a calibrated instrument-panel edge.",
    "The entire interface sits on a deep charcoal base with layered repeating-linear-gradient scanlines and a radial green glow centered behind the working terminal.",
    "Headers, labels, and controls use uppercase IBM Plex Mono with command-prefix glyphs such as $, >, ::, and bracketed numeric indices.",
    "Information hierarchy is built from terminal rows, tabular metric cells, and fixed-width prompt blocks rather than soft cards or image-led marketing sections.",
    "Interactive elements expose a block cursor motif: focused inputs and active tabs show a rectangular phosphor caret or filled left marker instead of rounded highlights."
  ],
  "visualProfile": {
    "family": "brutalist",
    "material": "ink",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": false,
    "stickerBadges": false,
    "motion": "still",
    "density": "balanced",
    "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": "Phosphor Command Grid 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 IBM Plex Mono or a comparable technical monospace for all text, including numbers and form controls.",
      "Keep components square with explicit 1px borders, clear focus rings, and phosphor text-shadow only on high-value labels.",
      "Express navigation, filters, alerts, and actions through command-line language and bracketed status tokens.",
      "Balance CRT effects with legibility by keeping scanlines subtle and never placing heavy glow behind long paragraphs."
    ],
    "dont": [
      "Do not use rounded cards, pill chips, soft gradients, or consumer-app shadows.",
      "Do not turn the palette into neon cyberpunk; green is primary, amber and cyan are scarce operational accents.",
      "Do not use decorative glitch animation that moves text or disrupts reading.",
      "Do not replace structured dashboard content with nostalgic ASCII art unless it serves an actual interface purpose."
    ]
  }
}
related

More like this