NERV Command-Line Theology

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

:root {
  --background: #030304;
  --foreground: #F8F0E2;
  --card: #F1E6D2;
  --card-foreground: #F8F0E2;
  --popover: #F1E6D2;
  --popover-foreground: #F8F0E2;
  --primary: #F08A24;
  --primary-foreground: #ffffff;
  --secondary: #D8C7A6;
  --secondary-foreground: #111111;
  --muted: #8C8274;
  --muted-foreground: #F8F0E2;
  --accent: #A41412;
  --accent-foreground: #ffffff;
  --destructive: #A41412;
  --border: #2A2520;
  --input: #2A2520;
  --ring: #A41412;
  --chart-1: #F08A24;
  --chart-2: #D8C7A6;
  --chart-3: #A41412;
  --chart-4: #7F9A68;
  --chart-5: #F08A24;
  --sidebar: #F1E6D2;
  --sidebar-foreground: #F8F0E2;
  --sidebar-primary: #F08A24;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #A9B0AA;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #2A2520;
  --sidebar-ring: #A41412;
  --radius: 0;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #F08A24;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #A41412;
  --accent-foreground: #ffffff;
  --destructive: #A41412;
  --border: #303642;
  --input: #303642;
  --ring: #A41412;
  --chart-1: #F08A24;
  --chart-2: #D8C7A6;
  --chart-3: #A41412;
  --chart-4: #7F9A68;
  --chart-5: #F08A24;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #F08A24;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #A41412;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #A41412;
  --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 NervCommandLineTheologyShadcnKit() {
  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">NERV Command-Line Theology</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

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

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

{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "cssVars": {
    "dark": {
      "accent": "#A41412",
      "accent-foreground": "#ffffff",
      "background": "#0f1115",
      "border": "#303642",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "chart-1": "#F08A24",
      "chart-2": "#D8C7A6",
      "chart-3": "#A41412",
      "chart-4": "#7F9A68",
      "chart-5": "#F08A24",
      "destructive": "#A41412",
      "foreground": "#f8fafc",
      "input": "#303642",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#F08A24",
      "primary-foreground": "#ffffff",
      "radius": "0",
      "ring": "#A41412",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "sidebar": "#181b22",
      "sidebar-accent": "#A41412",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#F08A24",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#A41412"
    },
    "light": {
      "accent": "#A41412",
      "accent-foreground": "#ffffff",
      "background": "#030304",
      "border": "#2A2520",
      "card": "#F1E6D2",
      "card-foreground": "#F8F0E2",
      "chart-1": "#F08A24",
      "chart-2": "#D8C7A6",
      "chart-3": "#A41412",
      "chart-4": "#7F9A68",
      "chart-5": "#F08A24",
      "destructive": "#A41412",
      "foreground": "#F8F0E2",
      "input": "#2A2520",
      "muted": "#8C8274",
      "muted-foreground": "#F8F0E2",
      "popover": "#F1E6D2",
      "popover-foreground": "#F8F0E2",
      "primary": "#F08A24",
      "primary-foreground": "#ffffff",
      "radius": "0",
      "ring": "#A41412",
      "secondary": "#D8C7A6",
      "secondary-foreground": "#111111",
      "sidebar": "#F1E6D2",
      "sidebar-accent": "#A9B0AA",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#2A2520",
      "sidebar-foreground": "#F8F0E2",
      "sidebar-primary": "#F08A24",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#A41412"
    },
    "theme": {}
  },
  "meta": {
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "languageId": "nerv-command-line-theology",
    "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"
      ],
      "opacity": [
        "disabled",
        "muted",
        "overlay"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "breach_seal",
        "ivory_dossier",
        "terminal_glass",
        "void",
        "warning_strip"
      ],
      "typography": [
        "body_font",
        "google_fonts_url",
        "heading_font",
        "mono_font"
      ]
    },
    "slug": "nerv-command-line-theology",
    "source": "katagami"
  },
  "name": "nerv-command-line-theology",
  "title": "NERV Command-Line Theology shadcn Theme",
  "type": "registry:theme"
}

# NERV Command-Line Theology shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `nerv-command-line-theology`
Slug: `nerv-command-line-theology`

## Intent

NERV Command-Line Theology is a severe esoteric terminal liturgy for command rooms, incident consoles, and bureaucratic control systems where every prompt feels like a doctrine and every state change feels authorized by ritual. The language preserves the core NERV command-line theology concept without fan art: black operational voids, amber phosphor command light, blood-red breach seals, ivory bureaucratic dossiers, and occult typography arranged as sacred procedure.

## 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": "#A41412",
  "background": "#030304",
  "border": "#2A2520",
  "error": "#A41412",
  "info": "#A9B0AA",
  "muted": "#8C8274",
  "primary": "#F08A24",
  "secondary": "#D8C7A6",
  "success": "#7F9A68",
  "surface": "#F1E6D2",
  "text": "#F8F0E2",
  "warning": "#F08A24"
}

Typography:

{
  "body_font": "Crimson Pro",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Crimson+Pro:wght@400;500;600&family=IBM+Plex+Mono:wght@400;500;600;700&family=Oswald:wght@500;600;700&display=swap",
  "heading_font": "Oswald",
  "mono_font": "IBM Plex Mono"
}

## Visual character to preserve

- A black command nave uses CSS grid and repeating-linear-gradient hairlines to create a severe terminal altar, with visible coordinate gutters, prompt rows, and redacted doctrine blocks rather than decorative code noise.
- Bone-ivory bureaucratic panels sit over the black field as flat paper dossiers with hard 1px ink dividers, vertical section numbers, stamped approval cells, and zero-radius rectangular controls.
- Amber phosphor is restricted to command prompts, active rails, cursor blocks, and primary authorization buttons, implemented with solid fills and modest text-shadow rather than broad neon glow.
- Blood-red appears as narrow breach seals, status glyph cells, and crossed-out protocol tags; every red mark is paired with text labels or position so it is not the only state cue.
- Occult control-room typography combines condensed uppercase headings, serif doctrinal annotations, and monospaced system prompts, all aligned to a disciplined 8px baseline and 12-column ritual grid.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": true,
  "stickerBadges": true,
  "motion": "lift-rotate",
  "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/nerv-command-line-theology/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 only for active command, warning, cursor, or authorization states.; Pair every red breach indicator with text labels, position, or icon shape for accessibility.; Keep panels zero-radius with hard dividers, serial codes, redaction bars, barcode ticks, and command prompts.; Use a real application scene such as an incident command console or doctrine approval terminal, not a component inventory.; Preserve black negative space as a structural element; do not fill every surface with log text.; Style every button, input, checkbox, select, and badge with the same terminal liturgy tokens.
- Do not: Do not use cyan, purple, rainbow neon, matrix rain, generic glitch, or cyberpunk city imagery.; Do not include anime characters, logos, fan-service, or literal references; keep the influence bureaucratic and operational.; Do not use rounded SaaS cards, pill buttons, friendly emoji, gradients, or soft productivity dashboard patterns.; Do not let terminal text become unreadable wallpaper; each log row should have spacing and hierarchy.; Do not create three equal marketing cards or a component catalog; the composition must read as a lived control-room console.; Do not rely on red alone for errors or breach state.

## 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 NervCommandLineTheologyShadcnKit() {
  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">NERV Command-Line Theology</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": "At max-width 900px switch to a 6-column tablet grid with reduced overlap; at max-width 640px stack rail, dossier, terminal, and seal as single-column blocks; at min-width 1200px restore full ritual asymmetry.",
  "density": "Alternate high-density command clusters with large black negative space so the interface feels pressurized and sacred, not busy.",
  "grid": "Desktop uses a 12-column grid capped at 1320px; the terminal nave spans 8 columns, the ivory dossier spans 4 columns and overlaps by 32px, and the amber rail spans all columns.",
  "whitespace": "Use 64-128px outer margins on desktop, 32px on tablet, and 16px on mobile; internal doctrine cells follow an 8px baseline."
}

{
  "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": "nerv-command-line-theology",
    "name": "NERV Command-Line Theology",
    "slug": "nerv-command-line-theology"
  },
  "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": [
    "A black command nave uses CSS grid and repeating-linear-gradient hairlines to create a severe terminal altar, with visible coordinate gutters, prompt rows, and redacted doctrine blocks rather than decorative code noise.",
    "Bone-ivory bureaucratic panels sit over the black field as flat paper dossiers with hard 1px ink dividers, vertical section numbers, stamped approval cells, and zero-radius rectangular controls.",
    "Amber phosphor is restricted to command prompts, active rails, cursor blocks, and primary authorization buttons, implemented with solid fills and modest text-shadow rather than broad neon glow.",
    "Blood-red appears as narrow breach seals, status glyph cells, and crossed-out protocol tags; every red mark is paired with text labels or position so it is not the only state cue.",
    "Occult control-room typography combines condensed uppercase headings, serif doctrinal annotations, and monospaced system prompts, all aligned to a disciplined 8px baseline and 12-column ritual grid."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": true,
    "motion": "lift-rotate",
    "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": "NERV Command-Line Theology 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 only for active command, warning, cursor, or authorization states.",
      "Pair every red breach indicator with text labels, position, or icon shape for accessibility.",
      "Keep panels zero-radius with hard dividers, serial codes, redaction bars, barcode ticks, and command prompts.",
      "Use a real application scene such as an incident command console or doctrine approval terminal, not a component inventory.",
      "Preserve black negative space as a structural element; do not fill every surface with log text.",
      "Style every button, input, checkbox, select, and badge with the same terminal liturgy tokens."
    ],
    "dont": [
      "Do not use cyan, purple, rainbow neon, matrix rain, generic glitch, or cyberpunk city imagery.",
      "Do not include anime characters, logos, fan-service, or literal references; keep the influence bureaucratic and operational.",
      "Do not use rounded SaaS cards, pill buttons, friendly emoji, gradients, or soft productivity dashboard patterns.",
      "Do not let terminal text become unreadable wallpaper; each log row should have spacing and hierarchy.",
      "Do not create three equal marketing cards or a component catalog; the composition must read as a lived control-room console.",
      "Do not rely on red alone for errors or breach state."
    ]
  }
}