Systematic Illustration Atlas
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
colors12 items
typography8 items
- heading font
- Fraunces
- body font
- Source Sans 3
- mono font
- IBM Plex Mono
- base size
- 16px
- scale ratio
- 1.25
- line height
- 1.55
- letter spacing
- -0.015em
- google fonts url
- https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,600;9..144,700&family=IBM+Plex+Mono:wght@500;600&family=Source+Sans+3:wght@400;500;600;700&display=swap
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
radii5 items
- none
- 0
- sm
- 6px
- md
- 10px
- lg
- 18px
- full
- 9999px
shadows3 items
- sm
- 4px 4px 0 #24364B
- md
- 8px 8px 0 rgba(36,54,75,0.22)
- lg
- 14px 14px 0 rgba(36,54,75,0.16)
surfaces3 items
- treatment
- warm paper background with blueprint dot grid and white inked panels
- card style
- white cards with 2px navy outline, rounded corners, and controlled offset shadow
- bg pattern
- radial dot grid plus oversized translucent rounded blocks
borders4 items
- default width
- 2px
- accent width
- 4px
- style
- solid
- character
- inked product-documentation linework with occasional thick accent rails
motion3 items
- duration
- 180ms
- easing
- cubic-bezier(0.2, 0.8, 0.2, 1)
- philosophy
- small instructional state changes only; callouts lift and connectors draw attention without decorative bounce
rules
Build scenes as annotated product diagrams: a dominant interface or editorial panel, a supporting illustration vignette, and labeled connector chips aligned to an 8px grid.
Use Fraunces for concise editorial headlines, Source Sans 3 for explanatory UI copy, and IBM Plex Mono for labels, IDs, tokens, and measurement notes.
Moderate information density with generous margins; each illustration cluster should include one focal action and no more than three accent callouts.
layout
12-column desktop grid with 8px baseline; tablet collapses to 6 columns and mobile to a single annotated stack.
mobile 375px, tablet 768px, desktop 1200px and above
Use 24px minimum internal panel padding and 48-64px section rhythm so diagram labels breathe and remain readable.
guidance
- Use illustrations to clarify product flows, brand promises, or editorial arguments.
- Limit accents to coral, cyan-blue, and small success green moments against the restrained base palette.
- Document shape, stroke, and label rules beside example scenes so teams can reproduce them.
- Do not introduce new character styles, painterly gradients, or random decorative stickers.
- Do not place text over busy imagery or rely on color alone for meaning.
- Do not use large illustrations when a concise label, icon, or interface state would communicate better.
katagami spec
# Systematic Illustration Atlas ## Philosophy A disciplined illustration language for product, brand, and editorial systems where every image explains, orients, and reinforces identity through repeatable geometry rather than decorative one-offs. ### Values - Purposeful imagery tied to user comprehension - Repeatable brand geometry that scales across product and editorial contexts - Accessible contrast with restrained accent moments - Documented illustration rules that teams can reproduce ### Anti-Values - Mascot clutter or purely ornamental scenes - Unbounded palettes, arbitrary textures, and inconsistent stroke logic - Illustrations that replace clear interface communication ### Visual Character - Layered rounded-rectangle panels use 2px ink borders, 10px corner radii, and offset accent tabs to make each illustration feel like a documented system component. - Simple vector people and objects are built from circles, capsules, and clipped arcs with a consistent 2px stroke so product scenes remain reproducible. - Backgrounds use a quiet dot-grid and pale blueprint blocks while coral and cyan accents appear only on callouts, arrows, and active states. - Editorial compositions combine diagram labels, numbered chips, and connector rules so imagery communicates process rather than acting as decoration. ## Tokens ### Colors | Name | Value | |------|-------| | primary | `#1E3A5F` | | secondary | `#4F6F8F` | | accent | `#F26D5B` | | background | `#F7F3EA` | | surface | `#FFFFFF` | | text | `#17202A` | | muted | `#6C7A86` | | border | `#24364B` | | error | `#B42318` | | success | `#2F7D57` | | warning | `#B7791F` | | info | `#2D6CDF` | ### Typography - **Heading Font**: Fraunces - **Body Font**: Source Sans 3 - **Mono Font**: IBM Plex Mono - **Base Size**: 16px - **Scale Ratio**: 1.25 - **Line Height**: 1.55 - **Letter Spacing**: -0.015em - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,600;9..144,700&family=IBM+Plex+Mono:wght@500;600&family=Source+Sans+3:wght@400;500;600;700&display=swap ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Radii - **None**: 0 - **Sm**: 6px - **Md**: 10px - **Lg**: 18px - **Full**: 9999px ### Shadows - **Sm**: 4px 4px 0 #24364B - **Md**: 8px 8px 0 rgba(36,54,75,0.22) - **Lg**: 14px 14px 0 rgba(36,54,75,0.16) ### Surfaces - **Treatment**: warm paper background with blueprint dot grid and white inked panels - **Card Style**: white cards with 2px navy outline, rounded corners, and controlled offset shadow - **Bg Pattern**: radial dot grid plus oversized translucent rounded blocks ### Borders - **Default Width**: 2px - **Accent Width**: 4px - **Style**: solid - **Character**: inked product-documentation linework with occasional thick accent rails ### Motion - **Duration**: 180ms - **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1) - **Philosophy**: small instructional state changes only; callouts lift and connectors draw attention without decorative bounce ## Rules ### Composition Build scenes as annotated product diagrams: a dominant interface or editorial panel, a supporting illustration vignette, and labeled connector chips aligned to an 8px grid. ### Hierarchy Use Fraunces for concise editorial headlines, Source Sans 3 for explanatory UI copy, and IBM Plex Mono for labels, IDs, tokens, and measurement notes. ### Density Moderate information density with generous margins; each illustration cluster should include one focal action and no more than three accent callouts. ### Signature Patterns - Blueprint dot-grid fields sit behind every hero composition and are masked by rounded panels to give illustrations a systematic documentation context. - Offset paper-card shadows use flat navy duplicates rather than blur, making product, brand, and editorial graphics feel printable and repeatable. - Numbered mono chips attach to coral connector lines, turning decorative illustration details into purposeful interface communication cues. - Shape-library specimens show circles, capsules, arcs, and blocks in the artwork itself so the repeatable illustration grammar is visible. ## Layout ### Grid 12-column desktop grid with 8px baseline; tablet collapses to 6 columns and mobile to a single annotated stack. ### Breakpoints mobile 375px, tablet 768px, desktop 1200px and above ### Whitespace Use 24px minimum internal panel padding and 48-64px section rhythm so diagram labels breathe and remain readable. ## Guidance ### Do - Use illustrations to clarify product flows, brand promises, or editorial arguments. - Limit accents to coral, cyan-blue, and small success green moments against the restrained base palette. - Document shape, stroke, and label rules beside example scenes so teams can reproduce them. ### Don't - Do not introduce new character styles, painterly gradients, or random decorative stickers. - Do not place text over busy imagery or rely on color alone for meaning. - Do not use large illustrations when a concise label, icon, or interface state would communicate better.
DESIGN.md
---
version: "alpha"
name: "Systematic Illustration Atlas"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
primary: "#1E3A5F"
secondary: "#4F6F8F"
accent: "#F26D5B"
background: "#F7F3EA"
surface: "#FFFFFF"
text: "#17202A"
muted: "#6C7A86"
border: "#24364B"
error: "#B42318"
success: "#2F7D57"
warning: "#B7791F"
info: "#2D6CDF"
typography:
headline-lg:
fontFamily: "Fraunces"
fontSize: "1.953rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.015em"
headline-md:
fontFamily: "Fraunces"
fontSize: "1.563rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.015em"
body-md:
fontFamily: "Source Sans 3"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.55
letterSpacing: "-0.015em"
label-md:
fontFamily: "IBM Plex Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
none: "0px"
sm: "6px"
md: "10px"
lg: "18px"
full: "9999px"
spacing:
base: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
components:
color-reference-primary:
backgroundColor: "{colors.primary}"
color-reference-secondary:
backgroundColor: "{colors.secondary}"
color-reference-accent:
backgroundColor: "{colors.accent}"
color-reference-background:
backgroundColor: "{colors.background}"
color-reference-surface:
backgroundColor: "{colors.surface}"
color-reference-text:
backgroundColor: "{colors.text}"
color-reference-muted:
backgroundColor: "{colors.muted}"
color-reference-border:
backgroundColor: "{colors.border}"
color-reference-error:
backgroundColor: "{colors.error}"
color-reference-success:
backgroundColor: "{colors.success}"
color-reference-warning:
backgroundColor: "{colors.warning}"
color-reference-info:
backgroundColor: "{colors.info}"
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"
---
# Systematic Illustration Atlas
## Overview
A disciplined illustration language for product, brand, and editorial systems where every image explains, orients, and reinforces identity through repeatable geometry rather than decorative one-offs.
### Values
- Purposeful imagery tied to user comprehension
- Repeatable brand geometry that scales across product and editorial contexts
- Accessible contrast with restrained accent moments
- Documented illustration rules that teams can reproduce
### Anti-Values
- Mascot clutter or purely ornamental scenes
- Unbounded palettes, arbitrary textures, and inconsistent stroke logic
- Illustrations that replace clear interface communication
### Visual Character
- Layered rounded-rectangle panels use 2px ink borders, 10px corner radii, and offset accent tabs to make each illustration feel like a documented system component.
- Simple vector people and objects are built from circles, capsules, and clipped arcs with a consistent 2px stroke so product scenes remain reproducible.
- Backgrounds use a quiet dot-grid and pale blueprint blocks while coral and cyan accents appear only on callouts, arrows, and active states.
- Editorial compositions combine diagram labels, numbered chips, and connector rules so imagery communicates process rather than acting as decoration.
## Colors
Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.
| Token | Value |
|-------|-------|
| primary | `#1E3A5F` |
| secondary | `#4F6F8F` |
| accent | `#F26D5B` |
| background | `#F7F3EA` |
| surface | `#FFFFFF` |
| text | `#17202A` |
| muted | `#6C7A86` |
| border | `#24364B` |
| error | `#B42318` |
| success | `#2F7D57` |
| warning | `#B7791F` |
| info | `#2D6CDF` |
## Typography
- **Headline-Lg**: Fraunces, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Fraunces, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Source Sans 3, 16px, weight 400, line-height 1.55.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
### Grid
12-column desktop grid with 8px baseline; tablet collapses to 6 columns and mobile to a single annotated stack.
### Breakpoints
mobile 375px, tablet 768px, desktop 1200px and above
### Whitespace
Use 24px minimum internal panel padding and 48-64px section rhythm so diagram labels breathe and remain readable.
## Elevation & Depth
### Shadows
- **Sm**: 4px 4px 0 #24364B
- **Md**: 8px 8px 0 rgba(36,54,75,0.22)
- **Lg**: 14px 14px 0 rgba(36,54,75,0.16)
## Shapes
### Rounded
- **None**: `0px`
- **Sm**: `6px`
- **Md**: `10px`
- **Lg**: `18px`
- **Full**: `9999px`
### Surfaces
- **Treatment**: warm paper background with blueprint dot grid and white inked panels
- **Card Style**: white cards with 2px navy outline, rounded corners, and controlled offset shadow
- **Bg Pattern**: radial dot grid plus oversized translucent rounded blocks
### Borders
- **Default Width**: 2px
- **Accent Width**: 4px
- **Style**: solid
- **Character**: inked product-documentation linework with occasional thick accent rails
## Components
### Composition
Build scenes as annotated product diagrams: a dominant interface or editorial panel, a supporting illustration vignette, and labeled connector chips aligned to an 8px grid.
### Hierarchy
Use Fraunces for concise editorial headlines, Source Sans 3 for explanatory UI copy, and IBM Plex Mono for labels, IDs, tokens, and measurement notes.
### Density
Moderate information density with generous margins; each illustration cluster should include one focal action and no more than three accent callouts.
### Signature Patterns
- Blueprint dot-grid fields sit behind every hero composition and are masked by rounded panels to give illustrations a systematic documentation context.
- Offset paper-card shadows use flat navy duplicates rather than blur, making product, brand, and editorial graphics feel printable and repeatable.
- Numbered mono chips attach to coral connector lines, turning decorative illustration details into purposeful interface communication cues.
- Shape-library specimens show circles, capsules, arcs, and blocks in the artwork itself so the repeatable illustration grammar is visible.
## shadcn/ui Usage
When the target app uses shadcn/ui, copy DESIGN.md with shadcn instead of the plain DESIGN.md. It contains the same Katagami design-language source plus the shadcn/ui primitives, imports, theme variables, component recipes, and preview-shot guidance.
DESIGN.md with shadcn: `/language/en-019dddb0-3719-7613-aeb9-77ffc2ae6955/DESIGN.with-shadcn.md`.
The shadcn page also exposes optional machine-readable files for automation, but the human-facing handoff is DESIGN.md with shadcn.
Install recommended primitives with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.
Use these primitives in shadcn apps:
- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table
Implementation rule for agents: import shadcn primitives from `@/components/ui/*`, apply the generated CSS variables first, then compose the language-specific recipes from the companion MD. Katagami remains the source of truth; shadcn names are the implementation surface.
## Do's and Don'ts
- Do Use illustrations to clarify product flows, brand promises, or editorial arguments.
- Do Limit accents to coral, cyan-blue, and small success green moments against the restrained base palette.
- Do Document shape, stroke, and label rules beside example scenes so teams can reproduce them.
- Don't Do not introduce new character styles, painterly gradients, or random decorative stickers.
- Don't Do not place text over busy imagery or rely on color alone for meaning.
- Don't Do not use large illustrations when a concise label, icon, or interface state would communicate better.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "systematic-illustration-atlas",
"type": "registry:theme",
"title": "Systematic Illustration Atlas shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F7F3EA",
"foreground": "#17202A",
"card": "#FFFFFF",
"card-foreground": "#17202A",
"popover": "#FFFFFF",
"popover-foreground": "#17202A",
"primary": "#1E3A5F",
"primary-foreground": "#ffffff",
"secondary": "#4F6F8F",
"secondary-foreground": "#ffffff",
"muted": "#6C7A86",
"muted-foreground": "#17202A",
"accent": "#F26D5B",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#24364B",
"input": "#24364B",
"ring": "#F26D5B",
"chart-1": "#1E3A5F",
"chart-2": "#4F6F8F",
"chart-3": "#F26D5B",
"chart-4": "#2F7D57",
"chart-5": "#B7791F",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#17202A",
"sidebar-primary": "#1E3A5F",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#2D6CDF",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#24364B",
"sidebar-ring": "#F26D5B",
"radius": "10px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#1E3A5F",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#F26D5B",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#303642",
"input": "#303642",
"ring": "#F26D5B",
"chart-1": "#1E3A5F",
"chart-2": "#4F6F8F",
"chart-3": "#F26D5B",
"chart-4": "#2F7D57",
"chart-5": "#B7791F",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#1E3A5F",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#F26D5B",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#F26D5B",
"radius": "10px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019dddb0-3719-7613-aeb9-77ffc2ae6955",
"slug": "systematic-illustration-atlas",
"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": {
"colors": [
"accent",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
],
"spacing": [
"base",
"scale"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"motion": [
"duration",
"easing",
"philosophy"
]
}
}
}
```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: #F7F3EA;
--foreground: #17202A;
--card: #FFFFFF;
--card-foreground: #17202A;
--popover: #FFFFFF;
--popover-foreground: #17202A;
--primary: #1E3A5F;
--primary-foreground: #ffffff;
--secondary: #4F6F8F;
--secondary-foreground: #ffffff;
--muted: #6C7A86;
--muted-foreground: #17202A;
--accent: #F26D5B;
--accent-foreground: #ffffff;
--destructive: #B42318;
--border: #24364B;
--input: #24364B;
--ring: #F26D5B;
--chart-1: #1E3A5F;
--chart-2: #4F6F8F;
--chart-3: #F26D5B;
--chart-4: #2F7D57;
--chart-5: #B7791F;
--sidebar: #FFFFFF;
--sidebar-foreground: #17202A;
--sidebar-primary: #1E3A5F;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #2D6CDF;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #24364B;
--sidebar-ring: #F26D5B;
--radius: 10px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #1E3A5F;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #F26D5B;
--accent-foreground: #ffffff;
--destructive: #B42318;
--border: #303642;
--input: #303642;
--ring: #F26D5B;
--chart-1: #1E3A5F;
--chart-2: #4F6F8F;
--chart-3: #F26D5B;
--chart-4: #2F7D57;
--chart-5: #B7791F;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #1E3A5F;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #F26D5B;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #F26D5B;
--radius: 10px;
}
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 SystematicIllustrationAtlasShadcnKit() {
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">Systematic Illustration Atlas</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": "systematic-illustration-atlas",
"type": "registry:theme",
"title": "Systematic Illustration Atlas shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F7F3EA",
"foreground": "#17202A",
"card": "#FFFFFF",
"card-foreground": "#17202A",
"popover": "#FFFFFF",
"popover-foreground": "#17202A",
"primary": "#1E3A5F",
"primary-foreground": "#ffffff",
"secondary": "#4F6F8F",
"secondary-foreground": "#ffffff",
"muted": "#6C7A86",
"muted-foreground": "#17202A",
"accent": "#F26D5B",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#24364B",
"input": "#24364B",
"ring": "#F26D5B",
"chart-1": "#1E3A5F",
"chart-2": "#4F6F8F",
"chart-3": "#F26D5B",
"chart-4": "#2F7D57",
"chart-5": "#B7791F",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#17202A",
"sidebar-primary": "#1E3A5F",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#2D6CDF",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#24364B",
"sidebar-ring": "#F26D5B",
"radius": "10px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#1E3A5F",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#F26D5B",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#303642",
"input": "#303642",
"ring": "#F26D5B",
"chart-1": "#1E3A5F",
"chart-2": "#4F6F8F",
"chart-3": "#F26D5B",
"chart-4": "#2F7D57",
"chart-5": "#B7791F",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#1E3A5F",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#F26D5B",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#F26D5B",
"radius": "10px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019dddb0-3719-7613-aeb9-77ffc2ae6955",
"slug": "systematic-illustration-atlas",
"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": {
"colors": [
"accent",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
],
"spacing": [
"base",
"scale"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"motion": [
"duration",
"easing",
"philosophy"
]
}
}
}
# Systematic Illustration Atlas shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019dddb0-3719-7613-aeb9-77ffc2ae6955`
Slug: `systematic-illustration-atlas`
## Intent
A disciplined illustration language for product, brand, and editorial systems where every image explains, orients, and reinforces identity through repeatable geometry rather than decorative one-offs.
## 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:
{
"primary": "#1E3A5F",
"secondary": "#4F6F8F",
"accent": "#F26D5B",
"background": "#F7F3EA",
"surface": "#FFFFFF",
"text": "#17202A",
"muted": "#6C7A86",
"border": "#24364B",
"error": "#B42318",
"success": "#2F7D57",
"warning": "#B7791F",
"info": "#2D6CDF"
}
Typography:
{
"heading_font": "Fraunces",
"body_font": "Source Sans 3",
"mono_font": "IBM Plex Mono",
"base_size": "16px",
"scale_ratio": 1.25,
"line_height": 1.55,
"letter_spacing": "-0.015em",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,600;9..144,700&family=IBM+Plex+Mono:wght@500;600&family=Source+Sans+3:wght@400;500;600;700&display=swap"
}
## Visual character to preserve
- Layered rounded-rectangle panels use 2px ink borders, 10px corner radii, and offset accent tabs to make each illustration feel like a documented system component.
- Simple vector people and objects are built from circles, capsules, and clipped arcs with a consistent 2px stroke so product scenes remain reproducible.
- Backgrounds use a quiet dot-grid and pale blueprint blocks while coral and cyan accents appear only on callouts, arrows, and active states.
- Editorial compositions combine diagram labels, numbered chips, and connector rules so imagery communicates process rather than acting as decoration.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": false,
"motion": "lift",
"density": "balanced",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
}
## Signature component recipes
### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.
### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.
### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.
### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.
### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.
## Preview shots
- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.
## Implementation contract
- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/systematic-illustration-atlas/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use illustrations to clarify product flows, brand promises, or editorial arguments.; Limit accents to coral, cyan-blue, and small success green moments against the restrained base palette.; Document shape, stroke, and label rules beside example scenes so teams can reproduce them.
- Do not: Do not introduce new character styles, painterly gradients, or random decorative stickers.; Do not place text over busy imagery or rely on color alone for meaning.; Do not use large illustrations when a concise label, icon, or interface state would communicate better.
## 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 SystematicIllustrationAtlasShadcnKit() {
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">Systematic Illustration Atlas</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
{
"grid": "12-column desktop grid with 8px baseline; tablet collapses to 6 columns and mobile to a single annotated stack.",
"breakpoints": "mobile 375px, tablet 768px, desktop 1200px and above",
"whitespace": "Use 24px minimum internal panel padding and 48-64px section rhythm so diagram labels breathe and remain readable."
}
{
"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-019dddb0-3719-7613-aeb9-77ffc2ae6955",
"name": "Systematic Illustration Atlas",
"slug": "systematic-illustration-atlas"
},
"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": [
"Layered rounded-rectangle panels use 2px ink borders, 10px corner radii, and offset accent tabs to make each illustration feel like a documented system component.",
"Simple vector people and objects are built from circles, capsules, and clipped arcs with a consistent 2px stroke so product scenes remain reproducible.",
"Backgrounds use a quiet dot-grid and pale blueprint blocks while coral and cyan accents appear only on callouts, arrows, and active states.",
"Editorial compositions combine diagram labels, numbered chips, and connector rules so imagery communicates process rather than acting as decoration."
],
"visualProfile": {
"family": "paper-collage",
"material": "paper",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": false,
"motion": "still",
"density": "balanced",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "Systematic Illustration Atlas launch room",
"description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
"primaryAction": "Apply theme",
"secondaryAction": "Review states",
"stats": [
{
"label": "components",
"value": "16",
"tone": "accent"
},
{
"label": "states",
"value": "ready"
},
{
"label": "density",
"value": "balanced",
"tone": "warning"
}
],
"rows": [
{
"label": "Primary flow",
"value": "mapped",
"status": "active"
},
{
"label": "Token coverage",
"value": "semantic",
"status": "synced"
},
{
"label": "Responsive proof",
"value": "queued",
"status": "review"
}
],
"statuses": [
"Active",
"Synced",
"Draft"
]
}
},
{
"id": "detail-editor",
"title": "Detail editor",
"viewport": "tablet",
"primitives": [
"button",
"card",
"input",
"textarea",
"select",
"checkbox",
"switch",
"slider",
"dialog",
"sheet"
],
"composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
"mustShow": [
"focus ring",
"error or destructive state",
"dialog or sheet treatment",
"written guidance content"
],
"avoid": [
"unstyled browser controls",
"floating cards inside cards",
"missing labels"
],
"scene": {
"eyebrow": "editing flow",
"headline": "Language recipe editor",
"description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
"primaryAction": "Save recipe",
"secondaryAction": "Open sheet",
"fields": [
{
"label": "Component family",
"value": "Narrative cards"
},
{
"label": "State treatment",
"value": "Visible focus + validation"
},
{
"label": "Motion",
"value": "Small lift, no opacity-only fade"
}
],
"statuses": [
"Focus",
"Invalid",
"Confirmed"
]
}
},
{
"id": "data-operations",
"title": "Data operations",
"viewport": "mobile",
"primitives": [
"button",
"tabs",
"badge",
"dropdown-menu",
"table",
"tooltip",
"separator"
],
"composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
"mustShow": [
"responsive reflow",
"dense row styling",
"menu affordance",
"status badge system"
],
"avoid": [
"desktop-only tables",
"text overflow",
"default shadcn spacing without Katagami character"
],
"scene": {
"eyebrow": "operations",
"headline": "Compact review queue",
"description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
"primaryAction": "Resolve",
"secondaryAction": "Filter",
"rows": [
{
"label": "Button hierarchy",
"value": "approved",
"status": "ok"
},
{
"label": "Table rhythm",
"value": "needs pass",
"status": "watch"
},
{
"label": "Empty state",
"value": "designed",
"status": "done"
}
],
"statuses": [
"Queued",
"Blocked",
"Done"
]
}
}
],
"componentRecipes": [
{
"primitive": "button",
"intent": "Prove action hierarchy, focus, disabled, and destructive states."
},
{
"primitive": "card",
"intent": "Carry the language surface, border, elevation, and density rules."
},
{
"primitive": "input",
"intent": "Show labels, focus rings, validation, and spacing rhythm."
},
{
"primitive": "textarea",
"intent": "Show longer guidance, validation copy, and writing density."
},
{
"primitive": "select",
"intent": "Show filtering, selection contrast, and menu trigger styling."
},
{
"primitive": "dialog",
"intent": "Show centered decision states and overlay treatment."
},
{
"primitive": "sheet",
"intent": "Show contextual side panels and responsive editing."
},
{
"primitive": "tabs",
"intent": "Show navigational structure and active/inactive contrast."
},
{
"primitive": "badge",
"intent": "Show compact status vocabulary and semantic colors."
},
{
"primitive": "separator",
"intent": "Show section rhythm without generic gray dividers."
},
{
"primitive": "checkbox",
"intent": "Show binary selection with visible focus and checked states."
},
{
"primitive": "switch",
"intent": "Show settings toggles and on/off contrast."
},
{
"primitive": "slider",
"intent": "Show numeric adjustment with track/thumb styling."
},
{
"primitive": "tooltip",
"intent": "Show concise explanation styling above compact controls."
},
{
"primitive": "dropdown-menu",
"intent": "Show action menus, destructive items, and grouped choices."
},
{
"primitive": "table",
"intent": "Show dense operational data, separators, row states, and responsive behavior."
}
],
"qualityRules": {
"do": [
"Use illustrations to clarify product flows, brand promises, or editorial arguments.",
"Limit accents to coral, cyan-blue, and small success green moments against the restrained base palette.",
"Document shape, stroke, and label rules beside example scenes so teams can reproduce them."
],
"dont": [
"Do not introduce new character styles, painterly gradients, or random decorative stickers.",
"Do not place text over busy imagery or rely on color alone for meaning.",
"Do not use large illustrations when a concise label, icon, or interface state would communicate better."
]
}
}