Phosphor Command Grid
A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.
Download DESIGN.md
Portable DESIGN.md source of truth for most agents and apps.
specification
philosophy
tokens
borders4 items
- accent width
- 4px
- character
- phosphor green outlines with amber command headers for intervention states
- default width
- 2px
- style
- solid with stepped pixel corner notches
colors12 items
motion3 items
- duration
- 90ms
- easing
- steps(2, end)
- philosophy
- state changes snap in two-frame terminal ticks; hover inverts phosphor and off-black without fades
radii5 items
- full
- 0
- lg
- 0
- md
- 0
- none
- 0
- sm
- 0
shadows3 items
- lg
- 0 0 0 2px rgba(246,179,59,0.55), 0 0 30px rgba(57,255,136,0.14)
- md
- 0 0 0 2px rgba(57,255,136,0.45), 0 0 18px rgba(57,255,136,0.10)
- sm
- 0 0 0 1px rgba(57,255,136,0.35)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- fixed orthogonal 8px grid plus horizontal CRT scanlines at 3px cadence
- card style
- square bordered terminal slabs, no elevation, content clipped to hard row modules
- treatment
- off-black panels with visible scanline and 8px bitmap-grid overlays
typography8 items
- base size
- 16px
- body font
- IBM Plex Mono
- google fonts url
- https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600;700&family=Space+Mono:wght@400;700&display=swap
- heading font
- Space Mono
- letter spacing
- 0.01em
- line height
- 1.42
- mono font
- IBM Plex Mono
- scale ratio
- 1.2
rules
Use one dominant command surface occupying at least half the viewport, supported by a narrow left rail and a right diagnostic stack; avoid equal-card dashboards by making the active operations map the spatial anchor.
High-density by default: tight row heights, 8px cell units, and large separations only between command zones, not within related evidence groups.
Headlines are command banners, second-level labels are bracketed uppercase codes, and body content is arranged in dense rows with amber reserved only for operator interventions and warnings.
layout
Mobile collapses rail into a top command strip, diagnostic cards stack below the operation map, and matrix cells reduce from 16px to 10px.
Desktop uses a 72px left command rail, a 12-column 8px-based work grid, and a 360px diagnostic column locked to square terminal slabs.
Whitespace is tactical: 4-8px within rows, 16-24px between related panels, and 64px only around the main command surface to create scale contrast.
guidance
- Use amber for the single current intervention or destructive confirmation, not as general decoration.
- Build data visualizations from visible cells, stepped bars, row rules, and command labels.
- Keep all radii square and let borders, not shadows, distinguish active surfaces.
- Write real operational labels with codes, timestamps, and measurable states.
- Do not add neon gradients, glass blur, rounded pills, or sci-fi illustration.
- Do not turn the screen into a generic admin dashboard or component inventory.
- Do not use many status colors when phosphor, amber, and off-black can carry hierarchy.
- Do not soften the monospace density with oversized whitespace inside data groups.
katagami spec
# Phosphor Command Grid ## Philosophy A terminal-brutalist language for operational interfaces where every surface behaves like a raw command grid: phosphor status lines, amber interventions, off-black voids, bitmap dividers, and dense monospace evidence panels build authority without nostalgia cosplay. ### Values - Operational truth over decorative polish - Hard-edged hierarchy built from rows, ticks, and command prompts - Low-resolution texture used as structure, not ornament - High-contrast restraint with a narrow phosphor and amber signal palette ### Anti-Values - Glossy cyberpunk gradients or arcade nostalgia that obscures product state - Rounded SaaS cards, soft shadows, and friendly illustrations - Semantic rainbow status systems that replace the core terminal grammar ### Visual Character - All primary containers use square 0px radii, 2px phosphor borders, and inset one-pixel grid seams drawn with repeating-linear-gradient backgrounds. - Navigation, labels, and metadata render in uppercase monospace with bracketed command prefixes such as [SYS], > RUN, and :: ACK to create interface rhythm. - The page background is off-black with a fixed 8px bitmap grid and subtle CRT scanlines layered through CSS pseudo-elements. - Hierarchy is created by amber block headers, phosphor outlines, and dense row separators rather than elevation, blur, or rounded cards. - Charts and maps are built from pixel-cell matrices, stepped bars, and dithered masks so data feels assembled from low-resolution tiles. ## Tokens ### Borders - **Accent Width**: 4px - **Character**: phosphor green outlines with amber command headers for intervention states - **Default Width**: 2px - **Style**: solid with stepped pixel corner notches ### Colors | Name | Value | |------|-------| | accent | `#D8FF6A` | | background | `#050706` | | border | `#2BD66F` | | error | `#FF5C49` | | info | `#6AD8FF` | | muted | `#6E8A76` | | primary | `#39FF88` | | secondary | `#F6B33B` | | success | `#39FF88` | | surface | `#0A0F0B` | | text | `#D8FFE5` | | warning | `#F6B33B` | ### Motion - **Duration**: 90ms - **Easing**: steps(2, end) - **Philosophy**: state changes snap in two-frame terminal ticks; hover inverts phosphor and off-black without fades ### Radii - **Full**: 0 - **Lg**: 0 - **Md**: 0 - **None**: 0 - **Sm**: 0 ### Shadows - **Lg**: 0 0 0 2px rgba(246,179,59,0.55), 0 0 30px rgba(57,255,136,0.14) - **Md**: 0 0 0 2px rgba(57,255,136,0.45), 0 0 18px rgba(57,255,136,0.10) - **Sm**: 0 0 0 1px rgba(57,255,136,0.35) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: fixed orthogonal 8px grid plus horizontal CRT scanlines at 3px cadence - **Card Style**: square bordered terminal slabs, no elevation, content clipped to hard row modules - **Treatment**: off-black panels with visible scanline and 8px bitmap-grid overlays ### Typography - **Base Size**: 16px - **Body Font**: IBM Plex Mono - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600;700&family=Space+Mono:wght@400;700&display=swap - **Heading Font**: Space Mono - **Letter Spacing**: 0.01em - **Line Height**: 1.42 - **Mono Font**: IBM Plex Mono - **Scale Ratio**: 1.2 ## Rules ### Composition Use one dominant command surface occupying at least half the viewport, supported by a narrow left rail and a right diagnostic stack; avoid equal-card dashboards by making the active operations map the spatial anchor. ### Density High-density by default: tight row heights, 8px cell units, and large separations only between command zones, not within related evidence groups. ### Hierarchy Headlines are command banners, second-level labels are bracketed uppercase codes, and body content is arranged in dense rows with amber reserved only for operator interventions and warnings. ### Signature Patterns - Bitmap matrix panels appear in maps, meters, and thumbnails using CSS grid cells with alternating phosphor opacity to create live low-resolution data surfaces. - Command-strip headers use amber block fills, black inset text, and left-side prompt glyphs to mark the one area requiring human action. - CRT underlay is implemented as layered repeating-linear-gradients on body and panels, visible but low contrast so it organizes surfaces without becoming texture noise. - Pixel notch borders cut the top-right or bottom-left corner of key panels with pseudo-elements, making every container feel machined from terminal tiles. - Interaction states use step-timed color inversion and outline thickening, never opacity fades, so controls behave like toggled console modes. ## Layout ### Breakpoints Mobile collapses rail into a top command strip, diagnostic cards stack below the operation map, and matrix cells reduce from 16px to 10px. ### Grid Desktop uses a 72px left command rail, a 12-column 8px-based work grid, and a 360px diagnostic column locked to square terminal slabs. ### Whitespace Whitespace is tactical: 4-8px within rows, 16-24px between related panels, and 64px only around the main command surface to create scale contrast. ## Guidance ### Do - Use amber for the single current intervention or destructive confirmation, not as general decoration. - Build data visualizations from visible cells, stepped bars, row rules, and command labels. - Keep all radii square and let borders, not shadows, distinguish active surfaces. - Write real operational labels with codes, timestamps, and measurable states. ### Don't - Do not add neon gradients, glass blur, rounded pills, or sci-fi illustration. - Do not turn the screen into a generic admin dashboard or component inventory. - Do not use many status colors when phosphor, amber, and off-black can carry hierarchy. - Do not soften the monospace density with oversized whitespace inside data groups.
DESIGN.md
---
version: "alpha"
name: "Phosphor Command Grid"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#D8FF6A"
background: "#050706"
border: "#2BD66F"
error: "#FF5C49"
info: "#6AD8FF"
muted: "#6E8A76"
primary: "#39FF88"
secondary: "#F6B33B"
success: "#39FF88"
surface: "#0A0F0B"
text: "#D8FFE5"
warning: "#F6B33B"
typography:
headline-lg:
fontFamily: "Space Mono"
fontSize: "1.728rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "0.01em"
headline-md:
fontFamily: "Space Mono"
fontSize: "1.44rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "0.01em"
body-md:
fontFamily: "IBM Plex Mono"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.42
letterSpacing: "0.01em"
label-md:
fontFamily: "IBM Plex Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "0px"
lg: "0px"
md: "0px"
none: "0px"
sm: "0px"
spacing:
base: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
components:
color-reference-accent:
backgroundColor: "{colors.accent}"
color-reference-background:
backgroundColor: "{colors.background}"
color-reference-border:
backgroundColor: "{colors.border}"
color-reference-error:
backgroundColor: "{colors.error}"
color-reference-info:
backgroundColor: "{colors.info}"
color-reference-muted:
backgroundColor: "{colors.muted}"
color-reference-primary:
backgroundColor: "{colors.primary}"
color-reference-secondary:
backgroundColor: "{colors.secondary}"
color-reference-success:
backgroundColor: "{colors.success}"
color-reference-surface:
backgroundColor: "{colors.surface}"
color-reference-text:
backgroundColor: "{colors.text}"
color-reference-warning:
backgroundColor: "{colors.warning}"
button-primary:
backgroundColor: "{colors.primary}"
textColor: "#000000"
typography: "{typography.label-md}"
rounded: "{rounded.md}"
padding: "{spacing.md}"
card-surface:
backgroundColor: "{colors.surface}"
textColor: "{colors.text}"
rounded: "{rounded.md}"
padding: "{spacing.md}"
input-default:
backgroundColor: "{colors.surface}"
textColor: "{colors.text}"
rounded: "{rounded.md}"
height: "44px"
---
# Phosphor Command Grid
## Overview
A terminal-brutalist language for operational interfaces where every surface behaves like a raw command grid: phosphor status lines, amber interventions, off-black voids, bitmap dividers, and dense monospace evidence panels build authority without nostalgia cosplay.
### Values
- Operational truth over decorative polish
- Hard-edged hierarchy built from rows, ticks, and command prompts
- Low-resolution texture used as structure, not ornament
- High-contrast restraint with a narrow phosphor and amber signal palette
### Anti-Values
- Glossy cyberpunk gradients or arcade nostalgia that obscures product state
- Rounded SaaS cards, soft shadows, and friendly illustrations
- Semantic rainbow status systems that replace the core terminal grammar
### Visual Character
- All primary containers use square 0px radii, 2px phosphor borders, and inset one-pixel grid seams drawn with repeating-linear-gradient backgrounds.
- Navigation, labels, and metadata render in uppercase monospace with bracketed command prefixes such as [SYS], > RUN, and :: ACK to create interface rhythm.
- The page background is off-black with a fixed 8px bitmap grid and subtle CRT scanlines layered through CSS pseudo-elements.
- Hierarchy is created by amber block headers, phosphor outlines, and dense row separators rather than elevation, blur, or rounded cards.
- Charts and maps are built from pixel-cell matrices, stepped bars, and dithered masks so data feels assembled from low-resolution tiles.
## 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 | `#D8FF6A` |
| background | `#050706` |
| border | `#2BD66F` |
| error | `#FF5C49` |
| info | `#6AD8FF` |
| muted | `#6E8A76` |
| primary | `#39FF88` |
| secondary | `#F6B33B` |
| success | `#39FF88` |
| surface | `#0A0F0B` |
| text | `#D8FFE5` |
| warning | `#F6B33B` |
## Typography
- **Headline-Lg**: Space Mono, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Space Mono, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Mono, 16px, weight 400, line-height 1.42.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
### Breakpoints
Mobile collapses rail into a top command strip, diagnostic cards stack below the operation map, and matrix cells reduce from 16px to 10px.
### Grid
Desktop uses a 72px left command rail, a 12-column 8px-based work grid, and a 360px diagnostic column locked to square terminal slabs.
### Whitespace
Whitespace is tactical: 4-8px within rows, 16-24px between related panels, and 64px only around the main command surface to create scale contrast.
## Elevation & Depth
### Shadows
- **Lg**: 0 0 0 2px rgba(246,179,59,0.55), 0 0 30px rgba(57,255,136,0.14)
- **Md**: 0 0 0 2px rgba(57,255,136,0.45), 0 0 18px rgba(57,255,136,0.10)
- **Sm**: 0 0 0 1px rgba(57,255,136,0.35)
## Shapes
### Rounded
- **Full**: `0px`
- **Lg**: `0px`
- **Md**: `0px`
- **None**: `0px`
- **Sm**: `0px`
### Surfaces
- **Bg Pattern**: fixed orthogonal 8px grid plus horizontal CRT scanlines at 3px cadence
- **Card Style**: square bordered terminal slabs, no elevation, content clipped to hard row modules
- **Treatment**: off-black panels with visible scanline and 8px bitmap-grid overlays
### Borders
- **Accent Width**: 4px
- **Character**: phosphor green outlines with amber command headers for intervention states
- **Default Width**: 2px
- **Style**: solid with stepped pixel corner notches
## Components
### Composition
Use one dominant command surface occupying at least half the viewport, supported by a narrow left rail and a right diagnostic stack; avoid equal-card dashboards by making the active operations map the spatial anchor.
### Density
High-density by default: tight row heights, 8px cell units, and large separations only between command zones, not within related evidence groups.
### Hierarchy
Headlines are command banners, second-level labels are bracketed uppercase codes, and body content is arranged in dense rows with amber reserved only for operator interventions and warnings.
### Signature Patterns
- Bitmap matrix panels appear in maps, meters, and thumbnails using CSS grid cells with alternating phosphor opacity to create live low-resolution data surfaces.
- Command-strip headers use amber block fills, black inset text, and left-side prompt glyphs to mark the one area requiring human action.
- CRT underlay is implemented as layered repeating-linear-gradients on body and panels, visible but low contrast so it organizes surfaces without becoming texture noise.
- Pixel notch borders cut the top-right or bottom-left corner of key panels with pseudo-elements, making every container feel machined from terminal tiles.
- Interaction states use step-timed color inversion and outline thickening, never opacity fades, so controls behave like toggled console modes.
## 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-019e69a6-5032-76c3-82bb-3318dfe41ae0/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 amber for the single current intervention or destructive confirmation, not as general decoration.
- Do Build data visualizations from visible cells, stepped bars, row rules, and command labels.
- Do Keep all radii square and let borders, not shadows, distinguish active surfaces.
- Do Write real operational labels with codes, timestamps, and measurable states.
- Don't Do not add neon gradients, glass blur, rounded pills, or sci-fi illustration.
- Don't Do not turn the screen into a generic admin dashboard or component inventory.
- Don't Do not use many status colors when phosphor, amber, and off-black can carry hierarchy.
- Don't Do not soften the monospace density with oversized whitespace inside data groups.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "phosphor-command-grid",
"type": "registry:theme",
"title": "Phosphor Command Grid shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#050706",
"foreground": "#D8FFE5",
"card": "#0A0F0B",
"card-foreground": "#D8FFE5",
"popover": "#0A0F0B",
"popover-foreground": "#D8FFE5",
"primary": "#39FF88",
"primary-foreground": "#111111",
"secondary": "#F6B33B",
"secondary-foreground": "#ffffff",
"muted": "#6E8A76",
"muted-foreground": "#D8FFE5",
"accent": "#D8FF6A",
"accent-foreground": "#111111",
"destructive": "#FF5C49",
"border": "#2BD66F",
"input": "#2BD66F",
"ring": "#D8FF6A",
"chart-1": "#39FF88",
"chart-2": "#F6B33B",
"chart-3": "#D8FF6A",
"chart-4": "#39FF88",
"chart-5": "#F6B33B",
"sidebar": "#0A0F0B",
"sidebar-foreground": "#D8FFE5",
"sidebar-primary": "#39FF88",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#6AD8FF",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#2BD66F",
"sidebar-ring": "#D8FF6A",
"radius": "0"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#39FF88",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#D8FF6A",
"accent-foreground": "#111111",
"destructive": "#FF5C49",
"border": "#303642",
"input": "#303642",
"ring": "#D8FF6A",
"chart-1": "#39FF88",
"chart-2": "#F6B33B",
"chart-3": "#D8FF6A",
"chart-4": "#39FF88",
"chart-5": "#F6B33B",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#39FF88",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#D8FF6A",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#D8FF6A",
"radius": "0"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e69a6-5032-76c3-82bb-3318dfe41ae0",
"slug": "phosphor-command-grid",
"componentManifest": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"nativeTokenNames": {
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"colors": [
"accent",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"motion": [
"duration",
"easing",
"philosophy"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"spacing": [
"base",
"scale"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
]
}
}
}
```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: #050706;
--foreground: #D8FFE5;
--card: #0A0F0B;
--card-foreground: #D8FFE5;
--popover: #0A0F0B;
--popover-foreground: #D8FFE5;
--primary: #39FF88;
--primary-foreground: #111111;
--secondary: #F6B33B;
--secondary-foreground: #ffffff;
--muted: #6E8A76;
--muted-foreground: #D8FFE5;
--accent: #D8FF6A;
--accent-foreground: #111111;
--destructive: #FF5C49;
--border: #2BD66F;
--input: #2BD66F;
--ring: #D8FF6A;
--chart-1: #39FF88;
--chart-2: #F6B33B;
--chart-3: #D8FF6A;
--chart-4: #39FF88;
--chart-5: #F6B33B;
--sidebar: #0A0F0B;
--sidebar-foreground: #D8FFE5;
--sidebar-primary: #39FF88;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #6AD8FF;
--sidebar-accent-foreground: #111111;
--sidebar-border: #2BD66F;
--sidebar-ring: #D8FF6A;
--radius: 0;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #39FF88;
--primary-foreground: #111111;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #D8FF6A;
--accent-foreground: #111111;
--destructive: #FF5C49;
--border: #303642;
--input: #303642;
--ring: #D8FF6A;
--chart-1: #39FF88;
--chart-2: #F6B33B;
--chart-3: #D8FF6A;
--chart-4: #39FF88;
--chart-5: #F6B33B;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #39FF88;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #D8FF6A;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #D8FF6A;
--radius: 0;
}
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
Card,
CardContent,
CardDescription,
CardFooter,
CardHeader,
CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";
export function PhosphorCommandGridShadcnKit() {
return (
<section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
<div className="flex items-start justify-between gap-4">
<div>
<Badge variant="outline">shadcn/ui</Badge>
<h2 className="mt-3 text-2xl font-semibold tracking-tight">Phosphor Command Grid</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "phosphor-command-grid",
"type": "registry:theme",
"title": "Phosphor Command Grid shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#050706",
"foreground": "#D8FFE5",
"card": "#0A0F0B",
"card-foreground": "#D8FFE5",
"popover": "#0A0F0B",
"popover-foreground": "#D8FFE5",
"primary": "#39FF88",
"primary-foreground": "#111111",
"secondary": "#F6B33B",
"secondary-foreground": "#ffffff",
"muted": "#6E8A76",
"muted-foreground": "#D8FFE5",
"accent": "#D8FF6A",
"accent-foreground": "#111111",
"destructive": "#FF5C49",
"border": "#2BD66F",
"input": "#2BD66F",
"ring": "#D8FF6A",
"chart-1": "#39FF88",
"chart-2": "#F6B33B",
"chart-3": "#D8FF6A",
"chart-4": "#39FF88",
"chart-5": "#F6B33B",
"sidebar": "#0A0F0B",
"sidebar-foreground": "#D8FFE5",
"sidebar-primary": "#39FF88",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#6AD8FF",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#2BD66F",
"sidebar-ring": "#D8FF6A",
"radius": "0"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#39FF88",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#D8FF6A",
"accent-foreground": "#111111",
"destructive": "#FF5C49",
"border": "#303642",
"input": "#303642",
"ring": "#D8FF6A",
"chart-1": "#39FF88",
"chart-2": "#F6B33B",
"chart-3": "#D8FF6A",
"chart-4": "#39FF88",
"chart-5": "#F6B33B",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#39FF88",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#D8FF6A",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#D8FF6A",
"radius": "0"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e69a6-5032-76c3-82bb-3318dfe41ae0",
"slug": "phosphor-command-grid",
"componentManifest": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"nativeTokenNames": {
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"colors": [
"accent",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"motion": [
"duration",
"easing",
"philosophy"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"spacing": [
"base",
"scale"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
]
}
}
}
# Phosphor Command Grid shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e69a6-5032-76c3-82bb-3318dfe41ae0`
Slug: `phosphor-command-grid`
## Intent
A terminal-brutalist language for operational interfaces where every surface behaves like a raw command grid: phosphor status lines, amber interventions, off-black voids, bitmap dividers, and dense monospace evidence panels build authority without nostalgia cosplay.
## 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": "#D8FF6A",
"background": "#050706",
"border": "#2BD66F",
"error": "#FF5C49",
"info": "#6AD8FF",
"muted": "#6E8A76",
"primary": "#39FF88",
"secondary": "#F6B33B",
"success": "#39FF88",
"surface": "#0A0F0B",
"text": "#D8FFE5",
"warning": "#F6B33B"
}
Typography:
{
"base_size": "16px",
"body_font": "IBM Plex Mono",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600;700&family=Space+Mono:wght@400;700&display=swap",
"heading_font": "Space Mono",
"letter_spacing": "0.01em",
"line_height": 1.42,
"mono_font": "IBM Plex Mono",
"scale_ratio": 1.2
}
## Visual character to preserve
- All primary containers use square 0px radii, 2px phosphor borders, and inset one-pixel grid seams drawn with repeating-linear-gradient backgrounds.
- Navigation, labels, and metadata render in uppercase monospace with bracketed command prefixes such as [SYS], > RUN, and :: ACK to create interface rhythm.
- The page background is off-black with a fixed 8px bitmap grid and subtle CRT scanlines layered through CSS pseudo-elements.
- Hierarchy is created by amber block headers, phosphor outlines, and dense row separators rather than elevation, blur, or rounded cards.
- Charts and maps are built from pixel-cell matrices, stepped bars, and dithered masks so data feels assembled from low-resolution tiles.
## ShadSync visual profile
{
"family": "brutalist",
"material": "ink",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": false,
"motion": "still",
"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/phosphor-command-grid/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use amber for the single current intervention or destructive confirmation, not as general decoration.; Build data visualizations from visible cells, stepped bars, row rules, and command labels.; Keep all radii square and let borders, not shadows, distinguish active surfaces.; Write real operational labels with codes, timestamps, and measurable states.
- Do not: Do not add neon gradients, glass blur, rounded pills, or sci-fi illustration.; Do not turn the screen into a generic admin dashboard or component inventory.; Do not use many status colors when phosphor, amber, and off-black can carry hierarchy.; Do not soften the monospace density with oversized whitespace inside data groups.
## Copy-paste component example
This generated starter proves the import shape. Production Katagami agents should replace it with a language-specific product composition.
```tsx
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
Card,
CardContent,
CardDescription,
CardFooter,
CardHeader,
CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";
export function PhosphorCommandGridShadcnKit() {
return (
<section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
<div className="flex items-start justify-between gap-4">
<div>
<Badge variant="outline">shadcn/ui</Badge>
<h2 className="mt-3 text-2xl font-semibold tracking-tight">Phosphor Command Grid</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
```
## Layout notes
{
"breakpoints": "Mobile collapses rail into a top command strip, diagnostic cards stack below the operation map, and matrix cells reduce from 16px to 10px.",
"grid": "Desktop uses a 72px left command rail, a 12-column 8px-based work grid, and a 360px diagnostic column locked to square terminal slabs.",
"whitespace": "Whitespace is tactical: 4-8px within rows, 16-24px between related panels, and 64px only around the main command surface to create scale contrast."
}
{
"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-019e69a6-5032-76c3-82bb-3318dfe41ae0",
"name": "Phosphor Command Grid",
"slug": "phosphor-command-grid"
},
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"primitives": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"identityNotes": [
"All primary containers use square 0px radii, 2px phosphor borders, and inset one-pixel grid seams drawn with repeating-linear-gradient backgrounds.",
"Navigation, labels, and metadata render in uppercase monospace with bracketed command prefixes such as [SYS], > RUN, and :: ACK to create interface rhythm.",
"The page background is off-black with a fixed 8px bitmap grid and subtle CRT scanlines layered through CSS pseudo-elements.",
"Hierarchy is created by amber block headers, phosphor outlines, and dense row separators rather than elevation, blur, or rounded cards.",
"Charts and maps are built from pixel-cell matrices, stepped bars, and dithered masks so data feels assembled from low-resolution tiles."
],
"visualProfile": {
"family": "brutalist",
"material": "ink",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": false,
"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": "Phosphor Command Grid launch room",
"description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
"primaryAction": "Apply theme",
"secondaryAction": "Review states",
"stats": [
{
"label": "components",
"value": "16",
"tone": "accent"
},
{
"label": "states",
"value": "ready"
},
{
"label": "density",
"value": "balanced",
"tone": "warning"
}
],
"rows": [
{
"label": "Primary flow",
"value": "mapped",
"status": "active"
},
{
"label": "Token coverage",
"value": "semantic",
"status": "synced"
},
{
"label": "Responsive proof",
"value": "queued",
"status": "review"
}
],
"statuses": [
"Active",
"Synced",
"Draft"
]
}
},
{
"id": "detail-editor",
"title": "Detail editor",
"viewport": "tablet",
"primitives": [
"button",
"card",
"input",
"textarea",
"select",
"checkbox",
"switch",
"slider",
"dialog",
"sheet"
],
"composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
"mustShow": [
"focus ring",
"error or destructive state",
"dialog or sheet treatment",
"written guidance content"
],
"avoid": [
"unstyled browser controls",
"floating cards inside cards",
"missing labels"
],
"scene": {
"eyebrow": "editing flow",
"headline": "Language recipe editor",
"description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
"primaryAction": "Save recipe",
"secondaryAction": "Open sheet",
"fields": [
{
"label": "Component family",
"value": "Narrative cards"
},
{
"label": "State treatment",
"value": "Visible focus + validation"
},
{
"label": "Motion",
"value": "Small lift, no opacity-only fade"
}
],
"statuses": [
"Focus",
"Invalid",
"Confirmed"
]
}
},
{
"id": "data-operations",
"title": "Data operations",
"viewport": "mobile",
"primitives": [
"button",
"tabs",
"badge",
"dropdown-menu",
"table",
"tooltip",
"separator"
],
"composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
"mustShow": [
"responsive reflow",
"dense row styling",
"menu affordance",
"status badge system"
],
"avoid": [
"desktop-only tables",
"text overflow",
"default shadcn spacing without Katagami character"
],
"scene": {
"eyebrow": "operations",
"headline": "Compact review queue",
"description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
"primaryAction": "Resolve",
"secondaryAction": "Filter",
"rows": [
{
"label": "Button hierarchy",
"value": "approved",
"status": "ok"
},
{
"label": "Table rhythm",
"value": "needs pass",
"status": "watch"
},
{
"label": "Empty state",
"value": "designed",
"status": "done"
}
],
"statuses": [
"Queued",
"Blocked",
"Done"
]
}
}
],
"componentRecipes": [
{
"primitive": "button",
"intent": "Prove action hierarchy, focus, disabled, and destructive states."
},
{
"primitive": "card",
"intent": "Carry the language surface, border, elevation, and density rules."
},
{
"primitive": "input",
"intent": "Show labels, focus rings, validation, and spacing rhythm."
},
{
"primitive": "textarea",
"intent": "Show longer guidance, validation copy, and writing density."
},
{
"primitive": "select",
"intent": "Show filtering, selection contrast, and menu trigger styling."
},
{
"primitive": "dialog",
"intent": "Show centered decision states and overlay treatment."
},
{
"primitive": "sheet",
"intent": "Show contextual side panels and responsive editing."
},
{
"primitive": "tabs",
"intent": "Show navigational structure and active/inactive contrast."
},
{
"primitive": "badge",
"intent": "Show compact status vocabulary and semantic colors."
},
{
"primitive": "separator",
"intent": "Show section rhythm without generic gray dividers."
},
{
"primitive": "checkbox",
"intent": "Show binary selection with visible focus and checked states."
},
{
"primitive": "switch",
"intent": "Show settings toggles and on/off contrast."
},
{
"primitive": "slider",
"intent": "Show numeric adjustment with track/thumb styling."
},
{
"primitive": "tooltip",
"intent": "Show concise explanation styling above compact controls."
},
{
"primitive": "dropdown-menu",
"intent": "Show action menus, destructive items, and grouped choices."
},
{
"primitive": "table",
"intent": "Show dense operational data, separators, row states, and responsive behavior."
}
],
"qualityRules": {
"do": [
"Use amber for the single current intervention or destructive confirmation, not as general decoration.",
"Build data visualizations from visible cells, stepped bars, row rules, and command labels.",
"Keep all radii square and let borders, not shadows, distinguish active surfaces.",
"Write real operational labels with codes, timestamps, and measurable states."
],
"dont": [
"Do not add neon gradients, glass blur, rounded pills, or sci-fi illustration.",
"Do not turn the screen into a generic admin dashboard or component inventory.",
"Do not use many status colors when phosphor, amber, and off-black can carry hierarchy.",
"Do not soften the monospace density with oversized whitespace inside data groups."
]
}
}