Graphite Cockpit Notation

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

:root {
  --background: #101113;
  --foreground: #E8E0D2;
  --card: #181A1D;
  --card-foreground: #E8E0D2;
  --popover: #181A1D;
  --popover-foreground: #E8E0D2;
  --primary: #D8D3C7;
  --primary-foreground: #111111;
  --secondary: #8D9496;
  --secondary-foreground: #ffffff;
  --muted: #8F918C;
  --muted-foreground: #E8E0D2;
  --accent: #C8753A;
  --accent-foreground: #ffffff;
  --destructive: #B66345;
  --border: #E8E0D21A;
  --input: #E8E0D21A;
  --ring: #C8753A;
  --chart-1: #D8D3C7;
  --chart-2: #8D9496;
  --chart-3: #C8753A;
  --chart-4: #7F9A8B;
  --chart-5: #C8753A;
  --sidebar: #181A1D;
  --sidebar-foreground: #E8E0D2;
  --sidebar-primary: #D8D3C7;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #B8D8E8;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #E8E0D21A;
  --sidebar-ring: #C8753A;
  --radius: 16px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #D8D3C7;
  --primary-foreground: #111111;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #C8753A;
  --accent-foreground: #ffffff;
  --destructive: #B66345;
  --border: #303642;
  --input: #303642;
  --ring: #C8753A;
  --chart-1: #D8D3C7;
  --chart-2: #8D9496;
  --chart-3: #C8753A;
  --chart-4: #7F9A8B;
  --chart-5: #C8753A;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #D8D3C7;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #C8753A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #C8753A;
  --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 GraphiteCockpitNotationShadcnKit() {
  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">Graphite Cockpit Notation</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": "graphite-cockpit-notation",
  "type": "registry:theme",
  "title": "Graphite Cockpit Notation shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#101113",
      "foreground": "#E8E0D2",
      "card": "#181A1D",
      "card-foreground": "#E8E0D2",
      "popover": "#181A1D",
      "popover-foreground": "#E8E0D2",
      "primary": "#D8D3C7",
      "primary-foreground": "#111111",
      "secondary": "#8D9496",
      "secondary-foreground": "#ffffff",
      "muted": "#8F918C",
      "muted-foreground": "#E8E0D2",
      "accent": "#C8753A",
      "accent-foreground": "#ffffff",
      "destructive": "#B66345",
      "border": "#E8E0D21A",
      "input": "#E8E0D21A",
      "ring": "#C8753A",
      "chart-1": "#D8D3C7",
      "chart-2": "#8D9496",
      "chart-3": "#C8753A",
      "chart-4": "#7F9A8B",
      "chart-5": "#C8753A",
      "sidebar": "#181A1D",
      "sidebar-foreground": "#E8E0D2",
      "sidebar-primary": "#D8D3C7",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#B8D8E8",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#E8E0D21A",
      "sidebar-ring": "#C8753A",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#D8D3C7",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#C8753A",
      "accent-foreground": "#ffffff",
      "destructive": "#B66345",
      "border": "#303642",
      "input": "#303642",
      "ring": "#C8753A",
      "chart-1": "#D8D3C7",
      "chart-2": "#8D9496",
      "chart-3": "#C8753A",
      "chart-4": "#7F9A8B",
      "chart-5": "#C8753A",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#D8D3C7",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#C8753A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#C8753A",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e05d0-49f2-7b61-a2dd-8002831aaf79",
    "slug": "graphite-cockpit-notation",
    "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"
      ],
      "components": [
        "cockpit_panel",
        "fault_callout",
        "manga_rule"
      ],
      "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"
      ]
    }
  }
}

# Graphite Cockpit Notation shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e05d0-49f2-7b61-a2dd-8002831aaf79`
Slug: `graphite-cockpit-notation`

## Intent

Graphite Cockpit Notation treats the interface as a pilot-seat translation layer: the user is not browsing data, but looking through diagnostic glass at a machine whose body has been pulled apart for survival decisions. The language borrows from mecha maintenance manuals, flight symbology, manga panel structure, and turn-of-the-millennium hardware labels, then removes spectacle until only quiet operational unease remains.

## 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": "#C8753A",
  "background": "#101113",
  "border": "#E8E0D21A",
  "error": "#B66345",
  "info": "#B8D8E8",
  "muted": "#8F918C",
  "primary": "#D8D3C7",
  "secondary": "#8D9496",
  "success": "#7F9A8B",
  "surface": "#181A1D",
  "text": "#E8E0D2",
  "warning": "#C8753A"
}

Typography:

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

## Visual character to preserve

- A matte graphite page field uses radial soot and carbon-black panels, with off-white 1px manga construction lines forming asymmetric crop frames instead of rounded cards.
- Pale blue-white HUD geometry appears at low opacity as thin reticles, horizon rules, bracketed targeting marks, and viewport arcs positioned behind content rather than as glowing decoration.
- Small controlled orange callouts are restricted to numbered mechanical faults, hinge labels, warning arrows, and embodied pilot notes, never broad brand fills or gradients.
- Exploded machine anatomy is expressed through cropped SVG limb fragments, cutaway rails, leader lines, depth shadows, and sparse labels arranged like a maintenance overlay viewed from the seat.
- Interface motifs use restrained Y2K hardware language: tabular LCD strips, monospaced terminal snippets, beveled hairline seams, grouped cockpit controls, and diagnostic status rails.

## ShadSync visual profile

{
  "family": "brutalist",
  "material": "ink",
  "contour": "default",
  "border": "dashed",
  "underlay": false,
  "grain": false,
  "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/graphite-cockpit-notation/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 matte graphite, carbon black, off-white manga rules, pale blue-white HUD overlays, calibration gray, and one restrained orange warning accent.; Build scenes around a specific machine operation, pilot workload moment, or maintenance diagnosis rather than generic data browsing.; Crop the mecha or cockpit hardware so the viewer feels seated inside an instrumented body, not looking at poster art.; Use thin construction lines, cut marks, numbered callouts, and tabular LCD values to create technical drawing depth.; Keep typography tracked tightly: display -0.04em, body -0.02em, mono labels small but legible.; Let one panel dominate and one cluster become dense; never distribute equal cards just to fill a grid.; Write terminal microcopy as system state, actuator labels, or guidance cues, not hacker phrases.; Review by removing every glow, extra color, and redundant line until the design still reads as cockpit notation.
- Do not: Do not use green matrix rain, neon cyan-magenta cyberpunk, generic hacker dashboards, or code wallpaper.; Do not create fan-art character portraits, full mecha glamour shots, or anime faces as the primary subject.; Do not use SaaS card grids, equal analytics tiles, soft pastel surfaces, or template rounded cards.; Do not clutter the HUD with dozens of glowing rings, fake charts, or unreadable microtext.; Do not let orange become a brand wash; it must remain a controlled mechanical warning/callout signal.; Do not use pure white backgrounds, bright gradients, default browser controls, or arbitrary radius mixing.; Do not publish if the thumbnail cannot be described as matte graphite plus cropped exploded hardware plus sparse orange numbered callouts.

## 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 GraphiteCockpitNotationShadcnKit() {
  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">Graphite Cockpit Notation</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 375-767px single stack; tablet 768-1079px six-column cockpit; desktop 1080px+ twelve-column asymmetry with full-bleed background arcs.",
  "density": "A dense-left / spacious-right rhythm alternates by viewport: mechanical anatomy and diagnostics cluster tightly while narrative and status zones breathe. The smallest gap is 4px and the largest section separation is 96px or more.",
  "grid": "Desktop uses a 12-column max 1280px cockpit grid with 24px gutters, a dominant 7-column viewport, a 4-column diagnostic rail, and one deliberate full-bleed arc break. Tablet collapses to 6 columns; mobile becomes a single instrument stack with the anatomy crop first.",
  "responsive": "On narrow viewports the HUD arcs become background texture, leader lines shorten, tables scroll horizontally only when necessary, and orange warnings remain visible near their associated part.",
  "whitespace": "Whitespace is graphite silence, not padding. Related labels sit 4-12px apart, panel internals use 16-24px, and unrelated cockpit zones separate by 64-128px."
}

{
  "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": "en-019e05d0-49f2-7b61-a2dd-8002831aaf79",
    "name": "Graphite Cockpit Notation",
    "slug": "graphite-cockpit-notation"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "A matte graphite page field uses radial soot and carbon-black panels, with off-white 1px manga construction lines forming asymmetric crop frames instead of rounded cards.",
    "Pale blue-white HUD geometry appears at low opacity as thin reticles, horizon rules, bracketed targeting marks, and viewport arcs positioned behind content rather than as glowing decoration.",
    "Small controlled orange callouts are restricted to numbered mechanical faults, hinge labels, warning arrows, and embodied pilot notes, never broad brand fills or gradients.",
    "Exploded machine anatomy is expressed through cropped SVG limb fragments, cutaway rails, leader lines, depth shadows, and sparse labels arranged like a maintenance overlay viewed from the seat.",
    "Interface motifs use restrained Y2K hardware language: tabular LCD strips, monospaced terminal snippets, beveled hairline seams, grouped cockpit controls, and diagnostic status rails."
  ],
  "visualProfile": {
    "family": "brutalist",
    "material": "ink",
    "contour": "default",
    "border": "dashed",
    "underlay": false,
    "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": "Graphite Cockpit Notation 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 matte graphite, carbon black, off-white manga rules, pale blue-white HUD overlays, calibration gray, and one restrained orange warning accent.",
      "Build scenes around a specific machine operation, pilot workload moment, or maintenance diagnosis rather than generic data browsing.",
      "Crop the mecha or cockpit hardware so the viewer feels seated inside an instrumented body, not looking at poster art.",
      "Use thin construction lines, cut marks, numbered callouts, and tabular LCD values to create technical drawing depth.",
      "Keep typography tracked tightly: display -0.04em, body -0.02em, mono labels small but legible.",
      "Let one panel dominate and one cluster become dense; never distribute equal cards just to fill a grid.",
      "Write terminal microcopy as system state, actuator labels, or guidance cues, not hacker phrases.",
      "Review by removing every glow, extra color, and redundant line until the design still reads as cockpit notation."
    ],
    "dont": [
      "Do not use green matrix rain, neon cyan-magenta cyberpunk, generic hacker dashboards, or code wallpaper.",
      "Do not create fan-art character portraits, full mecha glamour shots, or anime faces as the primary subject.",
      "Do not use SaaS card grids, equal analytics tiles, soft pastel surfaces, or template rounded cards.",
      "Do not clutter the HUD with dozens of glowing rings, fake charts, or unreadable microtext.",
      "Do not let orange become a brand wash; it must remain a controlled mechanical warning/callout signal.",
      "Do not use pure white backgrounds, bright gradients, default browser controls, or arbitrary radius mixing.",
      "Do not publish if the thumbnail cannot be described as matte graphite plus cropped exploded hardware plus sparse orange numbered callouts."
    ]
  }
}