Signal Slate Operations

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

:root {
  --background: #F2F0EA;
  --foreground: #171A1D;
  --card: #FBFAF6;
  --card-foreground: #171A1D;
  --popover: #FBFAF6;
  --popover-foreground: #171A1D;
  --primary: #167C80;
  --primary-foreground: #ffffff;
  --secondary: #20363B;
  --secondary-foreground: #ffffff;
  --muted: #656C72;
  --muted-foreground: #171A1D;
  --accent: #B96E17;
  --accent-foreground: #ffffff;
  --destructive: #A64535;
  --border: #171A1D;
  --input: #171A1D;
  --ring: #B96E17;
  --chart-1: #167C80;
  --chart-2: #20363B;
  --chart-3: #B96E17;
  --chart-4: #28745D;
  --chart-5: #B96E17;
  --sidebar: #FBFAF6;
  --sidebar-foreground: #171A1D;
  --sidebar-primary: #167C80;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #167C80;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #171A1D;
  --sidebar-ring: #B96E17;
  --radius: 16px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #167C80;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #B96E17;
  --accent-foreground: #ffffff;
  --destructive: #A64535;
  --border: #303642;
  --input: #303642;
  --ring: #B96E17;
  --chart-1: #167C80;
  --chart-2: #20363B;
  --chart-3: #B96E17;
  --chart-4: #28745D;
  --chart-5: #B96E17;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #167C80;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #B96E17;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #B96E17;
  --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 SignalSlateOperationsShadcnKit() {
  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">Signal Slate Operations</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": "signal-slate-operations",
  "type": "registry:theme",
  "title": "Signal Slate Operations shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F2F0EA",
      "foreground": "#171A1D",
      "card": "#FBFAF6",
      "card-foreground": "#171A1D",
      "popover": "#FBFAF6",
      "popover-foreground": "#171A1D",
      "primary": "#167C80",
      "primary-foreground": "#ffffff",
      "secondary": "#20363B",
      "secondary-foreground": "#ffffff",
      "muted": "#656C72",
      "muted-foreground": "#171A1D",
      "accent": "#B96E17",
      "accent-foreground": "#ffffff",
      "destructive": "#A64535",
      "border": "#171A1D",
      "input": "#171A1D",
      "ring": "#B96E17",
      "chart-1": "#167C80",
      "chart-2": "#20363B",
      "chart-3": "#B96E17",
      "chart-4": "#28745D",
      "chart-5": "#B96E17",
      "sidebar": "#FBFAF6",
      "sidebar-foreground": "#171A1D",
      "sidebar-primary": "#167C80",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#167C80",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#171A1D",
      "sidebar-ring": "#B96E17",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#167C80",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#B96E17",
      "accent-foreground": "#ffffff",
      "destructive": "#A64535",
      "border": "#303642",
      "input": "#303642",
      "ring": "#B96E17",
      "chart-1": "#167C80",
      "chart-2": "#20363B",
      "chart-3": "#B96E17",
      "chart-4": "#28745D",
      "chart-5": "#B96E17",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#167C80",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#B96E17",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#B96E17",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "signal-slate-operations",
    "slug": "signal-slate-operations",
    "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"
      ]
    }
  }
}

# Signal Slate Operations shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `signal-slate-operations`
Slug: `signal-slate-operations`

## Intent

Signal Slate Operations is a restrained enterprise-system language for keyboard-first operational screens where people monitor consequential state without being seduced by decorative dashboard theatrics. It uses layered warm-neutral surfaces, tight typographic ledgers, and two strictly semantic accents: a trustworthy teal-blue for command focus and selection, and a high-attention amber only for priority, state escalation, or irreversible command affordance.

## 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": "#B96E17",
  "background": "#F2F0EA",
  "border": "#171A1D",
  "error": "#A64535",
  "info": "#167C80",
  "muted": "#656C72",
  "primary": "#167C80",
  "secondary": "#20363B",
  "success": "#28745D",
  "surface": "#FBFAF6",
  "text": "#171A1D",
  "warning": "#B96E17"
}

Typography:

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

## Visual character to preserve

- A fixed dark command rail uses 3px semantic left-edge markers and compact uppercase section labels rather than icon-heavy navigation.
- Main content sits on stepped warm-neutral planes with one large dominant operations board and smaller inset evidence panels divided by rgba hairlines.
- Rows use ledger-style CSS grids with tabular numerals, shortcut capsules, and selected-row teal outlines instead of colorful card clusters.
- Amber appears only as a priority strip, escalation badge, or destructive command button; neutral rows never borrow the warning hue for decoration.
- Compressed headings, negative tracking, and mono numeric fields create a dispatch-console hierarchy distinct from consumer SaaS typography.

## ShadSync visual profile

{
  "family": "system",
  "material": "flat",
  "contour": "pebble",
  "border": "solid",
  "underlay": true,
  "grain": false,
  "stickerBadges": true,
  "motion": "lift",
  "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/signal-slate-operations/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 warm neutral background and surface steps to distinguish regions before adding lines or color.; Reserve teal for active focus, selected rows, executable command affordances, and informational semantic state.; Reserve amber for priority incidents, escalation controls, overdue timing, and destructive or irreversible commands.; Make one operational object visually dominant through span, density, and typographic scale.; Use mono tabular numerals for times, route codes, counts, keyboard shortcuts, and telemetry values.; Group related metadata at 4-8px and separate unrelated operational regions at 64px or more.; Keep borders near-invisible with opacity values unless a semantic focus or warning state requires emphasis.
- Do not: Do not create three equal dashboard cards or generic KPI tiles as the primary composition.; Do not use teal and amber together as decorative brand colors or illustration colors.; Do not soften the interface with arbitrary radius values, pastel shadows, emojis, or friendly mascot details.; Do not reduce important state to pale grey text; essential labels and commands must meet accessible contrast.; Do not use gradients, glassmorphism, chart confetti, or marketing-style empty-state artwork.; Do not allow body text, display headings, and data readouts to share the same typographic voice.; Do not hide keyboard shortcuts on smaller screens when the workflow depends on command execution.

## 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 SignalSlateOperationsShadcnKit() {
  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">Signal Slate Operations</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": "1440px desktop full rail and split board; 900px tablet collapses rail to a horizontal command strip and stacks evidence below; 560px mobile converts ledgers to two-column row summaries with shortcuts preserved.",
  "density": "Designed for high-stakes operational density: the main board carries many rows while side panels remain compact and subordinate.",
  "grid": "Desktop uses a 280px command rail plus a 12-column content grid with 24px gutters and a max operational width of 1480px; the dominant board spans 8 columns and the evidence stack spans 4.",
  "responsive": "Preserve the primary operational object first, then fold supporting evidence and command history below it; never hide priority, focus, or command affordances.",
  "whitespace": "Whitespace is contrastive: 4px metadata clusters, 12-16px row interiors, 32px panel padding, and 80-96px between major screen regions to pass the 8:1 rhythm test."
}

{
  "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": "signal-slate-operations",
    "name": "Signal Slate Operations",
    "slug": "signal-slate-operations"
  },
  "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 fixed dark command rail uses 3px semantic left-edge markers and compact uppercase section labels rather than icon-heavy navigation.",
    "Main content sits on stepped warm-neutral planes with one large dominant operations board and smaller inset evidence panels divided by rgba hairlines.",
    "Rows use ledger-style CSS grids with tabular numerals, shortcut capsules, and selected-row teal outlines instead of colorful card clusters.",
    "Amber appears only as a priority strip, escalation badge, or destructive command button; neutral rows never borrow the warning hue for decoration.",
    "Compressed headings, negative tracking, and mono numeric fields create a dispatch-console hierarchy distinct from consumer SaaS typography."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "pebble",
    "border": "solid",
    "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": "Signal Slate Operations 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 warm neutral background and surface steps to distinguish regions before adding lines or color.",
      "Reserve teal for active focus, selected rows, executable command affordances, and informational semantic state.",
      "Reserve amber for priority incidents, escalation controls, overdue timing, and destructive or irreversible commands.",
      "Make one operational object visually dominant through span, density, and typographic scale.",
      "Use mono tabular numerals for times, route codes, counts, keyboard shortcuts, and telemetry values.",
      "Group related metadata at 4-8px and separate unrelated operational regions at 64px or more.",
      "Keep borders near-invisible with opacity values unless a semantic focus or warning state requires emphasis."
    ],
    "dont": [
      "Do not create three equal dashboard cards or generic KPI tiles as the primary composition.",
      "Do not use teal and amber together as decorative brand colors or illustration colors.",
      "Do not soften the interface with arbitrary radius values, pastel shadows, emojis, or friendly mascot details.",
      "Do not reduce important state to pale grey text; essential labels and commands must meet accessible contrast.",
      "Do not use gradients, glassmorphism, chart confetti, or marketing-style empty-state artwork.",
      "Do not allow body text, display headings, and data readouts to share the same typographic voice.",
      "Do not hide keyboard shortcuts on smaller screens when the workflow depends on command execution."
    ]
  }
}