White-Room Intrusion Kit

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

:root {
  --background: #F6F2EA;
  --foreground: #111111;
  --card: #EEE8DE;
  --card-foreground: #111111;
  --popover: #EEE8DE;
  --popover-foreground: #111111;
  --primary: #111111;
  --primary-foreground: #ffffff;
  --secondary: #5E5A52;
  --secondary-foreground: #ffffff;
  --muted: #777168;
  --muted-foreground: #111111;
  --accent: #12AFC4;
  --accent-foreground: #ffffff;
  --destructive: #8B2E24;
  --border: #111111;
  --input: #111111;
  --ring: #12AFC4;
  --chart-1: #111111;
  --chart-2: #5E5A52;
  --chart-3: #12AFC4;
  --chart-4: #2F6B55;
  --chart-5: #8A671A;
  --sidebar: #EEE8DE;
  --sidebar-foreground: #111111;
  --sidebar-primary: #111111;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #26717A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #111111;
  --sidebar-ring: #12AFC4;
  --radius: 0px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #111111;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #12AFC4;
  --accent-foreground: #ffffff;
  --destructive: #8B2E24;
  --border: #303642;
  --input: #303642;
  --ring: #12AFC4;
  --chart-1: #111111;
  --chart-2: #5E5A52;
  --chart-3: #12AFC4;
  --chart-4: #2F6B55;
  --chart-5: #8A671A;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #111111;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #12AFC4;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #12AFC4;
  --radius: 0px;
}

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 WhiteRoomIntrusionKitShadcnKit() {
  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">White-Room Intrusion Kit</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": "white-room-intrusion-kit",
  "type": "registry:theme",
  "title": "White-Room Intrusion Kit shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F6F2EA",
      "foreground": "#111111",
      "card": "#EEE8DE",
      "card-foreground": "#111111",
      "popover": "#EEE8DE",
      "popover-foreground": "#111111",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#5E5A52",
      "secondary-foreground": "#ffffff",
      "muted": "#777168",
      "muted-foreground": "#111111",
      "accent": "#12AFC4",
      "accent-foreground": "#ffffff",
      "destructive": "#8B2E24",
      "border": "#111111",
      "input": "#111111",
      "ring": "#12AFC4",
      "chart-1": "#111111",
      "chart-2": "#5E5A52",
      "chart-3": "#12AFC4",
      "chart-4": "#2F6B55",
      "chart-5": "#8A671A",
      "sidebar": "#EEE8DE",
      "sidebar-foreground": "#111111",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#26717A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#111111",
      "sidebar-ring": "#12AFC4",
      "radius": "0px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#12AFC4",
      "accent-foreground": "#ffffff",
      "destructive": "#8B2E24",
      "border": "#303642",
      "input": "#303642",
      "ring": "#12AFC4",
      "chart-1": "#111111",
      "chart-2": "#5E5A52",
      "chart-3": "#12AFC4",
      "chart-4": "#2F6B55",
      "chart-5": "#8A671A",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#12AFC4",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#12AFC4",
      "radius": "0px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "white-room-intrusion-kit",
    "slug": "white-room-intrusion-kit",
    "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",
        "display_letter_spacing",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}

# White-Room Intrusion Kit shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `white-room-intrusion-kit`
Slug: `white-room-intrusion-kit`

## Intent

White-Room Intrusion Kit treats security assessment software like a sealed diagnostic appliance on a clinical research bench: calm, off-white, exacting, and deliberately unheroic. Its interfaces make exploit evidence visible through sparse cyan coordinates, black schematic bones, packet rulers, and checklist apertures rather than through hacker spectacle or generic dashboards.

## 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": "#12AFC4",
  "background": "#F6F2EA",
  "border": "#111111",
  "error": "#8B2E24",
  "info": "#26717A",
  "muted": "#777168",
  "primary": "#111111",
  "secondary": "#5E5A52",
  "success": "#2F6B55",
  "surface": "#EEE8DE",
  "text": "#111111",
  "warning": "#8A671A"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Atkinson Hyperlegible",
  "display_letter_spacing": "-0.04em",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Azeret+Mono:wght@400;500;700&family=Saira+Condensed:wght@500;700&display=swap",
  "heading_font": "Saira Condensed",
  "letter_spacing": "-0.02em",
  "line_height": 1.55,
  "mono_font": "Azeret Mono",
  "scale_ratio": 1.22
}

## Visual character to preserve

- Off-white appliance panels use square corners, inset black 1px hairlines, and warm-gray offset shadows no larger than 8px to feel sealed and physical.
- Asymmetric CSS grid areas create manga-like black line structure with one dominant diagnostic bench, one narrow terminal transcript, and small isolated evidence panes.
- Cyan intrusion markers are tiny absolute-positioned pins, checksum beads, row ticks, and cursor pips limited to active exploit evidence coordinates.
- Packet dissection rulers and hairline port maps are built from repeating-linear-gradient ticks, black stems, and microtype labels rather than icons.
- Air-gapped modal frames use double black outlines, clipped corner notches, and sparse monospace captions to imply sealed white hardware shells.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "stickerBadges": false,
  "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/white-room-intrusion-kit/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 off-white, paper gray, absolute black, and one restrained cyan marker channel exactly as semantic evidence.; Name screens as specific assessment tools, exploit workbenches, packet dissection instruments, quarantine probes, or port-mapping appliances.; Build layouts from asymmetrical schematics, calibrated gutters, black rule structure, and sparse terminal panes.; Let microtype, numeric strings, checksum beads, and ruler ticks create atmosphere without decorative illustration.; Use cyan only for active exploit evidence, cursor pips, breach coordinates, and verified checksum ticks.; Keep controls square, quiet, and instrument-like with visible focus states and no browser-default styling.; Make monochrome reproduction viable by ensuring structure remains clear when cyan is removed.
- Do not: Do not use green matrix rain, neon cyberpunk cities, purple glow, hoodie hackers, skull malware, or fan-art character imagery.; Do not arrange the product as three equal SaaS cards, a generic SOC dashboard, or a KPI analytics grid.; Do not use cyan as a broad brand wash, gradient, glow, or secondary decorative line system.; Do not introduce rounded pill-heavy SaaS controls, soft pastel illustrations, emoji, or generic icon libraries.; Do not rely on color alone for status; pair every marker with labels, coordinates, position, or rule changes.; Do not fill sterile voids just because the screen feels quiet; absence is part of the instrument.

## 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 WhiteRoomIntrusionKitShadcnKit() {
  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">White-Room Intrusion Kit</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 below 640px stacks modules in source order; tablet at 768px uses two columns with the terminal below the bench; desktop at 1180px restores the asymmetrical 12-column instrument layout.",
  "density": "Alternates sterile open bench space with compact forensic notation; the largest gap is 96px and the tightest diagnostic cluster gap is 4px.",
  "grid": "Desktop uses a 12-column max-width 1320px grid with 16px calibrated gutters, spanning a dominant 7-column specimen bench, 3-column terminal rail, and 2-column evidence strip.",
  "responsive": "Preserve hairline rules and marker semantics at all sizes; reduce microtype volume on mobile but keep the diagnostic bench, exploit chain, transcript, and port map visible.",
  "whitespace": "Whitespace is treated as sterile air around evidence: large blank panel interiors are intentional and must not be filled with icons, charts, or decorative copy."
}

{
  "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": "white-room-intrusion-kit",
    "name": "White-Room Intrusion Kit",
    "slug": "white-room-intrusion-kit"
  },
  "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": [
    "Off-white appliance panels use square corners, inset black 1px hairlines, and warm-gray offset shadows no larger than 8px to feel sealed and physical.",
    "Asymmetric CSS grid areas create manga-like black line structure with one dominant diagnostic bench, one narrow terminal transcript, and small isolated evidence panes.",
    "Cyan intrusion markers are tiny absolute-positioned pins, checksum beads, row ticks, and cursor pips limited to active exploit evidence coordinates.",
    "Packet dissection rulers and hairline port maps are built from repeating-linear-gradient ticks, black stems, and microtype labels rather than icons.",
    "Air-gapped modal frames use double black outlines, clipped corner notches, and sparse monospace captions to imply sealed white hardware shells."
  ],
  "visualProfile": {
    "family": "brutalist",
    "material": "ink",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": false,
    "stickerBadges": false,
    "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": "White-Room Intrusion Kit 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 off-white, paper gray, absolute black, and one restrained cyan marker channel exactly as semantic evidence.",
      "Name screens as specific assessment tools, exploit workbenches, packet dissection instruments, quarantine probes, or port-mapping appliances.",
      "Build layouts from asymmetrical schematics, calibrated gutters, black rule structure, and sparse terminal panes.",
      "Let microtype, numeric strings, checksum beads, and ruler ticks create atmosphere without decorative illustration.",
      "Use cyan only for active exploit evidence, cursor pips, breach coordinates, and verified checksum ticks.",
      "Keep controls square, quiet, and instrument-like with visible focus states and no browser-default styling.",
      "Make monochrome reproduction viable by ensuring structure remains clear when cyan is removed."
    ],
    "dont": [
      "Do not use green matrix rain, neon cyberpunk cities, purple glow, hoodie hackers, skull malware, or fan-art character imagery.",
      "Do not arrange the product as three equal SaaS cards, a generic SOC dashboard, or a KPI analytics grid.",
      "Do not use cyan as a broad brand wash, gradient, glow, or secondary decorative line system.",
      "Do not introduce rounded pill-heavy SaaS controls, soft pastel illustrations, emoji, or generic icon libraries.",
      "Do not rely on color alone for status; pair every marker with labels, coordinates, position, or rule changes.",
      "Do not fill sterile voids just because the screen feels quiet; absence is part of the instrument."
    ]
  }
}