Chromatic Field Product System
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
- borders are separators and touch targets; accent color appears as full fields, paired chips, or rings rather than one-sided stripes
- default width
- 1px
- style
- solid with translucent warm-neutral color or focused blue ring
colors12 items
motion3 items
- duration
- 180ms
- easing
- cubic-bezier(0.2, 0.8, 0.2, 1)
- philosophy
- color fields translate and saturate on touch while panels stay calm; no bounce, no layout jank, no decorative glow
radii5 items
- full
- 9999px
- lg
- 26px
- md
- 18px
- none
- 0
- sm
- 10px
shadows3 items
- lg
- 0 28px 80px rgba(49,87,246,0.12), 0 18px 48px rgba(55,47,33,0.10)
- md
- 0 18px 42px rgba(55,47,33,0.10), 0 2px 8px rgba(55,47,33,0.05)
- sm
- 0 1px 2px rgba(24,25,21,0.06), inset 0 0 0 1px rgba(255,255,255,0.55)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- subtle scattered point-grid texture at low opacity; no square-grid backgrounds and no decorative side rails
- card style
- single-layer ivory cards with 18px or 26px committed radius, hairline warm border, no nested card wrappers, and integrated color-field headers
- treatment
- warm neutral canvas with ivory panels, faint non-boxy point texture, and vivid matte color fields used as active planes
typography8 items
- base size
- 16px
- body font
- Hanken Grotesk
- google fonts url
- https://fonts.googleapis.com/css2?family=Hanken+Grotesk:wght@400;500;600;700&family=Onest:wght@500;600;700;800&family=Spline+Sans+Mono:wght@500;600&display=swap
- heading font
- Onest
- letter spacing
- -0.02em
- line height
- 1.5
- mono font
- Spline Sans Mono
- scale ratio
- 1.25
rules
Start with a mobile product shell: a neutral canvas, bottom or top color-field navigation, dominant task card, and secondary content grouped by semantic swatch planes rather than side rails.
Balanced mobile density: tight 8-12px control gaps inside groups, 24-32px section gaps, and at least one 64px breath gap around the primary product decision.
Use Onest for compact high-confidence headings, Hanken Grotesk for readable product text, and Spline Sans Mono for small catalog labels; vivid fields denote state and category before decoration.
layout
mobile 0-639px, tablet 640-1023px, desktop 1024px+ with max content width 1180px
Mobile-first single column with an asymmetric desktop split: 420px device-stage beside a flexible product-detail column and one deliberate overlap break.
Use 8px internal rhythm, 24px group rhythm, and 64px hero/task separation so vivid color has room to feel authored.
guidance
- Use color as navigation, grouping, progress, content state, and interaction feedback.
- Keep the neutral foundation warm, quiet, and sharply typeset so vivid accents feel premium.
- Pair complementary or tetradic hues in controlled planes with explicit labels and accessible contrast.
- Style every form and control state; make touch feedback structural through movement, rings, and saturation.
- Do not use decorative side stripes, left rails, square-grid wallpapers, confetti, or generic startup blobs.
- Do not make a rainbow interface; limit visible color sets to named product categories and stateful pairings.
- Do not wrap every item in nested cards or build a generic admin dashboard scene.
- Do not use color merely as small garnish or status dots detached from product meaning.
katagami spec
# Chromatic Field Product System ## Philosophy A clean mobile-first product language where authored color-theory fields are not garnish but the navigation, grouping, progress, and decision logic of a calm premium interface. ### Values - Quiet neutral foundation with color carrying structure and meaning - Apple-clean typography and spacing that make vivid pairings feel intentional - Mobile-first hierarchy with tactile touch states and useful content density - Catalog-like color exercises translated into real application states ### Anti-Values - Childish rainbow decoration, confetti, generic blobs, or neon cyberpunk glow - Decorative side rails, left stripes, square-grid wallpaper, and SaaS dashboard templates - Color used only as a small accent when it should organize product meaning ### Visual Character - Large rounded-rectangle color fields sit inside navigation and content groups as selectable planes, never as thin side stripes or wallpaper. - Neutral shell uses warm off-white surfaces, hairline translucent borders, and shallow inset shadows so vivid swatches feel premium rather than loud. - Complementary and tetradic color pairs are assigned to product categories with paired chips, progress arcs, and card headers that carry actual state. - Mobile cards use asymmetrical internal grids with one dominant content field and one smaller color-theory control cluster to avoid equal template rows. - Touch states move color fields by two pixels with a crisp ring and saturation lift, tying interaction behavior to the swatch-plane geometry. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: borders are separators and touch targets; accent color appears as full fields, paired chips, or rings rather than one-sided stripes - **Default Width**: 1px - **Style**: solid with translucent warm-neutral color or focused blue ring ### Colors | Name | Value | |------|-------| | accent | `#16B88F` | | background | `#F7F4EE` | | border | `#DAD3C6` | | error | `#C93A32` | | info | `#3157F6` | | muted | `#6D6A61` | | primary | `#3157F6` | | secondary | `#F25A3C` | | success | `#168A68` | | surface | `#FFFDF8` | | text | `#181915` | | warning | `#C98216` | ### Motion - **Duration**: 180ms - **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1) - **Philosophy**: color fields translate and saturate on touch while panels stay calm; no bounce, no layout jank, no decorative glow ### Radii - **Full**: 9999px - **Lg**: 26px - **Md**: 18px - **None**: 0 - **Sm**: 10px ### Shadows - **Lg**: 0 28px 80px rgba(49,87,246,0.12), 0 18px 48px rgba(55,47,33,0.10) - **Md**: 0 18px 42px rgba(55,47,33,0.10), 0 2px 8px rgba(55,47,33,0.05) - **Sm**: 0 1px 2px rgba(24,25,21,0.06), inset 0 0 0 1px rgba(255,255,255,0.55) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: subtle scattered point-grid texture at low opacity; no square-grid backgrounds and no decorative side rails - **Card Style**: single-layer ivory cards with 18px or 26px committed radius, hairline warm border, no nested card wrappers, and integrated color-field headers - **Treatment**: warm neutral canvas with ivory panels, faint non-boxy point texture, and vivid matte color fields used as active planes ### Typography - **Base Size**: 16px - **Body Font**: Hanken Grotesk - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Hanken+Grotesk:wght@400;500;600;700&family=Onest:wght@500;600;700;800&family=Spline+Sans+Mono:wght@500;600&display=swap - **Heading Font**: Onest - **Letter Spacing**: -0.02em - **Line Height**: 1.5 - **Mono Font**: Spline Sans Mono - **Scale Ratio**: 1.25 ## Rules ### Composition Start with a mobile product shell: a neutral canvas, bottom or top color-field navigation, dominant task card, and secondary content grouped by semantic swatch planes rather than side rails. ### Density Balanced mobile density: tight 8-12px control gaps inside groups, 24-32px section gaps, and at least one 64px breath gap around the primary product decision. ### Hierarchy Use Onest for compact high-confidence headings, Hanken Grotesk for readable product text, and Spline Sans Mono for small catalog labels; vivid fields denote state and category before decoration. ### Signature Patterns - Swatch-plane navigation uses four large pill-like color fields with active state as expanded area, raised label, and paired complementary chip. - Category cards contain a real painted header field behind content metadata, with text contrast chosen per swatch and no thin accent border. - Progress is shown as segmented complementary color bands inside a rounded track, with labels attached to segments so color carries data. - Empty states use a single catalog exercise panel: two overlapped color rectangles, a neutral instruction, and one product action rather than confetti. - Focus and press states use a two-pixel translate, a 2px blue or paired-color ring, and saturation change to make interaction geometry visible. ## Layout ### Breakpoints mobile 0-639px, tablet 640-1023px, desktop 1024px+ with max content width 1180px ### Grid Mobile-first single column with an asymmetric desktop split: 420px device-stage beside a flexible product-detail column and one deliberate overlap break. ### Whitespace Use 8px internal rhythm, 24px group rhythm, and 64px hero/task separation so vivid color has room to feel authored. ## Guidance ### Do - Use color as navigation, grouping, progress, content state, and interaction feedback. - Keep the neutral foundation warm, quiet, and sharply typeset so vivid accents feel premium. - Pair complementary or tetradic hues in controlled planes with explicit labels and accessible contrast. - Style every form and control state; make touch feedback structural through movement, rings, and saturation. ### Don't - Do not use decorative side stripes, left rails, square-grid wallpapers, confetti, or generic startup blobs. - Do not make a rainbow interface; limit visible color sets to named product categories and stateful pairings. - Do not wrap every item in nested cards or build a generic admin dashboard scene. - Do not use color merely as small garnish or status dots detached from product meaning.
DESIGN.md
---
version: "alpha"
name: "Chromatic Field Product System"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#16B88F"
background: "#F7F4EE"
border: "#DAD3C6"
error: "#C93A32"
info: "#3157F6"
muted: "#6D6A61"
primary: "#3157F6"
secondary: "#F25A3C"
success: "#168A68"
surface: "#FFFDF8"
text: "#181915"
warning: "#C98216"
typography:
headline-lg:
fontFamily: "Onest"
fontSize: "1.953rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.02em"
headline-md:
fontFamily: "Onest"
fontSize: "1.563rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.02em"
body-md:
fontFamily: "Hanken Grotesk"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.5
letterSpacing: "-0.02em"
label-md:
fontFamily: "Spline Sans Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "26px"
md: "18px"
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: "#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 Field Product System
## Overview
A clean mobile-first product language where authored color-theory fields are not garnish but the navigation, grouping, progress, and decision logic of a calm premium interface.
### Values
- Quiet neutral foundation with color carrying structure and meaning
- Apple-clean typography and spacing that make vivid pairings feel intentional
- Mobile-first hierarchy with tactile touch states and useful content density
- Catalog-like color exercises translated into real application states
### Anti-Values
- Childish rainbow decoration, confetti, generic blobs, or neon cyberpunk glow
- Decorative side rails, left stripes, square-grid wallpaper, and SaaS dashboard templates
- Color used only as a small accent when it should organize product meaning
### Visual Character
- Large rounded-rectangle color fields sit inside navigation and content groups as selectable planes, never as thin side stripes or wallpaper.
- Neutral shell uses warm off-white surfaces, hairline translucent borders, and shallow inset shadows so vivid swatches feel premium rather than loud.
- Complementary and tetradic color pairs are assigned to product categories with paired chips, progress arcs, and card headers that carry actual state.
- Mobile cards use asymmetrical internal grids with one dominant content field and one smaller color-theory control cluster to avoid equal template rows.
- Touch states move color fields by two pixels with a crisp ring and saturation lift, tying interaction behavior to the swatch-plane geometry.
## 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 | `#16B88F` |
| background | `#F7F4EE` |
| border | `#DAD3C6` |
| error | `#C93A32` |
| info | `#3157F6` |
| muted | `#6D6A61` |
| primary | `#3157F6` |
| secondary | `#F25A3C` |
| success | `#168A68` |
| surface | `#FFFDF8` |
| text | `#181915` |
| warning | `#C98216` |
## Typography
- **Headline-Lg**: Onest, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Onest, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Hanken Grotesk, 16px, weight 400, line-height 1.5.
- **Label-Md**: Spline Sans 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 0-639px, tablet 640-1023px, desktop 1024px+ with max content width 1180px
### Grid
Mobile-first single column with an asymmetric desktop split: 420px device-stage beside a flexible product-detail column and one deliberate overlap break.
### Whitespace
Use 8px internal rhythm, 24px group rhythm, and 64px hero/task separation so vivid color has room to feel authored.
## Elevation & Depth
### Shadows
- **Lg**: 0 28px 80px rgba(49,87,246,0.12), 0 18px 48px rgba(55,47,33,0.10)
- **Md**: 0 18px 42px rgba(55,47,33,0.10), 0 2px 8px rgba(55,47,33,0.05)
- **Sm**: 0 1px 2px rgba(24,25,21,0.06), inset 0 0 0 1px rgba(255,255,255,0.55)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `26px`
- **Md**: `18px`
- **None**: `0px`
- **Sm**: `10px`
### Surfaces
- **Bg Pattern**: subtle scattered point-grid texture at low opacity; no square-grid backgrounds and no decorative side rails
- **Card Style**: single-layer ivory cards with 18px or 26px committed radius, hairline warm border, no nested card wrappers, and integrated color-field headers
- **Treatment**: warm neutral canvas with ivory panels, faint non-boxy point texture, and vivid matte color fields used as active planes
### Borders
- **Accent Width**: 2px
- **Character**: borders are separators and touch targets; accent color appears as full fields, paired chips, or rings rather than one-sided stripes
- **Default Width**: 1px
- **Style**: solid with translucent warm-neutral color or focused blue ring
## Components
### Composition
Start with a mobile product shell: a neutral canvas, bottom or top color-field navigation, dominant task card, and secondary content grouped by semantic swatch planes rather than side rails.
### Density
Balanced mobile density: tight 8-12px control gaps inside groups, 24-32px section gaps, and at least one 64px breath gap around the primary product decision.
### Hierarchy
Use Onest for compact high-confidence headings, Hanken Grotesk for readable product text, and Spline Sans Mono for small catalog labels; vivid fields denote state and category before decoration.
### Signature Patterns
- Swatch-plane navigation uses four large pill-like color fields with active state as expanded area, raised label, and paired complementary chip.
- Category cards contain a real painted header field behind content metadata, with text contrast chosen per swatch and no thin accent border.
- Progress is shown as segmented complementary color bands inside a rounded track, with labels attached to segments so color carries data.
- Empty states use a single catalog exercise panel: two overlapped color rectangles, a neutral instruction, and one product action rather than confetti.
- Focus and press states use a two-pixel translate, a 2px blue or paired-color ring, and saturation change to make interaction geometry visible.
## 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-019e45e5-f47e-7a40-b400-4757dd81fd0a/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 Use color as navigation, grouping, progress, content state, and interaction feedback.
- Do Keep the neutral foundation warm, quiet, and sharply typeset so vivid accents feel premium.
- Do Pair complementary or tetradic hues in controlled planes with explicit labels and accessible contrast.
- Do Style every form and control state; make touch feedback structural through movement, rings, and saturation.
- Don't Do not use decorative side stripes, left rails, square-grid wallpapers, confetti, or generic startup blobs.
- Don't Do not make a rainbow interface; limit visible color sets to named product categories and stateful pairings.
- Don't Do not wrap every item in nested cards or build a generic admin dashboard scene.
- Don't Do not use color merely as small garnish or status dots detached from product meaning.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "chromatic-field-product-system",
"type": "registry:theme",
"title": "Chromatic Field Product System shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F7F4EE",
"foreground": "#181915",
"card": "#FFFDF8",
"card-foreground": "#181915",
"popover": "#FFFDF8",
"popover-foreground": "#181915",
"primary": "#3157F6",
"primary-foreground": "#ffffff",
"secondary": "#F25A3C",
"secondary-foreground": "#ffffff",
"muted": "#6D6A61",
"muted-foreground": "#181915",
"accent": "#16B88F",
"accent-foreground": "#ffffff",
"destructive": "#C93A32",
"border": "#DAD3C6",
"input": "#DAD3C6",
"ring": "#16B88F",
"chart-1": "#3157F6",
"chart-2": "#F25A3C",
"chart-3": "#16B88F",
"chart-4": "#168A68",
"chart-5": "#C98216",
"sidebar": "#FFFDF8",
"sidebar-foreground": "#181915",
"sidebar-primary": "#3157F6",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#3157F6",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#DAD3C6",
"sidebar-ring": "#16B88F",
"radius": "18px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#3157F6",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#16B88F",
"accent-foreground": "#ffffff",
"destructive": "#C93A32",
"border": "#303642",
"input": "#303642",
"ring": "#16B88F",
"chart-1": "#3157F6",
"chart-2": "#F25A3C",
"chart-3": "#16B88F",
"chart-4": "#168A68",
"chart-5": "#C98216",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#3157F6",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#16B88F",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#16B88F",
"radius": "18px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e45e5-f47e-7a40-b400-4757dd81fd0a",
"slug": "chromatic-field-product-system",
"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: #F7F4EE;
--foreground: #181915;
--card: #FFFDF8;
--card-foreground: #181915;
--popover: #FFFDF8;
--popover-foreground: #181915;
--primary: #3157F6;
--primary-foreground: #ffffff;
--secondary: #F25A3C;
--secondary-foreground: #ffffff;
--muted: #6D6A61;
--muted-foreground: #181915;
--accent: #16B88F;
--accent-foreground: #ffffff;
--destructive: #C93A32;
--border: #DAD3C6;
--input: #DAD3C6;
--ring: #16B88F;
--chart-1: #3157F6;
--chart-2: #F25A3C;
--chart-3: #16B88F;
--chart-4: #168A68;
--chart-5: #C98216;
--sidebar: #FFFDF8;
--sidebar-foreground: #181915;
--sidebar-primary: #3157F6;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #3157F6;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #DAD3C6;
--sidebar-ring: #16B88F;
--radius: 18px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #3157F6;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #16B88F;
--accent-foreground: #ffffff;
--destructive: #C93A32;
--border: #303642;
--input: #303642;
--ring: #16B88F;
--chart-1: #3157F6;
--chart-2: #F25A3C;
--chart-3: #16B88F;
--chart-4: #168A68;
--chart-5: #C98216;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #3157F6;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #16B88F;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #16B88F;
--radius: 18px;
}
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 ChromaticFieldProductSystemShadcnKit() {
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 Field Product System</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"cssVars": {
"dark": {
"accent": "#16B88F",
"accent-foreground": "#ffffff",
"background": "#0f1115",
"border": "#303642",
"card": "#181b22",
"card-foreground": "#f8fafc",
"chart-1": "#3157F6",
"chart-2": "#F25A3C",
"chart-3": "#16B88F",
"chart-4": "#168A68",
"chart-5": "#C98216",
"destructive": "#C93A32",
"foreground": "#f8fafc",
"input": "#303642",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#3157F6",
"primary-foreground": "#ffffff",
"radius": "18px",
"ring": "#16B88F",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"sidebar": "#181b22",
"sidebar-accent": "#16B88F",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#3157F6",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#16B88F"
},
"light": {
"accent": "#16B88F",
"accent-foreground": "#ffffff",
"background": "#F7F4EE",
"border": "#DAD3C6",
"card": "#FFFDF8",
"card-foreground": "#181915",
"chart-1": "#3157F6",
"chart-2": "#F25A3C",
"chart-3": "#16B88F",
"chart-4": "#168A68",
"chart-5": "#C98216",
"destructive": "#C93A32",
"foreground": "#181915",
"input": "#DAD3C6",
"muted": "#6D6A61",
"muted-foreground": "#181915",
"popover": "#FFFDF8",
"popover-foreground": "#181915",
"primary": "#3157F6",
"primary-foreground": "#ffffff",
"radius": "18px",
"ring": "#16B88F",
"secondary": "#F25A3C",
"secondary-foreground": "#ffffff",
"sidebar": "#FFFDF8",
"sidebar-accent": "#3157F6",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#DAD3C6",
"sidebar-foreground": "#181915",
"sidebar-primary": "#3157F6",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#16B88F"
},
"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-019e45e5-f47e-7a40-b400-4757dd81fd0a",
"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-field-product-system",
"source": "katagami"
},
"name": "chromatic-field-product-system",
"title": "Chromatic Field Product System shadcn Theme",
"type": "registry:theme"
}
# Chromatic Field Product System shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e45e5-f47e-7a40-b400-4757dd81fd0a`
Slug: `chromatic-field-product-system`
## Intent
A clean mobile-first product language where authored color-theory fields are not garnish but the navigation, grouping, progress, and decision logic of a calm premium interface.
## 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": "#16B88F",
"background": "#F7F4EE",
"border": "#DAD3C6",
"error": "#C93A32",
"info": "#3157F6",
"muted": "#6D6A61",
"primary": "#3157F6",
"secondary": "#F25A3C",
"success": "#168A68",
"surface": "#FFFDF8",
"text": "#181915",
"warning": "#C98216"
}
Typography:
{
"base_size": "16px",
"body_font": "Hanken Grotesk",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Hanken+Grotesk:wght@400;500;600;700&family=Onest:wght@500;600;700;800&family=Spline+Sans+Mono:wght@500;600&display=swap",
"heading_font": "Onest",
"letter_spacing": "-0.02em",
"line_height": 1.5,
"mono_font": "Spline Sans Mono",
"scale_ratio": 1.25
}
## Visual character to preserve
- Large rounded-rectangle color fields sit inside navigation and content groups as selectable planes, never as thin side stripes or wallpaper.
- Neutral shell uses warm off-white surfaces, hairline translucent borders, and shallow inset shadows so vivid swatches feel premium rather than loud.
- Complementary and tetradic color pairs are assigned to product categories with paired chips, progress arcs, and card headers that carry actual state.
- Mobile cards use asymmetrical internal grids with one dominant content field and one smaller color-theory control cluster to avoid equal template rows.
- Touch states move color fields by two pixels with a crisp ring and saturation lift, tying interaction behavior to the swatch-plane geometry.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"border": "solid",
"underlay": false,
"grain": true,
"stickerBadges": false,
"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-field-product-system/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use color as navigation, grouping, progress, content state, and interaction feedback.; Keep the neutral foundation warm, quiet, and sharply typeset so vivid accents feel premium.; Pair complementary or tetradic hues in controlled planes with explicit labels and accessible contrast.; Style every form and control state; make touch feedback structural through movement, rings, and saturation.
- Do not: Do not use decorative side stripes, left rails, square-grid wallpapers, confetti, or generic startup blobs.; Do not make a rainbow interface; limit visible color sets to named product categories and stateful pairings.; Do not wrap every item in nested cards or build a generic admin dashboard scene.; Do not use color merely as small garnish or status dots detached from product meaning.
## 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 ChromaticFieldProductSystemShadcnKit() {
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 Field Product System</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
```
## Layout notes
{
"breakpoints": "mobile 0-639px, tablet 640-1023px, desktop 1024px+ with max content width 1180px",
"grid": "Mobile-first single column with an asymmetric desktop split: 420px device-stage beside a flexible product-detail column and one deliberate overlap break.",
"whitespace": "Use 8px internal rhythm, 24px group rhythm, and 64px hero/task separation so vivid color has room to feel authored."
}
{
"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-019e45e5-f47e-7a40-b400-4757dd81fd0a",
"name": "Chromatic Field Product System",
"slug": "chromatic-field-product-system"
},
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"primitives": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"identityNotes": [
"Large rounded-rectangle color fields sit inside navigation and content groups as selectable planes, never as thin side stripes or wallpaper.",
"Neutral shell uses warm off-white surfaces, hairline translucent borders, and shallow inset shadows so vivid swatches feel premium rather than loud.",
"Complementary and tetradic color pairs are assigned to product categories with paired chips, progress arcs, and card headers that carry actual state.",
"Mobile cards use asymmetrical internal grids with one dominant content field and one smaller color-theory control cluster to avoid equal template rows.",
"Touch states move color fields by two pixels with a crisp ring and saturation lift, tying interaction behavior to the swatch-plane geometry."
],
"visualProfile": {
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"border": "solid",
"underlay": false,
"grain": true,
"stickerBadges": false,
"motion": "lift",
"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 Field Product System launch room",
"description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
"primaryAction": "Apply theme",
"secondaryAction": "Review states",
"stats": [
{
"label": "components",
"value": "16",
"tone": "accent"
},
{
"label": "states",
"value": "ready"
},
{
"label": "density",
"value": "balanced",
"tone": "warning"
}
],
"rows": [
{
"label": "Primary flow",
"value": "mapped",
"status": "active"
},
{
"label": "Token coverage",
"value": "semantic",
"status": "synced"
},
{
"label": "Responsive proof",
"value": "queued",
"status": "review"
}
],
"statuses": [
"Active",
"Synced",
"Draft"
]
}
},
{
"id": "detail-editor",
"title": "Detail editor",
"viewport": "tablet",
"primitives": [
"button",
"card",
"input",
"textarea",
"select",
"checkbox",
"switch",
"slider",
"dialog",
"sheet"
],
"composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
"mustShow": [
"focus ring",
"error or destructive state",
"dialog or sheet treatment",
"written guidance content"
],
"avoid": [
"unstyled browser controls",
"floating cards inside cards",
"missing labels"
],
"scene": {
"eyebrow": "editing flow",
"headline": "Language recipe editor",
"description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
"primaryAction": "Save recipe",
"secondaryAction": "Open sheet",
"fields": [
{
"label": "Component family",
"value": "Narrative cards"
},
{
"label": "State treatment",
"value": "Visible focus + validation"
},
{
"label": "Motion",
"value": "Small lift, no opacity-only fade"
}
],
"statuses": [
"Focus",
"Invalid",
"Confirmed"
]
}
},
{
"id": "data-operations",
"title": "Data operations",
"viewport": "mobile",
"primitives": [
"button",
"tabs",
"badge",
"dropdown-menu",
"table",
"tooltip",
"separator"
],
"composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
"mustShow": [
"responsive reflow",
"dense row styling",
"menu affordance",
"status badge system"
],
"avoid": [
"desktop-only tables",
"text overflow",
"default shadcn spacing without Katagami character"
],
"scene": {
"eyebrow": "operations",
"headline": "Compact review queue",
"description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
"primaryAction": "Resolve",
"secondaryAction": "Filter",
"rows": [
{
"label": "Button hierarchy",
"value": "approved",
"status": "ok"
},
{
"label": "Table rhythm",
"value": "needs pass",
"status": "watch"
},
{
"label": "Empty state",
"value": "designed",
"status": "done"
}
],
"statuses": [
"Queued",
"Blocked",
"Done"
]
}
}
],
"componentRecipes": [
{
"primitive": "button",
"intent": "Prove action hierarchy, focus, disabled, and destructive states."
},
{
"primitive": "card",
"intent": "Carry the language surface, border, elevation, and density rules."
},
{
"primitive": "input",
"intent": "Show labels, focus rings, validation, and spacing rhythm."
},
{
"primitive": "textarea",
"intent": "Show longer guidance, validation copy, and writing density."
},
{
"primitive": "select",
"intent": "Show filtering, selection contrast, and menu trigger styling."
},
{
"primitive": "dialog",
"intent": "Show centered decision states and overlay treatment."
},
{
"primitive": "sheet",
"intent": "Show contextual side panels and responsive editing."
},
{
"primitive": "tabs",
"intent": "Show navigational structure and active/inactive contrast."
},
{
"primitive": "badge",
"intent": "Show compact status vocabulary and semantic colors."
},
{
"primitive": "separator",
"intent": "Show section rhythm without generic gray dividers."
},
{
"primitive": "checkbox",
"intent": "Show binary selection with visible focus and checked states."
},
{
"primitive": "switch",
"intent": "Show settings toggles and on/off contrast."
},
{
"primitive": "slider",
"intent": "Show numeric adjustment with track/thumb styling."
},
{
"primitive": "tooltip",
"intent": "Show concise explanation styling above compact controls."
},
{
"primitive": "dropdown-menu",
"intent": "Show action menus, destructive items, and grouped choices."
},
{
"primitive": "table",
"intent": "Show dense operational data, separators, row states, and responsive behavior."
}
],
"qualityRules": {
"do": [
"Use color as navigation, grouping, progress, content state, and interaction feedback.",
"Keep the neutral foundation warm, quiet, and sharply typeset so vivid accents feel premium.",
"Pair complementary or tetradic hues in controlled planes with explicit labels and accessible contrast.",
"Style every form and control state; make touch feedback structural through movement, rings, and saturation."
],
"dont": [
"Do not use decorative side stripes, left rails, square-grid wallpapers, confetti, or generic startup blobs.",
"Do not make a rainbow interface; limit visible color sets to named product categories and stateful pairings.",
"Do not wrap every item in nested cards or build a generic admin dashboard scene.",
"Do not use color merely as small garnish or status dots detached from product meaning."
]
}
}