Procedural Data Mosaic
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
- 4px
- character
- dark civic-blue tile grout; alerts use a single red left rail or red corner cell, never a full red container
- default width
- 2px
- style
- solid with optional one-cell stepped corners
colors12 items
motion3 items
- duration
- 140ms
- easing
- steps(2, end)
- philosophy
- state changes snap by whole-cell increments like a refreshed terminal map; hover inverts one cell strip rather than fading
radii5 items
- full
- 9999px
- lg
- 0
- md
- 0
- none
- 0
- sm
- 0
shadows3 items
- lg
- 8px 8px 0 rgba(16,32,51,0.24)
- md
- 4px 4px 0 rgba(23,59,95,0.42)
- sm
- 2px 2px 0 #173B5F
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- repeating 8px grid plus sparse 16px heatmap squares aligned to the same lattice
- card style
- square tile panels with 2px navy border, 4px offset shadow, stepped corner cutouts, and cell-index labels
- treatment
- flat civic paper surfaces over a faint 8px bitmap grid; selected regions receive quantized blue-to-red cell fields
typography8 items
- base size
- 16px
- body font
- Atkinson Hyperlegible
- google fonts url
- https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Fragment+Mono:ital@0;1&family=IBM+Plex+Sans+Condensed:wght@500;600;700&display=swap
- heading font
- IBM Plex Sans Condensed
- letter spacing
- -0.015em
- line height
- 1.48
- mono font
- Fragment Mono
- scale ratio
- 1.22
rules
Anchor each screen with one dominant data artifact such as a pixel map or cell matrix, then attach controls and narrative panels to its grid edges rather than floating equal cards.
High information density is allowed when every value sits in an 8px rhythm; leave large civic margins around the main mosaic so the density feels planned, not crowded.
Use cell scale, border weight, and reserved alert red to rank content: civic-blue base areas, amber watch zones, and red action cells; headings act like public notices while mono labels act like instrumentation.
layout
mobile 375px stacks command panels below the mosaic; tablet 768px uses a two-column atlas; desktop 1200px+ uses asymmetric 7/5 civic operations layout
Twelve-column desktop grid based on 8px cells; the primary mosaic spans seven columns and supporting command panels snap to its right and bottom edges.
Whitespace is measured as empty cell fields: 16px between related controls, 32px between panels, and 64px civic breathing room around the main artifact.
guidance
- Make one dominant pixel-data artifact organize the whole page.
- Keep red scarce and tied to urgent state or exception data.
- Align all padding, seams, icons, and charts to an 8px cell rhythm.
- Use mono coordinate labels to explain source, district, and timestamp.
- Do not use rounded glass cards, blurred gradients, or soft SaaS shadows.
- Do not turn every element red, rainbow, or arcade-themed.
- Do not present a component inventory instead of a concrete civic data scene.
- Do not smooth charts into continuous curves when cell matrices can carry the message.
katagami spec
# Procedural Data Mosaic ## Philosophy Procedural Data Mosaic turns civic telemetry into a gridded public interface: every pixel cell behaves like evidence, identity texture, chart mark, and navigation tile at once. The language borrows from heatmaps, 8-bit atlases, terminal alert states, and ceramic mosaic craft, but applies them with contemporary restraint for maps, public services, operations tools, and data-rich brand worlds. ### Values - data as material, not decoration - civic clarity under pressure - low-resolution texture with high-resolution hierarchy - limited-palette discipline - systems that can scale from map to badge to package ### Anti-Values - nostalgic game cosplay without functional data logic - generic dashboard cards that merely wear pixel borders - rainbow heatmaps with no semantic restraint - soft SaaS gradients and arbitrary rounded corners ### Visual Character - Use an 8px base CSS grid with square-corner panels, stepped clip-path notches, and cell-aligned padding so every container locks to a visible pixel lattice. - Layer quantized heatmap backgrounds with repeating-linear-gradient cell seams and conic/radial hot cells, reserving alert red for only the highest-priority marks. - Set large headings in IBM Plex Sans Condensed and operational labels in Fragment Mono with uppercase tracking, creating separate civic poster and terminal voices. - Render charts, badges, progress, and map districts as arrays of square cells instead of smooth bars, with blue baseline cells and red/amber exception cells. - Use no blur and almost no shadow; depth comes from one-pixel dark offsets, doubled borders, and stacked grid panels like printed tiles. ## Tokens ### Borders - **Accent Width**: 4px - **Character**: dark civic-blue tile grout; alerts use a single red left rail or red corner cell, never a full red container - **Default Width**: 2px - **Style**: solid with optional one-cell stepped corners ### Colors | Name | Value | |------|-------| | accent | `#E83D3D` | | background | `#E9F1F5` | | border | `#173B5F` | | error | `#D72638` | | info | `#2C7DB8` | | muted | `#5F7488` | | primary | `#0B4F8A` | | secondary | `#0E2A47` | | success | `#1F9D6A` | | surface | `#F8FBFC` | | text | `#102033` | | warning | `#F2A900` | ### Motion - **Duration**: 140ms - **Easing**: steps(2, end) - **Philosophy**: state changes snap by whole-cell increments like a refreshed terminal map; hover inverts one cell strip rather than fading ### Radii - **Full**: 9999px - **Lg**: 0 - **Md**: 0 - **None**: 0 - **Sm**: 0 ### Shadows - **Lg**: 8px 8px 0 rgba(16,32,51,0.24) - **Md**: 4px 4px 0 rgba(23,59,95,0.42) - **Sm**: 2px 2px 0 #173B5F ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: repeating 8px grid plus sparse 16px heatmap squares aligned to the same lattice - **Card Style**: square tile panels with 2px navy border, 4px offset shadow, stepped corner cutouts, and cell-index labels - **Treatment**: flat civic paper surfaces over a faint 8px bitmap grid; selected regions receive quantized blue-to-red cell fields ### Typography - **Base Size**: 16px - **Body Font**: Atkinson Hyperlegible - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Fragment+Mono:ital@0;1&family=IBM+Plex+Sans+Condensed:wght@500;600;700&display=swap - **Heading Font**: IBM Plex Sans Condensed - **Letter Spacing**: -0.015em - **Line Height**: 1.48 - **Mono Font**: Fragment Mono - **Scale Ratio**: 1.22 ## Rules ### Composition Anchor each screen with one dominant data artifact such as a pixel map or cell matrix, then attach controls and narrative panels to its grid edges rather than floating equal cards. ### Density High information density is allowed when every value sits in an 8px rhythm; leave large civic margins around the main mosaic so the density feels planned, not crowded. ### Hierarchy Use cell scale, border weight, and reserved alert red to rank content: civic-blue base areas, amber watch zones, and red action cells; headings act like public notices while mono labels act like instrumentation. ### Signature Patterns - Quantized heatmap panels appear as CSS grid matrices where every nth cell changes temperature, making charts and backgrounds share one data texture. - Stepped-corner containers use clip-path polygons and doubled borders to make product panels feel like cropped bitmap tiles without decorative radius. - Status controls include a one-cell red or amber rail, mono coordinate labels, and step-timed hover states that move exactly 8px. - Tables and lists replace smooth separators with grout lines and tiny cell chips that encode priority, ownership, or public-service district. - Hero typography overlays the mosaic on dark civic-blue plaques with pixel knockout counters and terminal-style coordinate captions. ## Layout ### Breakpoints mobile 375px stacks command panels below the mosaic; tablet 768px uses a two-column atlas; desktop 1200px+ uses asymmetric 7/5 civic operations layout ### Grid Twelve-column desktop grid based on 8px cells; the primary mosaic spans seven columns and supporting command panels snap to its right and bottom edges. ### Whitespace Whitespace is measured as empty cell fields: 16px between related controls, 32px between panels, and 64px civic breathing room around the main artifact. ## Guidance ### Do - Make one dominant pixel-data artifact organize the whole page. - Keep red scarce and tied to urgent state or exception data. - Align all padding, seams, icons, and charts to an 8px cell rhythm. - Use mono coordinate labels to explain source, district, and timestamp. ### Don't - Do not use rounded glass cards, blurred gradients, or soft SaaS shadows. - Do not turn every element red, rainbow, or arcade-themed. - Do not present a component inventory instead of a concrete civic data scene. - Do not smooth charts into continuous curves when cell matrices can carry the message.
DESIGN.md
---
version: "alpha"
name: "Procedural Data Mosaic"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#E83D3D"
background: "#E9F1F5"
border: "#173B5F"
error: "#D72638"
info: "#2C7DB8"
muted: "#5F7488"
primary: "#0B4F8A"
secondary: "#0E2A47"
success: "#1F9D6A"
surface: "#F8FBFC"
text: "#102033"
warning: "#F2A900"
typography:
headline-lg:
fontFamily: "IBM Plex Sans Condensed"
fontSize: "1.816rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.015em"
headline-md:
fontFamily: "IBM Plex Sans Condensed"
fontSize: "1.488rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.015em"
body-md:
fontFamily: "Atkinson Hyperlegible"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.48
letterSpacing: "-0.015em"
label-md:
fontFamily: "Fragment Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "0px"
md: "0px"
none: "0px"
sm: "0px"
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"
---
# Procedural Data Mosaic
## Overview
Procedural Data Mosaic turns civic telemetry into a gridded public interface: every pixel cell behaves like evidence, identity texture, chart mark, and navigation tile at once. The language borrows from heatmaps, 8-bit atlases, terminal alert states, and ceramic mosaic craft, but applies them with contemporary restraint for maps, public services, operations tools, and data-rich brand worlds.
### Values
- data as material, not decoration
- civic clarity under pressure
- low-resolution texture with high-resolution hierarchy
- limited-palette discipline
- systems that can scale from map to badge to package
### Anti-Values
- nostalgic game cosplay without functional data logic
- generic dashboard cards that merely wear pixel borders
- rainbow heatmaps with no semantic restraint
- soft SaaS gradients and arbitrary rounded corners
### Visual Character
- Use an 8px base CSS grid with square-corner panels, stepped clip-path notches, and cell-aligned padding so every container locks to a visible pixel lattice.
- Layer quantized heatmap backgrounds with repeating-linear-gradient cell seams and conic/radial hot cells, reserving alert red for only the highest-priority marks.
- Set large headings in IBM Plex Sans Condensed and operational labels in Fragment Mono with uppercase tracking, creating separate civic poster and terminal voices.
- Render charts, badges, progress, and map districts as arrays of square cells instead of smooth bars, with blue baseline cells and red/amber exception cells.
- Use no blur and almost no shadow; depth comes from one-pixel dark offsets, doubled borders, and stacked grid panels like printed tiles.
## 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 | `#E83D3D` |
| background | `#E9F1F5` |
| border | `#173B5F` |
| error | `#D72638` |
| info | `#2C7DB8` |
| muted | `#5F7488` |
| primary | `#0B4F8A` |
| secondary | `#0E2A47` |
| success | `#1F9D6A` |
| surface | `#F8FBFC` |
| text | `#102033` |
| warning | `#F2A900` |
## Typography
- **Headline-Lg**: IBM Plex Sans Condensed, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: IBM Plex Sans Condensed, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Atkinson Hyperlegible, 16px, weight 400, line-height 1.48.
- **Label-Md**: Fragment 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 stacks command panels below the mosaic; tablet 768px uses a two-column atlas; desktop 1200px+ uses asymmetric 7/5 civic operations layout
### Grid
Twelve-column desktop grid based on 8px cells; the primary mosaic spans seven columns and supporting command panels snap to its right and bottom edges.
### Whitespace
Whitespace is measured as empty cell fields: 16px between related controls, 32px between panels, and 64px civic breathing room around the main artifact.
## Elevation & Depth
### Shadows
- **Lg**: 8px 8px 0 rgba(16,32,51,0.24)
- **Md**: 4px 4px 0 rgba(23,59,95,0.42)
- **Sm**: 2px 2px 0 #173B5F
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `0px`
- **Md**: `0px`
- **None**: `0px`
- **Sm**: `0px`
### Surfaces
- **Bg Pattern**: repeating 8px grid plus sparse 16px heatmap squares aligned to the same lattice
- **Card Style**: square tile panels with 2px navy border, 4px offset shadow, stepped corner cutouts, and cell-index labels
- **Treatment**: flat civic paper surfaces over a faint 8px bitmap grid; selected regions receive quantized blue-to-red cell fields
### Borders
- **Accent Width**: 4px
- **Character**: dark civic-blue tile grout; alerts use a single red left rail or red corner cell, never a full red container
- **Default Width**: 2px
- **Style**: solid with optional one-cell stepped corners
## Components
### Composition
Anchor each screen with one dominant data artifact such as a pixel map or cell matrix, then attach controls and narrative panels to its grid edges rather than floating equal cards.
### Density
High information density is allowed when every value sits in an 8px rhythm; leave large civic margins around the main mosaic so the density feels planned, not crowded.
### Hierarchy
Use cell scale, border weight, and reserved alert red to rank content: civic-blue base areas, amber watch zones, and red action cells; headings act like public notices while mono labels act like instrumentation.
### Signature Patterns
- Quantized heatmap panels appear as CSS grid matrices where every nth cell changes temperature, making charts and backgrounds share one data texture.
- Stepped-corner containers use clip-path polygons and doubled borders to make product panels feel like cropped bitmap tiles without decorative radius.
- Status controls include a one-cell red or amber rail, mono coordinate labels, and step-timed hover states that move exactly 8px.
- Tables and lists replace smooth separators with grout lines and tiny cell chips that encode priority, ownership, or public-service district.
- Hero typography overlays the mosaic on dark civic-blue plaques with pixel knockout counters and terminal-style coordinate captions.
## 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-019e6996-1e42-7b90-8222-5e83fe93c7af/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 Make one dominant pixel-data artifact organize the whole page.
- Do Keep red scarce and tied to urgent state or exception data.
- Do Align all padding, seams, icons, and charts to an 8px cell rhythm.
- Do Use mono coordinate labels to explain source, district, and timestamp.
- Don't Do not use rounded glass cards, blurred gradients, or soft SaaS shadows.
- Don't Do not turn every element red, rainbow, or arcade-themed.
- Don't Do not present a component inventory instead of a concrete civic data scene.
- Don't Do not smooth charts into continuous curves when cell matrices can carry the message.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "procedural-data-mosaic",
"type": "registry:theme",
"title": "Procedural Data Mosaic shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#E9F1F5",
"foreground": "#102033",
"card": "#F8FBFC",
"card-foreground": "#102033",
"popover": "#F8FBFC",
"popover-foreground": "#102033",
"primary": "#0B4F8A",
"primary-foreground": "#ffffff",
"secondary": "#0E2A47",
"secondary-foreground": "#ffffff",
"muted": "#5F7488",
"muted-foreground": "#102033",
"accent": "#E83D3D",
"accent-foreground": "#ffffff",
"destructive": "#D72638",
"border": "#173B5F",
"input": "#173B5F",
"ring": "#E83D3D",
"chart-1": "#0B4F8A",
"chart-2": "#0E2A47",
"chart-3": "#E83D3D",
"chart-4": "#1F9D6A",
"chart-5": "#F2A900",
"sidebar": "#F8FBFC",
"sidebar-foreground": "#102033",
"sidebar-primary": "#0B4F8A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#2C7DB8",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#173B5F",
"sidebar-ring": "#E83D3D",
"radius": "0"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#0B4F8A",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#E83D3D",
"accent-foreground": "#ffffff",
"destructive": "#D72638",
"border": "#303642",
"input": "#303642",
"ring": "#E83D3D",
"chart-1": "#0B4F8A",
"chart-2": "#0E2A47",
"chart-3": "#E83D3D",
"chart-4": "#1F9D6A",
"chart-5": "#F2A900",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#0B4F8A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#E83D3D",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#E83D3D",
"radius": "0"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e6996-1e42-7b90-8222-5e83fe93c7af",
"slug": "procedural-data-mosaic",
"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: #E9F1F5;
--foreground: #102033;
--card: #F8FBFC;
--card-foreground: #102033;
--popover: #F8FBFC;
--popover-foreground: #102033;
--primary: #0B4F8A;
--primary-foreground: #ffffff;
--secondary: #0E2A47;
--secondary-foreground: #ffffff;
--muted: #5F7488;
--muted-foreground: #102033;
--accent: #E83D3D;
--accent-foreground: #ffffff;
--destructive: #D72638;
--border: #173B5F;
--input: #173B5F;
--ring: #E83D3D;
--chart-1: #0B4F8A;
--chart-2: #0E2A47;
--chart-3: #E83D3D;
--chart-4: #1F9D6A;
--chart-5: #F2A900;
--sidebar: #F8FBFC;
--sidebar-foreground: #102033;
--sidebar-primary: #0B4F8A;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #2C7DB8;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #173B5F;
--sidebar-ring: #E83D3D;
--radius: 0;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #0B4F8A;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #E83D3D;
--accent-foreground: #ffffff;
--destructive: #D72638;
--border: #303642;
--input: #303642;
--ring: #E83D3D;
--chart-1: #0B4F8A;
--chart-2: #0E2A47;
--chart-3: #E83D3D;
--chart-4: #1F9D6A;
--chart-5: #F2A900;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #0B4F8A;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #E83D3D;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #E83D3D;
--radius: 0;
}
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 ProceduralDataMosaicShadcnKit() {
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">Procedural Data Mosaic</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",
"name": "procedural-data-mosaic",
"type": "registry:theme",
"title": "Procedural Data Mosaic shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#E9F1F5",
"foreground": "#102033",
"card": "#F8FBFC",
"card-foreground": "#102033",
"popover": "#F8FBFC",
"popover-foreground": "#102033",
"primary": "#0B4F8A",
"primary-foreground": "#ffffff",
"secondary": "#0E2A47",
"secondary-foreground": "#ffffff",
"muted": "#5F7488",
"muted-foreground": "#102033",
"accent": "#E83D3D",
"accent-foreground": "#ffffff",
"destructive": "#D72638",
"border": "#173B5F",
"input": "#173B5F",
"ring": "#E83D3D",
"chart-1": "#0B4F8A",
"chart-2": "#0E2A47",
"chart-3": "#E83D3D",
"chart-4": "#1F9D6A",
"chart-5": "#F2A900",
"sidebar": "#F8FBFC",
"sidebar-foreground": "#102033",
"sidebar-primary": "#0B4F8A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#2C7DB8",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#173B5F",
"sidebar-ring": "#E83D3D",
"radius": "0"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#0B4F8A",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#E83D3D",
"accent-foreground": "#ffffff",
"destructive": "#D72638",
"border": "#303642",
"input": "#303642",
"ring": "#E83D3D",
"chart-1": "#0B4F8A",
"chart-2": "#0E2A47",
"chart-3": "#E83D3D",
"chart-4": "#1F9D6A",
"chart-5": "#F2A900",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#0B4F8A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#E83D3D",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#E83D3D",
"radius": "0"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e6996-1e42-7b90-8222-5e83fe93c7af",
"slug": "procedural-data-mosaic",
"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"
]
}
}
}
# Procedural Data Mosaic shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e6996-1e42-7b90-8222-5e83fe93c7af`
Slug: `procedural-data-mosaic`
## Intent
Procedural Data Mosaic turns civic telemetry into a gridded public interface: every pixel cell behaves like evidence, identity texture, chart mark, and navigation tile at once. The language borrows from heatmaps, 8-bit atlases, terminal alert states, and ceramic mosaic craft, but applies them with contemporary restraint for maps, public services, operations tools, and data-rich brand worlds.
## 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": "#E83D3D",
"background": "#E9F1F5",
"border": "#173B5F",
"error": "#D72638",
"info": "#2C7DB8",
"muted": "#5F7488",
"primary": "#0B4F8A",
"secondary": "#0E2A47",
"success": "#1F9D6A",
"surface": "#F8FBFC",
"text": "#102033",
"warning": "#F2A900"
}
Typography:
{
"base_size": "16px",
"body_font": "Atkinson Hyperlegible",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Fragment+Mono:ital@0;1&family=IBM+Plex+Sans+Condensed:wght@500;600;700&display=swap",
"heading_font": "IBM Plex Sans Condensed",
"letter_spacing": "-0.015em",
"line_height": 1.48,
"mono_font": "Fragment Mono",
"scale_ratio": 1.22
}
## Visual character to preserve
- Use an 8px base CSS grid with square-corner panels, stepped clip-path notches, and cell-aligned padding so every container locks to a visible pixel lattice.
- Layer quantized heatmap backgrounds with repeating-linear-gradient cell seams and conic/radial hot cells, reserving alert red for only the highest-priority marks.
- Set large headings in IBM Plex Sans Condensed and operational labels in Fragment Mono with uppercase tracking, creating separate civic poster and terminal voices.
- Render charts, badges, progress, and map districts as arrays of square cells instead of smooth bars, with blue baseline cells and red/amber exception cells.
- Use no blur and almost no shadow; depth comes from one-pixel dark offsets, doubled borders, and stacked grid panels like printed tiles.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": true,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
}
## Signature component recipes
### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.
### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.
### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.
### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.
### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.
## Preview shots
- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.
## Implementation contract
- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/procedural-data-mosaic/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: Make one dominant pixel-data artifact organize the whole page.; Keep red scarce and tied to urgent state or exception data.; Align all padding, seams, icons, and charts to an 8px cell rhythm.; Use mono coordinate labels to explain source, district, and timestamp.
- Do not: Do not use rounded glass cards, blurred gradients, or soft SaaS shadows.; Do not turn every element red, rainbow, or arcade-themed.; Do not present a component inventory instead of a concrete civic data scene.; Do not smooth charts into continuous curves when cell matrices can carry the message.
## 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 ProceduralDataMosaicShadcnKit() {
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">Procedural Data Mosaic</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 stacks command panels below the mosaic; tablet 768px uses a two-column atlas; desktop 1200px+ uses asymmetric 7/5 civic operations layout",
"grid": "Twelve-column desktop grid based on 8px cells; the primary mosaic spans seven columns and supporting command panels snap to its right and bottom edges.",
"whitespace": "Whitespace is measured as empty cell fields: 16px between related controls, 32px between panels, and 64px civic breathing room around the main artifact."
}
{
"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-019e6996-1e42-7b90-8222-5e83fe93c7af",
"name": "Procedural Data Mosaic",
"slug": "procedural-data-mosaic"
},
"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": [
"Use an 8px base CSS grid with square-corner panels, stepped clip-path notches, and cell-aligned padding so every container locks to a visible pixel lattice.",
"Layer quantized heatmap backgrounds with repeating-linear-gradient cell seams and conic/radial hot cells, reserving alert red for only the highest-priority marks.",
"Set large headings in IBM Plex Sans Condensed and operational labels in Fragment Mono with uppercase tracking, creating separate civic poster and terminal voices.",
"Render charts, badges, progress, and map districts as arrays of square cells instead of smooth bars, with blue baseline cells and red/amber exception cells.",
"Use no blur and almost no shadow; depth comes from one-pixel dark offsets, doubled borders, and stacked grid panels like printed tiles."
],
"visualProfile": {
"family": "brutalist",
"material": "ink",
"contour": "default",
"border": "solid",
"underlay": true,
"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": "Procedural Data Mosaic 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": [
"Make one dominant pixel-data artifact organize the whole page.",
"Keep red scarce and tied to urgent state or exception data.",
"Align all padding, seams, icons, and charts to an 8px cell rhythm.",
"Use mono coordinate labels to explain source, district, and timestamp."
],
"dont": [
"Do not use rounded glass cards, blurred gradients, or soft SaaS shadows.",
"Do not turn every element red, rainbow, or arcade-themed.",
"Do not present a component inventory instead of a concrete civic data scene.",
"Do not smooth charts into continuous curves when cell matrices can carry the message."
]
}
}