back to gallery
design language·retro-futurism-crt

Retro Futurism CRT

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
Retro Futurism CRT imagines a control interface from an optimistic late-20th-century future: phosphor-glow telemetry, chamfered instrument housings, and vector-grid depth cues rendered with disciplined information hierarchy. It should feel like a mission console that is technical, cinematic, and legible under pressure.
values
instrument-panel clarity over decorative clutterluminous status communication with immediate scanabilitymachine-age optimism expressed through vector geometrytactile chrome framing around digital phosphor surfacesdense telemetry balanced by strict sectional rhythm
anti-values
×soft consumer-app minimalism×borderless glassy ambiguity×pastel friendliness×organic blob shapes×casual editorial whitespace that weakens control-room focus
tokens
colors12 items
primary
#7CFF72
secondary
#6BE7FF
accent
#FFB347
background
#07110E
surface
#0C1B17
text
#D8FFD7
muted
#82A89B
border
#35584F
error
#FF6E6E
success
#7CFF72
warning
#FFB347
info
#6BE7FF
typography8 items
heading font
Orbitron
body font
Chakra Petch
mono font
Share Tech Mono
base size
16px
scale ratio
1.2
line height
1.45
letter spacing
0.04em
google fonts url
https://fonts.googleapis.com/css2?family=Orbitron:wght@500;700;800&family=Chakra+Petch:wght@400;500;600;700&family=Share+Tech+Mono&display=swap
spacing2 items
base
8px
scale
4px, 8px, 12px, 16px, 24px, 32px, 48px, 64px
radii5 items
none
0px
sm
6px
md
12px
lg
18px
full
999px
shadows3 items
sm
0 0 0 1px rgba(124,255,114,0.12), 0 0 14px rgba(124,255,114,0.10)
md
0 0 0 2px rgba(107,231,255,0.14), 0 0 22px rgba(124,255,114,0.16), inset 0 1px 0 rgba(216,255,215,0.08)
lg
0 0 0 2px rgba(255,179,71,0.16), 0 0 36px rgba(124,255,114,0.20), inset 0 0 22px rgba(107,231,255,0.06)
surfaces3 items
treatment
gradient
card style
raised instrument module with chrome shell, dark phosphor face, and inner glow
bg pattern
grid
borders4 items
default width
2px
accent width
3px
style
solid
character
technical and structural; frames behave like equipment housings with crisp outer metal and luminous inner seams
motion3 items
duration
180ms
easing
cubic-bezier(0.2, 0.8, 0.2, 1)
philosophy
snappy
responsive2 items
breakpoints
1200, 1024, 768, 480
column progression
12 -> 8 -> 4 -> 1
rules
composition
Compose screens as an operations console: a top signal bar, a dominant hero instrument cluster, then segmented telemetry bays. Use framed modules with visible seams and reserved display zones rather than free-floating cards.
hierarchy
Headlines are compact and coded; numerical readouts and statuses carry the highest contrast. Labels live in micro-uppercase rails, body copy stays secondary, and alerts interrupt with amber or red glow blocks.
density
Moderately high density. Fit substantial information into each frame, but separate modules with obvious housing gaps and contrasting underlays so density feels engineered rather than crowded.
signature patterns
all primary containers use polygonal chamfered corners via clip-path paired with double-frame bordersdisplay surfaces include repeating scanline overlays using layered linear-gradientssection headers are rendered as status rails with left title, centered rule, and right signal codecharts, hero areas, and key cards sit on perspective grid or vector horizon backgroundsinteractive controls use phosphor bloom on hover/focus plus inset highlight bars rather than flat fills
layout
grid
Desktop uses a 12-column command-deck grid with a 3-column sidebar, 6-column main instrument area, and 3-column telemetry stack. Tablet collapses to 8 columns and nests telemetry under the hero. Phone becomes a single column with rail headers stacked above content.
breakpoints
1200px+ full command deck; <=1024px 8-column split console; <=768px stacked modules with horizontal scroll for dense data; <=480px single-column, full-width actions, and compressed rail metadata.
whitespace
Whitespace is reserved as machinery spacing: tight within data clusters, larger between framed modules, and generous around hero telemetry to preserve the sensation of a protected display cavity.
guidance
do
  • Use luminous green as the default data state and reserve amber for warnings or emphasized actions.
  • Frame every important region as if it were mounted hardware, with visible shell and inset screen layers.
  • Prefer coded labels, tabular numerics, and crisp monospace metadata for system credibility.
  • Apply scanlines and vector grids selectively to display zones, not indiscriminately to all surfaces.
  • Let hover and focus states brighten the phosphor bloom rather than radically changing component shape.
avoid
  • Do not introduce rounded consumer-app pills or soft blurred glass cards.
  • Do not rely on large illustrations or playful iconography to carry identity.
  • Do not flatten hierarchy by making all text equally bright.
  • Do not remove framing borders; the housing effect is core to the language.
  • Do not use slow easing or bouncy motion that breaks instrument precision.
katagami spec
# Retro Futurism CRT

## Philosophy

Retro Futurism CRT imagines a control interface from an optimistic late-20th-century future: phosphor-glow telemetry, chamfered instrument housings, and vector-grid depth cues rendered with disciplined information hierarchy. It should feel like a mission console that is technical, cinematic, and legible under pressure.

### Values

- instrument-panel clarity over decorative clutter
- luminous status communication with immediate scanability
- machine-age optimism expressed through vector geometry
- tactile chrome framing around digital phosphor surfaces
- dense telemetry balanced by strict sectional rhythm

### Anti-Values

- soft consumer-app minimalism
- borderless glassy ambiguity
- pastel friendliness
- organic blob shapes
- casual editorial whitespace that weakens control-room focus

### Visual Character

- every major panel uses chamfered corners with a 2px chrome outer frame and 1px inner phosphor inset
- dark backgrounds carry horizontal scanline overlays and faint radial CRT vignetting
- section headers sit inside narrow status rails with uppercase micro-labels and right-aligned signal codes
- data zones use neon grid underlays or vector horizon lines behind content blocks
- interactive emphasis relies on dual glows: soft outer bloom plus sharp inset highlight in green or amber

## Tokens

### Colors

| Name | Value |
|------|-------|
| primary | `#7CFF72` |
| secondary | `#6BE7FF` |
| accent | `#FFB347` |
| background | `#07110E` |
| surface | `#0C1B17` |
| text | `#D8FFD7` |
| muted | `#82A89B` |
| border | `#35584F` |
| error | `#FF6E6E` |
| success | `#7CFF72` |
| warning | `#FFB347` |
| info | `#6BE7FF` |

### Typography

- **Heading Font**: Orbitron
- **Body Font**: Chakra Petch
- **Mono Font**: Share Tech Mono
- **Base Size**: 16px
- **Scale Ratio**: 1.2
- **Line Height**: 1.45
- **Letter Spacing**: 0.04em
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Orbitron:wght@500;700;800&family=Chakra+Petch:wght@400;500;600;700&family=Share+Tech+Mono&display=swap

### Spacing

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

### Radii

- **None**: 0px
- **Sm**: 6px
- **Md**: 12px
- **Lg**: 18px
- **Full**: 999px

### Shadows

- **Sm**: 0 0 0 1px rgba(124,255,114,0.12), 0 0 14px rgba(124,255,114,0.10)
- **Md**: 0 0 0 2px rgba(107,231,255,0.14), 0 0 22px rgba(124,255,114,0.16), inset 0 1px 0 rgba(216,255,215,0.08)
- **Lg**: 0 0 0 2px rgba(255,179,71,0.16), 0 0 36px rgba(124,255,114,0.20), inset 0 0 22px rgba(107,231,255,0.06)

### Surfaces

- **Treatment**: gradient
- **Card Style**: raised instrument module with chrome shell, dark phosphor face, and inner glow
- **Bg Pattern**: grid

### Borders

- **Default Width**: 2px
- **Accent Width**: 3px
- **Style**: solid
- **Character**: technical and structural; frames behave like equipment housings with crisp outer metal and luminous inner seams

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1)
- **Philosophy**: snappy

### Responsive

- **Breakpoints**: [1200,1024,768,480]
- **Column Progression**: 12 -> 8 -> 4 -> 1

## Rules

### Composition

Compose screens as an operations console: a top signal bar, a dominant hero instrument cluster, then segmented telemetry bays. Use framed modules with visible seams and reserved display zones rather than free-floating cards.

### Hierarchy

Headlines are compact and coded; numerical readouts and statuses carry the highest contrast. Labels live in micro-uppercase rails, body copy stays secondary, and alerts interrupt with amber or red glow blocks.

### Density

Moderately high density. Fit substantial information into each frame, but separate modules with obvious housing gaps and contrasting underlays so density feels engineered rather than crowded.

### Signature Patterns

- all primary containers use polygonal chamfered corners via clip-path paired with double-frame borders
- display surfaces include repeating scanline overlays using layered linear-gradients
- section headers are rendered as status rails with left title, centered rule, and right signal code
- charts, hero areas, and key cards sit on perspective grid or vector horizon backgrounds
- interactive controls use phosphor bloom on hover/focus plus inset highlight bars rather than flat fills

## Layout

### Grid

Desktop uses a 12-column command-deck grid with a 3-column sidebar, 6-column main instrument area, and 3-column telemetry stack. Tablet collapses to 8 columns and nests telemetry under the hero. Phone becomes a single column with rail headers stacked above content.

### Breakpoints

1200px+ full command deck; <=1024px 8-column split console; <=768px stacked modules with horizontal scroll for dense data; <=480px single-column, full-width actions, and compressed rail metadata.

### Whitespace

Whitespace is reserved as machinery spacing: tight within data clusters, larger between framed modules, and generous around hero telemetry to preserve the sensation of a protected display cavity.

## Guidance

### Do

- Use luminous green as the default data state and reserve amber for warnings or emphasized actions.
- Frame every important region as if it were mounted hardware, with visible shell and inset screen layers.
- Prefer coded labels, tabular numerics, and crisp monospace metadata for system credibility.
- Apply scanlines and vector grids selectively to display zones, not indiscriminately to all surfaces.
- Let hover and focus states brighten the phosphor bloom rather than radically changing component shape.

### Don't

- Do not introduce rounded consumer-app pills or soft blurred glass cards.
- Do not rely on large illustrations or playful iconography to carry identity.
- Do not flatten hierarchy by making all text equally bright.
- Do not remove framing borders; the housing effect is core to the language.
- Do not use slow easing or bouncy motion that breaks instrument precision.
DESIGN.md
---
version: "alpha"
name: "Retro Futurism CRT"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  primary: "#7CFF72"
  secondary: "#6BE7FF"
  accent: "#FFB347"
  background: "#07110E"
  surface: "#0C1B17"
  text: "#D8FFD7"
  muted: "#82A89B"
  border: "#35584F"
  error: "#FF6E6E"
  success: "#7CFF72"
  warning: "#FFB347"
  info: "#6BE7FF"
typography:
  headline-lg:
    fontFamily: "Orbitron"
    fontSize: "1.953rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "0.04em"
  headline-md:
    fontFamily: "Orbitron"
    fontSize: "1.563rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "0.04em"
  body-md:
    fontFamily: "Chakra Petch"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "0.04em"
  label-md:
    fontFamily: "Share Tech Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  none: "0px"
  sm: "6px"
  md: "12px"
  lg: "18px"
  full: "999px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
components:
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  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"
---

# Retro Futurism CRT

## Overview

Retro Futurism CRT imagines a control interface from an optimistic late-20th-century future: phosphor-glow telemetry, chamfered instrument housings, and vector-grid depth cues rendered with disciplined information hierarchy. It should feel like a mission console that is technical, cinematic, and legible under pressure.

### Values

- instrument-panel clarity over decorative clutter
- luminous status communication with immediate scanability
- machine-age optimism expressed through vector geometry
- tactile chrome framing around digital phosphor surfaces
- dense telemetry balanced by strict sectional rhythm

### Anti-Values

- soft consumer-app minimalism
- borderless glassy ambiguity
- pastel friendliness
- organic blob shapes
- casual editorial whitespace that weakens control-room focus

### Visual Character

- every major panel uses chamfered corners with a 2px chrome outer frame and 1px inner phosphor inset
- dark backgrounds carry horizontal scanline overlays and faint radial CRT vignetting
- section headers sit inside narrow status rails with uppercase micro-labels and right-aligned signal codes
- data zones use neon grid underlays or vector horizon lines behind content blocks
- interactive emphasis relies on dual glows: soft outer bloom plus sharp inset highlight in green or amber

## Colors

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

| Token | Value |
|-------|-------|
| primary | `#7CFF72` |
| secondary | `#6BE7FF` |
| accent | `#FFB347` |
| background | `#07110E` |
| surface | `#0C1B17` |
| text | `#D8FFD7` |
| muted | `#82A89B` |
| border | `#35584F` |
| error | `#FF6E6E` |
| success | `#7CFF72` |
| warning | `#FFB347` |
| info | `#6BE7FF` |

## Typography

- **Headline-Lg**: Orbitron, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Orbitron, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Chakra Petch, 16px, weight 400, line-height 1.5.
- **Label-Md**: Share Tech 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`

### Grid

Desktop uses a 12-column command-deck grid with a 3-column sidebar, 6-column main instrument area, and 3-column telemetry stack. Tablet collapses to 8 columns and nests telemetry under the hero. Phone becomes a single column with rail headers stacked above content.

### Breakpoints

1200px+ full command deck; <=1024px 8-column split console; <=768px stacked modules with horizontal scroll for dense data; <=480px single-column, full-width actions, and compressed rail metadata.

### Whitespace

Whitespace is reserved as machinery spacing: tight within data clusters, larger between framed modules, and generous around hero telemetry to preserve the sensation of a protected display cavity.

## Elevation & Depth

### Shadows

- **Sm**: 0 0 0 1px rgba(124,255,114,0.12), 0 0 14px rgba(124,255,114,0.10)
- **Md**: 0 0 0 2px rgba(107,231,255,0.14), 0 0 22px rgba(124,255,114,0.16), inset 0 1px 0 rgba(216,255,215,0.08)
- **Lg**: 0 0 0 2px rgba(255,179,71,0.16), 0 0 36px rgba(124,255,114,0.20), inset 0 0 22px rgba(107,231,255,0.06)

## Shapes

### Rounded

- **None**: `0px`
- **Sm**: `6px`
- **Md**: `12px`
- **Lg**: `18px`
- **Full**: `999px`

### Surfaces

- **Treatment**: gradient
- **Card Style**: raised instrument module with chrome shell, dark phosphor face, and inner glow
- **Bg Pattern**: grid

### Borders

- **Default Width**: 2px
- **Accent Width**: 3px
- **Style**: solid
- **Character**: technical and structural; frames behave like equipment housings with crisp outer metal and luminous inner seams

## Components

### Composition

Compose screens as an operations console: a top signal bar, a dominant hero instrument cluster, then segmented telemetry bays. Use framed modules with visible seams and reserved display zones rather than free-floating cards.

### Hierarchy

Headlines are compact and coded; numerical readouts and statuses carry the highest contrast. Labels live in micro-uppercase rails, body copy stays secondary, and alerts interrupt with amber or red glow blocks.

### Density

Moderately high density. Fit substantial information into each frame, but separate modules with obvious housing gaps and contrasting underlays so density feels engineered rather than crowded.

### Signature Patterns

- all primary containers use polygonal chamfered corners via clip-path paired with double-frame borders
- display surfaces include repeating scanline overlays using layered linear-gradients
- section headers are rendered as status rails with left title, centered rule, and right signal code
- charts, hero areas, and key cards sit on perspective grid or vector horizon backgrounds
- interactive controls use phosphor bloom on hover/focus plus inset highlight bars rather than flat fills

## 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-019d9bb7-cf57-77d3-8aef-013948be7ddf/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 luminous green as the default data state and reserve amber for warnings or emphasized actions.
- Do Frame every important region as if it were mounted hardware, with visible shell and inset screen layers.
- Do Prefer coded labels, tabular numerics, and crisp monospace metadata for system credibility.
- Do Apply scanlines and vector grids selectively to display zones, not indiscriminately to all surfaces.
- Do Let hover and focus states brighten the phosphor bloom rather than radically changing component shape.
- Don't Do not introduce rounded consumer-app pills or soft blurred glass cards.
- Don't Do not rely on large illustrations or playful iconography to carry identity.
- Don't Do not flatten hierarchy by making all text equally bright.
- Don't Do not remove framing borders; the housing effect is core to the language.
- Don't Do not use slow easing or bouncy motion that breaks instrument precision.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "retro-futurism-crt",
  "type": "registry:theme",
  "title": "Retro Futurism CRT shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#07110E",
      "foreground": "#D8FFD7",
      "card": "#0C1B17",
      "card-foreground": "#D8FFD7",
      "popover": "#0C1B17",
      "popover-foreground": "#D8FFD7",
      "primary": "#7CFF72",
      "primary-foreground": "#111111",
      "secondary": "#6BE7FF",
      "secondary-foreground": "#111111",
      "muted": "#82A89B",
      "muted-foreground": "#D8FFD7",
      "accent": "#FFB347",
      "accent-foreground": "#ffffff",
      "destructive": "#FF6E6E",
      "border": "#35584F",
      "input": "#35584F",
      "ring": "#FFB347",
      "chart-1": "#7CFF72",
      "chart-2": "#6BE7FF",
      "chart-3": "#FFB347",
      "chart-4": "#7CFF72",
      "chart-5": "#FFB347",
      "sidebar": "#0C1B17",
      "sidebar-foreground": "#D8FFD7",
      "sidebar-primary": "#7CFF72",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#6BE7FF",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#35584F",
      "sidebar-ring": "#FFB347",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#7CFF72",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#FFB347",
      "accent-foreground": "#ffffff",
      "destructive": "#FF6E6E",
      "border": "#303642",
      "input": "#303642",
      "ring": "#FFB347",
      "chart-1": "#7CFF72",
      "chart-2": "#6BE7FF",
      "chart-3": "#FFB347",
      "chart-4": "#7CFF72",
      "chart-5": "#FFB347",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#7CFF72",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#FFB347",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#FFB347",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019d9bb7-cf57-77d3-8aef-013948be7ddf",
    "slug": "retro-futurism-crt",
    "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": {
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "responsive": [
        "breakpoints",
        "column_progression"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · retro-futurism-crt
DESIGN.md

at a glance

Palette

Typography

headline-lgOrbitron · 31px · 700

The quick brown fox jumps

headline-mdOrbitron · 25px · 600

The quick brown fox jumps

body-mdChakra Petch · 16px · 400

The quick brown fox jumps

label-mdShare Tech 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

none0px
sm6px
md12px
lg18px
full999px
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: #07110E;
  --foreground: #D8FFD7;
  --card: #0C1B17;
  --card-foreground: #D8FFD7;
  --popover: #0C1B17;
  --popover-foreground: #D8FFD7;
  --primary: #7CFF72;
  --primary-foreground: #111111;
  --secondary: #6BE7FF;
  --secondary-foreground: #111111;
  --muted: #82A89B;
  --muted-foreground: #D8FFD7;
  --accent: #FFB347;
  --accent-foreground: #ffffff;
  --destructive: #FF6E6E;
  --border: #35584F;
  --input: #35584F;
  --ring: #FFB347;
  --chart-1: #7CFF72;
  --chart-2: #6BE7FF;
  --chart-3: #FFB347;
  --chart-4: #7CFF72;
  --chart-5: #FFB347;
  --sidebar: #0C1B17;
  --sidebar-foreground: #D8FFD7;
  --sidebar-primary: #7CFF72;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #6BE7FF;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #35584F;
  --sidebar-ring: #FFB347;
  --radius: 12px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #7CFF72;
  --primary-foreground: #111111;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #FFB347;
  --accent-foreground: #ffffff;
  --destructive: #FF6E6E;
  --border: #303642;
  --input: #303642;
  --ring: #FFB347;
  --chart-1: #7CFF72;
  --chart-2: #6BE7FF;
  --chart-3: #FFB347;
  --chart-4: #7CFF72;
  --chart-5: #FFB347;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #7CFF72;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #FFB347;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #FFB347;
  --radius: 12px;
}
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 RetroFuturismCrtShadcnKit() {
  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">Retro Futurism CRT</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": "retro-futurism-crt",
  "type": "registry:theme",
  "title": "Retro Futurism CRT shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#07110E",
      "foreground": "#D8FFD7",
      "card": "#0C1B17",
      "card-foreground": "#D8FFD7",
      "popover": "#0C1B17",
      "popover-foreground": "#D8FFD7",
      "primary": "#7CFF72",
      "primary-foreground": "#111111",
      "secondary": "#6BE7FF",
      "secondary-foreground": "#111111",
      "muted": "#82A89B",
      "muted-foreground": "#D8FFD7",
      "accent": "#FFB347",
      "accent-foreground": "#ffffff",
      "destructive": "#FF6E6E",
      "border": "#35584F",
      "input": "#35584F",
      "ring": "#FFB347",
      "chart-1": "#7CFF72",
      "chart-2": "#6BE7FF",
      "chart-3": "#FFB347",
      "chart-4": "#7CFF72",
      "chart-5": "#FFB347",
      "sidebar": "#0C1B17",
      "sidebar-foreground": "#D8FFD7",
      "sidebar-primary": "#7CFF72",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#6BE7FF",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#35584F",
      "sidebar-ring": "#FFB347",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#7CFF72",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#FFB347",
      "accent-foreground": "#ffffff",
      "destructive": "#FF6E6E",
      "border": "#303642",
      "input": "#303642",
      "ring": "#FFB347",
      "chart-1": "#7CFF72",
      "chart-2": "#6BE7FF",
      "chart-3": "#FFB347",
      "chart-4": "#7CFF72",
      "chart-5": "#FFB347",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#7CFF72",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#FFB347",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#FFB347",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019d9bb7-cf57-77d3-8aef-013948be7ddf",
    "slug": "retro-futurism-crt",
    "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": {
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "responsive": [
        "breakpoints",
        "column_progression"
      ]
    }
  }
}
component recipescompatibility fallback
# Retro Futurism CRT shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019d9bb7-cf57-77d3-8aef-013948be7ddf`
Slug: `retro-futurism-crt`

## Intent

Retro Futurism CRT imagines a control interface from an optimistic late-20th-century future: phosphor-glow telemetry, chamfered instrument housings, and vector-grid depth cues rendered with disciplined information hierarchy. It should feel like a mission console that is technical, cinematic, and legible under pressure.

## 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:

{
  "primary": "#7CFF72",
  "secondary": "#6BE7FF",
  "accent": "#FFB347",
  "background": "#07110E",
  "surface": "#0C1B17",
  "text": "#D8FFD7",
  "muted": "#82A89B",
  "border": "#35584F",
  "error": "#FF6E6E",
  "success": "#7CFF72",
  "warning": "#FFB347",
  "info": "#6BE7FF"
}

Typography:

{
  "heading_font": "Orbitron",
  "body_font": "Chakra Petch",
  "mono_font": "Share Tech Mono",
  "base_size": "16px",
  "scale_ratio": "1.2",
  "line_height": "1.45",
  "letter_spacing": "0.04em",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Orbitron:wght@500;700;800&family=Chakra+Petch:wght@400;500;600;700&family=Share+Tech+Mono&display=swap"
}

## Visual character to preserve

- every major panel uses chamfered corners with a 2px chrome outer frame and 1px inner phosphor inset
- dark backgrounds carry horizontal scanline overlays and faint radial CRT vignetting
- section headers sit inside narrow status rails with uppercase micro-labels and right-aligned signal codes
- data zones use neon grid underlays or vector horizon lines behind content blocks
- interactive emphasis relies on dual glows: soft outer bloom plus sharp inset highlight in green or amber

## ShadSync visual profile

{
  "family": "system",
  "material": "flat",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": false,
  "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/retro-futurism-crt/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 luminous green as the default data state and reserve amber for warnings or emphasized actions.; Frame every important region as if it were mounted hardware, with visible shell and inset screen layers.; Prefer coded labels, tabular numerics, and crisp monospace metadata for system credibility.; Apply scanlines and vector grids selectively to display zones, not indiscriminately to all surfaces.; Let hover and focus states brighten the phosphor bloom rather than radically changing component shape.
- Do not: Do not introduce rounded consumer-app pills or soft blurred glass cards.; Do not rely on large illustrations or playful iconography to carry identity.; Do not flatten hierarchy by making all text equally bright.; Do not remove framing borders; the housing effect is core to the language.; Do not use slow easing or bouncy motion that breaks instrument precision.

## 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 RetroFuturismCrtShadcnKit() {
  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">Retro Futurism CRT</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

{
  "grid": "Desktop uses a 12-column command-deck grid with a 3-column sidebar, 6-column main instrument area, and 3-column telemetry stack. Tablet collapses to 8 columns and nests telemetry under the hero. Phone becomes a single column with rail headers stacked above content.",
  "breakpoints": "1200px+ full command deck; <=1024px 8-column split console; <=768px stacked modules with horizontal scroll for dense data; <=480px single-column, full-width actions, and compressed rail metadata.",
  "whitespace": "Whitespace is reserved as machinery spacing: tight within data clusters, larger between framed modules, and generous around hero telemetry to preserve the sensation of a protected display cavity."
}
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-019d9bb7-cf57-77d3-8aef-013948be7ddf",
    "name": "Retro Futurism CRT",
    "slug": "retro-futurism-crt"
  },
  "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 panel uses chamfered corners with a 2px chrome outer frame and 1px inner phosphor inset",
    "dark backgrounds carry horizontal scanline overlays and faint radial CRT vignetting",
    "section headers sit inside narrow status rails with uppercase micro-labels and right-aligned signal codes",
    "data zones use neon grid underlays or vector horizon lines behind content blocks",
    "interactive emphasis relies on dual glows: soft outer bloom plus sharp inset highlight in green or amber"
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "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": "Retro Futurism CRT 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 luminous green as the default data state and reserve amber for warnings or emphasized actions.",
      "Frame every important region as if it were mounted hardware, with visible shell and inset screen layers.",
      "Prefer coded labels, tabular numerics, and crisp monospace metadata for system credibility.",
      "Apply scanlines and vector grids selectively to display zones, not indiscriminately to all surfaces.",
      "Let hover and focus states brighten the phosphor bloom rather than radically changing component shape."
    ],
    "dont": [
      "Do not introduce rounded consumer-app pills or soft blurred glass cards.",
      "Do not rely on large illustrations or playful iconography to carry identity.",
      "Do not flatten hierarchy by making all text equally bright.",
      "Do not remove framing borders; the housing effect is core to the language.",
      "Do not use slow easing or bouncy motion that breaks instrument precision."
    ]
  }
}
related

More like this