back to gallery
design language·signal-white-pixel-lime

Signal White Pixel Lime

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

Download DESIGN.md

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

the spec

specification

philosophy
summary
A clean product interface language where a quiet white hardware-calibration surface is activated by sparse neon-lime pixel states, indigo command structure, and cyan measurement feedback. It uses pixel logic as precision, not nostalgia: activation blocks, segmented counters, and crisp focus brackets make the UI distinctive while preserving premium readability.
values
white-space as instrument panel clarityvivid color only when it communicates live statepixel forms as modern precision markspremium readable typography with small pixel accentsscene-specific controls over generic dashboard modules
anti-values
×arcade skins or Minecraft-style block overload×rainbow accent sprawl and decorative color garnish×square-grid or dotted texture backgrounds×side rails, card stripes, chipped corners, and uneven borders
tokens
borders4 items
accent width
2px
character
even continuous hairlines; accent borders become squared lime bracket segments on focus but never chipped corners
default width
1px
style
solid
colors12 items
accent
#C6FF00
background
#F8FAFC
border
#D8DEE8
error
#E11D48
info
#0891B2
muted
#64748B
primary
#312E81
secondary
#06B6D4
success
#16A34A
surface
#FFFFFF
text
#111827
warning
#EAB308
motion3 items
duration
160ms
easing
cubic-bezier(0.2, 0.8, 0.2, 1)
philosophy
micro-snaps between pixel steps and calm surface lifts; no glow floods or generic opacity-only fades
radii5 items
full
9999px
lg
22px
md
16px
none
0
sm
10px
shadows3 items
lg
0 28px 80px rgba(49,46,129,0.12)
md
0 16px 40px rgba(49,46,129,0.08)
sm
0 1px 2px rgba(17,24,39,0.05)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
plain neutral field with optional isolated pixel glyphs tied to specific live controls only
card style
large rounded rectangles with one-pixel borders, white fill, and status pixels embedded inside controls rather than as side accents
treatment
clean white and frost-neutral panels with restrained hairlines, no grid, no dotted repeat texture
typography8 items
base size
16px
body font
IBM Plex Sans
google fonts url
https://fonts.googleapis.com/css2?family=Afacad+Flux:wght@500;650;750&family=IBM+Plex+Sans:wght@400;500;600;700&family=Pixelify+Sans:wght@400;500;600&display=swap
heading font
Afacad Flux
letter spacing
-0.02em
line height
1.5
mono font
Pixelify Sans
scale ratio
1.22
rules
composition
Build one dominant white workspace with a precise product task, then offset a compact signal stack or inspector so the composition breaks the grid without becoming a dashboard.
density

Medium-low density with large 48px+ macro gaps between major regions and tight 4px to 8px groupings inside pixel state controls.

hierarchy
Use Afacad Flux for concise command headings, IBM Plex Sans for all readable content, and Pixelify Sans only for tiny state labels, display numerals, badges, and counters.
signature patterns
Lime pixel ladders appear as short sequences of 4px squares that fill to show activation, progress, or live signal strength.Focused inputs and active tabs use squared lime bracket corners layered over a normal rounded white component border.Cyan measurement chips pair a value with a tiny pixel glyph and are used only for telemetry, links, and secondary confirmation.Indigo command pills use dark fill with a single embedded lime terminal pixel at the end of the label rather than decorative stripes.The main workspace is a single calm rounded white sheet while a smaller inspector panel intentionally overlaps or offsets one edge.
layout
breakpoints

desktop 1200px, tablet 768px, mobile 375px with inspector stacking below the workspace

grid

A flexible 12-column desktop structure collapses to stacked sheets; never use a visible square grid background.

whitespace

Use generous neutral margins, at least 64px around the hero workspace on desktop, and preserve clear separation between product task zones.

guidance
do
  • Use neon lime only for focus, activation, progress, current position, or live signal.
  • Keep body copy in IBM Plex Sans and reserve Pixelify Sans for micro labels, counters, badges, and display numerals.
  • Make pixel motifs functional inside controls, charts, and state indicators rather than floating decoration.
  • Use indigo as the stable command color and cyan as the measured feedback color.
avoid
  • Do not use square-grid backgrounds, repeated dotted textures, card side rails, or stripe accents.
  • Do not add chipped diagonal corners, uneven borders, arcade blocks, or low-resolution gimmicks that hurt readability.
  • Do not expand the palette into rainbow status color unless a semantic error/warning/success token is required.
  • Do not present a generic SaaS dashboard or a component catalog as the primary embodiment.
katagami spec
# Signal White Pixel Lime

## Philosophy

A clean product interface language where a quiet white hardware-calibration surface is activated by sparse neon-lime pixel states, indigo command structure, and cyan measurement feedback. It uses pixel logic as precision, not nostalgia: activation blocks, segmented counters, and crisp focus brackets make the UI distinctive while preserving premium readability.

### Values

- white-space as instrument panel clarity
- vivid color only when it communicates live state
- pixel forms as modern precision marks
- premium readable typography with small pixel accents
- scene-specific controls over generic dashboard modules

### Anti-Values

- arcade skins or Minecraft-style block overload
- rainbow accent sprawl and decorative color garnish
- square-grid or dotted texture backgrounds
- side rails, card stripes, chipped corners, and uneven borders

### Visual Character

- White and near-white surfaces use single-pixel #D8DEE8 hairline borders with broad 22px radius corners and almost no shadow.
- Neon lime appears as 4px square pixel clusters only inside live states, progress steps, focus rings, and active control terminals.
- Indigo anchors titles, nav pills, and primary actions while cyan is reserved for measured links, telemetry values, and secondary states.
- Pixel-influenced typography is isolated to tiny labels, counters, badges, and numerals while long text stays in a readable sans face.
- Layouts use one large calm workspace panel interrupted by a compact offset signal stack instead of equal dashboard card rows.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: even continuous hairlines; accent borders become squared lime bracket segments on focus but never chipped corners
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#C6FF00` |
| background | `#F8FAFC` |
| border | `#D8DEE8` |
| error | `#E11D48` |
| info | `#0891B2` |
| muted | `#64748B` |
| primary | `#312E81` |
| secondary | `#06B6D4` |
| success | `#16A34A` |
| surface | `#FFFFFF` |
| text | `#111827` |
| warning | `#EAB308` |

### Motion

- **Duration**: 160ms
- **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1)
- **Philosophy**: micro-snaps between pixel steps and calm surface lifts; no glow floods or generic opacity-only fades

### Radii

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

### Shadows

- **Lg**: 0 28px 80px rgba(49,46,129,0.12)
- **Md**: 0 16px 40px rgba(49,46,129,0.08)
- **Sm**: 0 1px 2px rgba(17,24,39,0.05)

### Spacing

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

### Surfaces

- **Bg Pattern**: plain neutral field with optional isolated pixel glyphs tied to specific live controls only
- **Card Style**: large rounded rectangles with one-pixel borders, white fill, and status pixels embedded inside controls rather than as side accents
- **Treatment**: clean white and frost-neutral panels with restrained hairlines, no grid, no dotted repeat texture

### Typography

- **Base Size**: 16px
- **Body Font**: IBM Plex Sans
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Afacad+Flux:wght@500;650;750&family=IBM+Plex+Sans:wght@400;500;600;700&family=Pixelify+Sans:wght@400;500;600&display=swap
- **Heading Font**: Afacad Flux
- **Letter Spacing**: -0.02em
- **Line Height**: 1.5
- **Mono Font**: Pixelify Sans
- **Scale Ratio**: 1.22

## Rules

### Composition

Build one dominant white workspace with a precise product task, then offset a compact signal stack or inspector so the composition breaks the grid without becoming a dashboard.

### Density

Medium-low density with large 48px+ macro gaps between major regions and tight 4px to 8px groupings inside pixel state controls.

### Hierarchy

Use Afacad Flux for concise command headings, IBM Plex Sans for all readable content, and Pixelify Sans only for tiny state labels, display numerals, badges, and counters.

### Signature Patterns

- Lime pixel ladders appear as short sequences of 4px squares that fill to show activation, progress, or live signal strength.
- Focused inputs and active tabs use squared lime bracket corners layered over a normal rounded white component border.
- Cyan measurement chips pair a value with a tiny pixel glyph and are used only for telemetry, links, and secondary confirmation.
- Indigo command pills use dark fill with a single embedded lime terminal pixel at the end of the label rather than decorative stripes.
- The main workspace is a single calm rounded white sheet while a smaller inspector panel intentionally overlaps or offsets one edge.

## Layout

### Breakpoints

desktop 1200px, tablet 768px, mobile 375px with inspector stacking below the workspace

### Grid

A flexible 12-column desktop structure collapses to stacked sheets; never use a visible square grid background.

### Whitespace

Use generous neutral margins, at least 64px around the hero workspace on desktop, and preserve clear separation between product task zones.

## Guidance

### Do

- Use neon lime only for focus, activation, progress, current position, or live signal.
- Keep body copy in IBM Plex Sans and reserve Pixelify Sans for micro labels, counters, badges, and display numerals.
- Make pixel motifs functional inside controls, charts, and state indicators rather than floating decoration.
- Use indigo as the stable command color and cyan as the measured feedback color.

### Don't

- Do not use square-grid backgrounds, repeated dotted textures, card side rails, or stripe accents.
- Do not add chipped diagonal corners, uneven borders, arcade blocks, or low-resolution gimmicks that hurt readability.
- Do not expand the palette into rainbow status color unless a semantic error/warning/success token is required.
- Do not present a generic SaaS dashboard or a component catalog as the primary embodiment.
DESIGN.md
---
version: "alpha"
name: "Signal White Pixel Lime"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#C6FF00"
  background: "#F8FAFC"
  border: "#D8DEE8"
  error: "#E11D48"
  info: "#0891B2"
  muted: "#64748B"
  primary: "#312E81"
  secondary: "#06B6D4"
  success: "#16A34A"
  surface: "#FFFFFF"
  text: "#111827"
  warning: "#EAB308"
typography:
  headline-lg:
    fontFamily: "Afacad Flux"
    fontSize: "1.816rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Afacad Flux"
    fontSize: "1.488rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "IBM Plex Sans"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "Pixelify Sans"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "22px"
  md: "16px"
  none: "0px"
  sm: "10px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#ffffff"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  card-surface:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  input-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    height: "44px"
---

# Signal White Pixel Lime

## Overview

A clean product interface language where a quiet white hardware-calibration surface is activated by sparse neon-lime pixel states, indigo command structure, and cyan measurement feedback. It uses pixel logic as precision, not nostalgia: activation blocks, segmented counters, and crisp focus brackets make the UI distinctive while preserving premium readability.

### Values

- white-space as instrument panel clarity
- vivid color only when it communicates live state
- pixel forms as modern precision marks
- premium readable typography with small pixel accents
- scene-specific controls over generic dashboard modules

### Anti-Values

- arcade skins or Minecraft-style block overload
- rainbow accent sprawl and decorative color garnish
- square-grid or dotted texture backgrounds
- side rails, card stripes, chipped corners, and uneven borders

### Visual Character

- White and near-white surfaces use single-pixel #D8DEE8 hairline borders with broad 22px radius corners and almost no shadow.
- Neon lime appears as 4px square pixel clusters only inside live states, progress steps, focus rings, and active control terminals.
- Indigo anchors titles, nav pills, and primary actions while cyan is reserved for measured links, telemetry values, and secondary states.
- Pixel-influenced typography is isolated to tiny labels, counters, badges, and numerals while long text stays in a readable sans face.
- Layouts use one large calm workspace panel interrupted by a compact offset signal stack instead of equal dashboard card rows.

## 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 | `#C6FF00` |
| background | `#F8FAFC` |
| border | `#D8DEE8` |
| error | `#E11D48` |
| info | `#0891B2` |
| muted | `#64748B` |
| primary | `#312E81` |
| secondary | `#06B6D4` |
| success | `#16A34A` |
| surface | `#FFFFFF` |
| text | `#111827` |
| warning | `#EAB308` |

## Typography

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

## Layout

### Spacing Tokens

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

### Breakpoints

desktop 1200px, tablet 768px, mobile 375px with inspector stacking below the workspace

### Grid

A flexible 12-column desktop structure collapses to stacked sheets; never use a visible square grid background.

### Whitespace

Use generous neutral margins, at least 64px around the hero workspace on desktop, and preserve clear separation between product task zones.

## Elevation & Depth

### Shadows

- **Lg**: 0 28px 80px rgba(49,46,129,0.12)
- **Md**: 0 16px 40px rgba(49,46,129,0.08)
- **Sm**: 0 1px 2px rgba(17,24,39,0.05)

## Shapes

### Rounded

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

### Surfaces

- **Bg Pattern**: plain neutral field with optional isolated pixel glyphs tied to specific live controls only
- **Card Style**: large rounded rectangles with one-pixel borders, white fill, and status pixels embedded inside controls rather than as side accents
- **Treatment**: clean white and frost-neutral panels with restrained hairlines, no grid, no dotted repeat texture

### Borders

- **Accent Width**: 2px
- **Character**: even continuous hairlines; accent borders become squared lime bracket segments on focus but never chipped corners
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Build one dominant white workspace with a precise product task, then offset a compact signal stack or inspector so the composition breaks the grid without becoming a dashboard.

### Density

Medium-low density with large 48px+ macro gaps between major regions and tight 4px to 8px groupings inside pixel state controls.

### Hierarchy

Use Afacad Flux for concise command headings, IBM Plex Sans for all readable content, and Pixelify Sans only for tiny state labels, display numerals, badges, and counters.

### Signature Patterns

- Lime pixel ladders appear as short sequences of 4px squares that fill to show activation, progress, or live signal strength.
- Focused inputs and active tabs use squared lime bracket corners layered over a normal rounded white component border.
- Cyan measurement chips pair a value with a tiny pixel glyph and are used only for telemetry, links, and secondary confirmation.
- Indigo command pills use dark fill with a single embedded lime terminal pixel at the end of the label rather than decorative stripes.
- The main workspace is a single calm rounded white sheet while a smaller inspector panel intentionally overlaps or offsets one edge.

## 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-019e4bf7-5831-73f1-bf21-57b9b8b4ae96/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 neon lime only for focus, activation, progress, current position, or live signal.
- Do Keep body copy in IBM Plex Sans and reserve Pixelify Sans for micro labels, counters, badges, and display numerals.
- Do Make pixel motifs functional inside controls, charts, and state indicators rather than floating decoration.
- Do Use indigo as the stable command color and cyan as the measured feedback color.
- Don't Do not use square-grid backgrounds, repeated dotted textures, card side rails, or stripe accents.
- Don't Do not add chipped diagonal corners, uneven borders, arcade blocks, or low-resolution gimmicks that hurt readability.
- Don't Do not expand the palette into rainbow status color unless a semantic error/warning/success token is required.
- Don't Do not present a generic SaaS dashboard or a component catalog as the primary embodiment.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "signal-white-pixel-lime",
  "type": "registry:theme",
  "title": "Signal White Pixel Lime shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F8FAFC",
      "foreground": "#111827",
      "card": "#FFFFFF",
      "card-foreground": "#111827",
      "popover": "#FFFFFF",
      "popover-foreground": "#111827",
      "primary": "#312E81",
      "primary-foreground": "#ffffff",
      "secondary": "#06B6D4",
      "secondary-foreground": "#ffffff",
      "muted": "#64748B",
      "muted-foreground": "#111827",
      "accent": "#C6FF00",
      "accent-foreground": "#111111",
      "destructive": "#E11D48",
      "border": "#D8DEE8",
      "input": "#D8DEE8",
      "ring": "#C6FF00",
      "chart-1": "#312E81",
      "chart-2": "#06B6D4",
      "chart-3": "#C6FF00",
      "chart-4": "#16A34A",
      "chart-5": "#EAB308",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#111827",
      "sidebar-primary": "#312E81",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#0891B2",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8DEE8",
      "sidebar-ring": "#C6FF00",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#312E81",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#C6FF00",
      "accent-foreground": "#111111",
      "destructive": "#E11D48",
      "border": "#303642",
      "input": "#303642",
      "ring": "#C6FF00",
      "chart-1": "#312E81",
      "chart-2": "#06B6D4",
      "chart-3": "#C6FF00",
      "chart-4": "#16A34A",
      "chart-5": "#EAB308",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#312E81",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#C6FF00",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#C6FF00",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e4bf7-5831-73f1-bf21-57b9b8b4ae96",
    "slug": "signal-white-pixel-lime",
    "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 · signal-white-pixel-lime
DESIGN.md

at a glance

Palette

Typography

headline-lgAfacad Flux · 29px · 700

The quick brown fox jumps

headline-mdAfacad Flux · 24px · 600

The quick brown fox jumps

body-mdIBM Plex Sans · 16px · 400

The quick brown fox jumps

label-mdPixelify Sans · 12px · 600

The quick brown fox jumps

Components

New
Card title

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

Spacing

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

Shape

full9999px
lg22px
md16px
none0px
sm10px
shadcn/ui

implementation kit

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

DESIGN.md with shadcn

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

advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #F8FAFC;
  --foreground: #111827;
  --card: #FFFFFF;
  --card-foreground: #111827;
  --popover: #FFFFFF;
  --popover-foreground: #111827;
  --primary: #312E81;
  --primary-foreground: #ffffff;
  --secondary: #06B6D4;
  --secondary-foreground: #ffffff;
  --muted: #64748B;
  --muted-foreground: #111827;
  --accent: #C6FF00;
  --accent-foreground: #111111;
  --destructive: #E11D48;
  --border: #D8DEE8;
  --input: #D8DEE8;
  --ring: #C6FF00;
  --chart-1: #312E81;
  --chart-2: #06B6D4;
  --chart-3: #C6FF00;
  --chart-4: #16A34A;
  --chart-5: #EAB308;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #111827;
  --sidebar-primary: #312E81;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #0891B2;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D8DEE8;
  --sidebar-ring: #C6FF00;
  --radius: 16px;
}

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

export function SignalWhitePixelLimeShadcnKit() {
  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">Signal White Pixel Lime</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": "signal-white-pixel-lime",
  "type": "registry:theme",
  "title": "Signal White Pixel Lime shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F8FAFC",
      "foreground": "#111827",
      "card": "#FFFFFF",
      "card-foreground": "#111827",
      "popover": "#FFFFFF",
      "popover-foreground": "#111827",
      "primary": "#312E81",
      "primary-foreground": "#ffffff",
      "secondary": "#06B6D4",
      "secondary-foreground": "#ffffff",
      "muted": "#64748B",
      "muted-foreground": "#111827",
      "accent": "#C6FF00",
      "accent-foreground": "#111111",
      "destructive": "#E11D48",
      "border": "#D8DEE8",
      "input": "#D8DEE8",
      "ring": "#C6FF00",
      "chart-1": "#312E81",
      "chart-2": "#06B6D4",
      "chart-3": "#C6FF00",
      "chart-4": "#16A34A",
      "chart-5": "#EAB308",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#111827",
      "sidebar-primary": "#312E81",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#0891B2",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8DEE8",
      "sidebar-ring": "#C6FF00",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#312E81",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#C6FF00",
      "accent-foreground": "#111111",
      "destructive": "#E11D48",
      "border": "#303642",
      "input": "#303642",
      "ring": "#C6FF00",
      "chart-1": "#312E81",
      "chart-2": "#06B6D4",
      "chart-3": "#C6FF00",
      "chart-4": "#16A34A",
      "chart-5": "#EAB308",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#312E81",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#C6FF00",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#C6FF00",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e4bf7-5831-73f1-bf21-57b9b8b4ae96",
    "slug": "signal-white-pixel-lime",
    "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
# Signal White Pixel Lime shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4bf7-5831-73f1-bf21-57b9b8b4ae96`
Slug: `signal-white-pixel-lime`

## Intent

A clean product interface language where a quiet white hardware-calibration surface is activated by sparse neon-lime pixel states, indigo command structure, and cyan measurement feedback. It uses pixel logic as precision, not nostalgia: activation blocks, segmented counters, and crisp focus brackets make the UI distinctive while preserving premium readability.

## 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": "#C6FF00",
  "background": "#F8FAFC",
  "border": "#D8DEE8",
  "error": "#E11D48",
  "info": "#0891B2",
  "muted": "#64748B",
  "primary": "#312E81",
  "secondary": "#06B6D4",
  "success": "#16A34A",
  "surface": "#FFFFFF",
  "text": "#111827",
  "warning": "#EAB308"
}

Typography:

{
  "base_size": "16px",
  "body_font": "IBM Plex Sans",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Afacad+Flux:wght@500;650;750&family=IBM+Plex+Sans:wght@400;500;600;700&family=Pixelify+Sans:wght@400;500;600&display=swap",
  "heading_font": "Afacad Flux",
  "letter_spacing": "-0.02em",
  "line_height": 1.5,
  "mono_font": "Pixelify Sans",
  "scale_ratio": 1.22
}

## Visual character to preserve

- White and near-white surfaces use single-pixel #D8DEE8 hairline borders with broad 22px radius corners and almost no shadow.
- Neon lime appears as 4px square pixel clusters only inside live states, progress steps, focus rings, and active control terminals.
- Indigo anchors titles, nav pills, and primary actions while cyan is reserved for measured links, telemetry values, and secondary states.
- Pixel-influenced typography is isolated to tiny labels, counters, badges, and numerals while long text stays in a readable sans face.
- Layouts use one large calm workspace panel interrupted by a compact offset signal stack instead of equal dashboard card rows.

## ShadSync visual profile

{
  "family": "brutalist",
  "material": "ink",
  "contour": "pebble",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "stickerBadges": true,
  "motion": "lift",
  "density": "dense",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

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

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

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

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

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

## Preview shots

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

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/signal-white-pixel-lime/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 neon lime only for focus, activation, progress, current position, or live signal.; Keep body copy in IBM Plex Sans and reserve Pixelify Sans for micro labels, counters, badges, and display numerals.; Make pixel motifs functional inside controls, charts, and state indicators rather than floating decoration.; Use indigo as the stable command color and cyan as the measured feedback color.
- Do not: Do not use square-grid backgrounds, repeated dotted textures, card side rails, or stripe accents.; Do not add chipped diagonal corners, uneven borders, arcade blocks, or low-resolution gimmicks that hurt readability.; Do not expand the palette into rainbow status color unless a semantic error/warning/success token is required.; Do not present a generic SaaS dashboard or a component catalog as the primary embodiment.

## 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 SignalWhitePixelLimeShadcnKit() {
  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">Signal White Pixel Lime</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 1200px, tablet 768px, mobile 375px with inspector stacking below the workspace",
  "grid": "A flexible 12-column desktop structure collapses to stacked sheets; never use a visible square grid background.",
  "whitespace": "Use generous neutral margins, at least 64px around the hero workspace on desktop, and preserve clear separation between product task zones."
}
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-019e4bf7-5831-73f1-bf21-57b9b8b4ae96",
    "name": "Signal White Pixel Lime",
    "slug": "signal-white-pixel-lime"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "White and near-white surfaces use single-pixel #D8DEE8 hairline borders with broad 22px radius corners and almost no shadow.",
    "Neon lime appears as 4px square pixel clusters only inside live states, progress steps, focus rings, and active control terminals.",
    "Indigo anchors titles, nav pills, and primary actions while cyan is reserved for measured links, telemetry values, and secondary states.",
    "Pixel-influenced typography is isolated to tiny labels, counters, badges, and numerals while long text stays in a readable sans face.",
    "Layouts use one large calm workspace panel interrupted by a compact offset signal stack instead of equal dashboard card rows."
  ],
  "visualProfile": {
    "family": "brutalist",
    "material": "ink",
    "contour": "pebble",
    "border": "solid",
    "underlay": true,
    "grain": false,
    "stickerBadges": true,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Signal White Pixel Lime 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 neon lime only for focus, activation, progress, current position, or live signal.",
      "Keep body copy in IBM Plex Sans and reserve Pixelify Sans for micro labels, counters, badges, and display numerals.",
      "Make pixel motifs functional inside controls, charts, and state indicators rather than floating decoration.",
      "Use indigo as the stable command color and cyan as the measured feedback color."
    ],
    "dont": [
      "Do not use square-grid backgrounds, repeated dotted textures, card side rails, or stripe accents.",
      "Do not add chipped diagonal corners, uneven borders, arcade blocks, or low-resolution gimmicks that hurt readability.",
      "Do not expand the palette into rainbow status color unless a semantic error/warning/success token is required.",
      "Do not present a generic SaaS dashboard or a component catalog as the primary embodiment."
    ]
  }
}
related

More like this