Chromatic Route System

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

:root {
  --background: #FAFAF7;
  --foreground: #171A20;
  --card: #FFFFFF;
  --card-foreground: #171A20;
  --popover: #FFFFFF;
  --popover-foreground: #171A20;
  --primary: #245CFF;
  --primary-foreground: #ffffff;
  --secondary: #13A56F;
  --secondary-foreground: #ffffff;
  --muted: #6C7280;
  --muted-foreground: #171A20;
  --accent: #F6C945;
  --accent-foreground: #111111;
  --destructive: #E5484D;
  --border: #DFE2E7;
  --input: #DFE2E7;
  --ring: #F6C945;
  --chart-1: #245CFF;
  --chart-2: #13A56F;
  --chart-3: #F6C945;
  --chart-4: #13A56F;
  --chart-5: #F2A900;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #171A20;
  --sidebar-primary: #245CFF;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #245CFF;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #DFE2E7;
  --sidebar-ring: #F6C945;
  --radius: 16px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #245CFF;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #F6C945;
  --accent-foreground: #111111;
  --destructive: #E5484D;
  --border: #303642;
  --input: #303642;
  --ring: #F6C945;
  --chart-1: #245CFF;
  --chart-2: #13A56F;
  --chart-3: #F6C945;
  --chart-4: #13A56F;
  --chart-5: #F2A900;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #245CFF;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #F6C945;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #F6C945;
  --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 ChromaticRouteSystemShadcnKit() {
  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 Route System</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": "#F6C945",
      "accent-foreground": "#111111",
      "background": "#0f1115",
      "border": "#303642",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "chart-1": "#245CFF",
      "chart-2": "#13A56F",
      "chart-3": "#F6C945",
      "chart-4": "#13A56F",
      "chart-5": "#F2A900",
      "destructive": "#E5484D",
      "foreground": "#f8fafc",
      "input": "#303642",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#245CFF",
      "primary-foreground": "#ffffff",
      "radius": "16px",
      "ring": "#F6C945",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "sidebar": "#181b22",
      "sidebar-accent": "#F6C945",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#245CFF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#F6C945"
    },
    "light": {
      "accent": "#F6C945",
      "accent-foreground": "#111111",
      "background": "#FAFAF7",
      "border": "#DFE2E7",
      "card": "#FFFFFF",
      "card-foreground": "#171A20",
      "chart-1": "#245CFF",
      "chart-2": "#13A56F",
      "chart-3": "#F6C945",
      "chart-4": "#13A56F",
      "chart-5": "#F2A900",
      "destructive": "#E5484D",
      "foreground": "#171A20",
      "input": "#DFE2E7",
      "muted": "#6C7280",
      "muted-foreground": "#171A20",
      "popover": "#FFFFFF",
      "popover-foreground": "#171A20",
      "primary": "#245CFF",
      "primary-foreground": "#ffffff",
      "radius": "16px",
      "ring": "#F6C945",
      "secondary": "#13A56F",
      "secondary-foreground": "#ffffff",
      "sidebar": "#FFFFFF",
      "sidebar-accent": "#245CFF",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#DFE2E7",
      "sidebar-foreground": "#171A20",
      "sidebar-primary": "#245CFF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#F6C945"
    },
    "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-019e464b-0c6d-72c3-b9da-ae9e75171a16",
    "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-route-system",
    "source": "katagami"
  },
  "name": "chromatic-route-system",
  "title": "Chromatic Route System shadcn Theme",
  "type": "registry:theme"
}

# Chromatic Route System shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e464b-0c6d-72c3-b9da-ae9e75171a16`
Slug: `chromatic-route-system`

## Intent

Chromatic Route System treats color as a compact routing layer for premium product software: a mostly white interface where a few memorable hues define domain, priority, risk, and next action instead of decorating generic cards.

## 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": "#F6C945",
  "background": "#FAFAF7",
  "border": "#DFE2E7",
  "error": "#E5484D",
  "info": "#245CFF",
  "muted": "#6C7280",
  "primary": "#245CFF",
  "secondary": "#13A56F",
  "success": "#13A56F",
  "surface": "#FFFFFF",
  "text": "#171A20",
  "warning": "#F2A900"
}

Typography:

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

## Visual character to preserve

- White and warm-neutral canvases use large asymmetric CSS grid regions with one oversized workflow plane and several smaller decision artifacts, never equal three-card rows.
- Color appears as filled route capsules, soft destination halos, status rings, and selected-tab fields rather than decorative side rails or stripes on cards.
- Panels use a committed 24px geometry with 1px warm gray borders, low blurred shadows, and inset tinted planes reserved for active workflow states.
- Typography pairs Onest for calm product headings with Source Sans 3 for dense readable body copy and IBM Plex Mono for route codes, giving hierarchy more than size changes.
- Micro-interactions slide elements along a route axis with colored focus rings and destination glow changes instead of generic opacity fades.

## ShadSync visual profile

{
  "family": "system",
  "material": "flat",
  "contour": "pebble",
  "border": "solid",
  "underlay": false,
  "grain": false,
  "stickerBadges": false,
  "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/chromatic-route-system/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 color to encode product area, workflow route, priority, risk, or interaction state with a clear legend.; Keep the base white or warm neutral and let one active route color dominate each scene.; Use route capsules, halos, rings, and selected fields consistently across controls and data.; Make specific product scenes where labels and states prove the color architecture.
- Do not: Do not use rainbow palettes, arbitrary color variety, confetti, startup blobs, or neon cyberpunk effects.; Do not put decorative left rails, side stripes, or stripe accents on cards, buttons, rows, or panels.; Do not use square-grid backgrounds, generic dashboards, equal card rows, or component-catalog scenes.; Do not let semantic status colors replace the stronger structural route system.

## 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 ChromaticRouteSystemShadcnKit() {
  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 Route System</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 and up uses nav, route plane, and inspector; tablet stacks inspector below the route plane; mobile collapses navigation into top route chips and single-column cards.",
  "grid": "CSS grid with 12 abstract columns for placement only; no visible square grid texture or repeated background grid is allowed. The desktop shell uses a 280px navigation/context column plus a flexible route plane and inspector.",
  "whitespace": "Large 48-64px outer spacing frames the product, while related labels, route chips, and fields use 6-12px proximity to make relationships obvious."
}

{
  "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-019e464b-0c6d-72c3-b9da-ae9e75171a16",
    "name": "Chromatic Route System",
    "slug": "chromatic-route-system"
  },
  "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": [
    "White and warm-neutral canvases use large asymmetric CSS grid regions with one oversized workflow plane and several smaller decision artifacts, never equal three-card rows.",
    "Color appears as filled route capsules, soft destination halos, status rings, and selected-tab fields rather than decorative side rails or stripes on cards.",
    "Panels use a committed 24px geometry with 1px warm gray borders, low blurred shadows, and inset tinted planes reserved for active workflow states.",
    "Typography pairs Onest for calm product headings with Source Sans 3 for dense readable body copy and IBM Plex Mono for route codes, giving hierarchy more than size changes.",
    "Micro-interactions slide elements along a route axis with colored focus rings and destination glow changes instead of generic opacity fades."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "pebble",
    "border": "solid",
    "underlay": false,
    "grain": false,
    "stickerBadges": false,
    "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": "Chromatic Route System 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 color to encode product area, workflow route, priority, risk, or interaction state with a clear legend.",
      "Keep the base white or warm neutral and let one active route color dominate each scene.",
      "Use route capsules, halos, rings, and selected fields consistently across controls and data.",
      "Make specific product scenes where labels and states prove the color architecture."
    ],
    "dont": [
      "Do not use rainbow palettes, arbitrary color variety, confetti, startup blobs, or neon cyberpunk effects.",
      "Do not put decorative left rails, side stripes, or stripe accents on cards, buttons, rows, or panels.",
      "Do not use square-grid backgrounds, generic dashboards, equal card rows, or component-catalog scenes.",
      "Do not let semantic status colors replace the stronger structural route system."
    ]
  }
}