Technical Mono

npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table

:root {
  --background: #0A0A0A;
  --foreground: #E8E8E8;
  --card: #141414;
  --card-foreground: #E8E8E8;
  --popover: #141414;
  --popover-foreground: #E8E8E8;
  --primary: #00FF41;
  --primary-foreground: #111111;
  --secondary: #8BE9FD;
  --secondary-foreground: #111111;
  --muted: #8A8A8A;
  --muted-foreground: #E8E8E8;
  --accent: #FFB000;
  --accent-foreground: #ffffff;
  --destructive: #FF5F56;
  --border: #333333;
  --input: #333333;
  --ring: #FFB000;
  --chart-1: #00FF41;
  --chart-2: #8BE9FD;
  --chart-3: #FFB000;
  --chart-4: #00FF41;
  --chart-5: #FFB000;
  --sidebar: #141414;
  --sidebar-foreground: #E8E8E8;
  --sidebar-primary: #00FF41;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #8BE9FD;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #333333;
  --sidebar-ring: #FFB000;
  --radius: 0;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #00FF41;
  --primary-foreground: #111111;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #FFB000;
  --accent-foreground: #ffffff;
  --destructive: #FF5F56;
  --border: #303642;
  --input: #303642;
  --ring: #FFB000;
  --chart-1: #00FF41;
  --chart-2: #8BE9FD;
  --chart-3: #FFB000;
  --chart-4: #00FF41;
  --chart-5: #FFB000;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #00FF41;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #FFB000;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #FFB000;
  --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 TechnicalMonoShadcnKit() {
  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">Technical Mono</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": "technical-mono",
  "type": "registry:theme",
  "title": "Technical Mono shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#0A0A0A",
      "foreground": "#E8E8E8",
      "card": "#141414",
      "card-foreground": "#E8E8E8",
      "popover": "#141414",
      "popover-foreground": "#E8E8E8",
      "primary": "#00FF41",
      "primary-foreground": "#111111",
      "secondary": "#8BE9FD",
      "secondary-foreground": "#111111",
      "muted": "#8A8A8A",
      "muted-foreground": "#E8E8E8",
      "accent": "#FFB000",
      "accent-foreground": "#ffffff",
      "destructive": "#FF5F56",
      "border": "#333333",
      "input": "#333333",
      "ring": "#FFB000",
      "chart-1": "#00FF41",
      "chart-2": "#8BE9FD",
      "chart-3": "#FFB000",
      "chart-4": "#00FF41",
      "chart-5": "#FFB000",
      "sidebar": "#141414",
      "sidebar-foreground": "#E8E8E8",
      "sidebar-primary": "#00FF41",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#8BE9FD",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#333333",
      "sidebar-ring": "#FFB000",
      "radius": "0"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#00FF41",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#FFB000",
      "accent-foreground": "#ffffff",
      "destructive": "#FF5F56",
      "border": "#303642",
      "input": "#303642",
      "ring": "#FFB000",
      "chart-1": "#00FF41",
      "chart-2": "#8BE9FD",
      "chart-3": "#FFB000",
      "chart-4": "#00FF41",
      "chart-5": "#FFB000",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#00FF41",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#FFB000",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#FFB000",
      "radius": "0"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019daf17-e112-78b3-818b-a757526f4aab",
    "slug": "technical-mono",
    "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": {
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ]
    }
  }
}

# Technical Mono shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019daf17-e112-78b3-818b-a757526f4aab`
Slug: `technical-mono`

## Intent

Technical Mono is a dense operational interface language derived from terminal UIs, code editors, infrastructure dashboards, and contemporary neobrutalist web patterns. It treats the interface as an exposed instrument panel rather than a polished consumer shell: structure stays visible, state is expressed through fixed-width text markers, and layout rhythm follows character cells instead of soft cards. The result should feel precise, machine-adjacent, and intentionally uncompromising without becoming unusable.

## 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:

{
  "primary": "#00FF41",
  "secondary": "#8BE9FD",
  "accent": "#FFB000",
  "background": "#0A0A0A",
  "surface": "#141414",
  "text": "#E8E8E8",
  "muted": "#8A8A8A",
  "border": "#333333",
  "error": "#FF5F56",
  "success": "#00FF41",
  "warning": "#FFB000",
  "info": "#8BE9FD"
}

Typography:

{
  "heading_font": "IBM Plex Mono",
  "body_font": "IBM Plex Mono",
  "mono_font": "IBM Plex Mono",
  "base_size": "16px",
  "scale_ratio": 1.125,
  "line_height": 1.5,
  "letter_spacing": "0.01em",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:ital,wght@0,300;0,400;0,500;0,600;0,700;1,400&display=swap"
}

## Visual character to preserve

- Every primary region is boxed with a visible 1px solid border and rectangular corners so the page reads like a terminal multiplexer or engineering console rather than floating cards.
- All typography uses IBM Plex Mono with widths expressed in ch units, causing labels, values, and panels to align to a character grid similar to a code editor gutter and terminal buffer.
- Section headers appear as uppercase prompt-style labels such as // OVERVIEW, > ACTIVE QUEUE, and $ PATCH WINDOW with increased letter spacing and subdued gray coloring above each data region.
- State is communicated through inline fixed-width markers like [OK], [WARN], [ERR], and [SYNC] rendered as text tokens, not badges with soft pills or icon circles.
- Nested groups switch from solid 1px borders to dashed separators so hierarchy stays visible while preserving the raw wireframe feel of developer tooling and anti-polished web brutalism.

## ShadSync visual profile

{
  "family": "brutalist",
  "material": "ink",
  "contour": "pebble",
  "border": "dashed",
  "underlay": false,
  "grain": false,
  "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/technical-mono/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 IBM Plex Mono for headings, labels, controls, and data values so the interface reads as one calibrated technical surface.; Keep borders continuously visible so grouping and hierarchy remain obvious without shadows or background flourishes.; Express state with textual markers such as [OK], [WARN], [ERR], and [SYNC] paired with restrained semantic color.; Design complete operational scenes like deployment consoles, audit panels, and queue management views rather than component catalogs.; Use ch-based widths and explicit grid tracks to preserve the feeling of a measured character-cell workspace.
- Do not: Do not introduce rounded corners, blurred glass, or soft drop shadows.; Do not use non-monospace fonts, decorative illustrations, or emoji iconography.; Do not hide hierarchy behind oversized whitespace or floating card compositions.; Do not rely on generic colored dots as the only status signal when explicit text tokens can communicate state.; Do not add gradients, glossy materials, or atmospheric effects that break the austere terminal language.

## 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 TechnicalMonoShadcnKit() {
  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">Technical Mono</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

{
  "grid": "Desktop uses a four-zone shell with top command bar, left navigation rail, central operations column, and right diagnostics column. Modules use CSS Grid tracks that mix fixed ch widths with fluid fractions so the character grid remains stable.",
  "breakpoints": "xs 0-479px: single-column stack; sm 480-767px: stacked content with compact top bar; md 768-1023px: two-column content with nav moved above main; lg 1024-1439px: three-column operations layout; xl 1440px+: full workspace with persistent diagnostics pane.",
  "whitespace": "Whitespace stays economical and functional. Most padding remains between 12px and 16px, nested controls use 8px spacing, and separation is primarily communicated through borders and rule lines rather than large empty gaps."
}

{
  "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-019daf17-e112-78b3-818b-a757526f4aab",
    "name": "Technical Mono",
    "slug": "technical-mono"
  },
  "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": [
    "Every primary region is boxed with a visible 1px solid border and rectangular corners so the page reads like a terminal multiplexer or engineering console rather than floating cards.",
    "All typography uses IBM Plex Mono with widths expressed in ch units, causing labels, values, and panels to align to a character grid similar to a code editor gutter and terminal buffer.",
    "Section headers appear as uppercase prompt-style labels such as // OVERVIEW, > ACTIVE QUEUE, and $ PATCH WINDOW with increased letter spacing and subdued gray coloring above each data region.",
    "State is communicated through inline fixed-width markers like [OK], [WARN], [ERR], and [SYNC] rendered as text tokens, not badges with soft pills or icon circles.",
    "Nested groups switch from solid 1px borders to dashed separators so hierarchy stays visible while preserving the raw wireframe feel of developer tooling and anti-polished web brutalism."
  ],
  "visualProfile": {
    "family": "brutalist",
    "material": "ink",
    "contour": "pebble",
    "border": "dashed",
    "underlay": false,
    "grain": false,
    "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": "Technical Mono 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 IBM Plex Mono for headings, labels, controls, and data values so the interface reads as one calibrated technical surface.",
      "Keep borders continuously visible so grouping and hierarchy remain obvious without shadows or background flourishes.",
      "Express state with textual markers such as [OK], [WARN], [ERR], and [SYNC] paired with restrained semantic color.",
      "Design complete operational scenes like deployment consoles, audit panels, and queue management views rather than component catalogs.",
      "Use ch-based widths and explicit grid tracks to preserve the feeling of a measured character-cell workspace."
    ],
    "dont": [
      "Do not introduce rounded corners, blurred glass, or soft drop shadows.",
      "Do not use non-monospace fonts, decorative illustrations, or emoji iconography.",
      "Do not hide hierarchy behind oversized whitespace or floating card compositions.",
      "Do not rely on generic colored dots as the only status signal when explicit text tokens can communicate state.",
      "Do not add gradients, glossy materials, or atmospheric effects that break the austere terminal language."
    ]
  }
}