back to gallery
design language·aya-context-map-sumi

AYA Context Map Sumi

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
AYA Context Map Sumi is a quiet, text-first workspace language for document-adjacent analytics: navigation behaves like a context map, surfaces read as layered paper, and small semantic colors mark status without turning the product into a dashboard.
values
document primacy before chromenegative space as orientationcompact metrics that stay marginalsemantic color used only when it clarifies state
anti-values
×literal Japanese ornament, motifs, fans, waves, or red-circle cliches×loud SaaS gradients and oversized rounded cards×component inventory screens without a believable document workflow
tokens
borders4 items
accent width
2px
character
sumi hairlines that separate context layers without enclosing every object heavily
default width
1px
style
solid
colors12 items
accent
#c76f2a
background
#f6f3ed
border
#d8d2c6
error
#9f3f35
info
#3f6d8f
muted
#7b746a
primary
#1f3f5f
secondary
#5b5348
success
#4f7a5b
surface
#fbfaf6
text
#24211d
warning
#b98225
motion3 items
duration
140ms
easing
cubic-bezier(0.2, 0, 0.1, 1)
philosophy
motion confirms focus and layer changes with short fades and outline shifts; no spring, bounce, or parallax
radii5 items
full
9999px
lg
6px
md
4px
none
0
sm
2px
shadows3 items
lg
0 18px 48px rgba(36,33,29,0.08)
md
0 8px 24px rgba(36,33,29,0.06)
sm
0 1px 0 rgba(36,33,29,0.05)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
low-opacity crosshair ruling and linear paper grain at 8px rhythm
card style
flat rectangular panels with hairline borders, square micro-color markers, and almost no elevation
treatment
washi-like restraint through warm neutral fills, subtle paper grain, and inset edge bands
typography9 items
base size
16px
body font
IBM Plex Sans JP
document font
Source Serif 4
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Sans+JP:wght@400;500;600&family=Source+Serif+4:opsz,wght@8..60,400;8..60,600&family=JetBrains+Mono:wght@400;500;600&display=swap
heading font
IBM Plex Sans JP
letter spacing
-0.012em
line height
1.55
mono font
JetBrains Mono
scale ratio
1.2
rules
composition
Compose the app as a document workspace: left context rail, central text plane, and right marginal signals column, all aligned to an 8px baseline and separated by hairlines.
density

Maintain calm compact density with 12-16px internal padding, tight metadata rows, and generous gutters around the primary reading pane.

hierarchy

Let type size, column position, indentation, and restrained weight changes establish order; color appears only for state, provenance, and active navigation.

signature patterns
Context-map rail uses connected vertical ticks and active indigo rule segments to show where the current document sits in a chain of evidence.Marginal metric cards use mono numerals, tiny persimmon or success squares, and a ruled baseline so analytics feel attached to the document margin.Document excerpts sit on flat washi panels with serif text, inset top hairlines, and annotation chips that float inline rather than becoming cards.Interactive rows reveal a two-pixel semantic left strip on hover or selected state while keeping the rest of the surface neutral.
layout
breakpoints

mobile 375px single column; tablet 768px rail over document with hidden metrics drawer; desktop 1200px full three-column context map

grid

Desktop uses 64px outer gutters with 260px context rail, minmax central document column, and 300px marginal analytics column.

whitespace

Whitespace is directional: wider around the document body, tighter inside rails, and consistent 8px rhythm for marginal signals.

guidance
do
  • Use hairlines, indentation, and small markers to connect context.
  • Keep document text readable and dominant over metrics.
  • Use sumi, indigo, persimmon, success, and warning tokens semantically only.
  • Show analytics as marginal signals attached to passages.
avoid
  • Do not use literal Japanese motifs, textures, icons, or tourist imagery.
  • Do not fill large cards with accent colors or gradients.
  • Do not make a generic KPI dashboard; every metric needs document context.
  • Do not use pill-heavy rounded SaaS styling.
katagami spec
# AYA Context Map Sumi

## Philosophy

AYA Context Map Sumi is a quiet, text-first workspace language for document-adjacent analytics: navigation behaves like a context map, surfaces read as layered paper, and small semantic colors mark status without turning the product into a dashboard.

### Values

- document primacy before chrome
- negative space as orientation
- compact metrics that stay marginal
- semantic color used only when it clarifies state

### Anti-Values

- literal Japanese ornament, motifs, fans, waves, or red-circle cliches
- loud SaaS gradients and oversized rounded cards
- component inventory screens without a believable document workflow

### Visual Character

- Use a three-column CSS grid with a narrow context-map rail, a dominant reading pane, and a slim marginal analytics column that collapses below tablet width.
- Render surfaces with warm off-white backgrounds, one-pixel sumi hairline borders, and inset linear-gradient edge bands instead of shadows or heavy cards.
- Apply compact typography with IBM Plex Sans JP for interface text, Source Serif 4 for document excerpts, and JetBrains Mono for metrics and IDs.
- Place semantic micro-color strips and small square status markers on the left edge of rows, never as full-card fills or decorative illustrations.
- Use focus and hover states as calm indigo outline rings plus background tint shifts, with transitions under 160ms and no bouncing motion.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: sumi hairlines that separate context layers without enclosing every object heavily
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#c76f2a` |
| background | `#f6f3ed` |
| border | `#d8d2c6` |
| error | `#9f3f35` |
| info | `#3f6d8f` |
| muted | `#7b746a` |
| primary | `#1f3f5f` |
| secondary | `#5b5348` |
| success | `#4f7a5b` |
| surface | `#fbfaf6` |
| text | `#24211d` |
| warning | `#b98225` |

### Motion

- **Duration**: 140ms
- **Easing**: cubic-bezier(0.2, 0, 0.1, 1)
- **Philosophy**: motion confirms focus and layer changes with short fades and outline shifts; no spring, bounce, or parallax

### Radii

- **Full**: 9999px
- **Lg**: 6px
- **Md**: 4px
- **None**: 0
- **Sm**: 2px

### Shadows

- **Lg**: 0 18px 48px rgba(36,33,29,0.08)
- **Md**: 0 8px 24px rgba(36,33,29,0.06)
- **Sm**: 0 1px 0 rgba(36,33,29,0.05)

### Spacing

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

### Surfaces

- **Bg Pattern**: low-opacity crosshair ruling and linear paper grain at 8px rhythm
- **Card Style**: flat rectangular panels with hairline borders, square micro-color markers, and almost no elevation
- **Treatment**: washi-like restraint through warm neutral fills, subtle paper grain, and inset edge bands

### Typography

- **Base Size**: 16px
- **Body Font**: IBM Plex Sans JP
- **Document Font**: Source Serif 4
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Sans+JP:wght@400;500;600&family=Source+Serif+4:opsz,wght@8..60,400;8..60,600&family=JetBrains+Mono:wght@400;500;600&display=swap
- **Heading Font**: IBM Plex Sans JP
- **Letter Spacing**: -0.012em
- **Line Height**: 1.55
- **Mono Font**: JetBrains Mono
- **Scale Ratio**: 1.2

## Rules

### Composition

Compose the app as a document workspace: left context rail, central text plane, and right marginal signals column, all aligned to an 8px baseline and separated by hairlines.

### Density

Maintain calm compact density with 12-16px internal padding, tight metadata rows, and generous gutters around the primary reading pane.

### Hierarchy

Let type size, column position, indentation, and restrained weight changes establish order; color appears only for state, provenance, and active navigation.

### Signature Patterns

- Context-map rail uses connected vertical ticks and active indigo rule segments to show where the current document sits in a chain of evidence.
- Marginal metric cards use mono numerals, tiny persimmon or success squares, and a ruled baseline so analytics feel attached to the document margin.
- Document excerpts sit on flat washi panels with serif text, inset top hairlines, and annotation chips that float inline rather than becoming cards.
- Interactive rows reveal a two-pixel semantic left strip on hover or selected state while keeping the rest of the surface neutral.

## Layout

### Breakpoints

mobile 375px single column; tablet 768px rail over document with hidden metrics drawer; desktop 1200px full three-column context map

### Grid

Desktop uses 64px outer gutters with 260px context rail, minmax central document column, and 300px marginal analytics column.

### Whitespace

Whitespace is directional: wider around the document body, tighter inside rails, and consistent 8px rhythm for marginal signals.

## Guidance

### Do

- Use hairlines, indentation, and small markers to connect context.
- Keep document text readable and dominant over metrics.
- Use sumi, indigo, persimmon, success, and warning tokens semantically only.
- Show analytics as marginal signals attached to passages.

### Don't

- Do not use literal Japanese motifs, textures, icons, or tourist imagery.
- Do not fill large cards with accent colors or gradients.
- Do not make a generic KPI dashboard; every metric needs document context.
- Do not use pill-heavy rounded SaaS styling.
DESIGN.md
---
version: "alpha"
name: "AYA Context Map Sumi"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#c76f2a"
  background: "#f6f3ed"
  border: "#d8d2c6"
  error: "#9f3f35"
  info: "#3f6d8f"
  muted: "#7b746a"
  primary: "#1f3f5f"
  secondary: "#5b5348"
  success: "#4f7a5b"
  surface: "#fbfaf6"
  text: "#24211d"
  warning: "#b98225"
typography:
  headline-lg:
    fontFamily: "IBM Plex Sans JP"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.012em"
  headline-md:
    fontFamily: "IBM Plex Sans JP"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.012em"
  body-md:
    fontFamily: "IBM Plex Sans JP"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.55
    letterSpacing: "-0.012em"
  label-md:
    fontFamily: "JetBrains Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "6px"
  md: "4px"
  none: "0px"
  sm: "2px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#ffffff"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  card-surface:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  input-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    height: "44px"
---

# AYA Context Map Sumi

## Overview

AYA Context Map Sumi is a quiet, text-first workspace language for document-adjacent analytics: navigation behaves like a context map, surfaces read as layered paper, and small semantic colors mark status without turning the product into a dashboard.

### Values

- document primacy before chrome
- negative space as orientation
- compact metrics that stay marginal
- semantic color used only when it clarifies state

### Anti-Values

- literal Japanese ornament, motifs, fans, waves, or red-circle cliches
- loud SaaS gradients and oversized rounded cards
- component inventory screens without a believable document workflow

### Visual Character

- Use a three-column CSS grid with a narrow context-map rail, a dominant reading pane, and a slim marginal analytics column that collapses below tablet width.
- Render surfaces with warm off-white backgrounds, one-pixel sumi hairline borders, and inset linear-gradient edge bands instead of shadows or heavy cards.
- Apply compact typography with IBM Plex Sans JP for interface text, Source Serif 4 for document excerpts, and JetBrains Mono for metrics and IDs.
- Place semantic micro-color strips and small square status markers on the left edge of rows, never as full-card fills or decorative illustrations.
- Use focus and hover states as calm indigo outline rings plus background tint shifts, with transitions under 160ms and no bouncing motion.

## Colors

Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.

| Token | Value |
|-------|-------|
| accent | `#c76f2a` |
| background | `#f6f3ed` |
| border | `#d8d2c6` |
| error | `#9f3f35` |
| info | `#3f6d8f` |
| muted | `#7b746a` |
| primary | `#1f3f5f` |
| secondary | `#5b5348` |
| success | `#4f7a5b` |
| surface | `#fbfaf6` |
| text | `#24211d` |
| warning | `#b98225` |

## Typography

- **Headline-Lg**: IBM Plex Sans JP, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: IBM Plex Sans JP, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans JP, 16px, weight 400, line-height 1.55.
- **Label-Md**: JetBrains Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`

### Breakpoints

mobile 375px single column; tablet 768px rail over document with hidden metrics drawer; desktop 1200px full three-column context map

### Grid

Desktop uses 64px outer gutters with 260px context rail, minmax central document column, and 300px marginal analytics column.

### Whitespace

Whitespace is directional: wider around the document body, tighter inside rails, and consistent 8px rhythm for marginal signals.

## Elevation & Depth

### Shadows

- **Lg**: 0 18px 48px rgba(36,33,29,0.08)
- **Md**: 0 8px 24px rgba(36,33,29,0.06)
- **Sm**: 0 1px 0 rgba(36,33,29,0.05)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `6px`
- **Md**: `4px`
- **None**: `0px`
- **Sm**: `2px`

### Surfaces

- **Bg Pattern**: low-opacity crosshair ruling and linear paper grain at 8px rhythm
- **Card Style**: flat rectangular panels with hairline borders, square micro-color markers, and almost no elevation
- **Treatment**: washi-like restraint through warm neutral fills, subtle paper grain, and inset edge bands

### Borders

- **Accent Width**: 2px
- **Character**: sumi hairlines that separate context layers without enclosing every object heavily
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Compose the app as a document workspace: left context rail, central text plane, and right marginal signals column, all aligned to an 8px baseline and separated by hairlines.

### Density

Maintain calm compact density with 12-16px internal padding, tight metadata rows, and generous gutters around the primary reading pane.

### Hierarchy

Let type size, column position, indentation, and restrained weight changes establish order; color appears only for state, provenance, and active navigation.

### Signature Patterns

- Context-map rail uses connected vertical ticks and active indigo rule segments to show where the current document sits in a chain of evidence.
- Marginal metric cards use mono numerals, tiny persimmon or success squares, and a ruled baseline so analytics feel attached to the document margin.
- Document excerpts sit on flat washi panels with serif text, inset top hairlines, and annotation chips that float inline rather than becoming cards.
- Interactive rows reveal a two-pixel semantic left strip on hover or selected state while keeping the rest of the surface neutral.

## 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-019ee04b-c16c-79d0-bf58-4bdf87f7ecd9/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 hairlines, indentation, and small markers to connect context.
- Do Keep document text readable and dominant over metrics.
- Do Use sumi, indigo, persimmon, success, and warning tokens semantically only.
- Do Show analytics as marginal signals attached to passages.
- Don't Do not use literal Japanese motifs, textures, icons, or tourist imagery.
- Don't Do not fill large cards with accent colors or gradients.
- Don't Do not make a generic KPI dashboard; every metric needs document context.
- Don't Do not use pill-heavy rounded SaaS styling.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "aya-context-map-sumi",
  "type": "registry:theme",
  "title": "AYA Context Map Sumi shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#f6f3ed",
      "foreground": "#24211d",
      "card": "#fbfaf6",
      "card-foreground": "#24211d",
      "popover": "#fbfaf6",
      "popover-foreground": "#24211d",
      "primary": "#1f3f5f",
      "primary-foreground": "#ffffff",
      "secondary": "#5b5348",
      "secondary-foreground": "#ffffff",
      "muted": "#7b746a",
      "muted-foreground": "#24211d",
      "accent": "#c76f2a",
      "accent-foreground": "#ffffff",
      "destructive": "#9f3f35",
      "border": "#d8d2c6",
      "input": "#d8d2c6",
      "ring": "#c76f2a",
      "chart-1": "#1f3f5f",
      "chart-2": "#5b5348",
      "chart-3": "#c76f2a",
      "chart-4": "#4f7a5b",
      "chart-5": "#b98225",
      "sidebar": "#fbfaf6",
      "sidebar-foreground": "#24211d",
      "sidebar-primary": "#1f3f5f",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#3f6d8f",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#d8d2c6",
      "sidebar-ring": "#c76f2a",
      "radius": "4px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1f3f5f",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#c76f2a",
      "accent-foreground": "#ffffff",
      "destructive": "#9f3f35",
      "border": "#303642",
      "input": "#303642",
      "ring": "#c76f2a",
      "chart-1": "#1f3f5f",
      "chart-2": "#5b5348",
      "chart-3": "#c76f2a",
      "chart-4": "#4f7a5b",
      "chart-5": "#b98225",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1f3f5f",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#c76f2a",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#c76f2a",
      "radius": "4px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019ee04b-c16c-79d0-bf58-4bdf87f7ecd9",
    "slug": "aya-context-map-sumi",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "document_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · aya-context-map-sumi
DESIGN.md

at a glance

Palette

Typography

headline-lgIBM Plex Sans JP · 28px · 700

The quick brown fox jumps

headline-mdIBM Plex Sans JP · 23px · 600

The quick brown fox jumps

body-mdIBM Plex Sans JP · 16px · 400

The quick brown fox jumps

label-mdJetBrains 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

Shape

full9999px
lg6px
md4px
none0px
sm2px
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: #f6f3ed;
  --foreground: #24211d;
  --card: #fbfaf6;
  --card-foreground: #24211d;
  --popover: #fbfaf6;
  --popover-foreground: #24211d;
  --primary: #1f3f5f;
  --primary-foreground: #ffffff;
  --secondary: #5b5348;
  --secondary-foreground: #ffffff;
  --muted: #7b746a;
  --muted-foreground: #24211d;
  --accent: #c76f2a;
  --accent-foreground: #ffffff;
  --destructive: #9f3f35;
  --border: #d8d2c6;
  --input: #d8d2c6;
  --ring: #c76f2a;
  --chart-1: #1f3f5f;
  --chart-2: #5b5348;
  --chart-3: #c76f2a;
  --chart-4: #4f7a5b;
  --chart-5: #b98225;
  --sidebar: #fbfaf6;
  --sidebar-foreground: #24211d;
  --sidebar-primary: #1f3f5f;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #3f6d8f;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #d8d2c6;
  --sidebar-ring: #c76f2a;
  --radius: 4px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #1f3f5f;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #c76f2a;
  --accent-foreground: #ffffff;
  --destructive: #9f3f35;
  --border: #303642;
  --input: #303642;
  --ring: #c76f2a;
  --chart-1: #1f3f5f;
  --chart-2: #5b5348;
  --chart-3: #c76f2a;
  --chart-4: #4f7a5b;
  --chart-5: #b98225;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #1f3f5f;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #c76f2a;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #c76f2a;
  --radius: 4px;
}
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 AyaContextMapSumiShadcnKit() {
  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">AYA Context Map Sumi</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": "aya-context-map-sumi",
  "type": "registry:theme",
  "title": "AYA Context Map Sumi shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#f6f3ed",
      "foreground": "#24211d",
      "card": "#fbfaf6",
      "card-foreground": "#24211d",
      "popover": "#fbfaf6",
      "popover-foreground": "#24211d",
      "primary": "#1f3f5f",
      "primary-foreground": "#ffffff",
      "secondary": "#5b5348",
      "secondary-foreground": "#ffffff",
      "muted": "#7b746a",
      "muted-foreground": "#24211d",
      "accent": "#c76f2a",
      "accent-foreground": "#ffffff",
      "destructive": "#9f3f35",
      "border": "#d8d2c6",
      "input": "#d8d2c6",
      "ring": "#c76f2a",
      "chart-1": "#1f3f5f",
      "chart-2": "#5b5348",
      "chart-3": "#c76f2a",
      "chart-4": "#4f7a5b",
      "chart-5": "#b98225",
      "sidebar": "#fbfaf6",
      "sidebar-foreground": "#24211d",
      "sidebar-primary": "#1f3f5f",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#3f6d8f",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#d8d2c6",
      "sidebar-ring": "#c76f2a",
      "radius": "4px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1f3f5f",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#c76f2a",
      "accent-foreground": "#ffffff",
      "destructive": "#9f3f35",
      "border": "#303642",
      "input": "#303642",
      "ring": "#c76f2a",
      "chart-1": "#1f3f5f",
      "chart-2": "#5b5348",
      "chart-3": "#c76f2a",
      "chart-4": "#4f7a5b",
      "chart-5": "#b98225",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1f3f5f",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#c76f2a",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#c76f2a",
      "radius": "4px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019ee04b-c16c-79d0-bf58-4bdf87f7ecd9",
    "slug": "aya-context-map-sumi",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "document_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
component recipescompatibility fallback
# AYA Context Map Sumi shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019ee04b-c16c-79d0-bf58-4bdf87f7ecd9`
Slug: `aya-context-map-sumi`

## Intent

AYA Context Map Sumi is a quiet, text-first workspace language for document-adjacent analytics: navigation behaves like a context map, surfaces read as layered paper, and small semantic colors mark status without turning the product into a dashboard.

## Required primitives

- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Install with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

## Token cues

Colors:

{
  "accent": "#c76f2a",
  "background": "#f6f3ed",
  "border": "#d8d2c6",
  "error": "#9f3f35",
  "info": "#3f6d8f",
  "muted": "#7b746a",
  "primary": "#1f3f5f",
  "secondary": "#5b5348",
  "success": "#4f7a5b",
  "surface": "#fbfaf6",
  "text": "#24211d",
  "warning": "#b98225"
}

Typography:

{
  "base_size": "16px",
  "body_font": "IBM Plex Sans JP",
  "document_font": "Source Serif 4",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Sans+JP:wght@400;500;600&family=Source+Serif+4:opsz,wght@8..60,400;8..60,600&family=JetBrains+Mono:wght@400;500;600&display=swap",
  "heading_font": "IBM Plex Sans JP",
  "letter_spacing": "-0.012em",
  "line_height": 1.55,
  "mono_font": "JetBrains Mono",
  "scale_ratio": 1.2
}

## Visual character to preserve

- Use a three-column CSS grid with a narrow context-map rail, a dominant reading pane, and a slim marginal analytics column that collapses below tablet width.
- Render surfaces with warm off-white backgrounds, one-pixel sumi hairline borders, and inset linear-gradient edge bands instead of shadows or heavy cards.
- Apply compact typography with IBM Plex Sans JP for interface text, Source Serif 4 for document excerpts, and JetBrains Mono for metrics and IDs.
- Place semantic micro-color strips and small square status markers on the left edge of rows, never as full-card fills or decorative illustrations.
- Use focus and hover states as calm indigo outline rings plus background tint shifts, with transitions under 160ms and no bouncing motion.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": true,
  "stickerBadges": false,
  "motion": "lift",
  "density": "dense",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.

### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.

### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.

### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.

### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.

## Preview shots

- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/aya-context-map-sumi/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 hairlines, indentation, and small markers to connect context.; Keep document text readable and dominant over metrics.; Use sumi, indigo, persimmon, success, and warning tokens semantically only.; Show analytics as marginal signals attached to passages.
- Do not: Do not use literal Japanese motifs, textures, icons, or tourist imagery.; Do not fill large cards with accent colors or gradients.; Do not make a generic KPI dashboard; every metric needs document context.; Do not use pill-heavy rounded SaaS styling.

## 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 AyaContextMapSumiShadcnKit() {
  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">AYA Context Map Sumi</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

      <Tabs defaultValue="components">
        <TabsList>
          <TabsTrigger value="components">Components</TabsTrigger>
          <TabsTrigger value="states">States</TabsTrigger>
          <TabsTrigger value="export">Export</TabsTrigger>
        </TabsList>
      </Tabs>

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
```

## Layout notes

{
  "breakpoints": "mobile 375px single column; tablet 768px rail over document with hidden metrics drawer; desktop 1200px full three-column context map",
  "grid": "Desktop uses 64px outer gutters with 260px context rail, minmax central document column, and 300px marginal analytics column.",
  "whitespace": "Whitespace is directional: wider around the document body, tighter inside rails, and consistent 8px rhythm for marginal signals."
}
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-019ee04b-c16c-79d0-bf58-4bdf87f7ecd9",
    "name": "AYA Context Map Sumi",
    "slug": "aya-context-map-sumi"
  },
  "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 three-column CSS grid with a narrow context-map rail, a dominant reading pane, and a slim marginal analytics column that collapses below tablet width.",
    "Render surfaces with warm off-white backgrounds, one-pixel sumi hairline borders, and inset linear-gradient edge bands instead of shadows or heavy cards.",
    "Apply compact typography with IBM Plex Sans JP for interface text, Source Serif 4 for document excerpts, and JetBrains Mono for metrics and IDs.",
    "Place semantic micro-color strips and small square status markers on the left edge of rows, never as full-card fills or decorative illustrations.",
    "Use focus and hover states as calm indigo outline rings plus background tint shifts, with transitions under 160ms and no bouncing motion."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": false,
    "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": "AYA Context Map Sumi 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 hairlines, indentation, and small markers to connect context.",
      "Keep document text readable and dominant over metrics.",
      "Use sumi, indigo, persimmon, success, and warning tokens semantically only.",
      "Show analytics as marginal signals attached to passages."
    ],
    "dont": [
      "Do not use literal Japanese motifs, textures, icons, or tourist imagery.",
      "Do not fill large cards with accent colors or gradients.",
      "Do not make a generic KPI dashboard; every metric needs document context.",
      "Do not use pill-heavy rounded SaaS styling."
    ]
  }
}
related

More like this