back to gallery
design language·en-019ee032-

Quiet Intelligence Document Surface

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
A text-first product design language for document-adjacent analytics. The document stays visually sovereign while intelligence appears as precise annotations: inline deltas, source confidence, freshness, completion, risk, coverage, and provenance. Japanese influence is translated into operating principles—ma as purposeful breathing room, washi as soft material restraint, sumi as crisp textual authority, indigo as the single interactive thread, persimmon as quiet caution, katagami as masking/reveal logic, and weaving as cross-reference structure—never as literal motif or tourist decoration.
values
reading comprehension before instrumentationanalytics expressed as annotations rather than dashboard panelscompact confidence, freshness, risk, and coverage signals exactly where they help decisionsquiet material layering with white, light stone, graphite, and soft slate borderscraft abstraction through masks, reveal edges, alignment, thread navigation, and negative spacesemantic color that is subdued, labeled, and accessibleprecision over decoration and source legibility over visual novelty
anti-values
×dashboard-first layouts that make metrics compete with the document×literal Japanese motifs such as waves, temples, fans, koi, blossoms, faux brush type, or ornamental patterns×tourist cliches and surface-level cultural styling×large saturated status fields, rainbow analytics, or chart walls×cards as the default container for every idea×low-contrast pale text that looks calm but reduces comprehension
tokens
border3 items
focus
2px solid #3B4F8F
hairline
1px solid #E8E9E4
standard
1px solid #D9DDD8
color16 items
amber muted
#A7772F
blue status
#527E9C
border
#D9DDD8
border soft
#E8E9E4
danger
#9B4E42
green status
#4F7F68
indigo
#3B4F8F
indigo soft
#E8ECFA
persimmon
#B86A3D
persimmon soft
#F7E7DC
surface page
#F7F5F0
surface sheet
#FFFFFF
surface subtle
#FBFAF7
text muted
#7D837F
text primary
#23211E
text secondary
#5E625F
radius4 items
chip
999px
input
10px
panel
14px
sheet
18px
space6 items
lg
24px
md
16px
reading gap
40px
sm
8px
xl
32px
xs
4px
typography7 items
body line height
1.66
body size
16px
font stack
Inter, ui-sans-serif, system-ui, -apple-system, Segoe UI, sans-serif
labels
11-12px regular or medium; small caps avoided except sparingly for stable metadata
measure
68-76ch
metric numerals
tabular-nums
mono stack
Roboto Mono, ui-monospace, SFMono-Regular, Menlo, monospace
rules
color
Base surfaces are white and light stone; primary text is sumi/graphite; borders are soft slate. Indigo is the primary interactive affordance for links, focus, active mode, selected threads, and source reveal. Persimmon or muted amber is reserved for caution/destructive confirmation. Desaturated green and blue indicate completion, confidence, and informational status at low intensity.
composition
Use a document workspace, not a dashboard. Top navigation exposes modes—Read, Weave, Compare, Decide—while the central sheet remains dominant. The right margin hosts signals and summaries; a bottom provenance strip can show compact version or source state. Cards are rare and quiet: use them only for expanded explanations, comparison snippets, or decision summaries. Most analytics live inline, in the margin, in headers, or in footnotes.
density
Compact intelligence, generous reading. Keep document rhythm spacious, but let chips, source rows, and provenance notes be dense and scannable. Prefer 1px separators, short labels, and narrow rails over floating panels.
hierarchy
Body copy is the primary object. Use strong graphite text, comfortable line height, and a maximum reading measure of 68-76 characters. Metrics use tabular numerals and small labels, but never outrank headings or body copy. Margin signals align to paragraphs or sections so the user can connect evidence to reading position.
imagery
No literal cultural imagery. Texture, if present, is almost imperceptible paper grain or soft translucency. The craft reference is structural: cutouts, layers, threads, alignment, and rhythm.
interaction
Metric chips expand to concise explanations with source, timestamp, and why-it-matters copy. Status indicators include text labels for accessibility. Focus and keyboard states are explicit: indigo outline, offset halo, and clear active labels. Destructive states use restrained contrast, persimmon border/fill accents, and direct copy.
motion
Use short, quiet transitions for reveal and comparison: 120-180ms opacity/translate changes. Treat katagami as mask behavior: contextual layers slide or uncover along aligned edges. Avoid playful bounce or ornamental animation.
layout
breakpoints
Mobile < 700px collapses margin signals into inline expandable notes and a bottom provenance tray; tablet keeps the document plus collapsible signal rail; desktop shows the full right intelligence margin.
density

Medium-low visual density for reading areas; medium-high informational density only inside chips, provenance rows, and margin signal clusters.

grid
Desktop uses a three-zone reading shell: 176-220px mode/navigation column when needed, a flexible document column constrained to a comfortable measure, and a 280-340px right signal margin. The document column remains the optical center.
responsive
Read mode prioritizes the sheet; Weave introduces thread navigation; Compare uses paired text panes with shared signal margin; Decide condenses evidence into a restrained decision strip without losing source links.
whitespace

Ma is functional: generous gutters around the sheet, calm paragraph rhythm, and quiet space between annotations so signals do not form a dashboard grid.

guidance
do
  • Keep the document or selected source text visually dominant in every screen.
  • Place confidence, freshness, deltas, completion, coverage, and risk as inline or marginal annotations.
  • Use tabular numerals for metrics and concise plain-language labels for comprehension.
  • Use indigo consistently for active navigation, links, focus, selections, and thread paths.
  • Use persimmon or muted amber only for warnings, unresolved risk, or destructive confirmation.
  • Translate weaving into cross-reference structure and thread-like navigation, not decorative patterns.
  • Translate katagami into reveal, mask, layer, and alignment rules, not ornamental cutouts.
  • Make expanded chips explain what changed, why it matters, source confidence, and timestamp.
avoid
  • Do not build a hero dashboard of cards or charts before the document appears.
  • Do not use waves, temples, fans, koi, cherry blossom, faux brush typography, or other literal Japanese motifs.
  • Do not flood the UI with saturated semantic colors or multicolor metric systems.
  • Do not hide status meaning behind color-only dots.
  • Do not use small caps heavily for labels; they can become decorative and reduce readability.
  • Do not let cards, shadows, or panels fragment the reading surface.
  • Do not make warnings visually dramatic unless the action is truly destructive or blocking.
katagami spec
# Quiet Intelligence Document Surface

## Philosophy

A text-first product design language for document-adjacent analytics. The document stays visually sovereign while intelligence appears as precise annotations: inline deltas, source confidence, freshness, completion, risk, coverage, and provenance. Japanese influence is translated into operating principles—ma as purposeful breathing room, washi as soft material restraint, sumi as crisp textual authority, indigo as the single interactive thread, persimmon as quiet caution, katagami as masking/reveal logic, and weaving as cross-reference structure—never as literal motif or tourist decoration.

### Values

- reading comprehension before instrumentation
- analytics expressed as annotations rather than dashboard panels
- compact confidence, freshness, risk, and coverage signals exactly where they help decisions
- quiet material layering with white, light stone, graphite, and soft slate borders
- craft abstraction through masks, reveal edges, alignment, thread navigation, and negative space
- semantic color that is subdued, labeled, and accessible
- precision over decoration and source legibility over visual novelty

### Anti-Values

- dashboard-first layouts that make metrics compete with the document
- literal Japanese motifs such as waves, temples, fans, koi, blossoms, faux brush type, or ornamental patterns
- tourist cliches and surface-level cultural styling
- large saturated status fields, rainbow analytics, or chart walls
- cards as the default container for every idea
- low-contrast pale text that looks calm but reduces comprehension

### Visual Character

- A central reading sheet sits on a light stone canvas with controlled line length and low-chrome separators.
- The right margin acts as an intelligence selvage: compact signals, short summaries, source state, and risk notes align to the reading flow.
- Inline chips, footnote-like badges, and tiny thread markers expand into explanations without displacing the text.
- Indigo marks primary interaction, focus, selected references, and cross-document thread paths; persimmon appears only for caution and warnings.
- Layered context appears through thin masks, translucent reveal strips, and aligned cutout panels rather than decorative stencil patterns.

## Tokens

### Border

- **Focus**: 2px solid #3B4F8F
- **Hairline**: 1px solid #E8E9E4
- **Standard**: 1px solid #D9DDD8

### Color

- **Amber Muted**: #A7772F
- **Blue Status**: #527E9C
- **Border**: #D9DDD8
- **Border Soft**: #E8E9E4
- **Danger**: #9B4E42
- **Green Status**: #4F7F68
- **Indigo**: #3B4F8F
- **Indigo Soft**: #E8ECFA
- **Persimmon**: #B86A3D
- **Persimmon Soft**: #F7E7DC
- **Surface Page**: #F7F5F0
- **Surface Sheet**: #FFFFFF
- **Surface Subtle**: #FBFAF7
- **Text Muted**: #7D837F
- **Text Primary**: #23211E
- **Text Secondary**: #5E625F

### Radius

- **Chip**: 999px
- **Input**: 10px
- **Panel**: 14px
- **Sheet**: 18px

### Space

- **Lg**: 24px
- **Md**: 16px
- **Reading Gap**: 40px
- **Sm**: 8px
- **Xl**: 32px
- **Xs**: 4px

### Typography

- **Body Line Height**: 1.66
- **Body Size**: 16px
- **Font Stack**: Inter, ui-sans-serif, system-ui, -apple-system, Segoe UI, sans-serif
- **Labels**: 11-12px regular or medium; small caps avoided except sparingly for stable metadata
- **Measure**: 68-76ch
- **Metric Numerals**: tabular-nums
- **Mono Stack**: Roboto Mono, ui-monospace, SFMono-Regular, Menlo, monospace

## Rules

### Color

Base surfaces are white and light stone; primary text is sumi/graphite; borders are soft slate. Indigo is the primary interactive affordance for links, focus, active mode, selected threads, and source reveal. Persimmon or muted amber is reserved for caution/destructive confirmation. Desaturated green and blue indicate completion, confidence, and informational status at low intensity.

### Composition

Use a document workspace, not a dashboard. Top navigation exposes modes—Read, Weave, Compare, Decide—while the central sheet remains dominant. The right margin hosts signals and summaries; a bottom provenance strip can show compact version or source state. Cards are rare and quiet: use them only for expanded explanations, comparison snippets, or decision summaries. Most analytics live inline, in the margin, in headers, or in footnotes.

### Density

Compact intelligence, generous reading. Keep document rhythm spacious, but let chips, source rows, and provenance notes be dense and scannable. Prefer 1px separators, short labels, and narrow rails over floating panels.

### Hierarchy

Body copy is the primary object. Use strong graphite text, comfortable line height, and a maximum reading measure of 68-76 characters. Metrics use tabular numerals and small labels, but never outrank headings or body copy. Margin signals align to paragraphs or sections so the user can connect evidence to reading position.

### Imagery

No literal cultural imagery. Texture, if present, is almost imperceptible paper grain or soft translucency. The craft reference is structural: cutouts, layers, threads, alignment, and rhythm.

### Interaction

Metric chips expand to concise explanations with source, timestamp, and why-it-matters copy. Status indicators include text labels for accessibility. Focus and keyboard states are explicit: indigo outline, offset halo, and clear active labels. Destructive states use restrained contrast, persimmon border/fill accents, and direct copy.

### Motion

Use short, quiet transitions for reveal and comparison: 120-180ms opacity/translate changes. Treat katagami as mask behavior: contextual layers slide or uncover along aligned edges. Avoid playful bounce or ornamental animation.

## Layout

### Breakpoints

Mobile < 700px collapses margin signals into inline expandable notes and a bottom provenance tray; tablet keeps the document plus collapsible signal rail; desktop shows the full right intelligence margin.

### Density

Medium-low visual density for reading areas; medium-high informational density only inside chips, provenance rows, and margin signal clusters.

### Grid

Desktop uses a three-zone reading shell: 176-220px mode/navigation column when needed, a flexible document column constrained to a comfortable measure, and a 280-340px right signal margin. The document column remains the optical center.

### Responsive

Read mode prioritizes the sheet; Weave introduces thread navigation; Compare uses paired text panes with shared signal margin; Decide condenses evidence into a restrained decision strip without losing source links.

### Whitespace

Ma is functional: generous gutters around the sheet, calm paragraph rhythm, and quiet space between annotations so signals do not form a dashboard grid.

## Guidance

### Do

- Keep the document or selected source text visually dominant in every screen.
- Place confidence, freshness, deltas, completion, coverage, and risk as inline or marginal annotations.
- Use tabular numerals for metrics and concise plain-language labels for comprehension.
- Use indigo consistently for active navigation, links, focus, selections, and thread paths.
- Use persimmon or muted amber only for warnings, unresolved risk, or destructive confirmation.
- Translate weaving into cross-reference structure and thread-like navigation, not decorative patterns.
- Translate katagami into reveal, mask, layer, and alignment rules, not ornamental cutouts.
- Make expanded chips explain what changed, why it matters, source confidence, and timestamp.

### Don't

- Do not build a hero dashboard of cards or charts before the document appears.
- Do not use waves, temples, fans, koi, cherry blossom, faux brush typography, or other literal Japanese motifs.
- Do not flood the UI with saturated semantic colors or multicolor metric systems.
- Do not hide status meaning behind color-only dots.
- Do not use small caps heavily for labels; they can become decorative and reduce readability.
- Do not let cards, shadows, or panels fragment the reading surface.
- Do not make warnings visually dramatic unless the action is truly destructive or blocking.

### Accessibility

Maintain WCAG AA text contrast on white and stone surfaces. Every status color has a visible label and/or shape cue. Keyboard focus uses indigo outline plus offset halo. Chips expose explanations through click, Enter, Space, and hover/focus. Do not encode confidence, warning, or freshness by color alone.

### Usage Context

Best for AI research workspaces, document review, policy/compliance reading, knowledge synthesis, source comparison, editorial analytics, and decision tools where many context signals must support reading without becoming a dashboard.
DESIGN.md
---
version: "alpha"
name: "Quiet Intelligence Document Surface"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
typography:
  headline-lg:
    fontFamily: "Inter"
    fontSize: "1.953rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Inter"
    fontSize: "1.563rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "Inter"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "Inter"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
---

# Quiet Intelligence Document Surface

## Overview

A text-first product design language for document-adjacent analytics. The document stays visually sovereign while intelligence appears as precise annotations: inline deltas, source confidence, freshness, completion, risk, coverage, and provenance. Japanese influence is translated into operating principles—ma as purposeful breathing room, washi as soft material restraint, sumi as crisp textual authority, indigo as the single interactive thread, persimmon as quiet caution, katagami as masking/reveal logic, and weaving as cross-reference structure—never as literal motif or tourist decoration.

### Values

- reading comprehension before instrumentation
- analytics expressed as annotations rather than dashboard panels
- compact confidence, freshness, risk, and coverage signals exactly where they help decisions
- quiet material layering with white, light stone, graphite, and soft slate borders
- craft abstraction through masks, reveal edges, alignment, thread navigation, and negative space
- semantic color that is subdued, labeled, and accessible
- precision over decoration and source legibility over visual novelty

### Anti-Values

- dashboard-first layouts that make metrics compete with the document
- literal Japanese motifs such as waves, temples, fans, koi, blossoms, faux brush type, or ornamental patterns
- tourist cliches and surface-level cultural styling
- large saturated status fields, rainbow analytics, or chart walls
- cards as the default container for every idea
- low-contrast pale text that looks calm but reduces comprehension

### Visual Character

- A central reading sheet sits on a light stone canvas with controlled line length and low-chrome separators.
- The right margin acts as an intelligence selvage: compact signals, short summaries, source state, and risk notes align to the reading flow.
- Inline chips, footnote-like badges, and tiny thread markers expand into explanations without displacing the text.
- Indigo marks primary interaction, focus, selected references, and cross-document thread paths; persimmon appears only for caution and warnings.
- Layered context appears through thin masks, translucent reveal strips, and aligned cutout panels rather than decorative stencil patterns.

## Typography

- **Headline-Lg**: Inter, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Inter, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Inter, 16px, weight 400, line-height 1.5.
- **Label-Md**: Inter, 0.75rem, weight 600, line-height 1.

## Layout

### Breakpoints

Mobile < 700px collapses margin signals into inline expandable notes and a bottom provenance tray; tablet keeps the document plus collapsible signal rail; desktop shows the full right intelligence margin.

### Density

Medium-low visual density for reading areas; medium-high informational density only inside chips, provenance rows, and margin signal clusters.

### Grid

Desktop uses a three-zone reading shell: 176-220px mode/navigation column when needed, a flexible document column constrained to a comfortable measure, and a 280-340px right signal margin. The document column remains the optical center.

### Responsive

Read mode prioritizes the sheet; Weave introduces thread navigation; Compare uses paired text panes with shared signal margin; Decide condenses evidence into a restrained decision strip without losing source links.

### Whitespace

Ma is functional: generous gutters around the sheet, calm paragraph rhythm, and quiet space between annotations so signals do not form a dashboard grid.

## Components

### Color

Base surfaces are white and light stone; primary text is sumi/graphite; borders are soft slate. Indigo is the primary interactive affordance for links, focus, active mode, selected threads, and source reveal. Persimmon or muted amber is reserved for caution/destructive confirmation. Desaturated green and blue indicate completion, confidence, and informational status at low intensity.

### Composition

Use a document workspace, not a dashboard. Top navigation exposes modes—Read, Weave, Compare, Decide—while the central sheet remains dominant. The right margin hosts signals and summaries; a bottom provenance strip can show compact version or source state. Cards are rare and quiet: use them only for expanded explanations, comparison snippets, or decision summaries. Most analytics live inline, in the margin, in headers, or in footnotes.

### Density

Compact intelligence, generous reading. Keep document rhythm spacious, but let chips, source rows, and provenance notes be dense and scannable. Prefer 1px separators, short labels, and narrow rails over floating panels.

### Hierarchy

Body copy is the primary object. Use strong graphite text, comfortable line height, and a maximum reading measure of 68-76 characters. Metrics use tabular numerals and small labels, but never outrank headings or body copy. Margin signals align to paragraphs or sections so the user can connect evidence to reading position.

### Imagery

No literal cultural imagery. Texture, if present, is almost imperceptible paper grain or soft translucency. The craft reference is structural: cutouts, layers, threads, alignment, and rhythm.

### Interaction

Metric chips expand to concise explanations with source, timestamp, and why-it-matters copy. Status indicators include text labels for accessibility. Focus and keyboard states are explicit: indigo outline, offset halo, and clear active labels. Destructive states use restrained contrast, persimmon border/fill accents, and direct copy.

### Motion

Use short, quiet transitions for reveal and comparison: 120-180ms opacity/translate changes. Treat katagami as mask behavior: contextual layers slide or uncover along aligned edges. Avoid playful bounce or ornamental animation.

## 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-019ee032-9089-75e2-bac3-b76ae77ef8b2/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 Keep the document or selected source text visually dominant in every screen.
- Do Place confidence, freshness, deltas, completion, coverage, and risk as inline or marginal annotations.
- Do Use tabular numerals for metrics and concise plain-language labels for comprehension.
- Do Use indigo consistently for active navigation, links, focus, selections, and thread paths.
- Do Use persimmon or muted amber only for warnings, unresolved risk, or destructive confirmation.
- Do Translate weaving into cross-reference structure and thread-like navigation, not decorative patterns.
- Do Translate katagami into reveal, mask, layer, and alignment rules, not ornamental cutouts.
- Do Make expanded chips explain what changed, why it matters, source confidence, and timestamp.
- Don't Do not build a hero dashboard of cards or charts before the document appears.
- Don't Do not use waves, temples, fans, koi, cherry blossom, faux brush typography, or other literal Japanese motifs.
- Don't Do not flood the UI with saturated semantic colors or multicolor metric systems.
- Don't Do not hide status meaning behind color-only dots.
- Don't Do not use small caps heavily for labels; they can become decorative and reduce readability.
- Don't Do not let cards, shadows, or panels fragment the reading surface.
- Don't Do not make warnings visually dramatic unless the action is truly destructive or blocking.

### Accessibility

Maintain WCAG AA text contrast on white and stone surfaces. Every status color has a visible label and/or shape cue. Keyboard focus uses indigo outline plus offset halo. Chips expose explanations through click, Enter, Space, and hover/focus. Do not encode confidence, warning, or freshness by color alone.

### Usage Context

Best for AI research workspaces, document review, policy/compliance reading, knowledge synthesis, source comparison, editorial analytics, and decision tools where many context signals must support reading without becoming a dashboard.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "quiet-intelligence-document-surface",
  "type": "registry:theme",
  "title": "Quiet Intelligence Document Surface shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#ffffff",
      "foreground": "#111111",
      "card": "#ffffff",
      "card-foreground": "#111111",
      "popover": "#ffffff",
      "popover-foreground": "#111111",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#f4f4f5",
      "muted-foreground": "#111111",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#e4e4e7",
      "input": "#e4e4e7",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#ffffff",
      "sidebar-foreground": "#111111",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#e4e4e7",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#303642",
      "input": "#303642",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019ee032-9089-75e2-bac3-b76ae77ef8b2",
    "slug": "quiet-intelligence-document-surface",
    "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": {
      "border": [
        "focus",
        "hairline",
        "standard"
      ],
      "color": [
        "amber_muted",
        "blue_status",
        "border",
        "border_soft",
        "danger",
        "green_status",
        "indigo",
        "indigo_soft",
        "persimmon",
        "persimmon_soft",
        "surface_page",
        "surface_sheet",
        "surface_subtle",
        "text_muted",
        "text_primary",
        "text_secondary"
      ],
      "radius": [
        "chip",
        "input",
        "panel",
        "sheet"
      ],
      "space": [
        "lg",
        "md",
        "reading_gap",
        "sm",
        "xl",
        "xs"
      ],
      "typography": [
        "body_line_height",
        "body_size",
        "font_stack",
        "labels",
        "measure",
        "metric_numerals",
        "mono_stack"
      ]
    }
  }
}
```
in the wild

embodiments

Design Language Preview

Quiet Intelligence Document Surface

Color Palette

primary
secondary
accent
background
surface
text
muted
border
error
success
warning
info

Typography

h1

Heading One

h2

Heading Two

h3

Heading Three

h4

Heading Four

body

Body text demonstrates the reading experience. Good typography is invisible — it lets the content speak without drawing attention to the letterforms themselves.

caption

Caption text for supplementary information and metadata.

code
const theme = applyTokens(designLanguage);
render(<App theme={theme} />);

Buttons

Form Controls

Navigation

tabs
Overview content area with contextual information about the design language.
segmented control
dropdown menu

Feedback & Status

badges
NewDefaultActivePendingErrorOutline
alerts
Info: A new version is available.
Success: Changes saved successfully.
Warning: Storage is almost full.
Error: Failed to process request.
progress
66% complete
tooltip
avatar
AKJDML

Containers & Overlays

card

Card Title

Cards group related content and actions. This example shows a basic content card with a title and description.

accordion

Design tokens are the atomic values of a design system — colors, spacing, typography, and other values stored as key-value pairs.

dialog
separator

Data Display

table
NameStatusCategoryScore
Neo BrutalismPublishedMaximalist94
Aero GlassDraftSpatial87
Signal UIReviewEnterprise91
stat cards
Languages
42
+12%
Elements
3,150
+8%
Usage
18.4k
+23%
DESIGN.md

at a glance

Typography

headline-lgInter · 31px · 700

The quick brown fox jumps

headline-mdInter · 25px · 600

The quick brown fox jumps

body-mdInter · 16px · 400

The quick brown fox jumps

label-mdInter · 12px · 600

The quick brown fox jumps

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: #ffffff;
  --foreground: #111111;
  --card: #ffffff;
  --card-foreground: #111111;
  --popover: #ffffff;
  --popover-foreground: #111111;
  --primary: #111111;
  --primary-foreground: #ffffff;
  --secondary: #f4f4f5;
  --secondary-foreground: #111111;
  --muted: #f4f4f5;
  --muted-foreground: #111111;
  --accent: #111111;
  --accent-foreground: #ffffff;
  --destructive: #dc2626;
  --border: #e4e4e7;
  --input: #e4e4e7;
  --ring: #111111;
  --chart-1: #111111;
  --chart-2: #f4f4f5;
  --chart-3: #111111;
  --chart-4: #16a34a;
  --chart-5: #d97706;
  --sidebar: #ffffff;
  --sidebar-foreground: #111111;
  --sidebar-primary: #111111;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #111111;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #e4e4e7;
  --sidebar-ring: #111111;
  --radius: 0.625rem;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #111111;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #111111;
  --accent-foreground: #ffffff;
  --destructive: #dc2626;
  --border: #303642;
  --input: #303642;
  --ring: #111111;
  --chart-1: #111111;
  --chart-2: #f4f4f5;
  --chart-3: #111111;
  --chart-4: #16a34a;
  --chart-5: #d97706;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #111111;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #111111;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #111111;
  --radius: 0.625rem;
}
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 QuietIntelligenceDocumentSurfaceShadcnKit() {
  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">Quiet Intelligence Document Surface</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": "quiet-intelligence-document-surface",
  "type": "registry:theme",
  "title": "Quiet Intelligence Document Surface shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#ffffff",
      "foreground": "#111111",
      "card": "#ffffff",
      "card-foreground": "#111111",
      "popover": "#ffffff",
      "popover-foreground": "#111111",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#f4f4f5",
      "muted-foreground": "#111111",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#e4e4e7",
      "input": "#e4e4e7",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#ffffff",
      "sidebar-foreground": "#111111",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#e4e4e7",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#303642",
      "input": "#303642",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019ee032-9089-75e2-bac3-b76ae77ef8b2",
    "slug": "quiet-intelligence-document-surface",
    "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": {
      "border": [
        "focus",
        "hairline",
        "standard"
      ],
      "color": [
        "amber_muted",
        "blue_status",
        "border",
        "border_soft",
        "danger",
        "green_status",
        "indigo",
        "indigo_soft",
        "persimmon",
        "persimmon_soft",
        "surface_page",
        "surface_sheet",
        "surface_subtle",
        "text_muted",
        "text_primary",
        "text_secondary"
      ],
      "radius": [
        "chip",
        "input",
        "panel",
        "sheet"
      ],
      "space": [
        "lg",
        "md",
        "reading_gap",
        "sm",
        "xl",
        "xs"
      ],
      "typography": [
        "body_line_height",
        "body_size",
        "font_stack",
        "labels",
        "measure",
        "metric_numerals",
        "mono_stack"
      ]
    }
  }
}
component recipescompatibility fallback
# Quiet Intelligence Document Surface shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019ee032-9089-75e2-bac3-b76ae77ef8b2`
Slug: `en-019ee032-9089-75e2-bac3-b76ae77ef8b2`

## Intent

A text-first product design language for document-adjacent analytics. The document stays visually sovereign while intelligence appears as precise annotations: inline deltas, source confidence, freshness, completion, risk, coverage, and provenance. Japanese influence is translated into operating principles—ma as purposeful breathing room, washi as soft material restraint, sumi as crisp textual authority, indigo as the single interactive thread, persimmon as quiet caution, katagami as masking/reveal logic, and weaving as cross-reference structure—never as literal motif or tourist decoration.

## 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:

Defined by the Katagami source fields.

Typography:

{
  "body_line_height": "1.66",
  "body_size": "16px",
  "font_stack": "Inter, ui-sans-serif, system-ui, -apple-system, Segoe UI, sans-serif",
  "labels": "11-12px regular or medium; small caps avoided except sparingly for stable metadata",
  "measure": "68-76ch",
  "metric_numerals": "tabular-nums",
  "mono_stack": "Roboto Mono, ui-monospace, SFMono-Regular, Menlo, monospace"
}

## Visual character to preserve

- A central reading sheet sits on a light stone canvas with controlled line length and low-chrome separators.
- The right margin acts as an intelligence selvage: compact signals, short summaries, source state, and risk notes align to the reading flow.
- Inline chips, footnote-like badges, and tiny thread markers expand into explanations without displacing the text.
- Indigo marks primary interaction, focus, selected references, and cross-document thread paths; persimmon appears only for caution and warnings.
- Layered context appears through thin masks, translucent reveal strips, and aligned cutout panels rather than decorative stencil patterns.

## ShadSync visual profile

{
  "family": "system",
  "material": "flat",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": false,
  "stickerBadges": true,
  "motion": "still",
  "density": "dense",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

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

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

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

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

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

## Preview shots

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

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/en-019ee032-9089-75e2-bac3-b76ae77ef8b2/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: Keep the document or selected source text visually dominant in every screen.; Place confidence, freshness, deltas, completion, coverage, and risk as inline or marginal annotations.; Use tabular numerals for metrics and concise plain-language labels for comprehension.; Use indigo consistently for active navigation, links, focus, selections, and thread paths.; Use persimmon or muted amber only for warnings, unresolved risk, or destructive confirmation.; Translate weaving into cross-reference structure and thread-like navigation, not decorative patterns.; Translate katagami into reveal, mask, layer, and alignment rules, not ornamental cutouts.; Make expanded chips explain what changed, why it matters, source confidence, and timestamp.
- Do not: Do not build a hero dashboard of cards or charts before the document appears.; Do not use waves, temples, fans, koi, cherry blossom, faux brush typography, or other literal Japanese motifs.; Do not flood the UI with saturated semantic colors or multicolor metric systems.; Do not hide status meaning behind color-only dots.; Do not use small caps heavily for labels; they can become decorative and reduce readability.; Do not let cards, shadows, or panels fragment the reading surface.; Do not make warnings visually dramatic unless the action is truly destructive or blocking.

## 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 QuietIntelligenceDocumentSurfaceShadcnKit() {
  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">Quiet Intelligence Document Surface</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 < 700px collapses margin signals into inline expandable notes and a bottom provenance tray; tablet keeps the document plus collapsible signal rail; desktop shows the full right intelligence margin.",
  "density": "Medium-low visual density for reading areas; medium-high informational density only inside chips, provenance rows, and margin signal clusters.",
  "grid": "Desktop uses a three-zone reading shell: 176-220px mode/navigation column when needed, a flexible document column constrained to a comfortable measure, and a 280-340px right signal margin. The document column remains the optical center.",
  "responsive": "Read mode prioritizes the sheet; Weave introduces thread navigation; Compare uses paired text panes with shared signal margin; Decide condenses evidence into a restrained decision strip without losing source links.",
  "whitespace": "Ma is functional: generous gutters around the sheet, calm paragraph rhythm, and quiet space between annotations so signals do not form a dashboard grid."
}
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-019ee032-9089-75e2-bac3-b76ae77ef8b2",
    "name": "Quiet Intelligence Document Surface",
    "slug": "en-019ee032-9089-75e2-bac3-b76ae77ef8b2"
  },
  "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": [
    "A central reading sheet sits on a light stone canvas with controlled line length and low-chrome separators.",
    "The right margin acts as an intelligence selvage: compact signals, short summaries, source state, and risk notes align to the reading flow.",
    "Inline chips, footnote-like badges, and tiny thread markers expand into explanations without displacing the text.",
    "Indigo marks primary interaction, focus, selected references, and cross-document thread paths; persimmon appears only for caution and warnings.",
    "Layered context appears through thin masks, translucent reveal strips, and aligned cutout panels rather than decorative stencil patterns."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": false,
    "stickerBadges": true,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Quiet Intelligence Document Surface 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": [
      "Keep the document or selected source text visually dominant in every screen.",
      "Place confidence, freshness, deltas, completion, coverage, and risk as inline or marginal annotations.",
      "Use tabular numerals for metrics and concise plain-language labels for comprehension.",
      "Use indigo consistently for active navigation, links, focus, selections, and thread paths.",
      "Use persimmon or muted amber only for warnings, unresolved risk, or destructive confirmation.",
      "Translate weaving into cross-reference structure and thread-like navigation, not decorative patterns.",
      "Translate katagami into reveal, mask, layer, and alignment rules, not ornamental cutouts.",
      "Make expanded chips explain what changed, why it matters, source confidence, and timestamp."
    ],
    "dont": [
      "Do not build a hero dashboard of cards or charts before the document appears.",
      "Do not use waves, temples, fans, koi, cherry blossom, faux brush typography, or other literal Japanese motifs.",
      "Do not flood the UI with saturated semantic colors or multicolor metric systems.",
      "Do not hide status meaning behind color-only dots.",
      "Do not use small caps heavily for labels; they can become decorative and reduce readability.",
      "Do not let cards, shadows, or panels fragment the reading surface.",
      "Do not make warnings visually dramatic unless the action is truly destructive or blocking."
    ]
  }
}