Precision White Complementary Fields
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
- mineral hairlines with paired-color focus outlines that wrap complete controls rather than appearing as decorative stripes
- default width
- 1px
- style
- solid
colors12 items
motion3 items
- duration
- 180ms
- easing
- cubic-bezier(0.22, 1, 0.36, 1)
- philosophy
- short precise fades and 1-2px lifts; color planes swap or brighten to confirm state without bounce or spectacle
radii5 items
- full
- 9999px
- lg
- 24px
- md
- 14px
- none
- 0
- sm
- 8px
shadows3 items
- lg
- 0 36px 90px rgba(22, 22, 22, 0.12)
- md
- 0 18px 50px rgba(22, 22, 22, 0.08)
- sm
- 0 1px 2px rgba(22, 22, 22, 0.05)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- nearly invisible non-boxy point texture made from sparse radial dots at 32px spacing, never a square grid wallpaper
- card style
- large-radius white cards, one-pixel mineral border, no side rails, color only in top-level active planes, swatches, and semantic content zones
- treatment
- quiet porcelain white surfaces with faint warm tint and isolated painted color fields for active or comparative content
typography8 items
- base size
- 16px
- body font
- Geist
- google fonts url
- https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600;700&family=Geist+Mono:wght@500;600&family=Instrument+Sans:wght@500;600;700&display=swap
- heading font
- Instrument Sans
- letter spacing
- -0.018em
- line height
- 1.48
- mono font
- Geist Mono
- scale ratio
- 1.22
rules
Use a precision product shell with a calm white canvas, a narrow top command band, and large content work areas where color pairings mark decisions, relationships, and state.
Moderately airy, with compact controls and generous module gutters; avoid crowded dashboards while keeping enough rows, forms, and data to prove product utility.
Let black typography and whitespace establish reading order, then use saturated complementary fields only for selected items, comparative metrics, critical controls, and data marks.
layout
desktop 1200px, tablet 768px, mobile 375px with cards stacking and command actions wrapping below filters
Twelve-column desktop shell with max-width 1320px, two-column workbench areas, and collapsing single-column mobile sections.
Use 24-32px module gaps and 48-64px page rhythm around hero/workbench zones so saturated fields feel intentional and premium.
guidance
- Assign each complementary pair to a real product meaning such as confidence versus risk, planned versus live, or source versus output.
- Use full surfaces, chips, charts, focus rings, and data marks for color so it changes behavior or comprehension.
- Keep the foundation white, typographic, and calm with only a few saturated fields visible at once.
- Preserve complete border wraps and rectangular color fields rather than decorative side accents.
- Do not use rainbow confetti, generic blobs, neon glow, or arbitrary color sprinkled over neutral components.
- Do not add colored left rails, side stripes, or stripe-only accents to cards, buttons, rows, or panels.
- Do not build a square grid wallpaper or textbook page composition; any dot texture must stay barely visible and non-boxy.
- Do not let the scene become a generic admin dashboard with interchangeable cards and default charts.
katagami spec
# Precision White Complementary Fields ## Philosophy A product-first white interface language where authored complementary color pairings become functional structure: selection logic, comparative data, content frames, and interaction states rather than decoration. ### Values - precision before spectacle - color as product grammar - premium neutral quiet - visible analytical relationships - fresh contrast with restraint ### Anti-Values - rainbow garnish or arbitrary confetti - decorative side rails and generic dashboard chrome - neon cyberpunk glow - template SaaS card clutter ### Visual Character - White and porcelain surfaces use one-pixel mineral borders, generous radius, and hairline separators to create Apple-like calm without gray dashboard heaviness. - Complementary color pairs appear as paired rectangular fields, data chips, focus rings, and active states that map to real product categories and comparisons. - Content modules use asymmetrical editorial white space with compact color-theory swatches embedded inside headers, tables, and form controls as structural anchors. - Typography relies on sharp grotesk headings, tabular numerals, and restrained tracking so saturated ultramarine, orange, violet, lime, cyan, and red-orange remain premium. - Interactive components expose color through filled selection planes, split badges, and paired hover/focus states instead of side stripes, decorative rails, or wallpaper grids. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: mineral hairlines with paired-color focus outlines that wrap complete controls rather than appearing as decorative stripes - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#7A3FF2` | | background | `#FCFCFA` | | border | `#E4E2DC` | | error | `#D84A2B` | | info | `#00A6C8` | | muted | `#6D706E` | | primary | `#2155F4` | | secondary | `#F07A18` | | success | `#4B8F2F` | | surface | `#FFFFFF` | | text | `#161616` | | warning | `#D99A1B` | ### Motion - **Duration**: 180ms - **Easing**: cubic-bezier(0.22, 1, 0.36, 1) - **Philosophy**: short precise fades and 1-2px lifts; color planes swap or brighten to confirm state without bounce or spectacle ### Radii - **Full**: 9999px - **Lg**: 24px - **Md**: 14px - **None**: 0 - **Sm**: 8px ### Shadows - **Lg**: 0 36px 90px rgba(22, 22, 22, 0.12) - **Md**: 0 18px 50px rgba(22, 22, 22, 0.08) - **Sm**: 0 1px 2px rgba(22, 22, 22, 0.05) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: nearly invisible non-boxy point texture made from sparse radial dots at 32px spacing, never a square grid wallpaper - **Card Style**: large-radius white cards, one-pixel mineral border, no side rails, color only in top-level active planes, swatches, and semantic content zones - **Treatment**: quiet porcelain white surfaces with faint warm tint and isolated painted color fields for active or comparative content ### Typography - **Base Size**: 16px - **Body Font**: Geist - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600;700&family=Geist+Mono:wght@500;600&family=Instrument+Sans:wght@500;600;700&display=swap - **Heading Font**: Instrument Sans - **Letter Spacing**: -0.018em - **Line Height**: 1.48 - **Mono Font**: Geist Mono - **Scale Ratio**: 1.22 ## Rules ### Composition Use a precision product shell with a calm white canvas, a narrow top command band, and large content work areas where color pairings mark decisions, relationships, and state. ### Density Moderately airy, with compact controls and generous module gutters; avoid crowded dashboards while keeping enough rows, forms, and data to prove product utility. ### Hierarchy Let black typography and whitespace establish reading order, then use saturated complementary fields only for selected items, comparative metrics, critical controls, and data marks. ### Signature Patterns - Complementary-pair chips divide a pill into two labeled color fields so category relationships are visible as content-bearing tokens. - Painted field cards use a single saturated rectangular panel nested in a white card to hold active data, calls to action, or selected object previews. - Form focus states draw full wrapped dual-color outlines and tiny swatch captions, making interaction feedback structural rather than ornamental. - Tables use color marks as data glyphs inside cells and headers, never as row side stripes, enabling quick scanning without decorative rails. - Command bars place small catalog-like swatch exercises beside real filters, showing authored palette logic within product hierarchy. ## Layout ### Breakpoints desktop 1200px, tablet 768px, mobile 375px with cards stacking and command actions wrapping below filters ### Grid Twelve-column desktop shell with max-width 1320px, two-column workbench areas, and collapsing single-column mobile sections. ### Whitespace Use 24-32px module gaps and 48-64px page rhythm around hero/workbench zones so saturated fields feel intentional and premium. ## Guidance ### Do - Assign each complementary pair to a real product meaning such as confidence versus risk, planned versus live, or source versus output. - Use full surfaces, chips, charts, focus rings, and data marks for color so it changes behavior or comprehension. - Keep the foundation white, typographic, and calm with only a few saturated fields visible at once. - Preserve complete border wraps and rectangular color fields rather than decorative side accents. ### Don't - Do not use rainbow confetti, generic blobs, neon glow, or arbitrary color sprinkled over neutral components. - Do not add colored left rails, side stripes, or stripe-only accents to cards, buttons, rows, or panels. - Do not build a square grid wallpaper or textbook page composition; any dot texture must stay barely visible and non-boxy. - Do not let the scene become a generic admin dashboard with interchangeable cards and default charts.
DESIGN.md
---
version: "alpha"
name: "Precision White Complementary Fields"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#7A3FF2"
background: "#FCFCFA"
border: "#E4E2DC"
error: "#D84A2B"
info: "#00A6C8"
muted: "#6D706E"
primary: "#2155F4"
secondary: "#F07A18"
success: "#4B8F2F"
surface: "#FFFFFF"
text: "#161616"
warning: "#D99A1B"
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: "Geist"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.48
letterSpacing: "-0.018em"
label-md:
fontFamily: "Geist Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "24px"
md: "14px"
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"
---
# Precision White Complementary Fields
## Overview
A product-first white interface language where authored complementary color pairings become functional structure: selection logic, comparative data, content frames, and interaction states rather than decoration.
### Values
- precision before spectacle
- color as product grammar
- premium neutral quiet
- visible analytical relationships
- fresh contrast with restraint
### Anti-Values
- rainbow garnish or arbitrary confetti
- decorative side rails and generic dashboard chrome
- neon cyberpunk glow
- template SaaS card clutter
### Visual Character
- White and porcelain surfaces use one-pixel mineral borders, generous radius, and hairline separators to create Apple-like calm without gray dashboard heaviness.
- Complementary color pairs appear as paired rectangular fields, data chips, focus rings, and active states that map to real product categories and comparisons.
- Content modules use asymmetrical editorial white space with compact color-theory swatches embedded inside headers, tables, and form controls as structural anchors.
- Typography relies on sharp grotesk headings, tabular numerals, and restrained tracking so saturated ultramarine, orange, violet, lime, cyan, and red-orange remain premium.
- Interactive components expose color through filled selection planes, split badges, and paired hover/focus states instead of side stripes, decorative rails, or wallpaper grids.
## 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 | `#7A3FF2` |
| background | `#FCFCFA` |
| border | `#E4E2DC` |
| error | `#D84A2B` |
| info | `#00A6C8` |
| muted | `#6D706E` |
| primary | `#2155F4` |
| secondary | `#F07A18` |
| success | `#4B8F2F` |
| surface | `#FFFFFF` |
| text | `#161616` |
| warning | `#D99A1B` |
## 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**: Geist, 16px, weight 400, line-height 1.48.
- **Label-Md**: Geist 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
desktop 1200px, tablet 768px, mobile 375px with cards stacking and command actions wrapping below filters
### Grid
Twelve-column desktop shell with max-width 1320px, two-column workbench areas, and collapsing single-column mobile sections.
### Whitespace
Use 24-32px module gaps and 48-64px page rhythm around hero/workbench zones so saturated fields feel intentional and premium.
## Elevation & Depth
### Shadows
- **Lg**: 0 36px 90px rgba(22, 22, 22, 0.12)
- **Md**: 0 18px 50px rgba(22, 22, 22, 0.08)
- **Sm**: 0 1px 2px rgba(22, 22, 22, 0.05)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `24px`
- **Md**: `14px`
- **None**: `0px`
- **Sm**: `8px`
### Surfaces
- **Bg Pattern**: nearly invisible non-boxy point texture made from sparse radial dots at 32px spacing, never a square grid wallpaper
- **Card Style**: large-radius white cards, one-pixel mineral border, no side rails, color only in top-level active planes, swatches, and semantic content zones
- **Treatment**: quiet porcelain white surfaces with faint warm tint and isolated painted color fields for active or comparative content
### Borders
- **Accent Width**: 2px
- **Character**: mineral hairlines with paired-color focus outlines that wrap complete controls rather than appearing as decorative stripes
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Use a precision product shell with a calm white canvas, a narrow top command band, and large content work areas where color pairings mark decisions, relationships, and state.
### Density
Moderately airy, with compact controls and generous module gutters; avoid crowded dashboards while keeping enough rows, forms, and data to prove product utility.
### Hierarchy
Let black typography and whitespace establish reading order, then use saturated complementary fields only for selected items, comparative metrics, critical controls, and data marks.
### Signature Patterns
- Complementary-pair chips divide a pill into two labeled color fields so category relationships are visible as content-bearing tokens.
- Painted field cards use a single saturated rectangular panel nested in a white card to hold active data, calls to action, or selected object previews.
- Form focus states draw full wrapped dual-color outlines and tiny swatch captions, making interaction feedback structural rather than ornamental.
- Tables use color marks as data glyphs inside cells and headers, never as row side stripes, enabling quick scanning without decorative rails.
- Command bars place small catalog-like swatch exercises beside real filters, showing authored palette logic within product hierarchy.
## 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-8eed-7900-aec0-781822e646b4/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 each complementary pair to a real product meaning such as confidence versus risk, planned versus live, or source versus output.
- Do Use full surfaces, chips, charts, focus rings, and data marks for color so it changes behavior or comprehension.
- Do Keep the foundation white, typographic, and calm with only a few saturated fields visible at once.
- Do Preserve complete border wraps and rectangular color fields rather than decorative side accents.
- Don't Do not use rainbow confetti, generic blobs, neon glow, or arbitrary color sprinkled over neutral components.
- Don't Do not add colored left rails, side stripes, or stripe-only accents to cards, buttons, rows, or panels.
- Don't Do not build a square grid wallpaper or textbook page composition; any dot texture must stay barely visible and non-boxy.
- Don't Do not let the scene become a generic admin dashboard with interchangeable cards and default charts.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "precision-white-complementary-fields",
"type": "registry:theme",
"title": "Precision White Complementary Fields shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#FCFCFA",
"foreground": "#161616",
"card": "#FFFFFF",
"card-foreground": "#161616",
"popover": "#FFFFFF",
"popover-foreground": "#161616",
"primary": "#2155F4",
"primary-foreground": "#ffffff",
"secondary": "#F07A18",
"secondary-foreground": "#ffffff",
"muted": "#6D706E",
"muted-foreground": "#161616",
"accent": "#7A3FF2",
"accent-foreground": "#ffffff",
"destructive": "#D84A2B",
"border": "#E4E2DC",
"input": "#E4E2DC",
"ring": "#7A3FF2",
"chart-1": "#2155F4",
"chart-2": "#F07A18",
"chart-3": "#7A3FF2",
"chart-4": "#4B8F2F",
"chart-5": "#D99A1B",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#161616",
"sidebar-primary": "#2155F4",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#00A6C8",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#E4E2DC",
"sidebar-ring": "#7A3FF2",
"radius": "14px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#2155F4",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#7A3FF2",
"accent-foreground": "#ffffff",
"destructive": "#D84A2B",
"border": "#303642",
"input": "#303642",
"ring": "#7A3FF2",
"chart-1": "#2155F4",
"chart-2": "#F07A18",
"chart-3": "#7A3FF2",
"chart-4": "#4B8F2F",
"chart-5": "#D99A1B",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#2155F4",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#7A3FF2",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#7A3FF2",
"radius": "14px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e45e6-8eed-7900-aec0-781822e646b4",
"slug": "precision-white-complementary-fields",
"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: #FCFCFA;
--foreground: #161616;
--card: #FFFFFF;
--card-foreground: #161616;
--popover: #FFFFFF;
--popover-foreground: #161616;
--primary: #2155F4;
--primary-foreground: #ffffff;
--secondary: #F07A18;
--secondary-foreground: #ffffff;
--muted: #6D706E;
--muted-foreground: #161616;
--accent: #7A3FF2;
--accent-foreground: #ffffff;
--destructive: #D84A2B;
--border: #E4E2DC;
--input: #E4E2DC;
--ring: #7A3FF2;
--chart-1: #2155F4;
--chart-2: #F07A18;
--chart-3: #7A3FF2;
--chart-4: #4B8F2F;
--chart-5: #D99A1B;
--sidebar: #FFFFFF;
--sidebar-foreground: #161616;
--sidebar-primary: #2155F4;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #00A6C8;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #E4E2DC;
--sidebar-ring: #7A3FF2;
--radius: 14px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #2155F4;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #7A3FF2;
--accent-foreground: #ffffff;
--destructive: #D84A2B;
--border: #303642;
--input: #303642;
--ring: #7A3FF2;
--chart-1: #2155F4;
--chart-2: #F07A18;
--chart-3: #7A3FF2;
--chart-4: #4B8F2F;
--chart-5: #D99A1B;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #2155F4;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #7A3FF2;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #7A3FF2;
--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 PrecisionWhiteComplementaryFieldsShadcnKit() {
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">Precision White Complementary Fields</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": "#7A3FF2",
"accent-foreground": "#ffffff",
"background": "#0f1115",
"border": "#303642",
"card": "#181b22",
"card-foreground": "#f8fafc",
"chart-1": "#2155F4",
"chart-2": "#F07A18",
"chart-3": "#7A3FF2",
"chart-4": "#4B8F2F",
"chart-5": "#D99A1B",
"destructive": "#D84A2B",
"foreground": "#f8fafc",
"input": "#303642",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#2155F4",
"primary-foreground": "#ffffff",
"radius": "14px",
"ring": "#7A3FF2",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"sidebar": "#181b22",
"sidebar-accent": "#7A3FF2",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#2155F4",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#7A3FF2"
},
"light": {
"accent": "#7A3FF2",
"accent-foreground": "#ffffff",
"background": "#FCFCFA",
"border": "#E4E2DC",
"card": "#FFFFFF",
"card-foreground": "#161616",
"chart-1": "#2155F4",
"chart-2": "#F07A18",
"chart-3": "#7A3FF2",
"chart-4": "#4B8F2F",
"chart-5": "#D99A1B",
"destructive": "#D84A2B",
"foreground": "#161616",
"input": "#E4E2DC",
"muted": "#6D706E",
"muted-foreground": "#161616",
"popover": "#FFFFFF",
"popover-foreground": "#161616",
"primary": "#2155F4",
"primary-foreground": "#ffffff",
"radius": "14px",
"ring": "#7A3FF2",
"secondary": "#F07A18",
"secondary-foreground": "#ffffff",
"sidebar": "#FFFFFF",
"sidebar-accent": "#00A6C8",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#E4E2DC",
"sidebar-foreground": "#161616",
"sidebar-primary": "#2155F4",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#7A3FF2"
},
"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-8eed-7900-aec0-781822e646b4",
"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": "precision-white-complementary-fields",
"source": "katagami"
},
"name": "precision-white-complementary-fields",
"title": "Precision White Complementary Fields shadcn Theme",
"type": "registry:theme"
}
# Precision White Complementary Fields shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e45e6-8eed-7900-aec0-781822e646b4`
Slug: `precision-white-complementary-fields`
## Intent
A product-first white interface language where authored complementary color pairings become functional structure: selection logic, comparative data, content frames, and interaction states rather than 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": "#7A3FF2",
"background": "#FCFCFA",
"border": "#E4E2DC",
"error": "#D84A2B",
"info": "#00A6C8",
"muted": "#6D706E",
"primary": "#2155F4",
"secondary": "#F07A18",
"success": "#4B8F2F",
"surface": "#FFFFFF",
"text": "#161616",
"warning": "#D99A1B"
}
Typography:
{
"base_size": "16px",
"body_font": "Geist",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600;700&family=Geist+Mono:wght@500;600&family=Instrument+Sans:wght@500;600;700&display=swap",
"heading_font": "Instrument Sans",
"letter_spacing": "-0.018em",
"line_height": 1.48,
"mono_font": "Geist Mono",
"scale_ratio": 1.22
}
## Visual character to preserve
- White and porcelain surfaces use one-pixel mineral borders, generous radius, and hairline separators to create Apple-like calm without gray dashboard heaviness.
- Complementary color pairs appear as paired rectangular fields, data chips, focus rings, and active states that map to real product categories and comparisons.
- Content modules use asymmetrical editorial white space with compact color-theory swatches embedded inside headers, tables, and form controls as structural anchors.
- Typography relies on sharp grotesk headings, tabular numerals, and restrained tracking so saturated ultramarine, orange, violet, lime, cyan, and red-orange remain premium.
- Interactive components expose color through filled selection planes, split badges, and paired hover/focus states instead of side stripes, decorative rails, or wallpaper grids.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"border": "solid",
"underlay": false,
"grain": true,
"stickerBadges": true,
"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/precision-white-complementary-fields/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 each complementary pair to a real product meaning such as confidence versus risk, planned versus live, or source versus output.; Use full surfaces, chips, charts, focus rings, and data marks for color so it changes behavior or comprehension.; Keep the foundation white, typographic, and calm with only a few saturated fields visible at once.; Preserve complete border wraps and rectangular color fields rather than decorative side accents.
- Do not: Do not use rainbow confetti, generic blobs, neon glow, or arbitrary color sprinkled over neutral components.; Do not add colored left rails, side stripes, or stripe-only accents to cards, buttons, rows, or panels.; Do not build a square grid wallpaper or textbook page composition; any dot texture must stay barely visible and non-boxy.; Do not let the scene become a generic admin dashboard with interchangeable cards and default charts.
## 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 PrecisionWhiteComplementaryFieldsShadcnKit() {
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">Precision White Complementary Fields</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
```
## Layout notes
{
"breakpoints": "desktop 1200px, tablet 768px, mobile 375px with cards stacking and command actions wrapping below filters",
"grid": "Twelve-column desktop shell with max-width 1320px, two-column workbench areas, and collapsing single-column mobile sections.",
"whitespace": "Use 24-32px module gaps and 48-64px page rhythm around hero/workbench zones so saturated fields feel intentional and premium."
}
{
"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-8eed-7900-aec0-781822e646b4",
"name": "Precision White Complementary Fields",
"slug": "precision-white-complementary-fields"
},
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"primitives": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"identityNotes": [
"White and porcelain surfaces use one-pixel mineral borders, generous radius, and hairline separators to create Apple-like calm without gray dashboard heaviness.",
"Complementary color pairs appear as paired rectangular fields, data chips, focus rings, and active states that map to real product categories and comparisons.",
"Content modules use asymmetrical editorial white space with compact color-theory swatches embedded inside headers, tables, and form controls as structural anchors.",
"Typography relies on sharp grotesk headings, tabular numerals, and restrained tracking so saturated ultramarine, orange, violet, lime, cyan, and red-orange remain premium.",
"Interactive components expose color through filled selection planes, split badges, and paired hover/focus states instead of side stripes, decorative rails, or wallpaper grids."
],
"visualProfile": {
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"border": "solid",
"underlay": false,
"grain": true,
"stickerBadges": true,
"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": "Precision White Complementary Fields 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 each complementary pair to a real product meaning such as confidence versus risk, planned versus live, or source versus output.",
"Use full surfaces, chips, charts, focus rings, and data marks for color so it changes behavior or comprehension.",
"Keep the foundation white, typographic, and calm with only a few saturated fields visible at once.",
"Preserve complete border wraps and rectangular color fields rather than decorative side accents."
],
"dont": [
"Do not use rainbow confetti, generic blobs, neon glow, or arbitrary color sprinkled over neutral components.",
"Do not add colored left rails, side stripes, or stripe-only accents to cards, buttons, rows, or panels.",
"Do not build a square grid wallpaper or textbook page composition; any dot texture must stay barely visible and non-boxy.",
"Do not let the scene become a generic admin dashboard with interchangeable cards and default charts."
]
}
}