Terminal Brutalist Interface
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
- hard square phosphor strokes, never rounded, with amber warning edges only on active risk states
- default width
- 1px
- style
- solid with bracket-corner pseudo-elements
colors12 items
motion3 items
- duration
- 90ms
- easing
- steps(2, end)
- philosophy
- state changes snap in two-step terminal ticks; hover inverts cells or advances a caret instead of fading
radii5 items
- full
- 0
- lg
- 0
- md
- 0
- none
- 0
- sm
- 0
shadows3 items
- lg
- 0 0 0 1px rgba(245,166,35,0.42), 0 0 32px rgba(57,255,136,0.13)
- md
- 0 0 0 1px rgba(57,255,136,0.36), 0 0 18px rgba(57,255,136,0.10)
- sm
- 0 0 0 1px rgba(57,255,136,0.24)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- 8px repeating bitmap grid plus faint horizontal CRT scanlines
- card style
- square command panels with 1px phosphor borders, amber header strips, clipped bracket corners
- treatment
- matte off-black CRT glass with visible scanline and pixel-dot 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=Share+Tech+Mono&display=swap
- heading font
- Share Tech Mono
- letter spacing
- -0.01em
- line height
- 1.45
- mono font
- IBM Plex Mono
- scale ratio
- 1.2
rules
Organize screens as command-line workbenches: a fixed left rail, dominant event log or map artifact, right diagnostics stack, and dense footer prompt sharing one 8px ruler grid.
High density is intentional: compact rows, narrow gutters, and many small readouts are acceptable when aligned to the grid and separated by ASCII-like rules.
The largest element is always an active command or system state; amber labels name mode and risk, phosphor green carries actionable data, muted coordinates recede as machine context.
layout
desktop >=1200 uses rail/log/diagnostics; tablet 768-1199 stacks diagnostics below the log; mobile <640 collapses to prompt tabs and single-column panels.
8px base grid with 16-column desktop command layout, square modules, fixed-width log columns, and no off-grid decorative placement.
Whitespace is scarce but exact: outer margins use 24px desktop and 12px mobile, with empty space reserved for command focus rather than comfort.
guidance
- Use square cells, row numbers, command paths, and visible rulers to make hierarchy structural.
- Keep palette disciplined: off-black base, phosphor green primary, amber caution, and minimal semantic exceptions.
- Let interactions snap, invert, or move a caret so states feel terminal-native.
- Use dense real product data such as logs, coordinates, packet counts, and operator notes.
- Do not add rounded cards, glassmorphism, pastel gradients, or friendly illustration.
- Do not use pixel art as loose decoration without affecting controls, navigation, or data states.
- Do not spread many accent colors across the interface; reserve color for command meaning.
- Do not make the embodiment a component inventory instead of a plausible operations screen.
katagami spec
# Terminal Brutalist Interface ## Philosophy Terminal Brutalist Interface treats the screen as an exposed operations console: off-black space, phosphor green commands, amber warnings, monospace rows, hard rectangular cells, and raw pixel-grid evidence replace decorative polish. ### Values - Operational legibility under pressure - Raw system truth over lifestyle warmth - Low-resolution structure used as hierarchy - Every accent has a state or command purpose ### Anti-Values - Rounded SaaS softness and gradient ambience - Retro nostalgia that stops at surface decoration - Status colors used without structural grid behavior ### Visual Character - Use a global 8px bitmap grid with repeating-linear-gradient scanlines and square module placement for all panels, gutters, and data rows. - Build every surface from flat off-black rectangles with one-pixel phosphor borders, no radius, no blur, and inset terminal command bars. - Set hierarchy through monospace type contrast: large compressed command headings, amber uppercase labels, green body rows, and dim ghost coordinates. - Render status and focus as pixel blocks, bracket corners, caret glyphs, and inverted cells rather than soft shadows or rounded pills. - Use dense table-like composition with fixed-width code columns, ruler ticks, ASCII separators, and CRT phosphor noise as the only texture. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: hard square phosphor strokes, never rounded, with amber warning edges only on active risk states - **Default Width**: 1px - **Style**: solid with bracket-corner pseudo-elements ### Colors | Name | Value | |------|-------| | accent | `#B9FF5A` | | background | `#060807` | | border | `#1F5F3B` | | error | `#FF4D3D` | | info | `#63D7FF` | | muted | `#617263` | | primary | `#39FF88` | | secondary | `#F5A623` | | success | `#39FF88` | | surface | `#0B100D` | | text | `#D8FFE7` | | warning | `#F5A623` | ### Motion - **Duration**: 90ms - **Easing**: steps(2, end) - **Philosophy**: state changes snap in two-step terminal ticks; hover inverts cells or advances a caret instead of fading ### Radii - **Full**: 0 - **Lg**: 0 - **Md**: 0 - **None**: 0 - **Sm**: 0 ### Shadows - **Lg**: 0 0 0 1px rgba(245,166,35,0.42), 0 0 32px rgba(57,255,136,0.13) - **Md**: 0 0 0 1px rgba(57,255,136,0.36), 0 0 18px rgba(57,255,136,0.10) - **Sm**: 0 0 0 1px rgba(57,255,136,0.24) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: 8px repeating bitmap grid plus faint horizontal CRT scanlines - **Card Style**: square command panels with 1px phosphor borders, amber header strips, clipped bracket corners - **Treatment**: matte off-black CRT glass with visible scanline and pixel-dot 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=Share+Tech+Mono&display=swap - **Heading Font**: Share Tech Mono - **Letter Spacing**: -0.01em - **Line Height**: 1.45 - **Mono Font**: IBM Plex Mono - **Scale Ratio**: 1.2 ## Rules ### Composition Organize screens as command-line workbenches: a fixed left rail, dominant event log or map artifact, right diagnostics stack, and dense footer prompt sharing one 8px ruler grid. ### Density High density is intentional: compact rows, narrow gutters, and many small readouts are acceptable when aligned to the grid and separated by ASCII-like rules. ### Hierarchy The largest element is always an active command or system state; amber labels name mode and risk, phosphor green carries actionable data, muted coordinates recede as machine context. ### Signature Patterns - Bracket-corner panels appear on primary cards and selected rows; active panels add amber corner blocks to announce command focus. - Pixel raster underlays appear behind maps, charts, and hero regions; the grid brightens only under selected cells to create hierarchy. - Command prompt strips anchor headers, forms, and dialogs with a leading caret, uppercase command path, and blinking block cursor. - Status badges use inverted monospace cells with two-character codes and square dividers, changing color only for semantic machine states. - Tables and cards include ruler ticks, row numbers, and ASCII separators so data feels inspected rather than merely displayed. ## Layout ### Breakpoints desktop >=1200 uses rail/log/diagnostics; tablet 768-1199 stacks diagnostics below the log; mobile <640 collapses to prompt tabs and single-column panels. ### Grid 8px base grid with 16-column desktop command layout, square modules, fixed-width log columns, and no off-grid decorative placement. ### Whitespace Whitespace is scarce but exact: outer margins use 24px desktop and 12px mobile, with empty space reserved for command focus rather than comfort. ## Guidance ### Do - Use square cells, row numbers, command paths, and visible rulers to make hierarchy structural. - Keep palette disciplined: off-black base, phosphor green primary, amber caution, and minimal semantic exceptions. - Let interactions snap, invert, or move a caret so states feel terminal-native. - Use dense real product data such as logs, coordinates, packet counts, and operator notes. ### Don't - Do not add rounded cards, glassmorphism, pastel gradients, or friendly illustration. - Do not use pixel art as loose decoration without affecting controls, navigation, or data states. - Do not spread many accent colors across the interface; reserve color for command meaning. - Do not make the embodiment a component inventory instead of a plausible operations screen.
DESIGN.md
---
version: "alpha"
name: "Terminal Brutalist Interface"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#B9FF5A"
background: "#060807"
border: "#1F5F3B"
error: "#FF4D3D"
info: "#63D7FF"
muted: "#617263"
primary: "#39FF88"
secondary: "#F5A623"
success: "#39FF88"
surface: "#0B100D"
text: "#D8FFE7"
warning: "#F5A623"
typography:
headline-lg:
fontFamily: "Share Tech Mono"
fontSize: "1.728rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.01em"
headline-md:
fontFamily: "Share Tech Mono"
fontSize: "1.44rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.01em"
body-md:
fontFamily: "IBM Plex Mono"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.45
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"
---
# Terminal Brutalist Interface
## Overview
Terminal Brutalist Interface treats the screen as an exposed operations console: off-black space, phosphor green commands, amber warnings, monospace rows, hard rectangular cells, and raw pixel-grid evidence replace decorative polish.
### Values
- Operational legibility under pressure
- Raw system truth over lifestyle warmth
- Low-resolution structure used as hierarchy
- Every accent has a state or command purpose
### Anti-Values
- Rounded SaaS softness and gradient ambience
- Retro nostalgia that stops at surface decoration
- Status colors used without structural grid behavior
### Visual Character
- Use a global 8px bitmap grid with repeating-linear-gradient scanlines and square module placement for all panels, gutters, and data rows.
- Build every surface from flat off-black rectangles with one-pixel phosphor borders, no radius, no blur, and inset terminal command bars.
- Set hierarchy through monospace type contrast: large compressed command headings, amber uppercase labels, green body rows, and dim ghost coordinates.
- Render status and focus as pixel blocks, bracket corners, caret glyphs, and inverted cells rather than soft shadows or rounded pills.
- Use dense table-like composition with fixed-width code columns, ruler ticks, ASCII separators, and CRT phosphor noise as the only texture.
## 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 | `#B9FF5A` |
| background | `#060807` |
| border | `#1F5F3B` |
| error | `#FF4D3D` |
| info | `#63D7FF` |
| muted | `#617263` |
| primary | `#39FF88` |
| secondary | `#F5A623` |
| success | `#39FF88` |
| surface | `#0B100D` |
| text | `#D8FFE7` |
| warning | `#F5A623` |
## Typography
- **Headline-Lg**: Share Tech Mono, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Share Tech Mono, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Mono, 16px, weight 400, line-height 1.45.
- **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
desktop >=1200 uses rail/log/diagnostics; tablet 768-1199 stacks diagnostics below the log; mobile <640 collapses to prompt tabs and single-column panels.
### Grid
8px base grid with 16-column desktop command layout, square modules, fixed-width log columns, and no off-grid decorative placement.
### Whitespace
Whitespace is scarce but exact: outer margins use 24px desktop and 12px mobile, with empty space reserved for command focus rather than comfort.
## Elevation & Depth
### Shadows
- **Lg**: 0 0 0 1px rgba(245,166,35,0.42), 0 0 32px rgba(57,255,136,0.13)
- **Md**: 0 0 0 1px rgba(57,255,136,0.36), 0 0 18px rgba(57,255,136,0.10)
- **Sm**: 0 0 0 1px rgba(57,255,136,0.24)
## Shapes
### Rounded
- **Full**: `0px`
- **Lg**: `0px`
- **Md**: `0px`
- **None**: `0px`
- **Sm**: `0px`
### Surfaces
- **Bg Pattern**: 8px repeating bitmap grid plus faint horizontal CRT scanlines
- **Card Style**: square command panels with 1px phosphor borders, amber header strips, clipped bracket corners
- **Treatment**: matte off-black CRT glass with visible scanline and pixel-dot overlays
### Borders
- **Accent Width**: 2px
- **Character**: hard square phosphor strokes, never rounded, with amber warning edges only on active risk states
- **Default Width**: 1px
- **Style**: solid with bracket-corner pseudo-elements
## Components
### Composition
Organize screens as command-line workbenches: a fixed left rail, dominant event log or map artifact, right diagnostics stack, and dense footer prompt sharing one 8px ruler grid.
### Density
High density is intentional: compact rows, narrow gutters, and many small readouts are acceptable when aligned to the grid and separated by ASCII-like rules.
### Hierarchy
The largest element is always an active command or system state; amber labels name mode and risk, phosphor green carries actionable data, muted coordinates recede as machine context.
### Signature Patterns
- Bracket-corner panels appear on primary cards and selected rows; active panels add amber corner blocks to announce command focus.
- Pixel raster underlays appear behind maps, charts, and hero regions; the grid brightens only under selected cells to create hierarchy.
- Command prompt strips anchor headers, forms, and dialogs with a leading caret, uppercase command path, and blinking block cursor.
- Status badges use inverted monospace cells with two-character codes and square dividers, changing color only for semantic machine states.
- Tables and cards include ruler ticks, row numbers, and ASCII separators so data feels inspected rather than merely displayed.
## 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-019e66f7-860f-7b41-bc39-ca3f17abc8a7/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 square cells, row numbers, command paths, and visible rulers to make hierarchy structural.
- Do Keep palette disciplined: off-black base, phosphor green primary, amber caution, and minimal semantic exceptions.
- Do Let interactions snap, invert, or move a caret so states feel terminal-native.
- Do Use dense real product data such as logs, coordinates, packet counts, and operator notes.
- Don't Do not add rounded cards, glassmorphism, pastel gradients, or friendly illustration.
- Don't Do not use pixel art as loose decoration without affecting controls, navigation, or data states.
- Don't Do not spread many accent colors across the interface; reserve color for command meaning.
- Don't Do not make the embodiment a component inventory instead of a plausible operations screen.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "terminal-brutalist-interface",
"type": "registry:theme",
"title": "Terminal Brutalist Interface shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#060807",
"foreground": "#D8FFE7",
"card": "#0B100D",
"card-foreground": "#D8FFE7",
"popover": "#0B100D",
"popover-foreground": "#D8FFE7",
"primary": "#39FF88",
"primary-foreground": "#111111",
"secondary": "#F5A623",
"secondary-foreground": "#ffffff",
"muted": "#617263",
"muted-foreground": "#D8FFE7",
"accent": "#B9FF5A",
"accent-foreground": "#111111",
"destructive": "#FF4D3D",
"border": "#1F5F3B",
"input": "#1F5F3B",
"ring": "#B9FF5A",
"chart-1": "#39FF88",
"chart-2": "#F5A623",
"chart-3": "#B9FF5A",
"chart-4": "#39FF88",
"chart-5": "#F5A623",
"sidebar": "#0B100D",
"sidebar-foreground": "#D8FFE7",
"sidebar-primary": "#39FF88",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#63D7FF",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#1F5F3B",
"sidebar-ring": "#B9FF5A",
"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": "#B9FF5A",
"accent-foreground": "#111111",
"destructive": "#FF4D3D",
"border": "#303642",
"input": "#303642",
"ring": "#B9FF5A",
"chart-1": "#39FF88",
"chart-2": "#F5A623",
"chart-3": "#B9FF5A",
"chart-4": "#39FF88",
"chart-5": "#F5A623",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#39FF88",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#B9FF5A",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#B9FF5A",
"radius": "0"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e66f7-860f-7b41-bc39-ca3f17abc8a7",
"slug": "terminal-brutalist-interface",
"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: #060807;
--foreground: #D8FFE7;
--card: #0B100D;
--card-foreground: #D8FFE7;
--popover: #0B100D;
--popover-foreground: #D8FFE7;
--primary: #39FF88;
--primary-foreground: #111111;
--secondary: #F5A623;
--secondary-foreground: #ffffff;
--muted: #617263;
--muted-foreground: #D8FFE7;
--accent: #B9FF5A;
--accent-foreground: #111111;
--destructive: #FF4D3D;
--border: #1F5F3B;
--input: #1F5F3B;
--ring: #B9FF5A;
--chart-1: #39FF88;
--chart-2: #F5A623;
--chart-3: #B9FF5A;
--chart-4: #39FF88;
--chart-5: #F5A623;
--sidebar: #0B100D;
--sidebar-foreground: #D8FFE7;
--sidebar-primary: #39FF88;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #63D7FF;
--sidebar-accent-foreground: #111111;
--sidebar-border: #1F5F3B;
--sidebar-ring: #B9FF5A;
--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: #B9FF5A;
--accent-foreground: #111111;
--destructive: #FF4D3D;
--border: #303642;
--input: #303642;
--ring: #B9FF5A;
--chart-1: #39FF88;
--chart-2: #F5A623;
--chart-3: #B9FF5A;
--chart-4: #39FF88;
--chart-5: #F5A623;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #39FF88;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #B9FF5A;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #B9FF5A;
--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 TerminalBrutalistInterfaceShadcnKit() {
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">Terminal Brutalist Interface</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": "terminal-brutalist-interface",
"type": "registry:theme",
"title": "Terminal Brutalist Interface shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#060807",
"foreground": "#D8FFE7",
"card": "#0B100D",
"card-foreground": "#D8FFE7",
"popover": "#0B100D",
"popover-foreground": "#D8FFE7",
"primary": "#39FF88",
"primary-foreground": "#111111",
"secondary": "#F5A623",
"secondary-foreground": "#ffffff",
"muted": "#617263",
"muted-foreground": "#D8FFE7",
"accent": "#B9FF5A",
"accent-foreground": "#111111",
"destructive": "#FF4D3D",
"border": "#1F5F3B",
"input": "#1F5F3B",
"ring": "#B9FF5A",
"chart-1": "#39FF88",
"chart-2": "#F5A623",
"chart-3": "#B9FF5A",
"chart-4": "#39FF88",
"chart-5": "#F5A623",
"sidebar": "#0B100D",
"sidebar-foreground": "#D8FFE7",
"sidebar-primary": "#39FF88",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#63D7FF",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#1F5F3B",
"sidebar-ring": "#B9FF5A",
"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": "#B9FF5A",
"accent-foreground": "#111111",
"destructive": "#FF4D3D",
"border": "#303642",
"input": "#303642",
"ring": "#B9FF5A",
"chart-1": "#39FF88",
"chart-2": "#F5A623",
"chart-3": "#B9FF5A",
"chart-4": "#39FF88",
"chart-5": "#F5A623",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#39FF88",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#B9FF5A",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#B9FF5A",
"radius": "0"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e66f7-860f-7b41-bc39-ca3f17abc8a7",
"slug": "terminal-brutalist-interface",
"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"
]
}
}
}
# Terminal Brutalist Interface shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e66f7-860f-7b41-bc39-ca3f17abc8a7`
Slug: `terminal-brutalist-interface`
## Intent
Terminal Brutalist Interface treats the screen as an exposed operations console: off-black space, phosphor green commands, amber warnings, monospace rows, hard rectangular cells, and raw pixel-grid evidence replace decorative polish.
## 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": "#B9FF5A",
"background": "#060807",
"border": "#1F5F3B",
"error": "#FF4D3D",
"info": "#63D7FF",
"muted": "#617263",
"primary": "#39FF88",
"secondary": "#F5A623",
"success": "#39FF88",
"surface": "#0B100D",
"text": "#D8FFE7",
"warning": "#F5A623"
}
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=Share+Tech+Mono&display=swap",
"heading_font": "Share Tech Mono",
"letter_spacing": "-0.01em",
"line_height": 1.45,
"mono_font": "IBM Plex Mono",
"scale_ratio": 1.2
}
## Visual character to preserve
- Use a global 8px bitmap grid with repeating-linear-gradient scanlines and square module placement for all panels, gutters, and data rows.
- Build every surface from flat off-black rectangles with one-pixel phosphor borders, no radius, no blur, and inset terminal command bars.
- Set hierarchy through monospace type contrast: large compressed command headings, amber uppercase labels, green body rows, and dim ghost coordinates.
- Render status and focus as pixel blocks, bracket corners, caret glyphs, and inverted cells rather than soft shadows or rounded pills.
- Use dense table-like composition with fixed-width code columns, ruler ticks, ASCII separators, and CRT phosphor noise as the only texture.
## ShadSync visual profile
{
"family": "brutalist",
"material": "ink",
"contour": "pebble",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": true,
"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/terminal-brutalist-interface/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 square cells, row numbers, command paths, and visible rulers to make hierarchy structural.; Keep palette disciplined: off-black base, phosphor green primary, amber caution, and minimal semantic exceptions.; Let interactions snap, invert, or move a caret so states feel terminal-native.; Use dense real product data such as logs, coordinates, packet counts, and operator notes.
- Do not: Do not add rounded cards, glassmorphism, pastel gradients, or friendly illustration.; Do not use pixel art as loose decoration without affecting controls, navigation, or data states.; Do not spread many accent colors across the interface; reserve color for command meaning.; Do not make the embodiment a component inventory instead of a plausible operations screen.
## 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 TerminalBrutalistInterfaceShadcnKit() {
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">Terminal Brutalist Interface</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
```
## Layout notes
{
"breakpoints": "desktop >=1200 uses rail/log/diagnostics; tablet 768-1199 stacks diagnostics below the log; mobile <640 collapses to prompt tabs and single-column panels.",
"grid": "8px base grid with 16-column desktop command layout, square modules, fixed-width log columns, and no off-grid decorative placement.",
"whitespace": "Whitespace is scarce but exact: outer margins use 24px desktop and 12px mobile, with empty space reserved for command focus rather than comfort."
}
{
"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-019e66f7-860f-7b41-bc39-ca3f17abc8a7",
"name": "Terminal Brutalist Interface",
"slug": "terminal-brutalist-interface"
},
"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 a global 8px bitmap grid with repeating-linear-gradient scanlines and square module placement for all panels, gutters, and data rows.",
"Build every surface from flat off-black rectangles with one-pixel phosphor borders, no radius, no blur, and inset terminal command bars.",
"Set hierarchy through monospace type contrast: large compressed command headings, amber uppercase labels, green body rows, and dim ghost coordinates.",
"Render status and focus as pixel blocks, bracket corners, caret glyphs, and inverted cells rather than soft shadows or rounded pills.",
"Use dense table-like composition with fixed-width code columns, ruler ticks, ASCII separators, and CRT phosphor noise as the only texture."
],
"visualProfile": {
"family": "brutalist",
"material": "ink",
"contour": "pebble",
"border": "solid",
"underlay": true,
"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": "Terminal Brutalist Interface 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 square cells, row numbers, command paths, and visible rulers to make hierarchy structural.",
"Keep palette disciplined: off-black base, phosphor green primary, amber caution, and minimal semantic exceptions.",
"Let interactions snap, invert, or move a caret so states feel terminal-native.",
"Use dense real product data such as logs, coordinates, packet counts, and operator notes."
],
"dont": [
"Do not add rounded cards, glassmorphism, pastel gradients, or friendly illustration.",
"Do not use pixel art as loose decoration without affecting controls, navigation, or data states.",
"Do not spread many accent colors across the interface; reserve color for command meaning.",
"Do not make the embodiment a component inventory instead of a plausible operations screen."
]
}
}