Ledger Paper Command Shell

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

:root {
  --background: #F4F0E8;
  --foreground: #151515;
  --card: #FFFCF5;
  --card-foreground: #151515;
  --popover: #FFFCF5;
  --popover-foreground: #151515;
  --primary: #111111;
  --primary-foreground: #ffffff;
  --secondary: #3A352F;
  --secondary-foreground: #ffffff;
  --muted: #6E675E;
  --muted-foreground: #151515;
  --accent: #00A7C8;
  --accent-foreground: #ffffff;
  --destructive: #B3261E;
  --border: #C9C0B4;
  --input: #C9C0B4;
  --ring: #00A7C8;
  --chart-1: #111111;
  --chart-2: #3A352F;
  --chart-3: #00A7C8;
  --chart-4: #247A4D;
  --chart-5: #B46A00;
  --sidebar: #FFFCF5;
  --sidebar-foreground: #151515;
  --sidebar-primary: #111111;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #006C84;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #C9C0B4;
  --sidebar-ring: #00A7C8;
  --radius: 4px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #111111;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #00A7C8;
  --accent-foreground: #ffffff;
  --destructive: #B3261E;
  --border: #303642;
  --input: #303642;
  --ring: #00A7C8;
  --chart-1: #111111;
  --chart-2: #3A352F;
  --chart-3: #00A7C8;
  --chart-4: #247A4D;
  --chart-5: #B46A00;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #111111;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #00A7C8;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #00A7C8;
  --radius: 4px;
}

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 LedgerPaperCommandShellShadcnKit() {
  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">Ledger Paper Command Shell</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": "ledger-paper-command-shell",
  "type": "registry:theme",
  "title": "Ledger Paper Command Shell shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F4F0E8",
      "foreground": "#151515",
      "card": "#FFFCF5",
      "card-foreground": "#151515",
      "popover": "#FFFCF5",
      "popover-foreground": "#151515",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#3A352F",
      "secondary-foreground": "#ffffff",
      "muted": "#6E675E",
      "muted-foreground": "#151515",
      "accent": "#00A7C8",
      "accent-foreground": "#ffffff",
      "destructive": "#B3261E",
      "border": "#C9C0B4",
      "input": "#C9C0B4",
      "ring": "#00A7C8",
      "chart-1": "#111111",
      "chart-2": "#3A352F",
      "chart-3": "#00A7C8",
      "chart-4": "#247A4D",
      "chart-5": "#B46A00",
      "sidebar": "#FFFCF5",
      "sidebar-foreground": "#151515",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#006C84",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#C9C0B4",
      "sidebar-ring": "#00A7C8",
      "radius": "4px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#00A7C8",
      "accent-foreground": "#ffffff",
      "destructive": "#B3261E",
      "border": "#303642",
      "input": "#303642",
      "ring": "#00A7C8",
      "chart-1": "#111111",
      "chart-2": "#3A352F",
      "chart-3": "#00A7C8",
      "chart-4": "#247A4D",
      "chart-5": "#B46A00",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#00A7C8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#00A7C8",
      "radius": "4px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "ledger-paper-command-shell",
    "slug": "ledger-paper-command-shell",
    "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"
      ]
    }
  }
}

# Ledger Paper Command Shell shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `ledger-paper-command-shell`
Slug: `ledger-paper-command-shell`

## Intent

Ledger Paper Command Shell is an editorial data-app language for operational software that needs to feel authored, sober, and production-ready. It borrows from newspaper ledgers, trading-room work surfaces, and modern command centers: warm paper, charcoal type, rule-line structure, and one high-chroma cyan used only where data or action must pierce the page.

## 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": "#00A7C8",
  "background": "#F4F0E8",
  "border": "#C9C0B4",
  "error": "#B3261E",
  "info": "#006C84",
  "muted": "#6E675E",
  "primary": "#111111",
  "secondary": "#3A352F",
  "success": "#247A4D",
  "surface": "#FFFCF5",
  "text": "#151515",
  "warning": "#B46A00"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Saira",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Azeret+Mono:wght@400;500;600&family=Libre+Baskerville:wght@400;700&family=Saira:ital,wght@0,400;0,500;0,600;0,700;1,400&display=swap",
  "heading_font": "Libre Baskerville",
  "letter_spacing": "-0.018em",
  "line_height": 1.52,
  "mono_font": "Azeret Mono",
  "scale_ratio": 1.22
}

## Visual character to preserve

- Use a full-height app shell divided by 1px charcoal rule lines, including a narrow left rail, a masthead strip, and an offset marginal notes column.
- Render major modules as paper sections with square corners, no decorative cards, and internal ledger rules created by border-bottom and repeating-linear-gradient rows.
- Create hierarchy through a serif editorial headline, condensed uppercase sans labels, tabular numeric mono data, and visibly different tracking values.
- Reserve the cyan accent for a thin left selection rail, chart strokes, active filter underlines, focus outlines, and one primary command button only.
- Build dense data areas with aligned baselines, vertical dividers, inline status words, and sparse amber warning marks instead of icons or badges.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "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/ledger-paper-command-shell/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 paper, charcoal, taupe rules, cyan action marks, and rare amber warnings as the complete palette for product screens.; Make at least one data surface dominant, preferably a ledger table or chart that spans more columns than supporting modules.; Set numbers in Azeret Mono with tabular alignment and keep status language textual, never dependent on color alone.; Use square or nearly square corners, flat surfaces, and visible dividers before considering elevation.; Keep cyan below roughly five percent of the screen area and attach it to active or live states only.; Provide keyboard focus as a 2px cyan outline with offset or an accent-width rule paired with text state.
- Do not: Do not use gradient backgrounds, glowing pills, pulsing dots, emoji, unrelated icon tiles, or generic SaaS hero ornaments.; Do not create three equal rounded stat cards; vary module scale and let rules rather than cards define structure.; Do not introduce extra brand colors, rainbow charts, or decorative illustrations that weaken token discipline.; Do not hide hierarchy behind low-contrast gray text; muted copy must pass accessible contrast on paper surfaces.; Do not use oversized ultra-bold headings or tight-tracked marketing slogans; titles should feel editorial and precise.; Do not round every control into pills; tabs, filters, and buttons should look rule-joined and system-native.

## 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 LedgerPaperCommandShellShadcnKit() {
  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">Ledger Paper Command Shell</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 multi-column shell; 768px tablet collapses the marginal column below the chart; 375px mobile converts rail to top tabs and stacks all sections.",
  "density": "Designed for dense operational review with clear row rhythm, generous outer margins, and compact but touch-safe controls.",
  "grid": "Desktop uses a 72px rail plus a 12-column content grid with 24px gutters and a 320px marginal column inside a max-width-free app shell.",
  "responsive": "At tablet widths, shell columns become a two-row composition; at mobile widths, controls wrap, charts simplify, and minimum tap targets remain at least 44px.",
  "whitespace": "Whitespace appears as gutters and editorial pauses around headings, not as padded cards; dense tables are balanced by one open masthead area."
}

{
  "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": "ledger-paper-command-shell",
    "name": "Ledger Paper Command Shell",
    "slug": "ledger-paper-command-shell"
  },
  "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 full-height app shell divided by 1px charcoal rule lines, including a narrow left rail, a masthead strip, and an offset marginal notes column.",
    "Render major modules as paper sections with square corners, no decorative cards, and internal ledger rules created by border-bottom and repeating-linear-gradient rows.",
    "Create hierarchy through a serif editorial headline, condensed uppercase sans labels, tabular numeric mono data, and visibly different tracking values.",
    "Reserve the cyan accent for a thin left selection rail, chart strokes, active filter underlines, focus outlines, and one primary command button only.",
    "Build dense data areas with aligned baselines, vertical dividers, inline status words, and sparse amber warning marks instead of icons or badges."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": true,
    "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": "Ledger Paper Command Shell 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 paper, charcoal, taupe rules, cyan action marks, and rare amber warnings as the complete palette for product screens.",
      "Make at least one data surface dominant, preferably a ledger table or chart that spans more columns than supporting modules.",
      "Set numbers in Azeret Mono with tabular alignment and keep status language textual, never dependent on color alone.",
      "Use square or nearly square corners, flat surfaces, and visible dividers before considering elevation.",
      "Keep cyan below roughly five percent of the screen area and attach it to active or live states only.",
      "Provide keyboard focus as a 2px cyan outline with offset or an accent-width rule paired with text state."
    ],
    "dont": [
      "Do not use gradient backgrounds, glowing pills, pulsing dots, emoji, unrelated icon tiles, or generic SaaS hero ornaments.",
      "Do not create three equal rounded stat cards; vary module scale and let rules rather than cards define structure.",
      "Do not introduce extra brand colors, rainbow charts, or decorative illustrations that weaken token discipline.",
      "Do not hide hierarchy behind low-contrast gray text; muted copy must pass accessible contrast on paper surfaces.",
      "Do not use oversized ultra-bold headings or tight-tracked marketing slogans; titles should feel editorial and precise.",
      "Do not round every control into pills; tabs, filters, and buttons should look rule-joined and system-native."
    ]
  }
}