Ledger Prism Editorial Shell

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

:root {
  --background: #FBFAF4;
  --foreground: #151411;
  --card: #FFFDF7;
  --card-foreground: #151411;
  --popover: #FFFDF7;
  --popover-foreground: #151411;
  --primary: #2F5BFF;
  --primary-foreground: #ffffff;
  --secondary: #6D5BFF;
  --secondary-foreground: #ffffff;
  --muted: #6F6A60;
  --muted-foreground: #151411;
  --accent: #2447D8;
  --accent-foreground: #ffffff;
  --destructive: #A9443B;
  --border: #151411;
  --input: #151411;
  --ring: #2447D8;
  --chart-1: #2F5BFF;
  --chart-2: #6D5BFF;
  --chart-3: #2447D8;
  --chart-4: #3F7454;
  --chart-5: #9A6A18;
  --sidebar: #FFFDF7;
  --sidebar-foreground: #151411;
  --sidebar-primary: #2F5BFF;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #2F5BFF;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #151411;
  --sidebar-ring: #2447D8;
  --radius: 16px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #2F5BFF;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #2447D8;
  --accent-foreground: #ffffff;
  --destructive: #A9443B;
  --border: #303642;
  --input: #303642;
  --ring: #2447D8;
  --chart-1: #2F5BFF;
  --chart-2: #6D5BFF;
  --chart-3: #2447D8;
  --chart-4: #3F7454;
  --chart-5: #9A6A18;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #2F5BFF;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #2447D8;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #2447D8;
  --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 LedgerPrismEditorialShellShadcnKit() {
  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 Prism Editorial 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-prism-editorial-shell",
  "type": "registry:theme",
  "title": "Ledger Prism Editorial Shell shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FBFAF4",
      "foreground": "#151411",
      "card": "#FFFDF7",
      "card-foreground": "#151411",
      "popover": "#FFFDF7",
      "popover-foreground": "#151411",
      "primary": "#2F5BFF",
      "primary-foreground": "#ffffff",
      "secondary": "#6D5BFF",
      "secondary-foreground": "#ffffff",
      "muted": "#6F6A60",
      "muted-foreground": "#151411",
      "accent": "#2447D8",
      "accent-foreground": "#ffffff",
      "destructive": "#A9443B",
      "border": "#151411",
      "input": "#151411",
      "ring": "#2447D8",
      "chart-1": "#2F5BFF",
      "chart-2": "#6D5BFF",
      "chart-3": "#2447D8",
      "chart-4": "#3F7454",
      "chart-5": "#9A6A18",
      "sidebar": "#FFFDF7",
      "sidebar-foreground": "#151411",
      "sidebar-primary": "#2F5BFF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#2F5BFF",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#151411",
      "sidebar-ring": "#2447D8",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2F5BFF",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#2447D8",
      "accent-foreground": "#ffffff",
      "destructive": "#A9443B",
      "border": "#303642",
      "input": "#303642",
      "ring": "#2447D8",
      "chart-1": "#2F5BFF",
      "chart-2": "#6D5BFF",
      "chart-3": "#2447D8",
      "chart-4": "#3F7454",
      "chart-5": "#9A6A18",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2F5BFF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#2447D8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#2447D8",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "ledger-prism-editorial-shell",
    "slug": "ledger-prism-editorial-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 Prism Editorial Shell shadcn/ui Components

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

## Intent

A paper-led editorial operations language for dense research desks where articles, sources, charts, and review commands must coexist without becoming a generic analytics dashboard. It borrows from printed production ledgers: warm neutral sheets, ink-first hierarchy, faint ruled grids, and one vivid blue-violet prism accent used only for live selection, chart emphasis, and keyboard focus.

## 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": "#2447D8",
  "background": "#FBFAF4",
  "border": "#151411",
  "error": "#A9443B",
  "info": "#2F5BFF",
  "muted": "#6F6A60",
  "primary": "#2F5BFF",
  "secondary": "#6D5BFF",
  "success": "#3F7454",
  "surface": "#FFFDF7",
  "text": "#151411",
  "warning": "#9A6A18"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Albert Sans",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Albert+Sans:wght@400;500;600;700&family=DM+Mono:wght@400;500&family=STIX+Two+Text:wght@500;600;700&display=swap",
  "heading_font": "STIX Two Text",
  "letter_spacing": "-0.02em",
  "line_height": 1.55,
  "mono_font": "DM Mono",
  "scale_ratio": 1.25
}

## Visual character to preserve

- Use a warm paper page background with ivory panels, overlaid by repeating 1px horizontal and vertical grid rules at low black opacity.
- Build the shell as an asymmetric editorial desk: narrow left rail, dense source ledger, oversized reading pane, and a compact right inspector.
- Apply ink-like hierarchy with serif display titles, sans functional body text, uppercase micro labels, and mono command hints all tracked at -0.02em or tighter.
- Limit chroma to a single blue-violet prism family used for active rows, chart bars, focus rings, and command palette selection states.
- Use flat 16px rounded paper panels with near-invisible borders and no decorative shadows except a subtle ink lift on the command palette.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": true,
  "stickerBadges": false,
  "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/ledger-prism-editorial-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 warm neutral foundations, ink text, and muted gridlines before introducing blue-violet accent color.; Make the active state visible through full outlines, square markers, text weight, and command labels, not color alone.; Keep charts to a single accent family with neutral comparison marks and directly labeled values.; Use serif display type only for editorial object titles and major reading moments; keep operational controls in the sans face.; Vary density deliberately: compact ledgers and inspectors must sit beside a calmer reading panel.; Style all buttons, inputs, tabs, progress bars, tables, and command palette items with the same ruled-paper grammar.; Maintain WCAG AA contrast for text and focus states, with body copy at 15px or larger and touch targets near 44px on mobile.; Let near-invisible borders and printed rules do separation work before shadows or filled backgrounds.
- Do not: Do not use generic SaaS metric cards, colorful dashboards, CRM layouts, or vague analytics modules.; Do not add a third accent hue; status colors should be rare and semantic, not part of the brand palette.; Do not combine one-sided colored borders with rounded panels; use a separate square marker or full outline instead.; Do not use gradients, glassmorphism, pastel panels, emoji, stickers, or faux notebook decoration.; Do not center all panels or make every card equal width and weight.; Do not rely on opacity-only hover states; include border, transform, or color shifts with clear focus treatment.; Do not shrink text below accessibility thresholds to force density.; Do not hide the grid everywhere; the muted ledger rule is the language signature.

## 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 LedgerPrismEditorialShellShadcnKit() {
  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 Prism Editorial 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": "desktop >= 1200px uses four app regions; tablet 760px-1199px collapses inspector below the reader and keeps the ledger beside it; mobile < 760px stacks rail, reader, ledger, and inspector with horizontal command chips.",
  "density": "Use dense source and command areas only when paired with a calmer editorial surface so the screen reads as a working desk rather than a wall of widgets.",
  "grid": "Desktop uses a 56px rail, a 340px ledger column, a minmax 420px editorial reading pane, and a 300px inspector inside a 24px page gutter; columns are separated by 16px gaps over a visible 64px ledger grid.",
  "responsive": "At tablet and mobile sizes, preserve the same hierarchy by moving the inspector after the reading pane, converting the rail to a top strip, and keeping tables horizontally legible through compact rows rather than shrinking text below 15px.",
  "whitespace": "Whitespace ranges from 4px row metadata gaps to 96px page-level breathing zones; the reader pane receives the largest padding while ledgers remain compact."
}

{
  "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-prism-editorial-shell",
    "name": "Ledger Prism Editorial Shell",
    "slug": "ledger-prism-editorial-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 warm paper page background with ivory panels, overlaid by repeating 1px horizontal and vertical grid rules at low black opacity.",
    "Build the shell as an asymmetric editorial desk: narrow left rail, dense source ledger, oversized reading pane, and a compact right inspector.",
    "Apply ink-like hierarchy with serif display titles, sans functional body text, uppercase micro labels, and mono command hints all tracked at -0.02em or tighter.",
    "Limit chroma to a single blue-violet prism family used for active rows, chart bars, focus rings, and command palette selection states.",
    "Use flat 16px rounded paper panels with near-invisible borders and no decorative shadows except a subtle ink lift on the command palette."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": false,
    "motion": "lift",
    "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 Prism Editorial 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 warm neutral foundations, ink text, and muted gridlines before introducing blue-violet accent color.",
      "Make the active state visible through full outlines, square markers, text weight, and command labels, not color alone.",
      "Keep charts to a single accent family with neutral comparison marks and directly labeled values.",
      "Use serif display type only for editorial object titles and major reading moments; keep operational controls in the sans face.",
      "Vary density deliberately: compact ledgers and inspectors must sit beside a calmer reading panel.",
      "Style all buttons, inputs, tabs, progress bars, tables, and command palette items with the same ruled-paper grammar.",
      "Maintain WCAG AA contrast for text and focus states, with body copy at 15px or larger and touch targets near 44px on mobile.",
      "Let near-invisible borders and printed rules do separation work before shadows or filled backgrounds."
    ],
    "dont": [
      "Do not use generic SaaS metric cards, colorful dashboards, CRM layouts, or vague analytics modules.",
      "Do not add a third accent hue; status colors should be rare and semantic, not part of the brand palette.",
      "Do not combine one-sided colored borders with rounded panels; use a separate square marker or full outline instead.",
      "Do not use gradients, glassmorphism, pastel panels, emoji, stickers, or faux notebook decoration.",
      "Do not center all panels or make every card equal width and weight.",
      "Do not rely on opacity-only hover states; include border, transform, or color shifts with clear focus treatment.",
      "Do not shrink text below accessibility thresholds to force density.",
      "Do not hide the grid everywhere; the muted ledger rule is the language signature."
    ]
  }
}