Chromatic Decision Lab
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.
specification
philosophy
tokens
borders4 items
- accent width
- 2px
- character
- Cool graphite hairlines and semantic focus rings; accent borders encircle whole controls or cells, never a decorative side stripe.
- default width
- 1px
- style
- solid
colors12 items
motion3 items
- duration
- 160ms
- easing
- cubic-bezier(0.2, 0.8, 0.2, 1)
- philosophy
- Small product motions: color fields brighten, selections lift 2px, realtime cyan pulses softly, and panels never bounce or wobble.
radii5 items
- full
- 9999px
- lg
- 18px
- md
- 14px
- none
- 0
- sm
- 10px
shadows3 items
- lg
- 0 28px 70px rgba(23, 24, 28, 0.14)
- md
- 0 14px 34px rgba(23, 24, 28, 0.09)
- sm
- 0 1px 2px rgba(23, 24, 28, 0.06)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- Optional quiet radial point texture at 18px rhythm, opacity under 0.28, never square grid lines or boxed wallpaper.
- card style
- 18px rounded white panels with 1px cool border, faint inner highlight, no side rail accents, and color used as cells, badges, washes, or action surfaces.
- treatment
- Warm neutral canvas, white glass-like panels, and low-contrast graphite controls with semantic color fields embedded in the content plane.
typography8 items
- base size
- 16px
- body font
- Instrument Sans
- google fonts url
- https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Instrument+Sans:wght@400;500;600;700;800&display=swap
- heading font
- Instrument Sans
- letter spacing
- -0.018em
- line height
- 1.48
- mono font
- IBM Plex Mono
- scale ratio
- 1.22
rules
Use a product workbench composition: top command bar, left semantic token catalog, central workflow canvas, and right inspector. Each area has a real task and color carries state, ownership, or action meaning.
Moderately dense professional SaaS density with 8px rhythm, compact token chips, 44px controls, and enough negative space to keep the color exercises premium rather than playful.
Graphite text, scale, and spacing establish hierarchy first; vivid color is reserved for semantic roles, field states, active selections, data thresholds, realtime presence, and primary actions.
layout
mobile 375px, tablet 768px, desktop 1200px, wide 1440px
12-column desktop workbench with fixed 280px token catalog, flexible central canvas, and 340px inspector; tablet stacks inspector under canvas and mobile becomes a single-column task flow.
Use 8px base spacing with 24px panel padding, 32px section gaps, and 48px hero/workbench gutters so vivid color blocks have room to feel deliberate.
guidance
- Assign every vivid hue to a named semantic role and repeat it consistently across actions, states, rows, tabs, charts, and workflow steps.
- Use color as filled fields, cells, selected surfaces, focus rings, badges, and data-bearing marks with visible text labels or icons.
- Keep the foundation white, warm neutral, and graphite with exact spacing, crisp type, and restrained shadows.
- Show real SaaS workflows such as approvals, automation rules, collaboration states, realtime sync, and data operations.
- Do not use rainbow decoration, arbitrary confetti, generic startup blobs, neon gradients, or childish color stacking.
- Do not add decorative side rails, left stripes, square-grid wallpaper, textbook color-wheel pages, or template dashboard metric-card clichés.
- Do not let color appear only as garnish; it must encode action, state, data, selection, insight, ownership, or realtime behavior.
- Do not mix arbitrary corner radii or default browser controls; the 18px panel geometry and custom focus rings must remain consistent.
katagami spec
# Chromatic Decision Lab ## Philosophy A premium SaaS/product interface that treats vivid color as semantic infrastructure: actions, attention, confirmation, selection, insight, realtime presence, state, and data occupy authored fields inside a calm white and graphite operating surface. ### Values - Semantic color before decoration - Apple-clean restraint with measurable product hierarchy - Color-theory pairings used as workflow structure - Exact spacing and quiet premium materials - Production-ready token logic for states, data, and interactions ### Anti-Values - Rainbow garnish, confetti, blobs, neon cyberpunk, and ornamental color strips - Generic dashboard/admin layouts where metrics cards become the whole identity - Decorative side rails on cards, rows, buttons, or panels - Textbook color-wheel styling or square grid wallpaper ### Visual Character - White-to-warm-neutral app canvas with graphite typography, one-pixel cool borders, and subtle non-boxy dotted paper grain applied only to large quiet background areas. - Prominent semantic color fields appear as filled capsules, swatches, pills, heat cells, selection washes, and command surfaces rather than decorative rails or isolated icons. - Large rounded-rectangle workbench panels use a committed 18px geometry, soft inner borders, and measured shadows so color blocks sit inside a premium product hierarchy. - Data and workflow states use paired color roles: blue action, coral attention, lime confirmation, purple selection, yellow insight, and cyan realtime, with text labels and icons for accessibility. - Interface density is exact and catalog-like: aligned swatch rows, semantic token chips, matrix cells, and editorial whitespace create the feeling of a color laboratory inside real software. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: Cool graphite hairlines and semantic focus rings; accent borders encircle whole controls or cells, never a decorative side stripe. - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#FF6B57` | | background | `#F8F7F2` | | border | `#DDE0E7` | | error | `#D94A4A` | | info | `#1FC7E8` | | muted | `#6F737C` | | primary | `#246BFE` | | secondary | `#7A4DFF` | | success | `#78D83E` | | surface | `#FFFFFF` | | text | `#17181C` | | warning | `#FFD447` | ### Motion - **Duration**: 160ms - **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1) - **Philosophy**: Small product motions: color fields brighten, selections lift 2px, realtime cyan pulses softly, and panels never bounce or wobble. ### Radii - **Full**: 9999px - **Lg**: 18px - **Md**: 14px - **None**: 0 - **Sm**: 10px ### Shadows - **Lg**: 0 28px 70px rgba(23, 24, 28, 0.14) - **Md**: 0 14px 34px rgba(23, 24, 28, 0.09) - **Sm**: 0 1px 2px rgba(23, 24, 28, 0.06) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: Optional quiet radial point texture at 18px rhythm, opacity under 0.28, never square grid lines or boxed wallpaper. - **Card Style**: 18px rounded white panels with 1px cool border, faint inner highlight, no side rail accents, and color used as cells, badges, washes, or action surfaces. - **Treatment**: Warm neutral canvas, white glass-like panels, and low-contrast graphite controls with semantic color fields embedded in the content plane. ### Typography - **Base Size**: 16px - **Body Font**: Instrument Sans - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Instrument+Sans:wght@400;500;600;700;800&display=swap - **Heading Font**: Instrument Sans - **Letter Spacing**: -0.018em - **Line Height**: 1.48 - **Mono Font**: IBM Plex Mono - **Scale Ratio**: 1.22 ## Rules ### Composition Use a product workbench composition: top command bar, left semantic token catalog, central workflow canvas, and right inspector. Each area has a real task and color carries state, ownership, or action meaning. ### Density Moderately dense professional SaaS density with 8px rhythm, compact token chips, 44px controls, and enough negative space to keep the color exercises premium rather than playful. ### Hierarchy Graphite text, scale, and spacing establish hierarchy first; vivid color is reserved for semantic roles, field states, active selections, data thresholds, realtime presence, and primary actions. ### Signature Patterns - Semantic swatch headers pair a small mono token name with a filled color lozenge and a usage label so color is cataloged as production meaning. - Workflow cards expose state through full-surface tinted washes, colored heat cells, and whole-control focus rings instead of left stripes, ribbons, or garnish icons. - Complementary and tetradic pairings appear in operational matrices: blue-coral decision pairs, purple-yellow insight pairs, and cyan-lime realtime confirmation pairs. - Selection uses a purple halo and translucent lavender surface over the entire selected object, with a graphite label and keyboard hint to avoid relying on hue alone. - Realtime information uses cyan glow dots and micro progress tracks embedded in rows and controls, not animated sci-fi neon or background effects. ## Layout ### Breakpoints mobile 375px, tablet 768px, desktop 1200px, wide 1440px ### Grid 12-column desktop workbench with fixed 280px token catalog, flexible central canvas, and 340px inspector; tablet stacks inspector under canvas and mobile becomes a single-column task flow. ### Whitespace Use 8px base spacing with 24px panel padding, 32px section gaps, and 48px hero/workbench gutters so vivid color blocks have room to feel deliberate. ## Guidance ### Do - Assign every vivid hue to a named semantic role and repeat it consistently across actions, states, rows, tabs, charts, and workflow steps. - Use color as filled fields, cells, selected surfaces, focus rings, badges, and data-bearing marks with visible text labels or icons. - Keep the foundation white, warm neutral, and graphite with exact spacing, crisp type, and restrained shadows. - Show real SaaS workflows such as approvals, automation rules, collaboration states, realtime sync, and data operations. ### Don't - Do not use rainbow decoration, arbitrary confetti, generic startup blobs, neon gradients, or childish color stacking. - Do not add decorative side rails, left stripes, square-grid wallpaper, textbook color-wheel pages, or template dashboard metric-card clichés. - Do not let color appear only as garnish; it must encode action, state, data, selection, insight, ownership, or realtime behavior. - Do not mix arbitrary corner radii or default browser controls; the 18px panel geometry and custom focus rings must remain consistent. ### Accessibility Pair hue with text, iconography, shape, and state labels; keep interactive text contrast WCAG AA and use 2px whole-control focus rings.
DESIGN.md
---
version: "alpha"
name: "Chromatic Decision Lab"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#FF6B57"
background: "#F8F7F2"
border: "#DDE0E7"
error: "#D94A4A"
info: "#1FC7E8"
muted: "#6F737C"
primary: "#246BFE"
secondary: "#7A4DFF"
success: "#78D83E"
surface: "#FFFFFF"
text: "#17181C"
warning: "#FFD447"
typography:
headline-lg:
fontFamily: "Instrument Sans"
fontSize: "1.816rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.018em"
headline-md:
fontFamily: "Instrument Sans"
fontSize: "1.488rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.018em"
body-md:
fontFamily: "Instrument Sans"
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: "14px"
none: "0px"
sm: "10px"
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: "#000000"
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 Decision Lab
## Overview
A premium SaaS/product interface that treats vivid color as semantic infrastructure: actions, attention, confirmation, selection, insight, realtime presence, state, and data occupy authored fields inside a calm white and graphite operating surface.
### Values
- Semantic color before decoration
- Apple-clean restraint with measurable product hierarchy
- Color-theory pairings used as workflow structure
- Exact spacing and quiet premium materials
- Production-ready token logic for states, data, and interactions
### Anti-Values
- Rainbow garnish, confetti, blobs, neon cyberpunk, and ornamental color strips
- Generic dashboard/admin layouts where metrics cards become the whole identity
- Decorative side rails on cards, rows, buttons, or panels
- Textbook color-wheel styling or square grid wallpaper
### Visual Character
- White-to-warm-neutral app canvas with graphite typography, one-pixel cool borders, and subtle non-boxy dotted paper grain applied only to large quiet background areas.
- Prominent semantic color fields appear as filled capsules, swatches, pills, heat cells, selection washes, and command surfaces rather than decorative rails or isolated icons.
- Large rounded-rectangle workbench panels use a committed 18px geometry, soft inner borders, and measured shadows so color blocks sit inside a premium product hierarchy.
- Data and workflow states use paired color roles: blue action, coral attention, lime confirmation, purple selection, yellow insight, and cyan realtime, with text labels and icons for accessibility.
- Interface density is exact and catalog-like: aligned swatch rows, semantic token chips, matrix cells, and editorial whitespace create the feeling of a color laboratory inside real software.
## 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 | `#FF6B57` |
| background | `#F8F7F2` |
| border | `#DDE0E7` |
| error | `#D94A4A` |
| info | `#1FC7E8` |
| muted | `#6F737C` |
| primary | `#246BFE` |
| secondary | `#7A4DFF` |
| success | `#78D83E` |
| surface | `#FFFFFF` |
| text | `#17181C` |
| warning | `#FFD447` |
## Typography
- **Headline-Lg**: Instrument Sans, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Instrument Sans, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Instrument Sans, 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 workbench with fixed 280px token catalog, flexible central canvas, and 340px inspector; tablet stacks inspector under canvas and mobile becomes a single-column task flow.
### Whitespace
Use 8px base spacing with 24px panel padding, 32px section gaps, and 48px hero/workbench gutters so vivid color blocks have room to feel deliberate.
## Elevation & Depth
### Shadows
- **Lg**: 0 28px 70px rgba(23, 24, 28, 0.14)
- **Md**: 0 14px 34px rgba(23, 24, 28, 0.09)
- **Sm**: 0 1px 2px rgba(23, 24, 28, 0.06)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `18px`
- **Md**: `14px`
- **None**: `0px`
- **Sm**: `10px`
### Surfaces
- **Bg Pattern**: Optional quiet radial point texture at 18px rhythm, opacity under 0.28, never square grid lines or boxed wallpaper.
- **Card Style**: 18px rounded white panels with 1px cool border, faint inner highlight, no side rail accents, and color used as cells, badges, washes, or action surfaces.
- **Treatment**: Warm neutral canvas, white glass-like panels, and low-contrast graphite controls with semantic color fields embedded in the content plane.
### Borders
- **Accent Width**: 2px
- **Character**: Cool graphite hairlines and semantic focus rings; accent borders encircle whole controls or cells, never a decorative side stripe.
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Use a product workbench composition: top command bar, left semantic token catalog, central workflow canvas, and right inspector. Each area has a real task and color carries state, ownership, or action meaning.
### Density
Moderately dense professional SaaS density with 8px rhythm, compact token chips, 44px controls, and enough negative space to keep the color exercises premium rather than playful.
### Hierarchy
Graphite text, scale, and spacing establish hierarchy first; vivid color is reserved for semantic roles, field states, active selections, data thresholds, realtime presence, and primary actions.
### Signature Patterns
- Semantic swatch headers pair a small mono token name with a filled color lozenge and a usage label so color is cataloged as production meaning.
- Workflow cards expose state through full-surface tinted washes, colored heat cells, and whole-control focus rings instead of left stripes, ribbons, or garnish icons.
- Complementary and tetradic pairings appear in operational matrices: blue-coral decision pairs, purple-yellow insight pairs, and cyan-lime realtime confirmation pairs.
- Selection uses a purple halo and translucent lavender surface over the entire selected object, with a graphite label and keyboard hint to avoid relying on hue alone.
- Realtime information uses cyan glow dots and micro progress tracks embedded in rows and controls, not animated sci-fi neon or background effects.
## 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-019e45e6-e750-77f2-b8d1-d860492eb62f/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 named semantic role and repeat it consistently across actions, states, rows, tabs, charts, and workflow steps.
- Do Use color as filled fields, cells, selected surfaces, focus rings, badges, and data-bearing marks with visible text labels or icons.
- Do Keep the foundation white, warm neutral, and graphite with exact spacing, crisp type, and restrained shadows.
- Do Show real SaaS workflows such as approvals, automation rules, collaboration states, realtime sync, and data operations.
- Don't Do not use rainbow decoration, arbitrary confetti, generic startup blobs, neon gradients, or childish color stacking.
- Don't Do not add decorative side rails, left stripes, square-grid wallpaper, textbook color-wheel pages, or template dashboard metric-card clichés.
- Don't Do not let color appear only as garnish; it must encode action, state, data, selection, insight, ownership, or realtime behavior.
- Don't Do not mix arbitrary corner radii or default browser controls; the 18px panel geometry and custom focus rings must remain consistent.
### Accessibility
Pair hue with text, iconography, shape, and state labels; keep interactive text contrast WCAG AA and use 2px whole-control focus rings.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "chromatic-decision-lab",
"type": "registry:theme",
"title": "Chromatic Decision Lab shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F8F7F2",
"foreground": "#17181C",
"card": "#FFFFFF",
"card-foreground": "#17181C",
"popover": "#FFFFFF",
"popover-foreground": "#17181C",
"primary": "#246BFE",
"primary-foreground": "#ffffff",
"secondary": "#7A4DFF",
"secondary-foreground": "#ffffff",
"muted": "#6F737C",
"muted-foreground": "#17181C",
"accent": "#FF6B57",
"accent-foreground": "#ffffff",
"destructive": "#D94A4A",
"border": "#DDE0E7",
"input": "#DDE0E7",
"ring": "#FF6B57",
"chart-1": "#246BFE",
"chart-2": "#7A4DFF",
"chart-3": "#FF6B57",
"chart-4": "#78D83E",
"chart-5": "#FFD447",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#17181C",
"sidebar-primary": "#246BFE",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#1FC7E8",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#DDE0E7",
"sidebar-ring": "#FF6B57",
"radius": "14px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#246BFE",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#FF6B57",
"accent-foreground": "#ffffff",
"destructive": "#D94A4A",
"border": "#303642",
"input": "#303642",
"ring": "#FF6B57",
"chart-1": "#246BFE",
"chart-2": "#7A4DFF",
"chart-3": "#FF6B57",
"chart-4": "#78D83E",
"chart-5": "#FFD447",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#246BFE",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#FF6B57",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#FF6B57",
"radius": "14px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e45e6-e750-77f2-b8d1-d860492eb62f",
"slug": "chromatic-decision-lab",
"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"
]
}
}
}
```embodiments
at a glance
Typography
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Components
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
implementation kit
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
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #F8F7F2;
--foreground: #17181C;
--card: #FFFFFF;
--card-foreground: #17181C;
--popover: #FFFFFF;
--popover-foreground: #17181C;
--primary: #246BFE;
--primary-foreground: #ffffff;
--secondary: #7A4DFF;
--secondary-foreground: #ffffff;
--muted: #6F737C;
--muted-foreground: #17181C;
--accent: #FF6B57;
--accent-foreground: #ffffff;
--destructive: #D94A4A;
--border: #DDE0E7;
--input: #DDE0E7;
--ring: #FF6B57;
--chart-1: #246BFE;
--chart-2: #7A4DFF;
--chart-3: #FF6B57;
--chart-4: #78D83E;
--chart-5: #FFD447;
--sidebar: #FFFFFF;
--sidebar-foreground: #17181C;
--sidebar-primary: #246BFE;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #1FC7E8;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #DDE0E7;
--sidebar-ring: #FF6B57;
--radius: 14px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #246BFE;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #FF6B57;
--accent-foreground: #ffffff;
--destructive: #D94A4A;
--border: #303642;
--input: #303642;
--ring: #FF6B57;
--chart-1: #246BFE;
--chart-2: #7A4DFF;
--chart-3: #FF6B57;
--chart-4: #78D83E;
--chart-5: #FFD447;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #246BFE;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #FF6B57;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #FF6B57;
--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 ChromaticDecisionLabShadcnKit() {
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 Decision Lab</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": "#FF6B57",
"accent-foreground": "#ffffff",
"background": "#0f1115",
"border": "#303642",
"card": "#181b22",
"card-foreground": "#f8fafc",
"chart-1": "#246BFE",
"chart-2": "#7A4DFF",
"chart-3": "#FF6B57",
"chart-4": "#78D83E",
"chart-5": "#FFD447",
"destructive": "#D94A4A",
"foreground": "#f8fafc",
"input": "#303642",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#246BFE",
"primary-foreground": "#ffffff",
"radius": "14px",
"ring": "#FF6B57",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"sidebar": "#181b22",
"sidebar-accent": "#FF6B57",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#246BFE",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#FF6B57"
},
"light": {
"accent": "#FF6B57",
"accent-foreground": "#ffffff",
"background": "#F8F7F2",
"border": "#DDE0E7",
"card": "#FFFFFF",
"card-foreground": "#17181C",
"chart-1": "#246BFE",
"chart-2": "#7A4DFF",
"chart-3": "#FF6B57",
"chart-4": "#78D83E",
"chart-5": "#FFD447",
"destructive": "#D94A4A",
"foreground": "#17181C",
"input": "#DDE0E7",
"muted": "#6F737C",
"muted-foreground": "#17181C",
"popover": "#FFFFFF",
"popover-foreground": "#17181C",
"primary": "#246BFE",
"primary-foreground": "#ffffff",
"radius": "14px",
"ring": "#FF6B57",
"secondary": "#7A4DFF",
"secondary-foreground": "#ffffff",
"sidebar": "#FFFFFF",
"sidebar-accent": "#1FC7E8",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#DDE0E7",
"sidebar-foreground": "#17181C",
"sidebar-primary": "#246BFE",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#FF6B57"
},
"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-e750-77f2-b8d1-d860492eb62f",
"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-decision-lab",
"source": "katagami"
},
"name": "chromatic-decision-lab",
"title": "Chromatic Decision Lab shadcn Theme",
"type": "registry:theme"
}
# Chromatic Decision Lab shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e45e6-e750-77f2-b8d1-d860492eb62f`
Slug: `chromatic-decision-lab`
## Intent
A premium SaaS/product interface that treats vivid color as semantic infrastructure: actions, attention, confirmation, selection, insight, realtime presence, state, and data occupy authored fields inside a calm white and graphite operating surface.
## 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": "#FF6B57",
"background": "#F8F7F2",
"border": "#DDE0E7",
"error": "#D94A4A",
"info": "#1FC7E8",
"muted": "#6F737C",
"primary": "#246BFE",
"secondary": "#7A4DFF",
"success": "#78D83E",
"surface": "#FFFFFF",
"text": "#17181C",
"warning": "#FFD447"
}
Typography:
{
"base_size": "16px",
"body_font": "Instrument Sans",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Instrument+Sans:wght@400;500;600;700;800&display=swap",
"heading_font": "Instrument Sans",
"letter_spacing": "-0.018em",
"line_height": 1.48,
"mono_font": "IBM Plex Mono",
"scale_ratio": 1.22
}
## Visual character to preserve
- White-to-warm-neutral app canvas with graphite typography, one-pixel cool borders, and subtle non-boxy dotted paper grain applied only to large quiet background areas.
- Prominent semantic color fields appear as filled capsules, swatches, pills, heat cells, selection washes, and command surfaces rather than decorative rails or isolated icons.
- Large rounded-rectangle workbench panels use a committed 18px geometry, soft inner borders, and measured shadows so color blocks sit inside a premium product hierarchy.
- Data and workflow states use paired color roles: blue action, coral attention, lime confirmation, purple selection, yellow insight, and cyan realtime, with text labels and icons for accessibility.
- Interface density is exact and catalog-like: aligned swatch rows, semantic token chips, matrix cells, and editorial whitespace create the feeling of a color laboratory inside real software.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"border": "solid",
"underlay": false,
"grain": true,
"stickerBadges": true,
"motion": "lift",
"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-decision-lab/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 named semantic role and repeat it consistently across actions, states, rows, tabs, charts, and workflow steps.; Use color as filled fields, cells, selected surfaces, focus rings, badges, and data-bearing marks with visible text labels or icons.; Keep the foundation white, warm neutral, and graphite with exact spacing, crisp type, and restrained shadows.; Show real SaaS workflows such as approvals, automation rules, collaboration states, realtime sync, and data operations.
- Do not: Do not use rainbow decoration, arbitrary confetti, generic startup blobs, neon gradients, or childish color stacking.; Do not add decorative side rails, left stripes, square-grid wallpaper, textbook color-wheel pages, or template dashboard metric-card clichés.; Do not let color appear only as garnish; it must encode action, state, data, selection, insight, ownership, or realtime behavior.; Do not mix arbitrary corner radii or default browser controls; the 18px panel geometry and custom focus rings must remain consistent.
## 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 ChromaticDecisionLabShadcnKit() {
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 Decision Lab</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 workbench with fixed 280px token catalog, flexible central canvas, and 340px inspector; tablet stacks inspector under canvas and mobile becomes a single-column task flow.",
"whitespace": "Use 8px base spacing with 24px panel padding, 32px section gaps, and 48px hero/workbench gutters so vivid color blocks have room to feel deliberate."
}
{
"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-e750-77f2-b8d1-d860492eb62f",
"name": "Chromatic Decision Lab",
"slug": "chromatic-decision-lab"
},
"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-to-warm-neutral app canvas with graphite typography, one-pixel cool borders, and subtle non-boxy dotted paper grain applied only to large quiet background areas.",
"Prominent semantic color fields appear as filled capsules, swatches, pills, heat cells, selection washes, and command surfaces rather than decorative rails or isolated icons.",
"Large rounded-rectangle workbench panels use a committed 18px geometry, soft inner borders, and measured shadows so color blocks sit inside a premium product hierarchy.",
"Data and workflow states use paired color roles: blue action, coral attention, lime confirmation, purple selection, yellow insight, and cyan realtime, with text labels and icons for accessibility.",
"Interface density is exact and catalog-like: aligned swatch rows, semantic token chips, matrix cells, and editorial whitespace create the feeling of a color laboratory inside real software."
],
"visualProfile": {
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"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 Decision Lab 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 named semantic role and repeat it consistently across actions, states, rows, tabs, charts, and workflow steps.",
"Use color as filled fields, cells, selected surfaces, focus rings, badges, and data-bearing marks with visible text labels or icons.",
"Keep the foundation white, warm neutral, and graphite with exact spacing, crisp type, and restrained shadows.",
"Show real SaaS workflows such as approvals, automation rules, collaboration states, realtime sync, and data operations."
],
"dont": [
"Do not use rainbow decoration, arbitrary confetti, generic startup blobs, neon gradients, or childish color stacking.",
"Do not add decorative side rails, left stripes, square-grid wallpaper, textbook color-wheel pages, or template dashboard metric-card clichés.",
"Do not let color appear only as garnish; it must encode action, state, data, selection, insight, ownership, or realtime behavior.",
"Do not mix arbitrary corner radii or default browser controls; the 18px panel geometry and custom focus rings must remain consistent."
]
}
}