Lumen Pixel Control Surface
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.
specification
philosophy
tokens
borders4 items
- accent width
- 2px
- character
- cool blue translucent structural lines; accent width used as complete focus outline or inner aperture, never as a one-sided rail
- default width
- 1px
- style
- solid
colors12 items
motion3 items
- duration
- 180ms
- easing
- cubic-bezier(.2,.8,.2,1)
- philosophy
- state changes snap into alignment with a short lime aperture pulse; layout motion stays calm and functional
radii5 items
- full
- 9999px
- lg
- 22px
- md
- 14px
- none
- 0
- sm
- 8px
shadows3 items
- lg
- 0 32px 80px rgba(17,24,39,0.14)
- md
- 0 18px 45px rgba(36,55,168,0.10)
- sm
- 0 1px 2px rgba(17,24,39,0.06), 0 0 0 1px rgba(36,55,168,0.04)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- plain neutral field with occasional isolated pixel glyphs inside components only; no square grid and no repeated dots
- card style
- rounded 22px white panels, blue-tinted 1px border, inset white highlight, no side stripes or chipped corners
- treatment
- white neutral surfaces with very faint cyan/indigo atmospheric glows only behind major control areas
typography8 items
- base size
- 16px
- body font
- Hanken Grotesk
- google fonts url
- https://fonts.googleapis.com/css2?family=Hanken+Grotesk:wght@400;500;600;700;800&family=Spline+Sans+Mono:wght@400;500;600;700&display=swap
- heading font
- Hanken Grotesk
- letter spacing
- -0.02em
- line height
- 1.5
- mono font
- Spline Sans Mono
- scale ratio
- 1.24
rules
Use a scene-first product control desk with one dominant instrument panel, a compact right-side decision stack, and at least one small overlay module that breaks the main alignment without becoming decorative.
Medium-high instrument density is allowed inside panels, but generous exterior whitespace and dramatic 8px-to-64px spacing jumps keep the interface premium.
Reserve the largest type for the current calibration objective, use smooth grotesk body text for explanation, and use pixel-mono annotations only for coordinates, states, counts, and component labels.
layout
mobile 375px, tablet 768px, desktop 1200px with max content width 1320px
A responsive 12-column product surface where the main control panel spans seven to eight columns, the decision stack spans four, and mobile collapses into a single ordered instrument feed.
Use 64px outer air on desktop, 32px between major zones, 16px within panels, and 4-8px inside pixel badges to create strong proximity hierarchy.
guidance
- Use lime only for active, confirmed, focused, or ready-to-run states.
- Keep pixel typography in labels, counters, badges, coordinates, and short annotations while using readable grotesk body text.
- Let indigo and cyan provide structure through headers, dividers, outlines, and data visualizations on clean neutral surfaces.
- Style every form control with the same aperture, border, and pixel-state grammar.
- Do not use square-grid or dotted backgrounds as default texture.
- Do not add side rails, left stripes, chipped corners, uneven borders, or decorative card bars.
- Do not turn the system into a retro terminal, arcade screen, hacker UI, or Minecraft/block overload.
- Do not add rainbow status colors or warm accents except semantic error/warning tokens.
katagami spec
# Lumen Pixel Control Surface ## Philosophy A premium white control surface for calibration-heavy product software where pixel glyphs behave like precise signal punctuation, not nostalgia. Indigo anchors structure, cyan describes live surfaces, and a restrained lime pulse marks only decisive state changes. ### Values - Apple-like neutral calm with exact component spacing - Pixel typography as precision annotation rather than retro theming - Cool-electric color hierarchy with lime reserved for active signals - Readable product utility across dense instrument controls ### Anti-Values - Arcade, terminal, hacker, or game-skin pixel nostalgia - Square-grid backgrounds, dotted filler textures, side rails, or stripe garnish - Rainbow accents or warm decorative colors without product meaning - Low-resolution body typography that harms legibility ### Visual Character - Large white and warm-neutral canvases use soft translucent panels, 1px blue-tinted borders, and broad whitespace rather than textured or gridded backgrounds. - Indigo header blocks and cyan hairline dividers form stepped control bands with rounded-rectangle geometry and no one-sided color rails. - Tiny pixel glyph clusters appear inside badges, toggles, and status chips as 2px square CSS blocks that signal mode, lock, or sync state. - Pixel-influenced mono labels are uppercase, tightly spaced, and limited to counters, coordinates, badges, and annotations while body copy stays smooth and readable. - Neon lime is reserved for small active apertures, focus rings, and confirmation pulses so vivid color carries state instead of decoration. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: cool blue translucent structural lines; accent width used as complete focus outline or inner aperture, never as a one-sided rail - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#C8FF2E` | | background | `#F8FAF7` | | border | `#C9D8E8` | | error | `#C7325F` | | info | `#008FCB` | | muted | `#6B7280` | | primary | `#2437A8` | | secondary | `#00AFC7` | | success | `#0EAD69` | | surface | `#FFFFFF` | | text | `#111827` | | warning | `#D6A100` | ### Motion - **Duration**: 180ms - **Easing**: cubic-bezier(.2,.8,.2,1) - **Philosophy**: state changes snap into alignment with a short lime aperture pulse; layout motion stays calm and functional ### Radii - **Full**: 9999px - **Lg**: 22px - **Md**: 14px - **None**: 0 - **Sm**: 8px ### Shadows - **Lg**: 0 32px 80px rgba(17,24,39,0.14) - **Md**: 0 18px 45px rgba(36,55,168,0.10) - **Sm**: 0 1px 2px rgba(17,24,39,0.06), 0 0 0 1px rgba(36,55,168,0.04) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: plain neutral field with occasional isolated pixel glyphs inside components only; no square grid and no repeated dots - **Card Style**: rounded 22px white panels, blue-tinted 1px border, inset white highlight, no side stripes or chipped corners - **Treatment**: white neutral surfaces with very faint cyan/indigo atmospheric glows only behind major control areas ### Typography - **Base Size**: 16px - **Body Font**: Hanken Grotesk - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Hanken+Grotesk:wght@400;500;600;700;800&family=Spline+Sans+Mono:wght@400;500;600;700&display=swap - **Heading Font**: Hanken Grotesk - **Letter Spacing**: -0.02em - **Line Height**: 1.5 - **Mono Font**: Spline Sans Mono - **Scale Ratio**: 1.24 ## Rules ### Composition Use a scene-first product control desk with one dominant instrument panel, a compact right-side decision stack, and at least one small overlay module that breaks the main alignment without becoming decorative. ### Density Medium-high instrument density is allowed inside panels, but generous exterior whitespace and dramatic 8px-to-64px spacing jumps keep the interface premium. ### Hierarchy Reserve the largest type for the current calibration objective, use smooth grotesk body text for explanation, and use pixel-mono annotations only for coordinates, states, counts, and component labels. ### Signature Patterns - Signal aperture controls: active buttons, sliders, and selected tabs use a complete lime inner outline plus a tiny pixel glyph cluster to mark live state. - Stepped cyan dividers: panels separate content with short horizontal cyan line segments and rounded capsules, never full grids or decorative side stripes. - Pixel checksum labels: badges and data rows include mono uppercase labels with small square-bit sequences that encode state without replacing readable text. - Neutral depth stack: white panels float on a neutral base with blue-tinted borders and soft indigo shadows rather than heavy glass, gradients, or chrome. ## Layout ### Breakpoints mobile 375px, tablet 768px, desktop 1200px with max content width 1320px ### Grid A responsive 12-column product surface where the main control panel spans seven to eight columns, the decision stack spans four, and mobile collapses into a single ordered instrument feed. ### Whitespace Use 64px outer air on desktop, 32px between major zones, 16px within panels, and 4-8px inside pixel badges to create strong proximity hierarchy. ## Guidance ### Do - Use lime only for active, confirmed, focused, or ready-to-run states. - Keep pixel typography in labels, counters, badges, coordinates, and short annotations while using readable grotesk body text. - Let indigo and cyan provide structure through headers, dividers, outlines, and data visualizations on clean neutral surfaces. - Style every form control with the same aperture, border, and pixel-state grammar. ### Don't - Do not use square-grid or dotted backgrounds as default texture. - Do not add side rails, left stripes, chipped corners, uneven borders, or decorative card bars. - Do not turn the system into a retro terminal, arcade screen, hacker UI, or Minecraft/block overload. - Do not add rainbow status colors or warm accents except semantic error/warning tokens.
DESIGN.md
---
version: "alpha"
name: "Lumen Pixel Control Surface"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#C8FF2E"
background: "#F8FAF7"
border: "#C9D8E8"
error: "#C7325F"
info: "#008FCB"
muted: "#6B7280"
primary: "#2437A8"
secondary: "#00AFC7"
success: "#0EAD69"
surface: "#FFFFFF"
text: "#111827"
warning: "#D6A100"
typography:
headline-lg:
fontFamily: "Hanken Grotesk"
fontSize: "1.907rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.02em"
headline-md:
fontFamily: "Hanken Grotesk"
fontSize: "1.538rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.02em"
body-md:
fontFamily: "Hanken Grotesk"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.5
letterSpacing: "-0.02em"
label-md:
fontFamily: "Spline Sans Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "22px"
md: "14px"
none: "0px"
sm: "8px"
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 Control Surface
## Overview
A premium white control surface for calibration-heavy product software where pixel glyphs behave like precise signal punctuation, not nostalgia. Indigo anchors structure, cyan describes live surfaces, and a restrained lime pulse marks only decisive state changes.
### Values
- Apple-like neutral calm with exact component spacing
- Pixel typography as precision annotation rather than retro theming
- Cool-electric color hierarchy with lime reserved for active signals
- Readable product utility across dense instrument controls
### Anti-Values
- Arcade, terminal, hacker, or game-skin pixel nostalgia
- Square-grid backgrounds, dotted filler textures, side rails, or stripe garnish
- Rainbow accents or warm decorative colors without product meaning
- Low-resolution body typography that harms legibility
### Visual Character
- Large white and warm-neutral canvases use soft translucent panels, 1px blue-tinted borders, and broad whitespace rather than textured or gridded backgrounds.
- Indigo header blocks and cyan hairline dividers form stepped control bands with rounded-rectangle geometry and no one-sided color rails.
- Tiny pixel glyph clusters appear inside badges, toggles, and status chips as 2px square CSS blocks that signal mode, lock, or sync state.
- Pixel-influenced mono labels are uppercase, tightly spaced, and limited to counters, coordinates, badges, and annotations while body copy stays smooth and readable.
- Neon lime is reserved for small active apertures, focus rings, and confirmation pulses so vivid color carries state instead of decoration.
## 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 | `#C8FF2E` |
| background | `#F8FAF7` |
| border | `#C9D8E8` |
| error | `#C7325F` |
| info | `#008FCB` |
| muted | `#6B7280` |
| primary | `#2437A8` |
| secondary | `#00AFC7` |
| success | `#0EAD69` |
| surface | `#FFFFFF` |
| text | `#111827` |
| warning | `#D6A100` |
## Typography
- **Headline-Lg**: Hanken Grotesk, 1.907rem, weight 700, line-height 1.1.
- **Headline-Md**: Hanken Grotesk, 1.538rem, weight 600, line-height 1.15.
- **Body-Md**: Hanken Grotesk, 16px, weight 400, line-height 1.5.
- **Label-Md**: Spline Sans Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
### Breakpoints
mobile 375px, tablet 768px, desktop 1200px with max content width 1320px
### Grid
A responsive 12-column product surface where the main control panel spans seven to eight columns, the decision stack spans four, and mobile collapses into a single ordered instrument feed.
### Whitespace
Use 64px outer air on desktop, 32px between major zones, 16px within panels, and 4-8px inside pixel badges to create strong proximity hierarchy.
## Elevation & Depth
### Shadows
- **Lg**: 0 32px 80px rgba(17,24,39,0.14)
- **Md**: 0 18px 45px rgba(36,55,168,0.10)
- **Sm**: 0 1px 2px rgba(17,24,39,0.06), 0 0 0 1px rgba(36,55,168,0.04)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `22px`
- **Md**: `14px`
- **None**: `0px`
- **Sm**: `8px`
### Surfaces
- **Bg Pattern**: plain neutral field with occasional isolated pixel glyphs inside components only; no square grid and no repeated dots
- **Card Style**: rounded 22px white panels, blue-tinted 1px border, inset white highlight, no side stripes or chipped corners
- **Treatment**: white neutral surfaces with very faint cyan/indigo atmospheric glows only behind major control areas
### Borders
- **Accent Width**: 2px
- **Character**: cool blue translucent structural lines; accent width used as complete focus outline or inner aperture, never as a one-sided rail
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Use a scene-first product control desk with one dominant instrument panel, a compact right-side decision stack, and at least one small overlay module that breaks the main alignment without becoming decorative.
### Density
Medium-high instrument density is allowed inside panels, but generous exterior whitespace and dramatic 8px-to-64px spacing jumps keep the interface premium.
### Hierarchy
Reserve the largest type for the current calibration objective, use smooth grotesk body text for explanation, and use pixel-mono annotations only for coordinates, states, counts, and component labels.
### Signature Patterns
- Signal aperture controls: active buttons, sliders, and selected tabs use a complete lime inner outline plus a tiny pixel glyph cluster to mark live state.
- Stepped cyan dividers: panels separate content with short horizontal cyan line segments and rounded capsules, never full grids or decorative side stripes.
- Pixel checksum labels: badges and data rows include mono uppercase labels with small square-bit sequences that encode state without replacing readable text.
- Neutral depth stack: white panels float on a neutral base with blue-tinted borders and soft indigo shadows rather than heavy glass, gradients, or chrome.
## 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-17b7-73e0-9256-a1ca97bf6a51/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 lime only for active, confirmed, focused, or ready-to-run states.
- Do Keep pixel typography in labels, counters, badges, coordinates, and short annotations while using readable grotesk body text.
- Do Let indigo and cyan provide structure through headers, dividers, outlines, and data visualizations on clean neutral surfaces.
- Do Style every form control with the same aperture, border, and pixel-state grammar.
- Don't Do not use square-grid or dotted backgrounds as default texture.
- Don't Do not add side rails, left stripes, chipped corners, uneven borders, or decorative card bars.
- Don't Do not turn the system into a retro terminal, arcade screen, hacker UI, or Minecraft/block overload.
- Don't Do not add rainbow status colors or warm accents except semantic error/warning tokens.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "lumen-pixel-control-surface",
"type": "registry:theme",
"title": "Lumen Pixel Control Surface shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F8FAF7",
"foreground": "#111827",
"card": "#FFFFFF",
"card-foreground": "#111827",
"popover": "#FFFFFF",
"popover-foreground": "#111827",
"primary": "#2437A8",
"primary-foreground": "#ffffff",
"secondary": "#00AFC7",
"secondary-foreground": "#ffffff",
"muted": "#6B7280",
"muted-foreground": "#111827",
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"destructive": "#C7325F",
"border": "#C9D8E8",
"input": "#C9D8E8",
"ring": "#C8FF2E",
"chart-1": "#2437A8",
"chart-2": "#00AFC7",
"chart-3": "#C8FF2E",
"chart-4": "#0EAD69",
"chart-5": "#D6A100",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#111827",
"sidebar-primary": "#2437A8",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#008FCB",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#C9D8E8",
"sidebar-ring": "#C8FF2E",
"radius": "14px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#2437A8",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"destructive": "#C7325F",
"border": "#303642",
"input": "#303642",
"ring": "#C8FF2E",
"chart-1": "#2437A8",
"chart-2": "#00AFC7",
"chart-3": "#C8FF2E",
"chart-4": "#0EAD69",
"chart-5": "#D6A100",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#2437A8",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#C8FF2E",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#C8FF2E",
"radius": "14px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e4bf7-17b7-73e0-9256-a1ca97bf6a51",
"slug": "lumen-pixel-control-surface",
"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"
]
}
}
}
```embodiments
at a glance
Typography
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Components
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
implementation kit
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
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #F8FAF7;
--foreground: #111827;
--card: #FFFFFF;
--card-foreground: #111827;
--popover: #FFFFFF;
--popover-foreground: #111827;
--primary: #2437A8;
--primary-foreground: #ffffff;
--secondary: #00AFC7;
--secondary-foreground: #ffffff;
--muted: #6B7280;
--muted-foreground: #111827;
--accent: #C8FF2E;
--accent-foreground: #111111;
--destructive: #C7325F;
--border: #C9D8E8;
--input: #C9D8E8;
--ring: #C8FF2E;
--chart-1: #2437A8;
--chart-2: #00AFC7;
--chart-3: #C8FF2E;
--chart-4: #0EAD69;
--chart-5: #D6A100;
--sidebar: #FFFFFF;
--sidebar-foreground: #111827;
--sidebar-primary: #2437A8;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #008FCB;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #C9D8E8;
--sidebar-ring: #C8FF2E;
--radius: 14px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #2437A8;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #C8FF2E;
--accent-foreground: #111111;
--destructive: #C7325F;
--border: #303642;
--input: #303642;
--ring: #C8FF2E;
--chart-1: #2437A8;
--chart-2: #00AFC7;
--chart-3: #C8FF2E;
--chart-4: #0EAD69;
--chart-5: #D6A100;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #2437A8;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #C8FF2E;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #C8FF2E;
--radius: 14px;
}
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 LumenPixelControlSurfaceShadcnKit() {
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 Control Surface</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>
);
}
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"cssVars": {
"dark": {
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"background": "#0f1115",
"border": "#303642",
"card": "#181b22",
"card-foreground": "#f8fafc",
"chart-1": "#2437A8",
"chart-2": "#00AFC7",
"chart-3": "#C8FF2E",
"chart-4": "#0EAD69",
"chart-5": "#D6A100",
"destructive": "#C7325F",
"foreground": "#f8fafc",
"input": "#303642",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#2437A8",
"primary-foreground": "#ffffff",
"radius": "14px",
"ring": "#C8FF2E",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"sidebar": "#181b22",
"sidebar-accent": "#C8FF2E",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#2437A8",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#C8FF2E"
},
"light": {
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"background": "#F8FAF7",
"border": "#C9D8E8",
"card": "#FFFFFF",
"card-foreground": "#111827",
"chart-1": "#2437A8",
"chart-2": "#00AFC7",
"chart-3": "#C8FF2E",
"chart-4": "#0EAD69",
"chart-5": "#D6A100",
"destructive": "#C7325F",
"foreground": "#111827",
"input": "#C9D8E8",
"muted": "#6B7280",
"muted-foreground": "#111827",
"popover": "#FFFFFF",
"popover-foreground": "#111827",
"primary": "#2437A8",
"primary-foreground": "#ffffff",
"radius": "14px",
"ring": "#C8FF2E",
"secondary": "#00AFC7",
"secondary-foreground": "#ffffff",
"sidebar": "#FFFFFF",
"sidebar-accent": "#008FCB",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#C9D8E8",
"sidebar-foreground": "#111827",
"sidebar-primary": "#2437A8",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#C8FF2E"
},
"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-019e4bf7-17b7-73e0-9256-a1ca97bf6a51",
"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-control-surface",
"source": "katagami"
},
"name": "lumen-pixel-control-surface",
"title": "Lumen Pixel Control Surface shadcn Theme",
"type": "registry:theme"
}
# Lumen Pixel Control Surface shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4bf7-17b7-73e0-9256-a1ca97bf6a51`
Slug: `lumen-pixel-control-surface`
## Intent
A premium white control surface for calibration-heavy product software where pixel glyphs behave like precise signal punctuation, not nostalgia. Indigo anchors structure, cyan describes live surfaces, and a restrained lime pulse marks only decisive state changes.
## 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": "#C8FF2E",
"background": "#F8FAF7",
"border": "#C9D8E8",
"error": "#C7325F",
"info": "#008FCB",
"muted": "#6B7280",
"primary": "#2437A8",
"secondary": "#00AFC7",
"success": "#0EAD69",
"surface": "#FFFFFF",
"text": "#111827",
"warning": "#D6A100"
}
Typography:
{
"base_size": "16px",
"body_font": "Hanken Grotesk",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Hanken+Grotesk:wght@400;500;600;700;800&family=Spline+Sans+Mono:wght@400;500;600;700&display=swap",
"heading_font": "Hanken Grotesk",
"letter_spacing": "-0.02em",
"line_height": 1.5,
"mono_font": "Spline Sans Mono",
"scale_ratio": 1.24
}
## Visual character to preserve
- Large white and warm-neutral canvases use soft translucent panels, 1px blue-tinted borders, and broad whitespace rather than textured or gridded backgrounds.
- Indigo header blocks and cyan hairline dividers form stepped control bands with rounded-rectangle geometry and no one-sided color rails.
- Tiny pixel glyph clusters appear inside badges, toggles, and status chips as 2px square CSS blocks that signal mode, lock, or sync state.
- Pixel-influenced mono labels are uppercase, tightly spaced, and limited to counters, coordinates, badges, and annotations while body copy stays smooth and readable.
- Neon lime is reserved for small active apertures, focus rings, and confirmation pulses so vivid color carries state instead of decoration.
## ShadSync visual profile
{
"family": "system",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": true,
"stickerBadges": true,
"motion": "still",
"density": "balanced",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
}
## Signature component recipes
### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.
### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.
### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.
### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.
### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.
## Preview shots
- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.
## Implementation contract
- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/lumen-pixel-control-surface/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 lime only for active, confirmed, focused, or ready-to-run states.; Keep pixel typography in labels, counters, badges, coordinates, and short annotations while using readable grotesk body text.; Let indigo and cyan provide structure through headers, dividers, outlines, and data visualizations on clean neutral surfaces.; Style every form control with the same aperture, border, and pixel-state grammar.
- Do not: Do not use square-grid or dotted backgrounds as default texture.; Do not add side rails, left stripes, chipped corners, uneven borders, or decorative card bars.; Do not turn the system into a retro terminal, arcade screen, hacker UI, or Minecraft/block overload.; Do not add rainbow status colors or warm accents except semantic error/warning tokens.
## 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 LumenPixelControlSurfaceShadcnKit() {
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 Control Surface</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 with max content width 1320px",
"grid": "A responsive 12-column product surface where the main control panel spans seven to eight columns, the decision stack spans four, and mobile collapses into a single ordered instrument feed.",
"whitespace": "Use 64px outer air on desktop, 32px between major zones, 16px within panels, and 4-8px inside pixel badges to create strong proximity hierarchy."
}
{
"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-17b7-73e0-9256-a1ca97bf6a51",
"name": "Lumen Pixel Control Surface",
"slug": "lumen-pixel-control-surface"
},
"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": [
"Large white and warm-neutral canvases use soft translucent panels, 1px blue-tinted borders, and broad whitespace rather than textured or gridded backgrounds.",
"Indigo header blocks and cyan hairline dividers form stepped control bands with rounded-rectangle geometry and no one-sided color rails.",
"Tiny pixel glyph clusters appear inside badges, toggles, and status chips as 2px square CSS blocks that signal mode, lock, or sync state.",
"Pixel-influenced mono labels are uppercase, tightly spaced, and limited to counters, coordinates, badges, and annotations while body copy stays smooth and readable.",
"Neon lime is reserved for small active apertures, focus rings, and confirmation pulses so vivid color carries state instead of decoration."
],
"visualProfile": {
"family": "system",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": true,
"stickerBadges": true,
"motion": "still",
"density": "balanced",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "Lumen Pixel Control Surface 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 lime only for active, confirmed, focused, or ready-to-run states.",
"Keep pixel typography in labels, counters, badges, coordinates, and short annotations while using readable grotesk body text.",
"Let indigo and cyan provide structure through headers, dividers, outlines, and data visualizations on clean neutral surfaces.",
"Style every form control with the same aperture, border, and pixel-state grammar."
],
"dont": [
"Do not use square-grid or dotted backgrounds as default texture.",
"Do not add side rails, left stripes, chipped corners, uneven borders, or decorative card bars.",
"Do not turn the system into a retro terminal, arcade screen, hacker UI, or Minecraft/block overload.",
"Do not add rainbow status colors or warm accents except semantic error/warning tokens."
]
}
}