Optical Shellcode Terminal

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

:root {
  --background: #FBFCFC;
  --foreground: #111417;
  --card: #FFFFFF;
  --card-foreground: #111417;
  --popover: #FFFFFF;
  --popover-foreground: #111417;
  --primary: #0B0D0F;
  --primary-foreground: #ffffff;
  --secondary: #F7FAFB;
  --secondary-foreground: #111111;
  --muted: #667176;
  --muted-foreground: #111417;
  --accent: #8FD7E8;
  --accent-foreground: #111111;
  --destructive: #9B2F3B;
  --border: #0B0D0F;
  --input: #0B0D0F;
  --ring: #8FD7E8;
  --chart-1: #0B0D0F;
  --chart-2: #F7FAFB;
  --chart-3: #8FD7E8;
  --chart-4: #3F7A72;
  --chart-5: #A2793A;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #111417;
  --sidebar-primary: #0B0D0F;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #6FAFC4;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #0B0D0F;
  --sidebar-ring: #8FD7E8;
  --radius: 16px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #0B0D0F;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #8FD7E8;
  --accent-foreground: #111111;
  --destructive: #9B2F3B;
  --border: #303642;
  --input: #303642;
  --ring: #8FD7E8;
  --chart-1: #0B0D0F;
  --chart-2: #F7FAFB;
  --chart-3: #8FD7E8;
  --chart-4: #3F7A72;
  --chart-5: #A2793A;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #0B0D0F;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #8FD7E8;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #8FD7E8;
  --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 OpticalShellcodeTerminalShadcnKit() {
  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">Optical Shellcode Terminal</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": "optical-shellcode-terminal",
  "type": "registry:theme",
  "title": "Optical Shellcode Terminal shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FBFCFC",
      "foreground": "#111417",
      "card": "#FFFFFF",
      "card-foreground": "#111417",
      "popover": "#FFFFFF",
      "popover-foreground": "#111417",
      "primary": "#0B0D0F",
      "primary-foreground": "#ffffff",
      "secondary": "#F7FAFB",
      "secondary-foreground": "#111111",
      "muted": "#667176",
      "muted-foreground": "#111417",
      "accent": "#8FD7E8",
      "accent-foreground": "#111111",
      "destructive": "#9B2F3B",
      "border": "#0B0D0F",
      "input": "#0B0D0F",
      "ring": "#8FD7E8",
      "chart-1": "#0B0D0F",
      "chart-2": "#F7FAFB",
      "chart-3": "#8FD7E8",
      "chart-4": "#3F7A72",
      "chart-5": "#A2793A",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#111417",
      "sidebar-primary": "#0B0D0F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#6FAFC4",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#0B0D0F",
      "sidebar-ring": "#8FD7E8",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#0B0D0F",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#8FD7E8",
      "accent-foreground": "#111111",
      "destructive": "#9B2F3B",
      "border": "#303642",
      "input": "#303642",
      "ring": "#8FD7E8",
      "chart-1": "#0B0D0F",
      "chart-2": "#F7FAFB",
      "chart-3": "#8FD7E8",
      "chart-4": "#3F7A72",
      "chart-5": "#A2793A",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#0B0D0F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#8FD7E8",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#8FD7E8",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "optical-shellcode-terminal",
    "slug": "optical-shellcode-terminal",
    "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"
      ]
    }
  }
}

# Optical Shellcode Terminal shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `optical-shellcode-terminal`
Slug: `optical-shellcode-terminal`

## Intent

Optical Shellcode Terminal is a polished cybernetic minimalism system for interfaces that feel like a white shell around consciousness: quiet, clinical, translucent, and intellectually charged. It borrows the philosophical calm of late-90s anime cybernetics without cosplay, translating manga ink contours, shellcode terminals, optical camouflage, Y2K acrylic, and diagnostic grids into a restrained product language for speculative neural tools.

## 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": "#8FD7E8",
  "background": "#FBFCFC",
  "border": "#0B0D0F",
  "error": "#9B2F3B",
  "info": "#6FAFC4",
  "muted": "#667176",
  "primary": "#0B0D0F",
  "secondary": "#F7FAFB",
  "success": "#3F7A72",
  "surface": "#FFFFFF",
  "text": "#111417",
  "warning": "#A2793A"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Archivo",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Archivo:wdth,wght@85,300;85,400;90,500&family=Azeret+Mono:wght@300;400;500&family=Michroma&display=swap",
  "heading_font": "Michroma",
  "letter_spacing": "-0.02em",
  "line_height": 1.55,
  "mono_font": "Azeret Mono",
  "scale_ratio": 1.22
}

## Visual character to preserve

- Use a 12-column precision grid with two or more intentionally empty columns, plus absolute-positioned ghost coordinate labels in 10px monospace.
- Build panels as translucent white acrylic rectangles at 8-24% opacity with 1px rgba graphite borders and clipped terminal corner ticks.
- Insert sparse manga-like black ink contour lines as oversized SVG arcs or border silhouettes that structure the page without becoming illustration.
- Separate dense code/status areas with 1px repeating-linear-gradient scanline dividers and single-pixel pale cyan alert marks.
- Layer small floating terminal overlays above a sterile white field using minimal chrome highlights and almost no shadow depth.

## ShadSync visual profile

{
  "family": "brutalist",
  "material": "ink",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": false,
  "stickerBadges": false,
  "motion": "still",
  "density": "dense",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.

### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.

### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.

### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.

### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.

## Preview shots

- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/optical-shellcode-terminal/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 optical whites, soft blacks, pale cyan, and transparent acrylic as the only major visual vocabulary.; Keep terminal code blocks small and quiet, with expanded tracking and clinical labels rather than theatrical hacker glow.; Place at least one empty grid region with coordinates or crosshair dots so whitespace feels designed.; Use manga ink lines as SVG contour scaffolds, border arcs, or cropped silhouettes that support layout structure.; Make one panel visually dominant and vary section weights; avoid equal cards or repeated modular sameness.; Use body tracking at -0.02em, display tracking around -0.035em, display leading near 1.12, and body leading around 1.55.; Keep borders near-invisible and rely on tiny cyan ticks for system state changes.; Name scenes as specific speculative tools: memory-shell calibration, prosthetic identity audit, or autonomous consciousness interface.
- Do not: Do not use saturated neon cyan, magenta, green matrix rain, RGB gradients, or nightclub cyberpunk lighting.; Do not create generic dashboards, analytics cards, CRM tables, or component-library showcases.; Do not fill all empty space with widgets; the sterile void is part of the philosophical tone.; Do not use cartoon anime characters, fan-art panels, speech bubbles, or illustrative manga decoration.; Do not round every corner; use square terminal frames with only occasional 16px acrylic overlays.; Do not thicken borders beyond 1px except for sparse black contour silhouettes.; Do not use heavy shadows, plastic gloss, or skeuomorphic chrome; highlights must be cold and minimal.; Do not let cyan carry large surfaces; it belongs in pixels, hairlines, and terse status text only.

## 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 OpticalShellcodeTerminalShadcnKit() {
  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">Optical Shellcode Terminal</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

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

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

## Layout notes

{
  "breakpoints": "mobile <= 640px stacks overlays into a single column; tablet 641-1024px keeps a 6-column grid; desktop >= 1025px uses full 12-column asymmetry.",
  "density": "Low global density with one high-compression code pocket; the large blank zones are active optical camouflage, not unused space.",
  "grid": "Desktop uses a 12-column grid, 24px gutters, max-width 1320px, with columns 1-2 often left empty for coordinates and folio marks.",
  "responsive": "On mobile, preserve the shell feeling by retaining coordinate labels and contour arcs while reducing code density and moving overlays below the main title.",
  "whitespace": "Use dramatic 8:1 spacing rhythm: 4-8px inside telemetry rows, 48-96px between functional clusters, and 128px quiet fields on desktop."
}

{
  "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": "optical-shellcode-terminal",
    "name": "Optical Shellcode Terminal",
    "slug": "optical-shellcode-terminal"
  },
  "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 12-column precision grid with two or more intentionally empty columns, plus absolute-positioned ghost coordinate labels in 10px monospace.",
    "Build panels as translucent white acrylic rectangles at 8-24% opacity with 1px rgba graphite borders and clipped terminal corner ticks.",
    "Insert sparse manga-like black ink contour lines as oversized SVG arcs or border silhouettes that structure the page without becoming illustration.",
    "Separate dense code/status areas with 1px repeating-linear-gradient scanline dividers and single-pixel pale cyan alert marks.",
    "Layer small floating terminal overlays above a sterile white field using minimal chrome highlights and almost no shadow depth."
  ],
  "visualProfile": {
    "family": "brutalist",
    "material": "ink",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": false,
    "stickerBadges": false,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Optical Shellcode Terminal 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 optical whites, soft blacks, pale cyan, and transparent acrylic as the only major visual vocabulary.",
      "Keep terminal code blocks small and quiet, with expanded tracking and clinical labels rather than theatrical hacker glow.",
      "Place at least one empty grid region with coordinates or crosshair dots so whitespace feels designed.",
      "Use manga ink lines as SVG contour scaffolds, border arcs, or cropped silhouettes that support layout structure.",
      "Make one panel visually dominant and vary section weights; avoid equal cards or repeated modular sameness.",
      "Use body tracking at -0.02em, display tracking around -0.035em, display leading near 1.12, and body leading around 1.55.",
      "Keep borders near-invisible and rely on tiny cyan ticks for system state changes.",
      "Name scenes as specific speculative tools: memory-shell calibration, prosthetic identity audit, or autonomous consciousness interface."
    ],
    "dont": [
      "Do not use saturated neon cyan, magenta, green matrix rain, RGB gradients, or nightclub cyberpunk lighting.",
      "Do not create generic dashboards, analytics cards, CRM tables, or component-library showcases.",
      "Do not fill all empty space with widgets; the sterile void is part of the philosophical tone.",
      "Do not use cartoon anime characters, fan-art panels, speech bubbles, or illustrative manga decoration.",
      "Do not round every corner; use square terminal frames with only occasional 16px acrylic overlays.",
      "Do not thicken borders beyond 1px except for sparse black contour silhouettes.",
      "Do not use heavy shadows, plastic gloss, or skeuomorphic chrome; highlights must be cold and minimal.",
      "Do not let cyan carry large surfaces; it belongs in pixels, hairlines, and terse status text only."
    ]
  }
}