back to gallery
design language·chromatic-instrument-os

Chromatic Instrument OS

A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.

Download DESIGN.md

Portable DESIGN.md source of truth for most agents and apps.

the spec

specification

philosophy
summary
A premium product operating-system language where a near-white neutral shell behaves like calibrated instrumentation and strong color appears only as labeled semantic evidence, not decoration.
values
calibrated restraintsemantic chromaoperating-system claritycatalog intelligenceaccessible interaction states
anti-values
×rainbow gradients without product roles×startup blob decoration×textbook color-wheel layouts×confetti accents×neon cyberpunk spectacle
tokens
borders4 items
accent width
4px
character
warm gray hairlines with occasional clipped vertical accent bars that carry semantic state
default width
1px
style
solid
colors12 items
accent
#FFD84D
background
#F8F7F2
border
#DAD7CC
error
#F0643A
info
#3D7FC2
muted
#6E756F
primary
#1B4D8C
secondary
#9B8CFF
success
#6F9E47
surface
#FFFFFF
text
#17202A
warning
#FFD84D
motion3 items
duration
180ms
easing
cubic-bezier(.2,.8,.2,1)
philosophy
small instrument-like responses: controls lift 1px, color bars brighten, panels never bounce or spin
radii5 items
full
9999px
lg
18px
md
12px
none
0
sm
8px
shadows3 items
lg
0 24px 70px rgba(23,32,42,0.12)
md
0 12px 32px rgba(23,32,42,0.08)
sm
0 1px 2px rgba(23,32,42,0.06)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
subtle 16px measurement grid using rgba neutral hairlines only
card style
1px warm-gray border, 18px radius, restrained shadow, clipped semantic paint edge
treatment
warm near-white OS canvas with white cards and calibrated gray separators
typography8 items
base size
16px
body font
Onest
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Onest:wght@400;500;600;700;800&display=swap
heading font
Onest
letter spacing
-0.018em
line height
1.48
mono font
IBM Plex Mono
scale ratio
1.22
rules
composition

Use an OS shell: persistent navigation, compact toolbar, two-column work area, and right-side calibration rail with measured color roles.

density

Medium-high product density with generous gutters, compact rows, and no decorative empty hero space.

hierarchy

Start with neutral typography and spatial grouping; use vivid accents only for state, priority, selection, and category comparison.

signature patterns
Semantic paint rails: four-pixel vertical bars clipped into card edges and list rows to show exact status or category.Catalog collision chips: small adjacent swatches with labels and contrast numbers, never blended into gradients.Instrument focus halo: lavender outline plus lapis inner border on selected controls for accessible active state.Measured highlight wash: banana appears as translucent rule or row underlay behind important data, not as a large background.
layout
breakpoints

mobile 375px, tablet 768px, desktop 1200px, wide 1440px

grid

12-column desktop grid nested inside a fixed OS shell, collapsing to one column below tablet width.

whitespace

Whitespace is calm and instrumental: 24px panel gutters, 16px row rhythm, and large empty zones only around decision areas.

guidance
do
  • Assign every vivid hue to a semantic role before using it.
  • Keep the base shell near-white with warm neutral borders and text.
  • Use clipped paint bars, chips, focus rings, and meters for color expression.
  • Check contrast on every colored text or chip state.
avoid
  • Do not use rainbow gradients, arbitrary confetti, or decorative blobs.
  • Do not make color the background of the whole product shell.
  • Do not mix many radii or shadow styles in one screen.
  • Do not present a generic landing page or textbook color exercise.
katagami spec
# Chromatic Instrument OS

## Philosophy

A premium product operating-system language where a near-white neutral shell behaves like calibrated instrumentation and strong color appears only as labeled semantic evidence, not decoration.

### Values

- calibrated restraint
- semantic chroma
- operating-system clarity
- catalog intelligence
- accessible interaction states

### Anti-Values

- rainbow gradients without product roles
- startup blob decoration
- textbook color-wheel layouts
- confetti accents
- neon cyberpunk spectacle

### Visual Character

- Near-white shell uses a fixed chrome sidebar, quiet top bar, and hairline neutral panels with only one elevation depth.
- Sparse color appears as narrow painted tabs, meter ticks, focus rings, and status chips anchored to specific interface states.
- Cards use rectilinear Apple-clean geometry with 18px radius, 1px warm-gray borders, and clipped color swatches on one edge.
- Product hierarchy is built from dense neutral typography, small uppercase labels, and catalog-like rows rather than oversized hero marketing.
- Interactive controls expose color theory through paired accent marks: lapis for primary action, persimmon for risk, matcha for completion, lavender for selection, banana for attention.

## Tokens

### Borders

- **Accent Width**: 4px
- **Character**: warm gray hairlines with occasional clipped vertical accent bars that carry semantic state
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#FFD84D` |
| background | `#F8F7F2` |
| border | `#DAD7CC` |
| error | `#F0643A` |
| info | `#3D7FC2` |
| muted | `#6E756F` |
| primary | `#1B4D8C` |
| secondary | `#9B8CFF` |
| success | `#6F9E47` |
| surface | `#FFFFFF` |
| text | `#17202A` |
| warning | `#FFD84D` |

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(.2,.8,.2,1)
- **Philosophy**: small instrument-like responses: controls lift 1px, color bars brighten, panels never bounce or spin

### Radii

- **Full**: 9999px
- **Lg**: 18px
- **Md**: 12px
- **None**: 0
- **Sm**: 8px

### Shadows

- **Lg**: 0 24px 70px rgba(23,32,42,0.12)
- **Md**: 0 12px 32px rgba(23,32,42,0.08)
- **Sm**: 0 1px 2px rgba(23,32,42,0.06)

### Spacing

- **Base**: 8px
- **Scale**: [4,8,12,16,24,32,48,64]

### Surfaces

- **Bg Pattern**: subtle 16px measurement grid using rgba neutral hairlines only
- **Card Style**: 1px warm-gray border, 18px radius, restrained shadow, clipped semantic paint edge
- **Treatment**: warm near-white OS canvas with white cards and calibrated gray separators

### Typography

- **Base Size**: 16px
- **Body Font**: Onest
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Onest:wght@400;500;600;700;800&display=swap
- **Heading Font**: Onest
- **Letter Spacing**: -0.018em
- **Line Height**: 1.48
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.22

## Rules

### Composition

Use an OS shell: persistent navigation, compact toolbar, two-column work area, and right-side calibration rail with measured color roles.

### Density

Medium-high product density with generous gutters, compact rows, and no decorative empty hero space.

### Hierarchy

Start with neutral typography and spatial grouping; use vivid accents only for state, priority, selection, and category comparison.

### Signature Patterns

- Semantic paint rails: four-pixel vertical bars clipped into card edges and list rows to show exact status or category.
- Catalog collision chips: small adjacent swatches with labels and contrast numbers, never blended into gradients.
- Instrument focus halo: lavender outline plus lapis inner border on selected controls for accessible active state.
- Measured highlight wash: banana appears as translucent rule or row underlay behind important data, not as a large background.

## Layout

### Breakpoints

mobile 375px, tablet 768px, desktop 1200px, wide 1440px

### Grid

12-column desktop grid nested inside a fixed OS shell, collapsing to one column below tablet width.

### Whitespace

Whitespace is calm and instrumental: 24px panel gutters, 16px row rhythm, and large empty zones only around decision areas.

## Guidance

### Do

- Assign every vivid hue to a semantic role before using it.
- Keep the base shell near-white with warm neutral borders and text.
- Use clipped paint bars, chips, focus rings, and meters for color expression.
- Check contrast on every colored text or chip state.

### Don't

- Do not use rainbow gradients, arbitrary confetti, or decorative blobs.
- Do not make color the background of the whole product shell.
- Do not mix many radii or shadow styles in one screen.
- Do not present a generic landing page or textbook color exercise.
DESIGN.md
---
version: "alpha"
name: "Chromatic Instrument OS"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#FFD84D"
  background: "#F8F7F2"
  border: "#DAD7CC"
  error: "#F0643A"
  info: "#3D7FC2"
  muted: "#6E756F"
  primary: "#1B4D8C"
  secondary: "#9B8CFF"
  success: "#6F9E47"
  surface: "#FFFFFF"
  text: "#17202A"
  warning: "#FFD84D"
typography:
  headline-lg:
    fontFamily: "Onest"
    fontSize: "1.816rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.018em"
  headline-md:
    fontFamily: "Onest"
    fontSize: "1.488rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.018em"
  body-md:
    fontFamily: "Onest"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.48
    letterSpacing: "-0.018em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "18px"
  md: "12px"
  none: "0px"
  sm: "8px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#ffffff"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  card-surface:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  input-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    height: "44px"
---

# Chromatic Instrument OS

## Overview

A premium product operating-system language where a near-white neutral shell behaves like calibrated instrumentation and strong color appears only as labeled semantic evidence, not decoration.

### Values

- calibrated restraint
- semantic chroma
- operating-system clarity
- catalog intelligence
- accessible interaction states

### Anti-Values

- rainbow gradients without product roles
- startup blob decoration
- textbook color-wheel layouts
- confetti accents
- neon cyberpunk spectacle

### Visual Character

- Near-white shell uses a fixed chrome sidebar, quiet top bar, and hairline neutral panels with only one elevation depth.
- Sparse color appears as narrow painted tabs, meter ticks, focus rings, and status chips anchored to specific interface states.
- Cards use rectilinear Apple-clean geometry with 18px radius, 1px warm-gray borders, and clipped color swatches on one edge.
- Product hierarchy is built from dense neutral typography, small uppercase labels, and catalog-like rows rather than oversized hero marketing.
- Interactive controls expose color theory through paired accent marks: lapis for primary action, persimmon for risk, matcha for completion, lavender for selection, banana for attention.

## Colors

Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.

| Token | Value |
|-------|-------|
| accent | `#FFD84D` |
| background | `#F8F7F2` |
| border | `#DAD7CC` |
| error | `#F0643A` |
| info | `#3D7FC2` |
| muted | `#6E756F` |
| primary | `#1B4D8C` |
| secondary | `#9B8CFF` |
| success | `#6F9E47` |
| surface | `#FFFFFF` |
| text | `#17202A` |
| warning | `#FFD84D` |

## Typography

- **Headline-Lg**: Onest, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Onest, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Onest, 16px, weight 400, line-height 1.48.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`

### Breakpoints

mobile 375px, tablet 768px, desktop 1200px, wide 1440px

### Grid

12-column desktop grid nested inside a fixed OS shell, collapsing to one column below tablet width.

### Whitespace

Whitespace is calm and instrumental: 24px panel gutters, 16px row rhythm, and large empty zones only around decision areas.

## Elevation & Depth

### Shadows

- **Lg**: 0 24px 70px rgba(23,32,42,0.12)
- **Md**: 0 12px 32px rgba(23,32,42,0.08)
- **Sm**: 0 1px 2px rgba(23,32,42,0.06)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `18px`
- **Md**: `12px`
- **None**: `0px`
- **Sm**: `8px`

### Surfaces

- **Bg Pattern**: subtle 16px measurement grid using rgba neutral hairlines only
- **Card Style**: 1px warm-gray border, 18px radius, restrained shadow, clipped semantic paint edge
- **Treatment**: warm near-white OS canvas with white cards and calibrated gray separators

### Borders

- **Accent Width**: 4px
- **Character**: warm gray hairlines with occasional clipped vertical accent bars that carry semantic state
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use an OS shell: persistent navigation, compact toolbar, two-column work area, and right-side calibration rail with measured color roles.

### Density

Medium-high product density with generous gutters, compact rows, and no decorative empty hero space.

### Hierarchy

Start with neutral typography and spatial grouping; use vivid accents only for state, priority, selection, and category comparison.

### Signature Patterns

- Semantic paint rails: four-pixel vertical bars clipped into card edges and list rows to show exact status or category.
- Catalog collision chips: small adjacent swatches with labels and contrast numbers, never blended into gradients.
- Instrument focus halo: lavender outline plus lapis inner border on selected controls for accessible active state.
- Measured highlight wash: banana appears as translucent rule or row underlay behind important data, not as a large background.

## shadcn/ui Usage

When the target app uses shadcn/ui, copy DESIGN.md with shadcn instead of the plain DESIGN.md. It contains the same Katagami design-language source plus the shadcn/ui primitives, imports, theme variables, component recipes, and preview-shot guidance.

DESIGN.md with shadcn: `/language/en-019e4592-101b-70d1-a241-a258709f5601/DESIGN.with-shadcn.md`.

The shadcn page also exposes optional machine-readable files for automation, but the human-facing handoff is DESIGN.md with shadcn.

Install recommended primitives with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

Use these primitives in shadcn apps:
- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Implementation rule for agents: import shadcn primitives from `@/components/ui/*`, apply the generated CSS variables first, then compose the language-specific recipes from the companion MD. Katagami remains the source of truth; shadcn names are the implementation surface.

## Do's and Don'ts

- Do Assign every vivid hue to a semantic role before using it.
- Do Keep the base shell near-white with warm neutral borders and text.
- Do Use clipped paint bars, chips, focus rings, and meters for color expression.
- Do Check contrast on every colored text or chip state.
- Don't Do not use rainbow gradients, arbitrary confetti, or decorative blobs.
- Don't Do not make color the background of the whole product shell.
- Don't Do not mix many radii or shadow styles in one screen.
- Don't Do not present a generic landing page or textbook color exercise.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "chromatic-instrument-os",
  "type": "registry:theme",
  "title": "Chromatic Instrument OS shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F8F7F2",
      "foreground": "#17202A",
      "card": "#FFFFFF",
      "card-foreground": "#17202A",
      "popover": "#FFFFFF",
      "popover-foreground": "#17202A",
      "primary": "#1B4D8C",
      "primary-foreground": "#ffffff",
      "secondary": "#9B8CFF",
      "secondary-foreground": "#ffffff",
      "muted": "#6E756F",
      "muted-foreground": "#17202A",
      "accent": "#FFD84D",
      "accent-foreground": "#111111",
      "destructive": "#F0643A",
      "border": "#DAD7CC",
      "input": "#DAD7CC",
      "ring": "#FFD84D",
      "chart-1": "#1B4D8C",
      "chart-2": "#9B8CFF",
      "chart-3": "#FFD84D",
      "chart-4": "#6F9E47",
      "chart-5": "#FFD84D",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#17202A",
      "sidebar-primary": "#1B4D8C",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#3D7FC2",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#DAD7CC",
      "sidebar-ring": "#FFD84D",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1B4D8C",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#FFD84D",
      "accent-foreground": "#111111",
      "destructive": "#F0643A",
      "border": "#303642",
      "input": "#303642",
      "ring": "#FFD84D",
      "chart-1": "#1B4D8C",
      "chart-2": "#9B8CFF",
      "chart-3": "#FFD84D",
      "chart-4": "#6F9E47",
      "chart-5": "#FFD84D",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1B4D8C",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#FFD84D",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#FFD84D",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e4592-101b-70d1-a241-a258709f5601",
    "slug": "chromatic-instrument-os",
    "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"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · chromatic-instrument-os
DESIGN.md

at a glance

Palette

Typography

headline-lgOnest · 29px · 700

The quick brown fox jumps

headline-mdOnest · 24px · 600

The quick brown fox jumps

body-mdOnest · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

Components rendered with this language’s tokens — colors, type, and rounded corners as specified.

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl48px
  • 4xl64px

Shape

full9999px
lg18px
md12px
none0px
sm8px
shadcn/ui

implementation kit

needs agent-authored kitcompatibility fallback
shadcn compatibility only
The generated theme variables are available, but the polished shadcn component recipes and shots have not been authored by the Katagami agent yet.
fallbackprimitives render
Compatibility proof
Local shadcn-style primitives accept the generated theme variables.
primaryaccentsurfacemutederror
table rhythm
buttonok
cardok
inputok
recommendedcompatibility fallback

DESIGN.md with shadcn

Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.

advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #F8F7F2;
  --foreground: #17202A;
  --card: #FFFFFF;
  --card-foreground: #17202A;
  --popover: #FFFFFF;
  --popover-foreground: #17202A;
  --primary: #1B4D8C;
  --primary-foreground: #ffffff;
  --secondary: #9B8CFF;
  --secondary-foreground: #ffffff;
  --muted: #6E756F;
  --muted-foreground: #17202A;
  --accent: #FFD84D;
  --accent-foreground: #111111;
  --destructive: #F0643A;
  --border: #DAD7CC;
  --input: #DAD7CC;
  --ring: #FFD84D;
  --chart-1: #1B4D8C;
  --chart-2: #9B8CFF;
  --chart-3: #FFD84D;
  --chart-4: #6F9E47;
  --chart-5: #FFD84D;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #17202A;
  --sidebar-primary: #1B4D8C;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #3D7FC2;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #DAD7CC;
  --sidebar-ring: #FFD84D;
  --radius: 12px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #1B4D8C;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #FFD84D;
  --accent-foreground: #111111;
  --destructive: #F0643A;
  --border: #303642;
  --input: #303642;
  --ring: #FFD84D;
  --chart-1: #1B4D8C;
  --chart-2: #9B8CFF;
  --chart-3: #FFD84D;
  --chart-4: #6F9E47;
  --chart-5: #FFD84D;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #1B4D8C;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #FFD84D;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #FFD84D;
  --radius: 12px;
}
tsx starter
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 ChromaticInstrumentOsShadcnKit() {
  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 Instrument OS</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>
  );
}
theme JSONstored + verified
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "cssVars": {
    "dark": {
      "accent": "#FFD84D",
      "accent-foreground": "#111111",
      "background": "#0f1115",
      "border": "#303642",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "chart-1": "#1B4D8C",
      "chart-2": "#9B8CFF",
      "chart-3": "#FFD84D",
      "chart-4": "#6F9E47",
      "chart-5": "#FFD84D",
      "destructive": "#F0643A",
      "foreground": "#f8fafc",
      "input": "#303642",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1B4D8C",
      "primary-foreground": "#ffffff",
      "radius": "12px",
      "ring": "#FFD84D",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "sidebar": "#181b22",
      "sidebar-accent": "#FFD84D",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1B4D8C",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#FFD84D"
    },
    "light": {
      "accent": "#FFD84D",
      "accent-foreground": "#111111",
      "background": "#F8F7F2",
      "border": "#DAD7CC",
      "card": "#FFFFFF",
      "card-foreground": "#17202A",
      "chart-1": "#1B4D8C",
      "chart-2": "#9B8CFF",
      "chart-3": "#FFD84D",
      "chart-4": "#6F9E47",
      "chart-5": "#FFD84D",
      "destructive": "#F0643A",
      "foreground": "#17202A",
      "input": "#DAD7CC",
      "muted": "#6E756F",
      "muted-foreground": "#17202A",
      "popover": "#FFFFFF",
      "popover-foreground": "#17202A",
      "primary": "#1B4D8C",
      "primary-foreground": "#ffffff",
      "radius": "12px",
      "ring": "#FFD84D",
      "secondary": "#9B8CFF",
      "secondary-foreground": "#ffffff",
      "sidebar": "#FFFFFF",
      "sidebar-accent": "#3D7FC2",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#DAD7CC",
      "sidebar-foreground": "#17202A",
      "sidebar-primary": "#1B4D8C",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#FFD84D"
    },
    "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-019e4592-101b-70d1-a241-a258709f5601",
    "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-instrument-os",
    "source": "katagami"
  },
  "name": "chromatic-instrument-os",
  "title": "Chromatic Instrument OS shadcn Theme",
  "type": "registry:theme"
}
component recipescompatibility fallback
# Chromatic Instrument OS shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4592-101b-70d1-a241-a258709f5601`
Slug: `chromatic-instrument-os`

## Intent

A premium product operating-system language where a near-white neutral shell behaves like calibrated instrumentation and strong color appears only as labeled semantic evidence, not decoration.

## 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": "#FFD84D",
  "background": "#F8F7F2",
  "border": "#DAD7CC",
  "error": "#F0643A",
  "info": "#3D7FC2",
  "muted": "#6E756F",
  "primary": "#1B4D8C",
  "secondary": "#9B8CFF",
  "success": "#6F9E47",
  "surface": "#FFFFFF",
  "text": "#17202A",
  "warning": "#FFD84D"
}

Typography:

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

## Visual character to preserve

- Near-white shell uses a fixed chrome sidebar, quiet top bar, and hairline neutral panels with only one elevation depth.
- Sparse color appears as narrow painted tabs, meter ticks, focus rings, and status chips anchored to specific interface states.
- Cards use rectilinear Apple-clean geometry with 18px radius, 1px warm-gray borders, and clipped color swatches on one edge.
- Product hierarchy is built from dense neutral typography, small uppercase labels, and catalog-like rows rather than oversized hero marketing.
- Interactive controls expose color theory through paired accent marks: lapis for primary action, persimmon for risk, matcha for completion, lavender for selection, banana for attention.

## ShadSync visual profile

{
  "family": "system",
  "material": "flat",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": false,
  "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/chromatic-instrument-os/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: Assign every vivid hue to a semantic role before using it.; Keep the base shell near-white with warm neutral borders and text.; Use clipped paint bars, chips, focus rings, and meters for color expression.; Check contrast on every colored text or chip state.
- Do not: Do not use rainbow gradients, arbitrary confetti, or decorative blobs.; Do not make color the background of the whole product shell.; Do not mix many radii or shadow styles in one screen.; Do not present a generic landing page or textbook color exercise.

## 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 ChromaticInstrumentOsShadcnKit() {
  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 Instrument OS</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, wide 1440px",
  "grid": "12-column desktop grid nested inside a fixed OS shell, collapsing to one column below tablet width.",
  "whitespace": "Whitespace is calm and instrumental: 24px panel gutters, 16px row rhythm, and large empty zones only around decision areas."
}
preview shotscompatibility fallback
{
  "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-019e4592-101b-70d1-a241-a258709f5601",
    "name": "Chromatic Instrument OS",
    "slug": "chromatic-instrument-os"
  },
  "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": [
    "Near-white shell uses a fixed chrome sidebar, quiet top bar, and hairline neutral panels with only one elevation depth.",
    "Sparse color appears as narrow painted tabs, meter ticks, focus rings, and status chips anchored to specific interface states.",
    "Cards use rectilinear Apple-clean geometry with 18px radius, 1px warm-gray borders, and clipped color swatches on one edge.",
    "Product hierarchy is built from dense neutral typography, small uppercase labels, and catalog-like rows rather than oversized hero marketing.",
    "Interactive controls expose color theory through paired accent marks: lapis for primary action, persimmon for risk, matcha for completion, lavender for selection, banana for attention."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "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 Instrument OS 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": [
      "Assign every vivid hue to a semantic role before using it.",
      "Keep the base shell near-white with warm neutral borders and text.",
      "Use clipped paint bars, chips, focus rings, and meters for color expression.",
      "Check contrast on every colored text or chip state."
    ],
    "dont": [
      "Do not use rainbow gradients, arbitrary confetti, or decorative blobs.",
      "Do not make color the background of the whole product shell.",
      "Do not mix many radii or shadow styles in one screen.",
      "Do not present a generic landing page or textbook color exercise."
    ]
  }
}
related

More like this