back to gallery
design language·abstraction-ladder-atlas

Abstraction Ladder 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.

the spec

specification

philosophy
summary
Abstraction Ladder Atlas is a visual language for product illustration systems that can move deliberately from tiny icons to pictograms, spot illustrations, and full hero imagery without changing voice. It treats every graphic as a calibrated specimen on a shared drafting table: neutral foundation, visible registration, disciplined geometry, and semantic accents that become more expressive only when scale allows.
values
Systematic translation across icon, pictogram, spot, and hero scalesDrafting-table clarity where construction logic remains legibleSemantic restraint: accents clarify meaning instead of decoratingNeutral surfaces that let line, silhouette, and proportion carry identityExpressive range through density, layering, and scale rather than random style shiftsAccessible contrast and recognizable forms even at small sizes
anti-values
×One-off illustration moments that cannot collapse back to icons×Gratuitous gradients, mascot cuteness, or decorative flourish without semantic purpose×Generic dashboard minimalism where graphics feel pasted on after layout×Palette-first identity that disappears when colors are changed
tokens
colors12 items
primary
#1B1D22
secondary
#5F636A
accent
#F26B3A
background
#F5F0E8
surface
#FFFBF3
text
#17191D
muted
#767069
border
#C8BDAE
error
#B3261E
success
#1F7A4D
warning
#B46A00
info
#2764B8
typography8 items
heading font
Fraunces
body font
Atkinson Hyperlegible
mono font
IBM Plex Mono
base size
16px
scale ratio
1.28
line height
1.52
letter spacing
-0.02em
google fonts url
https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Fraunces:opsz,wght,SOFT,WONK@9..144,600..800,0,1&family=IBM+Plex+Mono:wght@400;600&display=swap
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64, 96
radii5 items
none
0
sm
6px
md
12px
lg
18px
full
9999px
shadows3 items
sm
0 1px 0 rgba(23,25,29,0.16)
md
0 10px 24px rgba(23,25,29,0.10)
lg
0 28px 64px rgba(23,25,29,0.14)
surfaces3 items
treatment
Warm paper field with subtle grid and transparent registration overlays; panels remain mostly flat so vector forms own the depth.
card style
Off-white cards with 1px measured borders, 6px corner radius, corner ticks, and occasional offset duplicate slabs.
bg pattern
Repeating 32px drafting grid using low-contrast border-colored linear gradients.
borders4 items
default width
1px
accent width
3px
style
solid with short corner tick pseudo-elements
character
Technical, measured, and printed; borders behave like crop marks rather than container chrome.
motion3 items
duration
180ms
easing
cubic-bezier(.2,.8,.2,1)
philosophy
Snappy calibration motion: hover states slide accent layers by 2px and reveal measurement marks, never bounce.
rules
composition
Compose screens as a working atlas: a narrow control rail, a central ladder canvas, and a right-side inspection stack. Align every card edge to an 8px grid. Large illustrations must be decomposable into smaller framed specimens. Keep primary action near the ladder title and secondary controls in compact tool strips.
hierarchy
Use Fraunces for large conceptual labels and section titles, Atkinson Hyperlegible for readable interface copy, and IBM Plex Mono for scale labels, coordinates, tags, and table values. Hierarchy comes from scale contrast, framed placement, and mono annotations rather than heavy color fills.
density
Medium-high density is acceptable because this language is for design-system work, but each cluster needs a measured gutter, a mono label, and a visible boundary so inspection never becomes visual noise.
signature patterns
Abstraction ladder cards: four adjacent framed panels named icon, pictogram, spot, and hero, with progressively larger vector assemblies inside.Registration-frame borders: cards use crop-mark pseudo-elements and baseline ticks so containers feel like print production artifacts.Offset semantic layers: illustration objects include a dark base silhouette plus a 2px shifted accent duplicate or dot to indicate meaning at larger scales.Measurement metadata strips: mono labels, coordinate pills, and contrast badges sit on top edges like annotations in a visual QA tool.Neutral-to-accent ramp: most UI remains paper and ink while orange, blue, green, and amber appear only on semantic chips, selected states, and key graphic nodes.
layout
density

Inspection-dense but gridded; graphics and controls share one atlas surface so designers can compare scale translations without changing context.

grid

Desktop uses a 12-column max 1360px grid with 24px gutters; the app shell allocates 240px tools, flexible ladder canvas, and 320px inspector.

breakpoints
1440 desktop three-column atlas, 768 tablet stacked rail over canvas with inspector cards in two columns, 375 mobile single column with horizontally scrollable ladder cells.
whitespace
Whitespace is measured as calibration space: 24px between major modules, 16px inside panels, and deliberate empty margins around vector specimens to reveal silhouette.
guidance
do
  • Design icons, pictograms, spot art, and hero art as members of the same family before polishing any single asset.
  • Use registration ticks, grid overlays, and mono labels to make scale and construction visible.
  • Reserve accent colors for semantic states, selected rungs, and meaningful illustration nodes.
  • Keep vector shapes flat and legible; add depth through offsets, overlap, and density rather than photoreal shadow.
  • Test the smallest icon form first, then add information only as the ladder scale increases.
  • Use accessible contrast for all labels and never place body text on saturated accent fields.
avoid
  • Do not introduce a new illustrative style for hero images that cannot simplify back into pictograms.
  • Do not use rainbow palettes, decorative gradients, or mascot expressions as shortcuts for personality.
  • Do not hide construction with glassmorphism, blurred depth, or excessive soft shadows.
  • Do not mix arbitrary radii; use squared technical panels and only small radii for controls.
  • Do not let metadata overwhelm the specimen; annotations should clarify, not become decoration.
  • Do not use blocked AI-tell typefaces or generic SaaS dashboard component arrangements.
katagami spec
# Abstraction Ladder Atlas

## Philosophy

Abstraction Ladder Atlas is a visual language for product illustration systems that can move deliberately from tiny icons to pictograms, spot illustrations, and full hero imagery without changing voice. It treats every graphic as a calibrated specimen on a shared drafting table: neutral foundation, visible registration, disciplined geometry, and semantic accents that become more expressive only when scale allows.

### Values

- Systematic translation across icon, pictogram, spot, and hero scales
- Drafting-table clarity where construction logic remains legible
- Semantic restraint: accents clarify meaning instead of decorating
- Neutral surfaces that let line, silhouette, and proportion carry identity
- Expressive range through density, layering, and scale rather than random style shifts
- Accessible contrast and recognizable forms even at small sizes

### Anti-Values

- One-off illustration moments that cannot collapse back to icons
- Gratuitous gradients, mascot cuteness, or decorative flourish without semantic purpose
- Generic dashboard minimalism where graphics feel pasted on after layout
- Palette-first identity that disappears when colors are changed

### Visual Character

- Use a four-rung horizontal abstraction ladder with repeating framed cells, each cell increasing detail density from 24px icon to full-width hero panel.
- Apply thin drafting registration lines, corner ticks, and measured baseline rules around cards and imagery instead of conventional soft shadows.
- Build illustrations from flat vector silhouettes, offset duplicate layers, and small semantic accent marks that are positioned on a visible alignment grid.
- Keep the interface on a warm neutral canvas with square-to-small-radius panels, using color only for labeled semantic states and graphic focal points.
- Pair compact grotesque body text with a high-contrast display serif for editorial hierarchy, then use mono labels as measurement annotations.

## Tokens

### Colors

| Name | Value |
|------|-------|
| primary | `#1B1D22` |
| secondary | `#5F636A` |
| accent | `#F26B3A` |
| background | `#F5F0E8` |
| surface | `#FFFBF3` |
| text | `#17191D` |
| muted | `#767069` |
| border | `#C8BDAE` |
| error | `#B3261E` |
| success | `#1F7A4D` |
| warning | `#B46A00` |
| info | `#2764B8` |

### Typography

- **Heading Font**: Fraunces
- **Body Font**: Atkinson Hyperlegible
- **Mono Font**: IBM Plex Mono
- **Base Size**: 16px
- **Scale Ratio**: 1.28
- **Line Height**: 1.52
- **Letter Spacing**: -0.02em
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Fraunces:opsz,wght,SOFT,WONK@9..144,600..800,0,1&family=IBM+Plex+Mono:wght@400;600&display=swap

### Spacing

- **Base**: 8px
- **Scale**: [4,8,12,16,24,32,48,64,96]

### Radii

- **None**: 0
- **Sm**: 6px
- **Md**: 12px
- **Lg**: 18px
- **Full**: 9999px

### Shadows

- **Sm**: 0 1px 0 rgba(23,25,29,0.16)
- **Md**: 0 10px 24px rgba(23,25,29,0.10)
- **Lg**: 0 28px 64px rgba(23,25,29,0.14)

### Surfaces

- **Treatment**: Warm paper field with subtle grid and transparent registration overlays; panels remain mostly flat so vector forms own the depth.
- **Card Style**: Off-white cards with 1px measured borders, 6px corner radius, corner ticks, and occasional offset duplicate slabs.
- **Bg Pattern**: Repeating 32px drafting grid using low-contrast border-colored linear gradients.

### Borders

- **Default Width**: 1px
- **Accent Width**: 3px
- **Style**: solid with short corner tick pseudo-elements
- **Character**: Technical, measured, and printed; borders behave like crop marks rather than container chrome.

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(.2,.8,.2,1)
- **Philosophy**: Snappy calibration motion: hover states slide accent layers by 2px and reveal measurement marks, never bounce.

## Rules

### Composition

Compose screens as a working atlas: a narrow control rail, a central ladder canvas, and a right-side inspection stack. Align every card edge to an 8px grid. Large illustrations must be decomposable into smaller framed specimens. Keep primary action near the ladder title and secondary controls in compact tool strips.

### Hierarchy

Use Fraunces for large conceptual labels and section titles, Atkinson Hyperlegible for readable interface copy, and IBM Plex Mono for scale labels, coordinates, tags, and table values. Hierarchy comes from scale contrast, framed placement, and mono annotations rather than heavy color fills.

### Density

Medium-high density is acceptable because this language is for design-system work, but each cluster needs a measured gutter, a mono label, and a visible boundary so inspection never becomes visual noise.

### Signature Patterns

- Abstraction ladder cards: four adjacent framed panels named icon, pictogram, spot, and hero, with progressively larger vector assemblies inside.
- Registration-frame borders: cards use crop-mark pseudo-elements and baseline ticks so containers feel like print production artifacts.
- Offset semantic layers: illustration objects include a dark base silhouette plus a 2px shifted accent duplicate or dot to indicate meaning at larger scales.
- Measurement metadata strips: mono labels, coordinate pills, and contrast badges sit on top edges like annotations in a visual QA tool.
- Neutral-to-accent ramp: most UI remains paper and ink while orange, blue, green, and amber appear only on semantic chips, selected states, and key graphic nodes.

## Layout

### Density

Inspection-dense but gridded; graphics and controls share one atlas surface so designers can compare scale translations without changing context.

### Grid

Desktop uses a 12-column max 1360px grid with 24px gutters; the app shell allocates 240px tools, flexible ladder canvas, and 320px inspector.

### Breakpoints

1440 desktop three-column atlas, 768 tablet stacked rail over canvas with inspector cards in two columns, 375 mobile single column with horizontally scrollable ladder cells.

### Whitespace

Whitespace is measured as calibration space: 24px between major modules, 16px inside panels, and deliberate empty margins around vector specimens to reveal silhouette.

## Guidance

### Do

- Design icons, pictograms, spot art, and hero art as members of the same family before polishing any single asset.
- Use registration ticks, grid overlays, and mono labels to make scale and construction visible.
- Reserve accent colors for semantic states, selected rungs, and meaningful illustration nodes.
- Keep vector shapes flat and legible; add depth through offsets, overlap, and density rather than photoreal shadow.
- Test the smallest icon form first, then add information only as the ladder scale increases.
- Use accessible contrast for all labels and never place body text on saturated accent fields.

### Don't

- Do not introduce a new illustrative style for hero images that cannot simplify back into pictograms.
- Do not use rainbow palettes, decorative gradients, or mascot expressions as shortcuts for personality.
- Do not hide construction with glassmorphism, blurred depth, or excessive soft shadows.
- Do not mix arbitrary radii; use squared technical panels and only small radii for controls.
- Do not let metadata overwhelm the specimen; annotations should clarify, not become decoration.
- Do not use blocked AI-tell typefaces or generic SaaS dashboard component arrangements.

### Usage Context

Best for product teams documenting graphic systems, illustration libraries, icon migration, onboarding visuals, and brand-to-product visual language governance.

### Accessibility

Maintain WCAG AA contrast, keep icon silhouettes recognizable without color, provide text labels for visual rungs, and ensure controls have focus states and generous hit targets.
DESIGN.md
---
version: "alpha"
name: "Abstraction Ladder Atlas"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  primary: "#1B1D22"
  secondary: "#5F636A"
  accent: "#F26B3A"
  background: "#F5F0E8"
  surface: "#FFFBF3"
  text: "#17191D"
  muted: "#767069"
  border: "#C8BDAE"
  error: "#B3261E"
  success: "#1F7A4D"
  warning: "#B46A00"
  info: "#2764B8"
typography:
  headline-lg:
    fontFamily: "Fraunces"
    fontSize: "2.097rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Fraunces"
    fontSize: "1.638rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "Atkinson Hyperlegible"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.52
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  none: "0px"
  sm: "6px"
  md: "12px"
  lg: "18px"
  full: "9999px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
  step-8: "96px"
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"
---

# Abstraction Ladder Atlas

## Overview

Abstraction Ladder Atlas is a visual language for product illustration systems that can move deliberately from tiny icons to pictograms, spot illustrations, and full hero imagery without changing voice. It treats every graphic as a calibrated specimen on a shared drafting table: neutral foundation, visible registration, disciplined geometry, and semantic accents that become more expressive only when scale allows.

### Values

- Systematic translation across icon, pictogram, spot, and hero scales
- Drafting-table clarity where construction logic remains legible
- Semantic restraint: accents clarify meaning instead of decorating
- Neutral surfaces that let line, silhouette, and proportion carry identity
- Expressive range through density, layering, and scale rather than random style shifts
- Accessible contrast and recognizable forms even at small sizes

### Anti-Values

- One-off illustration moments that cannot collapse back to icons
- Gratuitous gradients, mascot cuteness, or decorative flourish without semantic purpose
- Generic dashboard minimalism where graphics feel pasted on after layout
- Palette-first identity that disappears when colors are changed

### Visual Character

- Use a four-rung horizontal abstraction ladder with repeating framed cells, each cell increasing detail density from 24px icon to full-width hero panel.
- Apply thin drafting registration lines, corner ticks, and measured baseline rules around cards and imagery instead of conventional soft shadows.
- Build illustrations from flat vector silhouettes, offset duplicate layers, and small semantic accent marks that are positioned on a visible alignment grid.
- Keep the interface on a warm neutral canvas with square-to-small-radius panels, using color only for labeled semantic states and graphic focal points.
- Pair compact grotesque body text with a high-contrast display serif for editorial hierarchy, then use mono labels as measurement annotations.

## 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 | `#1B1D22` |
| secondary | `#5F636A` |
| accent | `#F26B3A` |
| background | `#F5F0E8` |
| surface | `#FFFBF3` |
| text | `#17191D` |
| muted | `#767069` |
| border | `#C8BDAE` |
| error | `#B3261E` |
| success | `#1F7A4D` |
| warning | `#B46A00` |
| info | `#2764B8` |

## Typography

- **Headline-Lg**: Fraunces, 2.097rem, weight 700, line-height 1.1.
- **Headline-Md**: Fraunces, 1.638rem, weight 600, line-height 1.15.
- **Body-Md**: Atkinson Hyperlegible, 16px, weight 400, line-height 1.52.
- **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`
- **Step-8**: `96px`

### Density

Inspection-dense but gridded; graphics and controls share one atlas surface so designers can compare scale translations without changing context.

### Grid

Desktop uses a 12-column max 1360px grid with 24px gutters; the app shell allocates 240px tools, flexible ladder canvas, and 320px inspector.

### Breakpoints

1440 desktop three-column atlas, 768 tablet stacked rail over canvas with inspector cards in two columns, 375 mobile single column with horizontally scrollable ladder cells.

### Whitespace

Whitespace is measured as calibration space: 24px between major modules, 16px inside panels, and deliberate empty margins around vector specimens to reveal silhouette.

## Elevation & Depth

### Shadows

- **Sm**: 0 1px 0 rgba(23,25,29,0.16)
- **Md**: 0 10px 24px rgba(23,25,29,0.10)
- **Lg**: 0 28px 64px rgba(23,25,29,0.14)

## Shapes

### Rounded

- **None**: `0px`
- **Sm**: `6px`
- **Md**: `12px`
- **Lg**: `18px`
- **Full**: `9999px`

### Surfaces

- **Treatment**: Warm paper field with subtle grid and transparent registration overlays; panels remain mostly flat so vector forms own the depth.
- **Card Style**: Off-white cards with 1px measured borders, 6px corner radius, corner ticks, and occasional offset duplicate slabs.
- **Bg Pattern**: Repeating 32px drafting grid using low-contrast border-colored linear gradients.

### Borders

- **Default Width**: 1px
- **Accent Width**: 3px
- **Style**: solid with short corner tick pseudo-elements
- **Character**: Technical, measured, and printed; borders behave like crop marks rather than container chrome.

## Components

### Composition

Compose screens as a working atlas: a narrow control rail, a central ladder canvas, and a right-side inspection stack. Align every card edge to an 8px grid. Large illustrations must be decomposable into smaller framed specimens. Keep primary action near the ladder title and secondary controls in compact tool strips.

### Hierarchy

Use Fraunces for large conceptual labels and section titles, Atkinson Hyperlegible for readable interface copy, and IBM Plex Mono for scale labels, coordinates, tags, and table values. Hierarchy comes from scale contrast, framed placement, and mono annotations rather than heavy color fills.

### Density

Medium-high density is acceptable because this language is for design-system work, but each cluster needs a measured gutter, a mono label, and a visible boundary so inspection never becomes visual noise.

### Signature Patterns

- Abstraction ladder cards: four adjacent framed panels named icon, pictogram, spot, and hero, with progressively larger vector assemblies inside.
- Registration-frame borders: cards use crop-mark pseudo-elements and baseline ticks so containers feel like print production artifacts.
- Offset semantic layers: illustration objects include a dark base silhouette plus a 2px shifted accent duplicate or dot to indicate meaning at larger scales.
- Measurement metadata strips: mono labels, coordinate pills, and contrast badges sit on top edges like annotations in a visual QA tool.
- Neutral-to-accent ramp: most UI remains paper and ink while orange, blue, green, and amber appear only on semantic chips, selected states, and key graphic nodes.

## 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-019dde35-27bf-7eb3-8468-a28fb29472f9/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 Design icons, pictograms, spot art, and hero art as members of the same family before polishing any single asset.
- Do Use registration ticks, grid overlays, and mono labels to make scale and construction visible.
- Do Reserve accent colors for semantic states, selected rungs, and meaningful illustration nodes.
- Do Keep vector shapes flat and legible; add depth through offsets, overlap, and density rather than photoreal shadow.
- Do Test the smallest icon form first, then add information only as the ladder scale increases.
- Do Use accessible contrast for all labels and never place body text on saturated accent fields.
- Don't Do not introduce a new illustrative style for hero images that cannot simplify back into pictograms.
- Don't Do not use rainbow palettes, decorative gradients, or mascot expressions as shortcuts for personality.
- Don't Do not hide construction with glassmorphism, blurred depth, or excessive soft shadows.
- Don't Do not mix arbitrary radii; use squared technical panels and only small radii for controls.
- Don't Do not let metadata overwhelm the specimen; annotations should clarify, not become decoration.
- Don't Do not use blocked AI-tell typefaces or generic SaaS dashboard component arrangements.

### Usage Context

Best for product teams documenting graphic systems, illustration libraries, icon migration, onboarding visuals, and brand-to-product visual language governance.

### Accessibility

Maintain WCAG AA contrast, keep icon silhouettes recognizable without color, provide text labels for visual rungs, and ensure controls have focus states and generous hit targets.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "abstraction-ladder-atlas",
  "type": "registry:theme",
  "title": "Abstraction Ladder Atlas shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F5F0E8",
      "foreground": "#17191D",
      "card": "#FFFBF3",
      "card-foreground": "#17191D",
      "popover": "#FFFBF3",
      "popover-foreground": "#17191D",
      "primary": "#1B1D22",
      "primary-foreground": "#ffffff",
      "secondary": "#5F636A",
      "secondary-foreground": "#ffffff",
      "muted": "#767069",
      "muted-foreground": "#17191D",
      "accent": "#F26B3A",
      "accent-foreground": "#ffffff",
      "destructive": "#B3261E",
      "border": "#C8BDAE",
      "input": "#C8BDAE",
      "ring": "#F26B3A",
      "chart-1": "#1B1D22",
      "chart-2": "#5F636A",
      "chart-3": "#F26B3A",
      "chart-4": "#1F7A4D",
      "chart-5": "#B46A00",
      "sidebar": "#FFFBF3",
      "sidebar-foreground": "#17191D",
      "sidebar-primary": "#1B1D22",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#2764B8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#C8BDAE",
      "sidebar-ring": "#F26B3A",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1B1D22",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#F26B3A",
      "accent-foreground": "#ffffff",
      "destructive": "#B3261E",
      "border": "#303642",
      "input": "#303642",
      "ring": "#F26B3A",
      "chart-1": "#1B1D22",
      "chart-2": "#5F636A",
      "chart-3": "#F26B3A",
      "chart-4": "#1F7A4D",
      "chart-5": "#B46A00",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1B1D22",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#F26B3A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#F26B3A",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019dde35-27bf-7eb3-8468-a28fb29472f9",
    "slug": "abstraction-ladder-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"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · abstraction-ladder-atlas
DESIGN.md

at a glance

Palette

Typography

headline-lgFraunces · 34px · 700

The quick brown fox jumps

headline-mdFraunces · 26px · 600

The quick brown fox jumps

body-mdAtkinson Hyperlegible · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

Components rendered with this language’s tokens — colors, type, and rounded corners as specified.

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl48px
  • 4xl64px
  • step-896px

Shape

none0px
sm6px
md12px
lg18px
full9999px
shadcn/ui

implementation kit

needs agent-authored kitcompatibility fallback
shadcn compatibility only
The generated theme variables are available, but the polished shadcn component recipes and shots have not been authored by the Katagami agent yet.
fallbackprimitives render
Compatibility proof
Local shadcn-style primitives accept the generated theme variables.
primaryaccentsurfacemutedwarningerror
table rhythm
buttonok
cardok
inputok
recommendedcompatibility fallback

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
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #F5F0E8;
  --foreground: #17191D;
  --card: #FFFBF3;
  --card-foreground: #17191D;
  --popover: #FFFBF3;
  --popover-foreground: #17191D;
  --primary: #1B1D22;
  --primary-foreground: #ffffff;
  --secondary: #5F636A;
  --secondary-foreground: #ffffff;
  --muted: #767069;
  --muted-foreground: #17191D;
  --accent: #F26B3A;
  --accent-foreground: #ffffff;
  --destructive: #B3261E;
  --border: #C8BDAE;
  --input: #C8BDAE;
  --ring: #F26B3A;
  --chart-1: #1B1D22;
  --chart-2: #5F636A;
  --chart-3: #F26B3A;
  --chart-4: #1F7A4D;
  --chart-5: #B46A00;
  --sidebar: #FFFBF3;
  --sidebar-foreground: #17191D;
  --sidebar-primary: #1B1D22;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #2764B8;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #C8BDAE;
  --sidebar-ring: #F26B3A;
  --radius: 12px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #1B1D22;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #F26B3A;
  --accent-foreground: #ffffff;
  --destructive: #B3261E;
  --border: #303642;
  --input: #303642;
  --ring: #F26B3A;
  --chart-1: #1B1D22;
  --chart-2: #5F636A;
  --chart-3: #F26B3A;
  --chart-4: #1F7A4D;
  --chart-5: #B46A00;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #1B1D22;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #F26B3A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #F26B3A;
  --radius: 12px;
}
tsx starter
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 AbstractionLadderAtlasShadcnKit() {
  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">Abstraction Ladder 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>
  );
}
theme JSONcompatibility fallback
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "abstraction-ladder-atlas",
  "type": "registry:theme",
  "title": "Abstraction Ladder Atlas shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F5F0E8",
      "foreground": "#17191D",
      "card": "#FFFBF3",
      "card-foreground": "#17191D",
      "popover": "#FFFBF3",
      "popover-foreground": "#17191D",
      "primary": "#1B1D22",
      "primary-foreground": "#ffffff",
      "secondary": "#5F636A",
      "secondary-foreground": "#ffffff",
      "muted": "#767069",
      "muted-foreground": "#17191D",
      "accent": "#F26B3A",
      "accent-foreground": "#ffffff",
      "destructive": "#B3261E",
      "border": "#C8BDAE",
      "input": "#C8BDAE",
      "ring": "#F26B3A",
      "chart-1": "#1B1D22",
      "chart-2": "#5F636A",
      "chart-3": "#F26B3A",
      "chart-4": "#1F7A4D",
      "chart-5": "#B46A00",
      "sidebar": "#FFFBF3",
      "sidebar-foreground": "#17191D",
      "sidebar-primary": "#1B1D22",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#2764B8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#C8BDAE",
      "sidebar-ring": "#F26B3A",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1B1D22",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#F26B3A",
      "accent-foreground": "#ffffff",
      "destructive": "#B3261E",
      "border": "#303642",
      "input": "#303642",
      "ring": "#F26B3A",
      "chart-1": "#1B1D22",
      "chart-2": "#5F636A",
      "chart-3": "#F26B3A",
      "chart-4": "#1F7A4D",
      "chart-5": "#B46A00",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1B1D22",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#F26B3A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#F26B3A",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019dde35-27bf-7eb3-8468-a28fb29472f9",
    "slug": "abstraction-ladder-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"
      ]
    }
  }
}
component recipescompatibility fallback
# Abstraction Ladder Atlas shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019dde35-27bf-7eb3-8468-a28fb29472f9`
Slug: `abstraction-ladder-atlas`

## Intent

Abstraction Ladder Atlas is a visual language for product illustration systems that can move deliberately from tiny icons to pictograms, spot illustrations, and full hero imagery without changing voice. It treats every graphic as a calibrated specimen on a shared drafting table: neutral foundation, visible registration, disciplined geometry, and semantic accents that become more expressive only when scale allows.

## 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": "#1B1D22",
  "secondary": "#5F636A",
  "accent": "#F26B3A",
  "background": "#F5F0E8",
  "surface": "#FFFBF3",
  "text": "#17191D",
  "muted": "#767069",
  "border": "#C8BDAE",
  "error": "#B3261E",
  "success": "#1F7A4D",
  "warning": "#B46A00",
  "info": "#2764B8"
}

Typography:

{
  "heading_font": "Fraunces",
  "body_font": "Atkinson Hyperlegible",
  "mono_font": "IBM Plex Mono",
  "base_size": "16px",
  "scale_ratio": 1.28,
  "line_height": 1.52,
  "letter_spacing": "-0.02em",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Fraunces:opsz,wght,SOFT,WONK@9..144,600..800,0,1&family=IBM+Plex+Mono:wght@400;600&display=swap"
}

## Visual character to preserve

- Use a four-rung horizontal abstraction ladder with repeating framed cells, each cell increasing detail density from 24px icon to full-width hero panel.
- Apply thin drafting registration lines, corner ticks, and measured baseline rules around cards and imagery instead of conventional soft shadows.
- Build illustrations from flat vector silhouettes, offset duplicate layers, and small semantic accent marks that are positioned on a visible alignment grid.
- Keep the interface on a warm neutral canvas with square-to-small-radius panels, using color only for labeled semantic states and graphic focal points.
- Pair compact grotesque body text with a high-contrast display serif for editorial hierarchy, then use mono labels as measurement annotations.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "pebble",
  "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/abstraction-ladder-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: Design icons, pictograms, spot art, and hero art as members of the same family before polishing any single asset.; Use registration ticks, grid overlays, and mono labels to make scale and construction visible.; Reserve accent colors for semantic states, selected rungs, and meaningful illustration nodes.; Keep vector shapes flat and legible; add depth through offsets, overlap, and density rather than photoreal shadow.; Test the smallest icon form first, then add information only as the ladder scale increases.; Use accessible contrast for all labels and never place body text on saturated accent fields.
- Do not: Do not introduce a new illustrative style for hero images that cannot simplify back into pictograms.; Do not use rainbow palettes, decorative gradients, or mascot expressions as shortcuts for personality.; Do not hide construction with glassmorphism, blurred depth, or excessive soft shadows.; Do not mix arbitrary radii; use squared technical panels and only small radii for controls.; Do not let metadata overwhelm the specimen; annotations should clarify, not become decoration.; Do not use blocked AI-tell typefaces or generic SaaS dashboard component arrangements.

## 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 AbstractionLadderAtlasShadcnKit() {
  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">Abstraction Ladder 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

{
  "density": "Inspection-dense but gridded; graphics and controls share one atlas surface so designers can compare scale translations without changing context.",
  "grid": "Desktop uses a 12-column max 1360px grid with 24px gutters; the app shell allocates 240px tools, flexible ladder canvas, and 320px inspector.",
  "breakpoints": "1440 desktop three-column atlas, 768 tablet stacked rail over canvas with inspector cards in two columns, 375 mobile single column with horizontally scrollable ladder cells.",
  "whitespace": "Whitespace is measured as calibration space: 24px between major modules, 16px inside panels, and deliberate empty margins around vector specimens to reveal silhouette."
}
preview shotscompatibility fallback
{
  "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-019dde35-27bf-7eb3-8468-a28fb29472f9",
    "name": "Abstraction Ladder Atlas",
    "slug": "abstraction-ladder-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": [
    "Use a four-rung horizontal abstraction ladder with repeating framed cells, each cell increasing detail density from 24px icon to full-width hero panel.",
    "Apply thin drafting registration lines, corner ticks, and measured baseline rules around cards and imagery instead of conventional soft shadows.",
    "Build illustrations from flat vector silhouettes, offset duplicate layers, and small semantic accent marks that are positioned on a visible alignment grid.",
    "Keep the interface on a warm neutral canvas with square-to-small-radius panels, using color only for labeled semantic states and graphic focal points.",
    "Pair compact grotesque body text with a high-contrast display serif for editorial hierarchy, then use mono labels as measurement annotations."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "pebble",
    "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": "Abstraction Ladder 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": [
      "Design icons, pictograms, spot art, and hero art as members of the same family before polishing any single asset.",
      "Use registration ticks, grid overlays, and mono labels to make scale and construction visible.",
      "Reserve accent colors for semantic states, selected rungs, and meaningful illustration nodes.",
      "Keep vector shapes flat and legible; add depth through offsets, overlap, and density rather than photoreal shadow.",
      "Test the smallest icon form first, then add information only as the ladder scale increases.",
      "Use accessible contrast for all labels and never place body text on saturated accent fields."
    ],
    "dont": [
      "Do not introduce a new illustrative style for hero images that cannot simplify back into pictograms.",
      "Do not use rainbow palettes, decorative gradients, or mascot expressions as shortcuts for personality.",
      "Do not hide construction with glassmorphism, blurred depth, or excessive soft shadows.",
      "Do not mix arbitrary radii; use squared technical panels and only small radii for controls.",
      "Do not let metadata overwhelm the specimen; annotations should clarify, not become decoration.",
      "Do not use blocked AI-tell typefaces or generic SaaS dashboard component arrangements."
    ]
  }
}