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

:root {
  --background: #070A10;
  --foreground: #F2EBDD;
  --card: #0D1320;
  --card-foreground: #F2EBDD;
  --popover: #0D1320;
  --popover-foreground: #F2EBDD;
  --primary: #E9E1D2;
  --primary-foreground: #111111;
  --secondary: #A9794E;
  --secondary-foreground: #ffffff;
  --muted: #8B9297;
  --muted-foreground: #F2EBDD;
  --accent: #C87946;
  --accent-foreground: #ffffff;
  --destructive: #B45A52;
  --border: #E9E1D2;
  --input: #E9E1D2;
  --ring: #C87946;
  --chart-1: #E9E1D2;
  --chart-2: #A9794E;
  --chart-3: #C87946;
  --chart-4: #9E9A73;
  --chart-5: #D39A55;
  --sidebar: #0D1320;
  --sidebar-foreground: #F2EBDD;
  --sidebar-primary: #E9E1D2;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #76909A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #E9E1D2;
  --sidebar-ring: #C87946;
  --radius: 16px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #E9E1D2;
  --primary-foreground: #111111;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #C87946;
  --accent-foreground: #ffffff;
  --destructive: #B45A52;
  --border: #303642;
  --input: #303642;
  --ring: #C87946;
  --chart-1: #E9E1D2;
  --chart-2: #A9794E;
  --chart-3: #C87946;
  --chart-4: #9E9A73;
  --chart-5: #D39A55;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #E9E1D2;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #C87946;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #C87946;
  --radius: 16px;
}

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 RainShellCommandShadcnKit() {
  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">Rain-Shell Command</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": "rain-shell-command",
  "type": "registry:theme",
  "title": "Rain-Shell Command shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#070A10",
      "foreground": "#F2EBDD",
      "card": "#0D1320",
      "card-foreground": "#F2EBDD",
      "popover": "#0D1320",
      "popover-foreground": "#F2EBDD",
      "primary": "#E9E1D2",
      "primary-foreground": "#111111",
      "secondary": "#A9794E",
      "secondary-foreground": "#ffffff",
      "muted": "#8B9297",
      "muted-foreground": "#F2EBDD",
      "accent": "#C87946",
      "accent-foreground": "#ffffff",
      "destructive": "#B45A52",
      "border": "#E9E1D2",
      "input": "#E9E1D2",
      "ring": "#C87946",
      "chart-1": "#E9E1D2",
      "chart-2": "#A9794E",
      "chart-3": "#C87946",
      "chart-4": "#9E9A73",
      "chart-5": "#D39A55",
      "sidebar": "#0D1320",
      "sidebar-foreground": "#F2EBDD",
      "sidebar-primary": "#E9E1D2",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#76909A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#E9E1D2",
      "sidebar-ring": "#C87946",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#E9E1D2",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#C87946",
      "accent-foreground": "#ffffff",
      "destructive": "#B45A52",
      "border": "#303642",
      "input": "#303642",
      "ring": "#C87946",
      "chart-1": "#E9E1D2",
      "chart-2": "#A9794E",
      "chart-3": "#C87946",
      "chart-4": "#9E9A73",
      "chart-5": "#D39A55",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#E9E1D2",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#C87946",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#C87946",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "rain-shell-command",
    "slug": "rain-shell-command",
    "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"
      ]
    }
  }
}

# Rain-Shell Command shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `rain-shell-command`
Slug: `rain-shell-command`

## Intent

Rain-Shell Command is a nocturnal interface language for private terminal work inside compressed capsule rooms: black manga-panel structure, midnight wet surfaces, amber vending-machine glow, and CRT-soft typed signals. It treats software as shelter rather than spectacle, making every active region feel like a reserved pod with a latch, a number plate, and a quiet machine breathing behind the curtain.

## 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": "#C87946",
  "background": "#070A10",
  "border": "#E9E1D2",
  "error": "#B45A52",
  "info": "#76909A",
  "muted": "#8B9297",
  "primary": "#E9E1D2",
  "secondary": "#A9794E",
  "success": "#9E9A73",
  "surface": "#0D1320",
  "text": "#F2EBDD",
  "warning": "#D39A55"
}

Typography:

{
  "base_size": "16px",
  "body_font": "IBM Plex Sans",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Archivo+SemiExpanded:wght@500;600;700&family=IBM+Plex+Sans:wght@400;500;600&family=Share+Tech+Mono&display=swap",
  "heading_font": "Archivo SemiExpanded",
  "letter_spacing": "-0.02em",
  "line_height": 1.55,
  "mono_font": "Share Tech Mono",
  "scale_ratio": 1.2
}

## Visual character to preserve

- Use nested berth rectangles with 1px ivory manga partitions, 0 or 16px radii, and sliding-door side rails that make panes read as capsule rooms.
- Reserve one large active terminal pane with amber inner glow while adjacent pods are dark, cropped, and partially sealed by black rain gutters.
- Apply CRT softness through subtle scanline overlays, low-opacity phosphor bloom, and typed cursor pulses rather than bright neon effects.
- Attach small pod number plates, latch tabs, ticket-printer strips, and tiny status LEDs to component edges as physical interface affordances.
- Sequence sections like black-and-white manga panels with asymmetric crops, vertical gutters, and occasional full-height threshold dividers.

## ShadSync visual profile

{
  "family": "brutalist",
  "material": "ink",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "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/rain-shell-command/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 one amber-lit active terminal pane per screen and keep surrounding pods visibly quieter.; Anchor components with pod IDs, reservation codes, latch tabs, and tiny LEDs rather than decorative icons.; Keep cyan desaturated and sparse, used only for rain-on-glass reflections or secondary info.; Use ivory partitions as manga panel structure, mostly at low opacity, with stronger lines only on active thresholds.; Maintain body text at 15-16px with -0.02em tracking and display headings at -0.04em tracking.; Let large wet-black gutters create solitude; do not fill every void with data.; Use monospace prompts, timestamps, and room codes to establish terminal authenticity.
- Do not: Do not use green matrix effects, neon rainbow cyberpunk, city-grid backgrounds, or hacker stock dashboards.; Do not place three equal cards in a row or use generic analytics KPI components.; Do not use character art, mecha silhouettes, anime faces, or kanji wallpaper as identity shortcuts.; Do not use novelty hacker fonts, unreadable code walls, or aggressive HUD reticles.; Do not make all panels glow; only the active berth receives warm illumination.; Do not use pure saturated cyan, mint, purple, or synthetic triadic accents.; Do not round every surface; square manga partitions and restrained hatch radii define the shell.

## 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 RainShellCommandShadcnKit() {
  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">Rain-Shell Command</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": "1440px desktop composition, 900px tablet stack with retained gutters, 560px mobile corridor with simplified latch plates.",
  "density": "Compact terminal clusters sit inside larger architectural voids, giving an 8:1 rhythm between 4px micro-label gaps and 96px scene margins.",
  "grid": "Desktop uses a 12-column shell with a 360px left pod stack and an 8-column active terminal; tablet collapses to stacked berths; mobile becomes a single vertical corridor of capsule panes.",
  "responsive": "At narrow widths, side rails become top number plates, panels crop less aggressively, and command rows wrap into ticket strips instead of shrinking below readable size.",
  "whitespace": "Whitespace is wet black negative space: broad margins and rain gutters isolate the active pane while tiny interior gaps keep terminal controls intimate."
}

{
  "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": "rain-shell-command",
    "name": "Rain-Shell Command",
    "slug": "rain-shell-command"
  },
  "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 nested berth rectangles with 1px ivory manga partitions, 0 or 16px radii, and sliding-door side rails that make panes read as capsule rooms.",
    "Reserve one large active terminal pane with amber inner glow while adjacent pods are dark, cropped, and partially sealed by black rain gutters.",
    "Apply CRT softness through subtle scanline overlays, low-opacity phosphor bloom, and typed cursor pulses rather than bright neon effects.",
    "Attach small pod number plates, latch tabs, ticket-printer strips, and tiny status LEDs to component edges as physical interface affordances.",
    "Sequence sections like black-and-white manga panels with asymmetric crops, vertical gutters, and occasional full-height threshold dividers."
  ],
  "visualProfile": {
    "family": "brutalist",
    "material": "ink",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "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": "Rain-Shell Command 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 one amber-lit active terminal pane per screen and keep surrounding pods visibly quieter.",
      "Anchor components with pod IDs, reservation codes, latch tabs, and tiny LEDs rather than decorative icons.",
      "Keep cyan desaturated and sparse, used only for rain-on-glass reflections or secondary info.",
      "Use ivory partitions as manga panel structure, mostly at low opacity, with stronger lines only on active thresholds.",
      "Maintain body text at 15-16px with -0.02em tracking and display headings at -0.04em tracking.",
      "Let large wet-black gutters create solitude; do not fill every void with data.",
      "Use monospace prompts, timestamps, and room codes to establish terminal authenticity."
    ],
    "dont": [
      "Do not use green matrix effects, neon rainbow cyberpunk, city-grid backgrounds, or hacker stock dashboards.",
      "Do not place three equal cards in a row or use generic analytics KPI components.",
      "Do not use character art, mecha silhouettes, anime faces, or kanji wallpaper as identity shortcuts.",
      "Do not use novelty hacker fonts, unreadable code walls, or aggressive HUD reticles.",
      "Do not make all panels glow; only the active berth receives warm illumination.",
      "Do not use pure saturated cyan, mint, purple, or synthetic triadic accents.",
      "Do not round every surface; square manga partitions and restrained hatch radii define the shell."
    ]
  }
}