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
- hard square civic-blue rules with red registration ticks and no rounded joins
- default width
- 1px
- style
- solid double-cell
colors12 items
motion3 items
- duration
- 140ms
- easing
- steps(2, end)
- philosophy
- state changes snap between quantized cells; hover and focus move by one 8px grid unit rather than fading
radii5 items
- full
- 0
- lg
- 0
- md
- 0
- none
- 0
- sm
- 0
shadows3 items
- lg
- 14px 14px 0 rgba(5,14,22,0.72)
- md
- 8px 8px 0 rgba(5,14,22,0.55)
- sm
- 4px 4px 0 rgba(227,59,47,0.28)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- layered linear gradients forming faint municipal map cells and sparse red alert pixels
- card style
- square double-border panels with clipped pixel notches and quantized cell headers
- treatment
- ink-dark civic panels over a fixed 8px bitmap grid
typography8 items
- base size
- 16px
- body font
- Atkinson Hyperlegible
- google fonts url
- https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Chakra+Petch:wght@500;600;700&family=JetBrains+Mono:wght@400;600;700&display=swap
- heading font
- Chakra Petch
- letter spacing
- -0.02em
- line height
- 1.48
- mono font
- JetBrains Mono
- scale ratio
- 1.25
rules
Build around one dominant operational mosaic map that occupies the visual center; secondary tools dock as tile rails, not equal cards.
High but ordered density: many small cells are allowed when labels, spacing bands, and color quantization keep scanning predictable.
Use scale, cell count, border weight, and alert-red registration marks to distinguish command surfaces from read-only telemetry.
layout
1440 desktop, 900 tablet rail wrap, 640 mobile single column with horizontal tile bands
A 12-column desktop grid nested over an 8px bitmap cell; central map spans 7 columns, rails span 3 and 2 columns.
Whitespace appears as deliberate empty cell bands: 8px inside groups, 24px between tools, and 64px around command changes.
guidance
- Anchor every screen with a meaningful mosaic or matrix artifact tied to product data.
- Keep colors quantized and name their status meaning before using them decoratively.
- Use square geometry, double borders, and one-cell motion consistently across components.
- Let monospace numerals and labels carry operational precision.
- Do not use rounded glass cards, blurred gradients, or soft shadows.
- Do not quote arcade sprites unless the sprite is an actual data state or navigation marker.
- Do not create generic dashboards with equal KPI cards instead of a dominant spatial artifact.
- Do not let red appear as decoration; reserve it for real alert, selection, or command hierarchy.
katagami spec
# Procedural Data Mosaic ## Philosophy Procedural Data Mosaic turns civic telemetry into a disciplined bitmap field: each pixel cell is both an interface unit and an identity mark, using quantized heatmaps, municipal blues, and hard alert reds to make public operations feel legible, urgent, and authored rather than nostalgic. ### Values - data made spatial and tactile - low-resolution restraint with high-information density - civic seriousness over arcade novelty - status systems that read at a glance ### Anti-Values - decorative retro gaming references without operational meaning - soft SaaS cards that erase the pixel grid - gradients or glass effects that blur the quantized data logic ### Visual Character - All major surfaces sit on an 8px bitmap grid with square corners, stepped notches, and background-size cell patterns rather than rounded card stacks. - Quantized heatmap blocks use discrete blue-to-red classes with no gradients, turning charts, badges, and navigation states into visible pixel cells. - Key panels use double-line civic borders with offset red or cyan registration ticks that behave like printed emergency-map crop marks. - Typography pairs condensed squared headings with monospace numeric labels, using tight tracking and tabular data rows to echo terminal readouts. - Responsive layouts preserve one dominant mosaic map artifact while side rails collapse into stacked tile bands instead of generic mobile cards. ## Tokens ### Borders - **Accent Width**: 4px - **Character**: hard square civic-blue rules with red registration ticks and no rounded joins - **Default Width**: 1px - **Style**: solid double-cell ### Colors | Name | Value | |------|-------| | accent | `#E33B2F` | | background | `#071927` | | border | `#2A6D91` | | error | `#FF4A3D` | | info | `#6CC8FF` | | muted | `#86A7B8` | | primary | `#0E4C8A` | | secondary | `#57A6D9` | | success | `#22B982` | | surface | `#102F45` | | text | `#EAF4F8` | | warning | `#F0B83E` | ### Motion - **Duration**: 140ms - **Easing**: steps(2, end) - **Philosophy**: state changes snap between quantized cells; hover and focus move by one 8px grid unit rather than fading ### Radii - **Full**: 0 - **Lg**: 0 - **Md**: 0 - **None**: 0 - **Sm**: 0 ### Shadows - **Lg**: 14px 14px 0 rgba(5,14,22,0.72) - **Md**: 8px 8px 0 rgba(5,14,22,0.55) - **Sm**: 4px 4px 0 rgba(227,59,47,0.28) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: layered linear gradients forming faint municipal map cells and sparse red alert pixels - **Card Style**: square double-border panels with clipped pixel notches and quantized cell headers - **Treatment**: ink-dark civic panels over a fixed 8px bitmap grid ### Typography - **Base Size**: 16px - **Body Font**: Atkinson Hyperlegible - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Chakra+Petch:wght@500;600;700&family=JetBrains+Mono:wght@400;600;700&display=swap - **Heading Font**: Chakra Petch - **Letter Spacing**: -0.02em - **Line Height**: 1.48 - **Mono Font**: JetBrains Mono - **Scale Ratio**: 1.25 ## Rules ### Composition Build around one dominant operational mosaic map that occupies the visual center; secondary tools dock as tile rails, not equal cards. ### Density High but ordered density: many small cells are allowed when labels, spacing bands, and color quantization keep scanning predictable. ### Hierarchy Use scale, cell count, border weight, and alert-red registration marks to distinguish command surfaces from read-only telemetry. ### Signature Patterns - Mosaic map matrices appear in product content, backgrounds, and controls, with each cell snapped to 8px and assigned one discrete status color. - Panel corners use stepped pixel notches created with clip-path or pseudo-elements, making containers feel plotted from bitmap coordinates. - Important actions and warnings receive red/cyan registration ticks offset outside the border to create a civic emergency-print artifact. - Tables and forms group data into monospace tile rows where active rows invert to pale text on civic-blue with a left alert-cell strip. - Motion uses CSS steps timing and one-cell translate offsets so interaction feels computational without becoming game-like. ## Layout ### Breakpoints 1440 desktop, 900 tablet rail wrap, 640 mobile single column with horizontal tile bands ### Grid A 12-column desktop grid nested over an 8px bitmap cell; central map spans 7 columns, rails span 3 and 2 columns. ### Whitespace Whitespace appears as deliberate empty cell bands: 8px inside groups, 24px between tools, and 64px around command changes. ## Guidance ### Do - Anchor every screen with a meaningful mosaic or matrix artifact tied to product data. - Keep colors quantized and name their status meaning before using them decoratively. - Use square geometry, double borders, and one-cell motion consistently across components. - Let monospace numerals and labels carry operational precision. ### Don't - Do not use rounded glass cards, blurred gradients, or soft shadows. - Do not quote arcade sprites unless the sprite is an actual data state or navigation marker. - Do not create generic dashboards with equal KPI cards instead of a dominant spatial artifact. - Do not let red appear as decoration; reserve it for real alert, selection, or command hierarchy.
DESIGN.md
---
version: "alpha"
name: "Procedural Data Mosaic"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#E33B2F"
background: "#071927"
border: "#2A6D91"
error: "#FF4A3D"
info: "#6CC8FF"
muted: "#86A7B8"
primary: "#0E4C8A"
secondary: "#57A6D9"
success: "#22B982"
surface: "#102F45"
text: "#EAF4F8"
warning: "#F0B83E"
typography:
headline-lg:
fontFamily: "Chakra Petch"
fontSize: "1.953rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.02em"
headline-md:
fontFamily: "Chakra Petch"
fontSize: "1.563rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.02em"
body-md:
fontFamily: "Atkinson Hyperlegible"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.48
letterSpacing: "-0.02em"
label-md:
fontFamily: "JetBrains Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "0px"
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 disciplined bitmap field: each pixel cell is both an interface unit and an identity mark, using quantized heatmaps, municipal blues, and hard alert reds to make public operations feel legible, urgent, and authored rather than nostalgic.
### Values
- data made spatial and tactile
- low-resolution restraint with high-information density
- civic seriousness over arcade novelty
- status systems that read at a glance
### Anti-Values
- decorative retro gaming references without operational meaning
- soft SaaS cards that erase the pixel grid
- gradients or glass effects that blur the quantized data logic
### Visual Character
- All major surfaces sit on an 8px bitmap grid with square corners, stepped notches, and background-size cell patterns rather than rounded card stacks.
- Quantized heatmap blocks use discrete blue-to-red classes with no gradients, turning charts, badges, and navigation states into visible pixel cells.
- Key panels use double-line civic borders with offset red or cyan registration ticks that behave like printed emergency-map crop marks.
- Typography pairs condensed squared headings with monospace numeric labels, using tight tracking and tabular data rows to echo terminal readouts.
- Responsive layouts preserve one dominant mosaic map artifact while side rails collapse into stacked tile bands instead of generic mobile cards.
## 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 | `#E33B2F` |
| background | `#071927` |
| border | `#2A6D91` |
| error | `#FF4A3D` |
| info | `#6CC8FF` |
| muted | `#86A7B8` |
| primary | `#0E4C8A` |
| secondary | `#57A6D9` |
| success | `#22B982` |
| surface | `#102F45` |
| text | `#EAF4F8` |
| warning | `#F0B83E` |
## Typography
- **Headline-Lg**: Chakra Petch, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Chakra Petch, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Atkinson Hyperlegible, 16px, weight 400, line-height 1.48.
- **Label-Md**: JetBrains 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
1440 desktop, 900 tablet rail wrap, 640 mobile single column with horizontal tile bands
### Grid
A 12-column desktop grid nested over an 8px bitmap cell; central map spans 7 columns, rails span 3 and 2 columns.
### Whitespace
Whitespace appears as deliberate empty cell bands: 8px inside groups, 24px between tools, and 64px around command changes.
## Elevation & Depth
### Shadows
- **Lg**: 14px 14px 0 rgba(5,14,22,0.72)
- **Md**: 8px 8px 0 rgba(5,14,22,0.55)
- **Sm**: 4px 4px 0 rgba(227,59,47,0.28)
## Shapes
### Rounded
- **Full**: `0px`
- **Lg**: `0px`
- **Md**: `0px`
- **None**: `0px`
- **Sm**: `0px`
### Surfaces
- **Bg Pattern**: layered linear gradients forming faint municipal map cells and sparse red alert pixels
- **Card Style**: square double-border panels with clipped pixel notches and quantized cell headers
- **Treatment**: ink-dark civic panels over a fixed 8px bitmap grid
### Borders
- **Accent Width**: 4px
- **Character**: hard square civic-blue rules with red registration ticks and no rounded joins
- **Default Width**: 1px
- **Style**: solid double-cell
## Components
### Composition
Build around one dominant operational mosaic map that occupies the visual center; secondary tools dock as tile rails, not equal cards.
### Density
High but ordered density: many small cells are allowed when labels, spacing bands, and color quantization keep scanning predictable.
### Hierarchy
Use scale, cell count, border weight, and alert-red registration marks to distinguish command surfaces from read-only telemetry.
### Signature Patterns
- Mosaic map matrices appear in product content, backgrounds, and controls, with each cell snapped to 8px and assigned one discrete status color.
- Panel corners use stepped pixel notches created with clip-path or pseudo-elements, making containers feel plotted from bitmap coordinates.
- Important actions and warnings receive red/cyan registration ticks offset outside the border to create a civic emergency-print artifact.
- Tables and forms group data into monospace tile rows where active rows invert to pale text on civic-blue with a left alert-cell strip.
- Motion uses CSS steps timing and one-cell translate offsets so interaction feels computational without becoming game-like.
## 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-019e66f7-ee8b-7e71-ba2d-b77fc725a49f/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 Anchor every screen with a meaningful mosaic or matrix artifact tied to product data.
- Do Keep colors quantized and name their status meaning before using them decoratively.
- Do Use square geometry, double borders, and one-cell motion consistently across components.
- Do Let monospace numerals and labels carry operational precision.
- Don't Do not use rounded glass cards, blurred gradients, or soft shadows.
- Don't Do not quote arcade sprites unless the sprite is an actual data state or navigation marker.
- Don't Do not create generic dashboards with equal KPI cards instead of a dominant spatial artifact.
- Don't Do not let red appear as decoration; reserve it for real alert, selection, or command hierarchy.
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": "#071927",
"foreground": "#EAF4F8",
"card": "#102F45",
"card-foreground": "#EAF4F8",
"popover": "#102F45",
"popover-foreground": "#EAF4F8",
"primary": "#0E4C8A",
"primary-foreground": "#ffffff",
"secondary": "#57A6D9",
"secondary-foreground": "#ffffff",
"muted": "#86A7B8",
"muted-foreground": "#EAF4F8",
"accent": "#E33B2F",
"accent-foreground": "#ffffff",
"destructive": "#FF4A3D",
"border": "#2A6D91",
"input": "#2A6D91",
"ring": "#E33B2F",
"chart-1": "#0E4C8A",
"chart-2": "#57A6D9",
"chart-3": "#E33B2F",
"chart-4": "#22B982",
"chart-5": "#F0B83E",
"sidebar": "#102F45",
"sidebar-foreground": "#EAF4F8",
"sidebar-primary": "#0E4C8A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#6CC8FF",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#2A6D91",
"sidebar-ring": "#E33B2F",
"radius": "0"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#0E4C8A",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#E33B2F",
"accent-foreground": "#ffffff",
"destructive": "#FF4A3D",
"border": "#303642",
"input": "#303642",
"ring": "#E33B2F",
"chart-1": "#0E4C8A",
"chart-2": "#57A6D9",
"chart-3": "#E33B2F",
"chart-4": "#22B982",
"chart-5": "#F0B83E",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#0E4C8A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#E33B2F",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#E33B2F",
"radius": "0"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e66f7-ee8b-7e71-ba2d-b77fc725a49f",
"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: #071927;
--foreground: #EAF4F8;
--card: #102F45;
--card-foreground: #EAF4F8;
--popover: #102F45;
--popover-foreground: #EAF4F8;
--primary: #0E4C8A;
--primary-foreground: #ffffff;
--secondary: #57A6D9;
--secondary-foreground: #ffffff;
--muted: #86A7B8;
--muted-foreground: #EAF4F8;
--accent: #E33B2F;
--accent-foreground: #ffffff;
--destructive: #FF4A3D;
--border: #2A6D91;
--input: #2A6D91;
--ring: #E33B2F;
--chart-1: #0E4C8A;
--chart-2: #57A6D9;
--chart-3: #E33B2F;
--chart-4: #22B982;
--chart-5: #F0B83E;
--sidebar: #102F45;
--sidebar-foreground: #EAF4F8;
--sidebar-primary: #0E4C8A;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #6CC8FF;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #2A6D91;
--sidebar-ring: #E33B2F;
--radius: 0;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #0E4C8A;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #E33B2F;
--accent-foreground: #ffffff;
--destructive: #FF4A3D;
--border: #303642;
--input: #303642;
--ring: #E33B2F;
--chart-1: #0E4C8A;
--chart-2: #57A6D9;
--chart-3: #E33B2F;
--chart-4: #22B982;
--chart-5: #F0B83E;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #0E4C8A;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #E33B2F;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #E33B2F;
--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": "#071927",
"foreground": "#EAF4F8",
"card": "#102F45",
"card-foreground": "#EAF4F8",
"popover": "#102F45",
"popover-foreground": "#EAF4F8",
"primary": "#0E4C8A",
"primary-foreground": "#ffffff",
"secondary": "#57A6D9",
"secondary-foreground": "#ffffff",
"muted": "#86A7B8",
"muted-foreground": "#EAF4F8",
"accent": "#E33B2F",
"accent-foreground": "#ffffff",
"destructive": "#FF4A3D",
"border": "#2A6D91",
"input": "#2A6D91",
"ring": "#E33B2F",
"chart-1": "#0E4C8A",
"chart-2": "#57A6D9",
"chart-3": "#E33B2F",
"chart-4": "#22B982",
"chart-5": "#F0B83E",
"sidebar": "#102F45",
"sidebar-foreground": "#EAF4F8",
"sidebar-primary": "#0E4C8A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#6CC8FF",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#2A6D91",
"sidebar-ring": "#E33B2F",
"radius": "0"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#0E4C8A",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#E33B2F",
"accent-foreground": "#ffffff",
"destructive": "#FF4A3D",
"border": "#303642",
"input": "#303642",
"ring": "#E33B2F",
"chart-1": "#0E4C8A",
"chart-2": "#57A6D9",
"chart-3": "#E33B2F",
"chart-4": "#22B982",
"chart-5": "#F0B83E",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#0E4C8A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#E33B2F",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#E33B2F",
"radius": "0"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e66f7-ee8b-7e71-ba2d-b77fc725a49f",
"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-019e66f7-ee8b-7e71-ba2d-b77fc725a49f`
Slug: `procedural-data-mosaic`
## Intent
Procedural Data Mosaic turns civic telemetry into a disciplined bitmap field: each pixel cell is both an interface unit and an identity mark, using quantized heatmaps, municipal blues, and hard alert reds to make public operations feel legible, urgent, and authored rather than nostalgic.
## 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": "#E33B2F",
"background": "#071927",
"border": "#2A6D91",
"error": "#FF4A3D",
"info": "#6CC8FF",
"muted": "#86A7B8",
"primary": "#0E4C8A",
"secondary": "#57A6D9",
"success": "#22B982",
"surface": "#102F45",
"text": "#EAF4F8",
"warning": "#F0B83E"
}
Typography:
{
"base_size": "16px",
"body_font": "Atkinson Hyperlegible",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Chakra+Petch:wght@500;600;700&family=JetBrains+Mono:wght@400;600;700&display=swap",
"heading_font": "Chakra Petch",
"letter_spacing": "-0.02em",
"line_height": 1.48,
"mono_font": "JetBrains Mono",
"scale_ratio": 1.25
}
## Visual character to preserve
- All major surfaces sit on an 8px bitmap grid with square corners, stepped notches, and background-size cell patterns rather than rounded card stacks.
- Quantized heatmap blocks use discrete blue-to-red classes with no gradients, turning charts, badges, and navigation states into visible pixel cells.
- Key panels use double-line civic borders with offset red or cyan registration ticks that behave like printed emergency-map crop marks.
- Typography pairs condensed squared headings with monospace numeric labels, using tight tracking and tabular data rows to echo terminal readouts.
- Responsive layouts preserve one dominant mosaic map artifact while side rails collapse into stacked tile bands instead of generic mobile cards.
## ShadSync visual profile
{
"family": "brutalist",
"material": "ink",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": false,
"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: Anchor every screen with a meaningful mosaic or matrix artifact tied to product data.; Keep colors quantized and name their status meaning before using them decoratively.; Use square geometry, double borders, and one-cell motion consistently across components.; Let monospace numerals and labels carry operational precision.
- Do not: Do not use rounded glass cards, blurred gradients, or soft shadows.; Do not quote arcade sprites unless the sprite is an actual data state or navigation marker.; Do not create generic dashboards with equal KPI cards instead of a dominant spatial artifact.; Do not let red appear as decoration; reserve it for real alert, selection, or command hierarchy.
## 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": "1440 desktop, 900 tablet rail wrap, 640 mobile single column with horizontal tile bands",
"grid": "A 12-column desktop grid nested over an 8px bitmap cell; central map spans 7 columns, rails span 3 and 2 columns.",
"whitespace": "Whitespace appears as deliberate empty cell bands: 8px inside groups, 24px between tools, and 64px around command changes."
}
{
"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-019e66f7-ee8b-7e71-ba2d-b77fc725a49f",
"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": [
"All major surfaces sit on an 8px bitmap grid with square corners, stepped notches, and background-size cell patterns rather than rounded card stacks.",
"Quantized heatmap blocks use discrete blue-to-red classes with no gradients, turning charts, badges, and navigation states into visible pixel cells.",
"Key panels use double-line civic borders with offset red or cyan registration ticks that behave like printed emergency-map crop marks.",
"Typography pairs condensed squared headings with monospace numeric labels, using tight tracking and tabular data rows to echo terminal readouts.",
"Responsive layouts preserve one dominant mosaic map artifact while side rails collapse into stacked tile bands instead of generic mobile cards."
],
"visualProfile": {
"family": "brutalist",
"material": "ink",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": false,
"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": [
"Anchor every screen with a meaningful mosaic or matrix artifact tied to product data.",
"Keep colors quantized and name their status meaning before using them decoratively.",
"Use square geometry, double borders, and one-cell motion consistently across components.",
"Let monospace numerals and labels carry operational precision."
],
"dont": [
"Do not use rounded glass cards, blurred gradients, or soft shadows.",
"Do not quote arcade sprites unless the sprite is an actual data state or navigation marker.",
"Do not create generic dashboards with equal KPI cards instead of a dominant spatial artifact.",
"Do not let red appear as decoration; reserve it for real alert, selection, or command hierarchy."
]
}
}