Chromatic Plate Interface

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

:root {
  --background: #F8F6F0;
  --foreground: #171715;
  --card: #FFFFFF;
  --card-foreground: #171715;
  --popover: #FFFFFF;
  --popover-foreground: #171715;
  --primary: #245BFF;
  --primary-foreground: #ffffff;
  --secondary: #FF5A3D;
  --secondary-foreground: #ffffff;
  --muted: #6E716A;
  --muted-foreground: #171715;
  --accent: #B6E547;
  --accent-foreground: #111111;
  --destructive: #B42318;
  --border: #D9D4C8;
  --input: #D9D4C8;
  --ring: #B6E547;
  --chart-1: #245BFF;
  --chart-2: #FF5A3D;
  --chart-3: #B6E547;
  --chart-4: #167A3F;
  --chart-5: #A15C00;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #171715;
  --sidebar-primary: #245BFF;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #6E56CF;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D9D4C8;
  --sidebar-ring: #B6E547;
  --radius: 14px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #245BFF;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #B6E547;
  --accent-foreground: #111111;
  --destructive: #B42318;
  --border: #303642;
  --input: #303642;
  --ring: #B6E547;
  --chart-1: #245BFF;
  --chart-2: #FF5A3D;
  --chart-3: #B6E547;
  --chart-4: #167A3F;
  --chart-5: #A15C00;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #245BFF;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #B6E547;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #B6E547;
  --radius: 14px;
}

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 ChromaticPlateInterfaceShadcnKit() {
  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">Chromatic Plate Interface</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",
  "cssVars": {
    "dark": {
      "accent": "#B6E547",
      "accent-foreground": "#111111",
      "background": "#0f1115",
      "border": "#303642",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "chart-1": "#245BFF",
      "chart-2": "#FF5A3D",
      "chart-3": "#B6E547",
      "chart-4": "#167A3F",
      "chart-5": "#A15C00",
      "destructive": "#B42318",
      "foreground": "#f8fafc",
      "input": "#303642",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#245BFF",
      "primary-foreground": "#ffffff",
      "radius": "14px",
      "ring": "#B6E547",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "sidebar": "#181b22",
      "sidebar-accent": "#B6E547",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#245BFF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#B6E547"
    },
    "light": {
      "accent": "#B6E547",
      "accent-foreground": "#111111",
      "background": "#F8F6F0",
      "border": "#D9D4C8",
      "card": "#FFFFFF",
      "card-foreground": "#171715",
      "chart-1": "#245BFF",
      "chart-2": "#FF5A3D",
      "chart-3": "#B6E547",
      "chart-4": "#167A3F",
      "chart-5": "#A15C00",
      "destructive": "#B42318",
      "foreground": "#171715",
      "input": "#D9D4C8",
      "muted": "#6E716A",
      "muted-foreground": "#171715",
      "popover": "#FFFFFF",
      "popover-foreground": "#171715",
      "primary": "#245BFF",
      "primary-foreground": "#ffffff",
      "radius": "14px",
      "ring": "#B6E547",
      "secondary": "#FF5A3D",
      "secondary-foreground": "#ffffff",
      "sidebar": "#FFFFFF",
      "sidebar-accent": "#6E56CF",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D9D4C8",
      "sidebar-foreground": "#171715",
      "sidebar-primary": "#245BFF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#B6E547"
    },
    "theme": {}
  },
  "meta": {
    "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",
    "languageId": "en-019e45e6-54d2-7b81-a5de-10a5d5ee7e7c",
    "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"
      ]
    },
    "slug": "chromatic-plate-interface",
    "source": "katagami"
  },
  "name": "chromatic-plate-interface",
  "title": "Chromatic Plate Interface shadcn Theme",
  "type": "registry:theme"
}

# Chromatic Plate Interface shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e45e6-54d2-7b81-a5de-10a5d5ee7e7c`
Slug: `chromatic-plate-interface`

## Intent

Chromatic Plate Interface is a premium product language where Apple-clean hierarchy is interrupted only by large, authored color fields that carry navigation, status, and content meaning for a color approval workflow.

## 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": "#B6E547",
  "background": "#F8F6F0",
  "border": "#D9D4C8",
  "error": "#B42318",
  "info": "#6E56CF",
  "muted": "#6E716A",
  "primary": "#245BFF",
  "secondary": "#FF5A3D",
  "success": "#167A3F",
  "surface": "#FFFFFF",
  "text": "#171715",
  "warning": "#A15C00"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Hanken Grotesk",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Azeret+Mono:wght@400;500;600&family=Bricolage+Grotesque:wght@500;600;700&family=Hanken+Grotesk:wght@400;500;600;700&display=swap",
  "heading_font": "Bricolage Grotesque",
  "letter_spacing": "-0.02em",
  "line_height": 1.55,
  "mono_font": "Azeret Mono",
  "scale_ratio": 1.25
}

## Visual character to preserve

- Large rectangular color plates use CSS grid areas as navigation, review queues, and status surfaces instead of small accent chips.
- Neutral surfaces are flat warm-white panels with one-pixel tinted borders, tiny point-grid paper texture, and no generic drop-shadow card stacks.
- Controls use a committed 14px radius geometry, inset focus rings, and color-filled active states that expand from the component body.
- Responsive layouts keep a dominant asymmetric plate beside precise list and form columns, then collapse into ordered full-width color slabs on mobile.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": true,
  "stickerBadges": true,
  "motion": "still",
  "density": "balanced",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.

### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.

### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.

### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.

### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.

## Preview shots

- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/chromatic-plate-interface/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: Make color blocks large enough to contain labels, data, controls, or product decisions.; Use complementary and tetradic pairings only when the product scene names their purpose.; Keep neutral typography, forms, and tables precise so color feels authored and premium.; Use dotted texture only as a quiet paper field, never as a square grid background.
- Do not: Do not add decorative side rails, left stripes, rainbow confetti, or small garnish accents.; Do not use color merely for badges when the structure could carry it as a region or state.; Do not create generic admin dashboards, equal metric-card rows, or textbook color-theory pages.; Do not use neon glow, gradient text, or arbitrary hue-wheel triads.

## 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 ChromaticPlateInterfaceShadcnKit() {
  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">Chromatic Plate Interface</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 375px, tablet 768px, desktop 1200px and above",
  "grid": "Desktop uses a 12-column CSS grid with a 5-column dominant plate, 4-column work queue, and 3-column inspector; mobile becomes one column with ordered slabs.",
  "whitespace": "Use a dramatic range from 8px row gaps to 64px page margins; leave neutral breathing room around every saturated plate."
}

{
  "artifact": "katagami:shadcn-preview-shots",
  "version": "preview-shots-v1",
  "generator": "katagami-ui-compatibility-projection",
  "generatedBy": "katagami-ui-projection",
  "requiresVisualProfile": true,
  "schema": "katagami:shadcn-preview-shots/renderable-v1",
  "renderable": true,
  "language": {
    "id": "en-019e45e6-54d2-7b81-a5de-10a5d5ee7e7c",
    "name": "Chromatic Plate Interface",
    "slug": "chromatic-plate-interface"
  },
  "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": [
    "Large rectangular color plates use CSS grid areas as navigation, review queues, and status surfaces instead of small accent chips.",
    "Neutral surfaces are flat warm-white panels with one-pixel tinted borders, tiny point-grid paper texture, and no generic drop-shadow card stacks.",
    "Controls use a committed 14px radius geometry, inset focus rings, and color-filled active states that expand from the component body.",
    "Responsive layouts keep a dominant asymmetric plate beside precise list and form columns, then collapse into ordered full-width color slabs on mobile."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": true,
    "motion": "still",
    "density": "balanced",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Chromatic Plate Interface 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": [
      "Make color blocks large enough to contain labels, data, controls, or product decisions.",
      "Use complementary and tetradic pairings only when the product scene names their purpose.",
      "Keep neutral typography, forms, and tables precise so color feels authored and premium.",
      "Use dotted texture only as a quiet paper field, never as a square grid background."
    ],
    "dont": [
      "Do not add decorative side rails, left stripes, rainbow confetti, or small garnish accents.",
      "Do not use color merely for badges when the structure could carry it as a region or state.",
      "Do not create generic admin dashboards, equal metric-card rows, or textbook color-theory pages.",
      "Do not use neon glow, gradient text, or arbitrary hue-wheel triads."
    ]
  }
}