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

:root {
  --background: #F7F3EA;
  --foreground: #151411;
  --card: #FFFEF8;
  --card-foreground: #151411;
  --popover: #FFFEF8;
  --popover-foreground: #151411;
  --primary: #11100E;
  --primary-foreground: #ffffff;
  --secondary: #5C6262;
  --secondary-foreground: #ffffff;
  --muted: #6B6962;
  --muted-foreground: #151411;
  --accent: #8F1E1A;
  --accent-foreground: #ffffff;
  --destructive: #8F1E1A;
  --border: #D8D1C3;
  --input: #D8D1C3;
  --ring: #8F1E1A;
  --chart-1: #11100E;
  --chart-2: #5C6262;
  --chart-3: #8F1E1A;
  --chart-4: #4D6656;
  --chart-5: #8B6A2D;
  --sidebar: #FFFEF8;
  --sidebar-foreground: #151411;
  --sidebar-primary: #11100E;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #465D6A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D8D1C3;
  --sidebar-ring: #8F1E1A;
  --radius: 0px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #11100E;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #8F1E1A;
  --accent-foreground: #ffffff;
  --destructive: #8F1E1A;
  --border: #303642;
  --input: #303642;
  --ring: #8F1E1A;
  --chart-1: #11100E;
  --chart-2: #5C6262;
  --chart-3: #8F1E1A;
  --chart-4: #4D6656;
  --chart-5: #8B6A2D;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #11100E;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #8F1E1A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #8F1E1A;
  --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 GhostPacketMetrographShadcnKit() {
  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">Ghost Packet Metrograph</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": "ghost-packet-metrograph",
  "type": "registry:theme",
  "title": "Ghost Packet Metrograph shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F3EA",
      "foreground": "#151411",
      "card": "#FFFEF8",
      "card-foreground": "#151411",
      "popover": "#FFFEF8",
      "popover-foreground": "#151411",
      "primary": "#11100E",
      "primary-foreground": "#ffffff",
      "secondary": "#5C6262",
      "secondary-foreground": "#ffffff",
      "muted": "#6B6962",
      "muted-foreground": "#151411",
      "accent": "#8F1E1A",
      "accent-foreground": "#ffffff",
      "destructive": "#8F1E1A",
      "border": "#D8D1C3",
      "input": "#D8D1C3",
      "ring": "#8F1E1A",
      "chart-1": "#11100E",
      "chart-2": "#5C6262",
      "chart-3": "#8F1E1A",
      "chart-4": "#4D6656",
      "chart-5": "#8B6A2D",
      "sidebar": "#FFFEF8",
      "sidebar-foreground": "#151411",
      "sidebar-primary": "#11100E",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#465D6A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8D1C3",
      "sidebar-ring": "#8F1E1A",
      "radius": "0px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#11100E",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#8F1E1A",
      "accent-foreground": "#ffffff",
      "destructive": "#8F1E1A",
      "border": "#303642",
      "input": "#303642",
      "ring": "#8F1E1A",
      "chart-1": "#11100E",
      "chart-2": "#5C6262",
      "chart-3": "#8F1E1A",
      "chart-4": "#4D6656",
      "chart-5": "#8B6A2D",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#11100E",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#8F1E1A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#8F1E1A",
      "radius": "0px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "ghost-packet-metrograph",
    "slug": "ghost-packet-metrograph",
    "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"
      ]
    }
  }
}

# Ghost Packet Metrograph shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `ghost-packet-metrograph`
Slug: `ghost-packet-metrograph`

## Intent

Ghost Packet Metrograph treats a metropolitan rail network as a haunted packet-switching instrument: the rider is never drawn, only inferred from route deltas, turnstile ticks, delayed timestamps, and gaps in sensor coverage. It borrows the discipline of NYCTA modular wayfinding, manga black motion grammar, and late-90s terminal telemetry without becoming a neon cyberpunk dashboard.

## 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": "#8F1E1A",
  "background": "#F7F3EA",
  "border": "#D8D1C3",
  "error": "#8F1E1A",
  "info": "#465D6A",
  "muted": "#6B6962",
  "primary": "#11100E",
  "secondary": "#5C6262",
  "success": "#4D6656",
  "surface": "#FFFEF8",
  "text": "#151411",
  "warning": "#8B6A2D"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Libre Franklin",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Archivo+Narrow:wght@500;600;700&family=Libre+Franklin:wght@400;500;600;700&family=Martian+Mono:wght@400;500;600&display=swap",
  "heading_font": "Archivo Narrow",
  "letter_spacing": "-0.02em",
  "line_height": 1.55,
  "mono_font": "Martian Mono",
  "scale_ratio": 1.25
}

## Visual character to preserve

- Tile-white page grounds are divided by oxidized grout lines using hard 1px and 3px black borders, with squared panels and no default card radius.
- Subway-route topology is drawn with orthogonal CSS grid tracks, circular route bullets, station ticks, and ghosted train-position bars clipped through panels.
- Black manga speed-line fields appear as repeating-linear-gradient vectors that cut across negative space like signal direction rather than decoration.
- Terminal telemetry uses narrow monospace microcopy, packet IDs, delayed timestamps, raster scan bands, and sparse dim-red alert pips beside service states.
- The unseen rider is represented by missing segments, reflected silhouette slivers, transparent route gaps, and labels that describe absence instead of a person.

## ShadSync visual profile

{
  "family": "brutalist",
  "material": "ink",
  "contour": "default",
  "border": "dashed",
  "underlay": false,
  "grain": true,
  "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/ghost-packet-metrograph/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: Start with tile white, black linework, and route topology before adding any accent color.; Use dim red only for exceptions, stale timestamps, vanished reads, or handoff failures.; Represent people through route traces, turnstile events, timestamps, and gaps instead of figures.; Make at least one panel structurally dominant and break the grid with a black vector field or full-bleed route line.; Use monospace telemetry for packet IDs, station codes, scan counts, and ghost logs.; Keep radii square except for route bullets and status pips.; Pair every color-coded state with text, shape, or border-weight changes for accessibility.
- Do not: Do not use green terminal rain, neon gradients, cyberpunk skyline glow, or saturated RGB accents.; Do not create three equal cards in a row or generic metric widgets unrelated to transit.; Do not illustrate anime characters, riders, agents, or hacker avatars.; Do not soften the system with glassmorphism, pill-heavy SaaS controls, or decorative shadows.; Do not use color as decoration; route colors must feel like muted diagnostics.; Do not let manga lines become random texture; they must point, divide, or imply signal motion.; Do not hide essential text in tiny raster labels below readable sizes.

## 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 GhostPacketMetrographShadcnKit() {
  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">Ghost Packet Metrograph</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 at 640px collapses to one column with horizontal strip-map sequencing; tablet at 900px keeps a two-column route/notice split; desktop at 1200px unlocks full topology.",
  "density": "High-density diagnostic clusters occupy no more than one third of a composition; the remaining field stays open, tiled, and silent to make absence legible.",
  "grid": "Desktop uses a 12-column transit-grid shell with 16px gutters and a max width of 1320px, allowing map panels to span 7-8 columns and notices to stack asymmetrically.",
  "whitespace": "Whitespace behaves like platform air and missing sensor data: large 64-96px pauses separate route regions, while station ticks and packet rows cluster at 4-12px."
}

{
  "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": "ghost-packet-metrograph",
    "name": "Ghost Packet Metrograph",
    "slug": "ghost-packet-metrograph"
  },
  "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": [
    "Tile-white page grounds are divided by oxidized grout lines using hard 1px and 3px black borders, with squared panels and no default card radius.",
    "Subway-route topology is drawn with orthogonal CSS grid tracks, circular route bullets, station ticks, and ghosted train-position bars clipped through panels.",
    "Black manga speed-line fields appear as repeating-linear-gradient vectors that cut across negative space like signal direction rather than decoration.",
    "Terminal telemetry uses narrow monospace microcopy, packet IDs, delayed timestamps, raster scan bands, and sparse dim-red alert pips beside service states.",
    "The unseen rider is represented by missing segments, reflected silhouette slivers, transparent route gaps, and labels that describe absence instead of a person."
  ],
  "visualProfile": {
    "family": "brutalist",
    "material": "ink",
    "contour": "default",
    "border": "dashed",
    "underlay": false,
    "grain": true,
    "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": "Ghost Packet Metrograph 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": [
      "Start with tile white, black linework, and route topology before adding any accent color.",
      "Use dim red only for exceptions, stale timestamps, vanished reads, or handoff failures.",
      "Represent people through route traces, turnstile events, timestamps, and gaps instead of figures.",
      "Make at least one panel structurally dominant and break the grid with a black vector field or full-bleed route line.",
      "Use monospace telemetry for packet IDs, station codes, scan counts, and ghost logs.",
      "Keep radii square except for route bullets and status pips.",
      "Pair every color-coded state with text, shape, or border-weight changes for accessibility."
    ],
    "dont": [
      "Do not use green terminal rain, neon gradients, cyberpunk skyline glow, or saturated RGB accents.",
      "Do not create three equal cards in a row or generic metric widgets unrelated to transit.",
      "Do not illustrate anime characters, riders, agents, or hacker avatars.",
      "Do not soften the system with glassmorphism, pill-heavy SaaS controls, or decorative shadows.",
      "Do not use color as decoration; route colors must feel like muted diagnostics.",
      "Do not let manga lines become random texture; they must point, divide, or imply signal motion.",
      "Do not hide essential text in tiny raster labels below readable sizes."
    ]
  }
}