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: #090A0C;
  --foreground: #E8E2D6;
  --card: #171A1E;
  --card-foreground: #E8E2D6;
  --popover: #171A1E;
  --popover-foreground: #E8E2D6;
  --primary: #E8E2D6;
  --primary-foreground: #111111;
  --secondary: #9AA0A3;
  --secondary-foreground: #ffffff;
  --muted: #858B8F;
  --muted-foreground: #E8E2D6;
  --accent: #D06A2C;
  --accent-foreground: #ffffff;
  --destructive: #D06A2C;
  --border: #E8E2D61A;
  --input: #E8E2D61A;
  --ring: #D06A2C;
  --chart-1: #E8E2D6;
  --chart-2: #9AA0A3;
  --chart-3: #D06A2C;
  --chart-4: #96A690;
  --chart-5: #C78645;
  --sidebar: #171A1E;
  --sidebar-foreground: #E8E2D6;
  --sidebar-primary: #E8E2D6;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #B9D7E6;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #E8E2D61A;
  --sidebar-ring: #D06A2C;
  --radius: 0px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #E8E2D6;
  --primary-foreground: #111111;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #D06A2C;
  --accent-foreground: #ffffff;
  --destructive: #D06A2C;
  --border: #303642;
  --input: #303642;
  --ring: #D06A2C;
  --chart-1: #E8E2D6;
  --chart-2: #9AA0A3;
  --chart-3: #D06A2C;
  --chart-4: #96A690;
  --chart-5: #C78645;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #E8E2D6;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #D06A2C;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #D06A2C;
  --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 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": "#090A0C",
      "foreground": "#E8E2D6",
      "card": "#171A1E",
      "card-foreground": "#E8E2D6",
      "popover": "#171A1E",
      "popover-foreground": "#E8E2D6",
      "primary": "#E8E2D6",
      "primary-foreground": "#111111",
      "secondary": "#9AA0A3",
      "secondary-foreground": "#ffffff",
      "muted": "#858B8F",
      "muted-foreground": "#E8E2D6",
      "accent": "#D06A2C",
      "accent-foreground": "#ffffff",
      "destructive": "#D06A2C",
      "border": "#E8E2D61A",
      "input": "#E8E2D61A",
      "ring": "#D06A2C",
      "chart-1": "#E8E2D6",
      "chart-2": "#9AA0A3",
      "chart-3": "#D06A2C",
      "chart-4": "#96A690",
      "chart-5": "#C78645",
      "sidebar": "#171A1E",
      "sidebar-foreground": "#E8E2D6",
      "sidebar-primary": "#E8E2D6",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#B9D7E6",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#E8E2D61A",
      "sidebar-ring": "#D06A2C",
      "radius": "0px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#E8E2D6",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#D06A2C",
      "accent-foreground": "#ffffff",
      "destructive": "#D06A2C",
      "border": "#303642",
      "input": "#303642",
      "ring": "#D06A2C",
      "chart-1": "#E8E2D6",
      "chart-2": "#9AA0A3",
      "chart-3": "#D06A2C",
      "chart-4": "#96A690",
      "chart-5": "#C78645",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#E8E2D6",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#D06A2C",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#D06A2C",
      "radius": "0px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "graphite-cockpit-notation",
    "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"
      ],
      "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"
      ]
    }
  }
}

# Graphite Cockpit Notation shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `graphite-cockpit-notation`
Slug: `graphite-cockpit-notation`

## Intent

Graphite Cockpit Notation turns a mecha pilot seat into a restrained graphic system: the interface is not a glowing spectacle but a mediated layer of perception, diagnostic uncertainty, and machine anatomy. It borrows from mobile-suit manuals, flight HUD human factors, black-and-white manga structure, and late-1990s hardware setup screens, then removes everything that feels like neon cyberpunk or hacker theater.

## 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": "#D06A2C",
  "background": "#090A0C",
  "border": "#E8E2D61A",
  "error": "#D06A2C",
  "info": "#B9D7E6",
  "muted": "#858B8F",
  "primary": "#E8E2D6",
  "secondary": "#9AA0A3",
  "success": "#96A690",
  "surface": "#171A1E",
  "text": "#E8E2D6",
  "warning": "#C78645"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Archivo",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Archivo:wght@400;500;600;700&family=Azeret+Mono:wght@400;500;600&family=Saira+Condensed:wght@500;600;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

- Use a carbon-black page with matte graphite panels, hard zero-radius rectangles, and near-invisible 1px rgba off-white borders instead of glossy surfaces.
- Layer pale blue-white HUD arcs, targeting reticles, short tick marks, and transparent monitor panes at low opacity over the structural layout.
- Draw exploded machine anatomy with thin off-white manga panel lines, diagonal cut leaders, numbered orange callouts, and small hinge labels.
- Set dense cockpit microcopy in monospaced uppercase strips while keeping human-readable system text in a condensed sans with mandatory negative tracking.
- Compose from the pilot-seat viewpoint: central forward aperture, side diagnostic rails, and one cropped limb or cockpit arc breaking the grid.

## ShadSync visual profile

{
  "family": "brutalist",
  "material": "ink",
  "contour": "default",
  "border": "dashed",
  "underlay": false,
  "grain": false,
  "stickerBadges": true,
  "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/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 and carbon black as the majority of the interface surface.; Make orange appear only on numbered faults, hinge labels, calibration warnings, and embodied mechanical risk.; Keep HUD marks pale blue-white, thin, low-opacity, and subordinate to text legibility.; Use off-white manga panel rules, construction lines, cut leaders, and cropped anatomy as the main decorative system.; Show a specific cockpit or maintenance product rather than a generic dashboard or component catalog.; Create asymmetry with a dominant cockpit aperture and one mechanical diagram breaking the grid.; Write terminal copy as short diagnostics, sensor states, and pilot workload labels rather than code strings.; Preserve negative tracking, compact condensed headings, and visible focus outlines.
- Do not: Do not use neon cyberpunk, saturated cyan-magenta gradients, green matrix rain, or nightclub glow.; Do not build equal SaaS cards, analytics charts, CRM tables, or startup landing-page sections.; Do not over-clutter the HUD with dozens of floating widgets; every mark needs a cockpit purpose.; Do not center fan-art characters or anime portraits; imply embodiment through controls, seat geometry, and warnings.; Do not use glossy glassmorphism, pill buttons everywhere, or friendly rounded app shells.; Do not rely on orange alone for urgent states; pair it with labels, numbers, and line-weight changes.; Do not create fake hacker code dumps, lorem terminal floods, or illegible microtext as filler.

## 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 below 720px stacks aperture, diagnostics, and anatomy while preserving callout leaders; tablet uses two columns; desktop uses asymmetric 3/6/3 rails.",
  "density": "Moderate-high cockpit density balanced by large carbon-black voids; tight 4-12px clusters are separated by 64-128px structural gaps.",
  "grid": "Desktop uses a 12-column max 1360px cockpit grid with 24px gutters, side diagnostic rails, a 6-column central aperture, and one full-bleed mechanical crop.",
  "responsive": "At narrow widths HUD arcs scale down, dense microcopy wraps into ribbons, nonessential ticks reduce opacity, and orange callouts remain text-labeled.",
  "whitespace": "Whitespace is not empty SaaS air; it is monitor darkness, blocked sensor view, and safety margin around critical symbology."
}

{
  "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": "graphite-cockpit-notation",
    "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": [
    "Use a carbon-black page with matte graphite panels, hard zero-radius rectangles, and near-invisible 1px rgba off-white borders instead of glossy surfaces.",
    "Layer pale blue-white HUD arcs, targeting reticles, short tick marks, and transparent monitor panes at low opacity over the structural layout.",
    "Draw exploded machine anatomy with thin off-white manga panel lines, diagonal cut leaders, numbered orange callouts, and small hinge labels.",
    "Set dense cockpit microcopy in monospaced uppercase strips while keeping human-readable system text in a condensed sans with mandatory negative tracking.",
    "Compose from the pilot-seat viewpoint: central forward aperture, side diagnostic rails, and one cropped limb or cockpit arc breaking the grid."
  ],
  "visualProfile": {
    "family": "brutalist",
    "material": "ink",
    "contour": "default",
    "border": "dashed",
    "underlay": false,
    "grain": false,
    "stickerBadges": true,
    "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": "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 and carbon black as the majority of the interface surface.",
      "Make orange appear only on numbered faults, hinge labels, calibration warnings, and embodied mechanical risk.",
      "Keep HUD marks pale blue-white, thin, low-opacity, and subordinate to text legibility.",
      "Use off-white manga panel rules, construction lines, cut leaders, and cropped anatomy as the main decorative system.",
      "Show a specific cockpit or maintenance product rather than a generic dashboard or component catalog.",
      "Create asymmetry with a dominant cockpit aperture and one mechanical diagram breaking the grid.",
      "Write terminal copy as short diagnostics, sensor states, and pilot workload labels rather than code strings.",
      "Preserve negative tracking, compact condensed headings, and visible focus outlines."
    ],
    "dont": [
      "Do not use neon cyberpunk, saturated cyan-magenta gradients, green matrix rain, or nightclub glow.",
      "Do not build equal SaaS cards, analytics charts, CRM tables, or startup landing-page sections.",
      "Do not over-clutter the HUD with dozens of floating widgets; every mark needs a cockpit purpose.",
      "Do not center fan-art characters or anime portraits; imply embodiment through controls, seat geometry, and warnings.",
      "Do not use glossy glassmorphism, pill buttons everywhere, or friendly rounded app shells.",
      "Do not rely on orange alone for urgent states; pair it with labels, numbers, and line-weight changes.",
      "Do not create fake hacker code dumps, lorem terminal floods, or illegible microtext as filler."
    ]
  }
}