back to gallery
design language·lumen-pixel-product-system

Lumen Pixel Product System

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 premium consumer product UI language for calm white surfaces where pixel cues behave like precision marks: compact state bits, stepped progress chips, and pixel-influenced annotation typography set against Apple-clean layouts with cool electric indigo, cyan, turquoise, and lime highlights.
values
clean consumer confidencepixel precision without game nostalgiacool-electric state claritypremium restrainttactile product usefulness
anti-values
×arcade skins or Minecraft-style block overload×rainbow accent sprawl or warm garnish×square-grid backgrounds and decorative dotted texture×generic SaaS dashboards with color as decoration
tokens
borders4 items
accent width
2px
character
even cool-gray hairlines with indigo/cyan focus rings; never uneven or chipped
default width
1px
style
solid
colors12 items
accent
#D7FF32
background
#FAFBFF
border
#DDE3F0
error
#E5484D
info
#00D5FF
muted
#6B7280
primary
#4038FF
secondary
#00BFD8
success
#7BEF2B
surface
#FFFFFF
text
#111827
warning
#F4C430
motion3 items
duration
180ms
easing
cubic-bezier(0.2, 0.8, 0.2, 1)
philosophy
quiet snap-to-precision transitions: controls brighten, bit clusters step forward, panels lift 2px without bounce
radii5 items
full
9999px
lg
28px
md
16px
none
0
sm
10px
shadows3 items
lg
0 30px 80px rgba(31, 45, 90, 0.14)
md
0 18px 45px rgba(26, 38, 80, 0.10)
sm
0 1px 2px rgba(17, 24, 39, 0.06)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
no square grid and no dotted texture; use only occasional isolated pixel glyph clusters as semantic state markers
card style
large even-radius white cards, 1px cool hairline border, soft shadow, interior pixel status bits rather than external stripes
treatment
porcelain white planes with subtle cool-blue edge light and restrained translucent command bands
typography8 items
base size
16px
body font
Manrope
google fonts url
https://fonts.googleapis.com/css2?family=Instrument+Sans:wght@500;600;700;800&family=Manrope:wght@400;500;600;700;800&family=Pixelify+Sans:wght@400;500;600;700&display=swap
heading font
Instrument Sans
letter spacing
-0.018em
line height
1.52
mono font
Pixelify Sans
scale ratio
1.22
rules
composition
Use a single hero product workspace as the dominant artifact, with generous white margins, a compact top command bar, and clustered device/status cards that feel like one consumer app screen rather than a module inventory.
density

Medium-light density: spacious shells and cards, compact pixel metadata, and only a few high-energy highlight moments per viewport.

hierarchy
Large smooth headings carry the consumer promise, while pixel typography is reserved for secondary proof labels, numerals, badges, and state annotations so readability remains premium.
signature patterns
Segmented pixel progress bars use 6 to 10 individual square bits that fill from indigo through cyan to sparse lime for meaningful completion states.Active controls use a soft cyan glow ring plus an internal two-square bit glyph instead of decorative side rails, card stripes, or large neon floods.Object cards include tiny pixel-font telemetry labels anchored to real data, with body content always set in the readable sans family.Command bands use translucent white surfaces over the neutral background with even radii, cool hairline borders, and compact pixel keycap hints.
layout
breakpoints

mobile 375px, tablet 768px, desktop 1200px and up

grid

A 12-column desktop product shell becomes two columns on tablet and a single stacked column on mobile; no visible square grid background is used.

whitespace

Whitespace is the premium material: 24-48px gutters on desktop, 20-32px between major cards, and compact 8px internal pixel clusters.

guidance
do
  • Use indigo, cyan/turquoise, and lime as a deliberately narrow cool-electric family tied to active, synced, and success states.
  • Keep pixel fonts to labels, counters, badges, key hints, and display numerals while preserving smooth sans body readability.
  • Make pixel elements functional: progress, sync states, selected bits, icon glyphs, and compact micro-illustrations.
  • Favor neutral white product scenes, generous spacing, even borders, and one committed radius system.
avoid
  • Do not use square-grid backgrounds, default dotted textures, decorative side rails, row stripes, or card accent bars.
  • Do not add arcade styling, block-game references, terminal hacker tropes, excessive neon glow, or unreadable low-resolution body text.
  • Do not scatter rainbow colors or warm accent garnish; reserve exceptions for required semantic warning/error states.
  • Do not use chipped diagonal corners, uneven borders, arbitrary mixed radii, or generic SaaS dashboard layouts.
katagami spec
# Lumen Pixel Product System

## Philosophy

A premium consumer product UI language for calm white surfaces where pixel cues behave like precision marks: compact state bits, stepped progress chips, and pixel-influenced annotation typography set against Apple-clean layouts with cool electric indigo, cyan, turquoise, and lime highlights.

### Values

- clean consumer confidence
- pixel precision without game nostalgia
- cool-electric state clarity
- premium restraint
- tactile product usefulness

### Anti-Values

- arcade skins or Minecraft-style block overload
- rainbow accent sprawl or warm garnish
- square-grid backgrounds and decorative dotted texture
- generic SaaS dashboards with color as decoration

### Visual Character

- Use matte white and porcelain-neutral full-bleed backgrounds with large rounded panels, hairline borders, and no repeated grid or dotted texture.
- Render pixel identity through tiny stepped bit clusters, square indicator glyphs, and segmented progress sequences placed inside controls and data states.
- Pair smooth modern sans headings and body text with a pixel-influenced display face only for badges, counters, keyboard hints, and micro annotations.
- Apply indigo as the calm primary anchor, cyan/turquoise as active focus light, and lime as sparse success energy inside small state elements.
- Compose screens around one dominant product artifact: a consumer device sync workspace with object cards, command bands, and precise status modules.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: even cool-gray hairlines with indigo/cyan focus rings; never uneven or chipped
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#D7FF32` |
| background | `#FAFBFF` |
| border | `#DDE3F0` |
| error | `#E5484D` |
| info | `#00D5FF` |
| muted | `#6B7280` |
| primary | `#4038FF` |
| secondary | `#00BFD8` |
| success | `#7BEF2B` |
| surface | `#FFFFFF` |
| text | `#111827` |
| warning | `#F4C430` |

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1)
- **Philosophy**: quiet snap-to-precision transitions: controls brighten, bit clusters step forward, panels lift 2px without bounce

### Radii

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

### Shadows

- **Lg**: 0 30px 80px rgba(31, 45, 90, 0.14)
- **Md**: 0 18px 45px rgba(26, 38, 80, 0.10)
- **Sm**: 0 1px 2px rgba(17, 24, 39, 0.06)

### Spacing

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

### Surfaces

- **Bg Pattern**: no square grid and no dotted texture; use only occasional isolated pixel glyph clusters as semantic state markers
- **Card Style**: large even-radius white cards, 1px cool hairline border, soft shadow, interior pixel status bits rather than external stripes
- **Treatment**: porcelain white planes with subtle cool-blue edge light and restrained translucent command bands

### Typography

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

## Rules

### Composition

Use a single hero product workspace as the dominant artifact, with generous white margins, a compact top command bar, and clustered device/status cards that feel like one consumer app screen rather than a module inventory.

### Density

Medium-light density: spacious shells and cards, compact pixel metadata, and only a few high-energy highlight moments per viewport.

### Hierarchy

Large smooth headings carry the consumer promise, while pixel typography is reserved for secondary proof labels, numerals, badges, and state annotations so readability remains premium.

### Signature Patterns

- Segmented pixel progress bars use 6 to 10 individual square bits that fill from indigo through cyan to sparse lime for meaningful completion states.
- Active controls use a soft cyan glow ring plus an internal two-square bit glyph instead of decorative side rails, card stripes, or large neon floods.
- Object cards include tiny pixel-font telemetry labels anchored to real data, with body content always set in the readable sans family.
- Command bands use translucent white surfaces over the neutral background with even radii, cool hairline borders, and compact pixel keycap hints.

## Layout

### Breakpoints

mobile 375px, tablet 768px, desktop 1200px and up

### Grid

A 12-column desktop product shell becomes two columns on tablet and a single stacked column on mobile; no visible square grid background is used.

### Whitespace

Whitespace is the premium material: 24-48px gutters on desktop, 20-32px between major cards, and compact 8px internal pixel clusters.

## Guidance

### Do

- Use indigo, cyan/turquoise, and lime as a deliberately narrow cool-electric family tied to active, synced, and success states.
- Keep pixel fonts to labels, counters, badges, key hints, and display numerals while preserving smooth sans body readability.
- Make pixel elements functional: progress, sync states, selected bits, icon glyphs, and compact micro-illustrations.
- Favor neutral white product scenes, generous spacing, even borders, and one committed radius system.

### Don't

- Do not use square-grid backgrounds, default dotted textures, decorative side rails, row stripes, or card accent bars.
- Do not add arcade styling, block-game references, terminal hacker tropes, excessive neon glow, or unreadable low-resolution body text.
- Do not scatter rainbow colors or warm accent garnish; reserve exceptions for required semantic warning/error states.
- Do not use chipped diagonal corners, uneven borders, arbitrary mixed radii, or generic SaaS dashboard layouts.
DESIGN.md
---
version: "alpha"
name: "Lumen Pixel Product System"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#D7FF32"
  background: "#FAFBFF"
  border: "#DDE3F0"
  error: "#E5484D"
  info: "#00D5FF"
  muted: "#6B7280"
  primary: "#4038FF"
  secondary: "#00BFD8"
  success: "#7BEF2B"
  surface: "#FFFFFF"
  text: "#111827"
  warning: "#F4C430"
typography:
  headline-lg:
    fontFamily: "Instrument Sans"
    fontSize: "1.816rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.018em"
  headline-md:
    fontFamily: "Instrument Sans"
    fontSize: "1.488rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.018em"
  body-md:
    fontFamily: "Manrope"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.52
    letterSpacing: "-0.018em"
  label-md:
    fontFamily: "Pixelify Sans"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "28px"
  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"
---

# Lumen Pixel Product System

## Overview

A premium consumer product UI language for calm white surfaces where pixel cues behave like precision marks: compact state bits, stepped progress chips, and pixel-influenced annotation typography set against Apple-clean layouts with cool electric indigo, cyan, turquoise, and lime highlights.

### Values

- clean consumer confidence
- pixel precision without game nostalgia
- cool-electric state clarity
- premium restraint
- tactile product usefulness

### Anti-Values

- arcade skins or Minecraft-style block overload
- rainbow accent sprawl or warm garnish
- square-grid backgrounds and decorative dotted texture
- generic SaaS dashboards with color as decoration

### Visual Character

- Use matte white and porcelain-neutral full-bleed backgrounds with large rounded panels, hairline borders, and no repeated grid or dotted texture.
- Render pixel identity through tiny stepped bit clusters, square indicator glyphs, and segmented progress sequences placed inside controls and data states.
- Pair smooth modern sans headings and body text with a pixel-influenced display face only for badges, counters, keyboard hints, and micro annotations.
- Apply indigo as the calm primary anchor, cyan/turquoise as active focus light, and lime as sparse success energy inside small state elements.
- Compose screens around one dominant product artifact: a consumer device sync workspace with object cards, command bands, and precise status modules.

## 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 | `#D7FF32` |
| background | `#FAFBFF` |
| border | `#DDE3F0` |
| error | `#E5484D` |
| info | `#00D5FF` |
| muted | `#6B7280` |
| primary | `#4038FF` |
| secondary | `#00BFD8` |
| success | `#7BEF2B` |
| surface | `#FFFFFF` |
| text | `#111827` |
| warning | `#F4C430` |

## Typography

- **Headline-Lg**: Instrument Sans, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Instrument Sans, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Manrope, 16px, weight 400, line-height 1.52.
- **Label-Md**: Pixelify Sans, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

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

### Breakpoints

mobile 375px, tablet 768px, desktop 1200px and up

### Grid

A 12-column desktop product shell becomes two columns on tablet and a single stacked column on mobile; no visible square grid background is used.

### Whitespace

Whitespace is the premium material: 24-48px gutters on desktop, 20-32px between major cards, and compact 8px internal pixel clusters.

## Elevation & Depth

### Shadows

- **Lg**: 0 30px 80px rgba(31, 45, 90, 0.14)
- **Md**: 0 18px 45px rgba(26, 38, 80, 0.10)
- **Sm**: 0 1px 2px rgba(17, 24, 39, 0.06)

## Shapes

### Rounded

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

### Surfaces

- **Bg Pattern**: no square grid and no dotted texture; use only occasional isolated pixel glyph clusters as semantic state markers
- **Card Style**: large even-radius white cards, 1px cool hairline border, soft shadow, interior pixel status bits rather than external stripes
- **Treatment**: porcelain white planes with subtle cool-blue edge light and restrained translucent command bands

### Borders

- **Accent Width**: 2px
- **Character**: even cool-gray hairlines with indigo/cyan focus rings; never uneven or chipped
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use a single hero product workspace as the dominant artifact, with generous white margins, a compact top command bar, and clustered device/status cards that feel like one consumer app screen rather than a module inventory.

### Density

Medium-light density: spacious shells and cards, compact pixel metadata, and only a few high-energy highlight moments per viewport.

### Hierarchy

Large smooth headings carry the consumer promise, while pixel typography is reserved for secondary proof labels, numerals, badges, and state annotations so readability remains premium.

### Signature Patterns

- Segmented pixel progress bars use 6 to 10 individual square bits that fill from indigo through cyan to sparse lime for meaningful completion states.
- Active controls use a soft cyan glow ring plus an internal two-square bit glyph instead of decorative side rails, card stripes, or large neon floods.
- Object cards include tiny pixel-font telemetry labels anchored to real data, with body content always set in the readable sans family.
- Command bands use translucent white surfaces over the neutral background with even radii, cool hairline borders, and compact pixel keycap hints.

## 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-019e4c0f-ce7e-7500-a578-aa8b915d8299/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 indigo, cyan/turquoise, and lime as a deliberately narrow cool-electric family tied to active, synced, and success states.
- Do Keep pixel fonts to labels, counters, badges, key hints, and display numerals while preserving smooth sans body readability.
- Do Make pixel elements functional: progress, sync states, selected bits, icon glyphs, and compact micro-illustrations.
- Do Favor neutral white product scenes, generous spacing, even borders, and one committed radius system.
- Don't Do not use square-grid backgrounds, default dotted textures, decorative side rails, row stripes, or card accent bars.
- Don't Do not add arcade styling, block-game references, terminal hacker tropes, excessive neon glow, or unreadable low-resolution body text.
- Don't Do not scatter rainbow colors or warm accent garnish; reserve exceptions for required semantic warning/error states.
- Don't Do not use chipped diagonal corners, uneven borders, arbitrary mixed radii, or generic SaaS dashboard layouts.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "lumen-pixel-product-system",
  "type": "registry:theme",
  "title": "Lumen Pixel Product System shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FAFBFF",
      "foreground": "#111827",
      "card": "#FFFFFF",
      "card-foreground": "#111827",
      "popover": "#FFFFFF",
      "popover-foreground": "#111827",
      "primary": "#4038FF",
      "primary-foreground": "#ffffff",
      "secondary": "#00BFD8",
      "secondary-foreground": "#ffffff",
      "muted": "#6B7280",
      "muted-foreground": "#111827",
      "accent": "#D7FF32",
      "accent-foreground": "#111111",
      "destructive": "#E5484D",
      "border": "#DDE3F0",
      "input": "#DDE3F0",
      "ring": "#D7FF32",
      "chart-1": "#4038FF",
      "chart-2": "#00BFD8",
      "chart-3": "#D7FF32",
      "chart-4": "#7BEF2B",
      "chart-5": "#F4C430",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#111827",
      "sidebar-primary": "#4038FF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#00D5FF",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#DDE3F0",
      "sidebar-ring": "#D7FF32",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#4038FF",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#D7FF32",
      "accent-foreground": "#111111",
      "destructive": "#E5484D",
      "border": "#303642",
      "input": "#303642",
      "ring": "#D7FF32",
      "chart-1": "#4038FF",
      "chart-2": "#00BFD8",
      "chart-3": "#D7FF32",
      "chart-4": "#7BEF2B",
      "chart-5": "#F4C430",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#4038FF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#D7FF32",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#D7FF32",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e4c0f-ce7e-7500-a578-aa8b915d8299",
    "slug": "lumen-pixel-product-system",
    "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 · lumen-pixel-product-system
DESIGN.md

at a glance

Palette

Typography

headline-lgInstrument Sans · 29px · 700

The quick brown fox jumps

headline-mdInstrument Sans · 24px · 600

The quick brown fox jumps

body-mdManrope · 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
lg28px
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: #FAFBFF;
  --foreground: #111827;
  --card: #FFFFFF;
  --card-foreground: #111827;
  --popover: #FFFFFF;
  --popover-foreground: #111827;
  --primary: #4038FF;
  --primary-foreground: #ffffff;
  --secondary: #00BFD8;
  --secondary-foreground: #ffffff;
  --muted: #6B7280;
  --muted-foreground: #111827;
  --accent: #D7FF32;
  --accent-foreground: #111111;
  --destructive: #E5484D;
  --border: #DDE3F0;
  --input: #DDE3F0;
  --ring: #D7FF32;
  --chart-1: #4038FF;
  --chart-2: #00BFD8;
  --chart-3: #D7FF32;
  --chart-4: #7BEF2B;
  --chart-5: #F4C430;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #111827;
  --sidebar-primary: #4038FF;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #00D5FF;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #DDE3F0;
  --sidebar-ring: #D7FF32;
  --radius: 16px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #4038FF;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #D7FF32;
  --accent-foreground: #111111;
  --destructive: #E5484D;
  --border: #303642;
  --input: #303642;
  --ring: #D7FF32;
  --chart-1: #4038FF;
  --chart-2: #00BFD8;
  --chart-3: #D7FF32;
  --chart-4: #7BEF2B;
  --chart-5: #F4C430;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #4038FF;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #D7FF32;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #D7FF32;
  --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 LumenPixelProductSystemShadcnKit() {
  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">Lumen Pixel Product System</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

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

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

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4c0f-ce7e-7500-a578-aa8b915d8299`
Slug: `lumen-pixel-product-system`

## Intent

A premium consumer product UI language for calm white surfaces where pixel cues behave like precision marks: compact state bits, stepped progress chips, and pixel-influenced annotation typography set against Apple-clean layouts with cool electric indigo, cyan, turquoise, and lime highlights.

## 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": "#D7FF32",
  "background": "#FAFBFF",
  "border": "#DDE3F0",
  "error": "#E5484D",
  "info": "#00D5FF",
  "muted": "#6B7280",
  "primary": "#4038FF",
  "secondary": "#00BFD8",
  "success": "#7BEF2B",
  "surface": "#FFFFFF",
  "text": "#111827",
  "warning": "#F4C430"
}

Typography:

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

## Visual character to preserve

- Use matte white and porcelain-neutral full-bleed backgrounds with large rounded panels, hairline borders, and no repeated grid or dotted texture.
- Render pixel identity through tiny stepped bit clusters, square indicator glyphs, and segmented progress sequences placed inside controls and data states.
- Pair smooth modern sans headings and body text with a pixel-influenced display face only for badges, counters, keyboard hints, and micro annotations.
- Apply indigo as the calm primary anchor, cyan/turquoise as active focus light, and lime as sparse success energy inside small state elements.
- Compose screens around one dominant product artifact: a consumer device sync workspace with object cards, command bands, and precise status modules.

## ShadSync visual profile

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

## Signature component recipes

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

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

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

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

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

## Preview shots

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

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/lumen-pixel-product-system/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 indigo, cyan/turquoise, and lime as a deliberately narrow cool-electric family tied to active, synced, and success states.; Keep pixel fonts to labels, counters, badges, key hints, and display numerals while preserving smooth sans body readability.; Make pixel elements functional: progress, sync states, selected bits, icon glyphs, and compact micro-illustrations.; Favor neutral white product scenes, generous spacing, even borders, and one committed radius system.
- Do not: Do not use square-grid backgrounds, default dotted textures, decorative side rails, row stripes, or card accent bars.; Do not add arcade styling, block-game references, terminal hacker tropes, excessive neon glow, or unreadable low-resolution body text.; Do not scatter rainbow colors or warm accent garnish; reserve exceptions for required semantic warning/error states.; Do not use chipped diagonal corners, uneven borders, arbitrary mixed radii, or generic SaaS dashboard layouts.

## 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 LumenPixelProductSystemShadcnKit() {
  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">Lumen Pixel Product System</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

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

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

## Layout notes

{
  "breakpoints": "mobile 375px, tablet 768px, desktop 1200px and up",
  "grid": "A 12-column desktop product shell becomes two columns on tablet and a single stacked column on mobile; no visible square grid background is used.",
  "whitespace": "Whitespace is the premium material: 24-48px gutters on desktop, 20-32px between major cards, and compact 8px internal pixel clusters."
}
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-019e4c0f-ce7e-7500-a578-aa8b915d8299",
    "name": "Lumen Pixel Product System",
    "slug": "lumen-pixel-product-system"
  },
  "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": [
    "Use matte white and porcelain-neutral full-bleed backgrounds with large rounded panels, hairline borders, and no repeated grid or dotted texture.",
    "Render pixel identity through tiny stepped bit clusters, square indicator glyphs, and segmented progress sequences placed inside controls and data states.",
    "Pair smooth modern sans headings and body text with a pixel-influenced display face only for badges, counters, keyboard hints, and micro annotations.",
    "Apply indigo as the calm primary anchor, cyan/turquoise as active focus light, and lime as sparse success energy inside small state elements.",
    "Compose screens around one dominant product artifact: a consumer device sync workspace with object cards, command bands, and precise status modules."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": true,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Lumen Pixel Product System 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 indigo, cyan/turquoise, and lime as a deliberately narrow cool-electric family tied to active, synced, and success states.",
      "Keep pixel fonts to labels, counters, badges, key hints, and display numerals while preserving smooth sans body readability.",
      "Make pixel elements functional: progress, sync states, selected bits, icon glyphs, and compact micro-illustrations.",
      "Favor neutral white product scenes, generous spacing, even borders, and one committed radius system."
    ],
    "dont": [
      "Do not use square-grid backgrounds, default dotted textures, decorative side rails, row stripes, or card accent bars.",
      "Do not add arcade styling, block-game references, terminal hacker tropes, excessive neon glow, or unreadable low-resolution body text.",
      "Do not scatter rainbow colors or warm accent garnish; reserve exceptions for required semantic warning/error states.",
      "Do not use chipped diagonal corners, uneven borders, arbitrary mixed radii, or generic SaaS dashboard layouts."
    ]
  }
}
related

More like this