back to gallery
design language·en-019ee038-

AYA Knot-and-Trail Decision Map

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 Knot-and-Trail Decision Map represents complex source reasoning as a calm linear reading trail with named convergence knots. It borrows from katagami restraint, loom ordering, and Tufte-style evidence trails without turning the interface into a decorative graph or literal weaving metaphor.
values
Linear comprehension first: the current trail is always readable as a sequence before it is explorable as a network.Knots are explicit decisions or convergences, named in language, and visually small enough to annotate flow rather than dominate it.Source provenance stays visible in compact ledgers, bundle cards, and audit footers rather than hidden behind hover-only affordances.Ma and shibui guide pacing: stone surfaces, quiet rails, and deliberate gaps make dense reasoning feel navigable.The loom is structural IA: warp-like source trails and weft-like document passages align content, but labels remain clear product language.
anti-values
×No default graph canvas as the primary navigation model.×No long breadcrumb strings that require parsing as prose.×No unlabeled colored dots; every chip, knot, and state needs text or accessible labeling.×No metaphor labels that replace clear IA terms such as Sources, Compare, Trail, Decision, Audit, or Bundle.×No hiding provenance, timestamps, or source relationships behind hover only.
tokens
color9 items
border quiet
#D7D5CE
knot plum
#7B4A68
surface base
#FDFCF9
surface stone
#F2F0EA
text muted
#686C70
text primary
#202226
trail active teal
#16706A
trail inactive
#D7D5CE
warning amber
#B7772B
radius3 items
card
10px
chip
999px
drawer
14px
spacing4 items
knot chip gap
6px
rail gap
12px
reader margin
48-88px desktop, 20-28px mobile
section gap
28-40px
stroke4 items
active trail
2px deep teal
focus
2px teal outline with 2px offset
knot dot
6-8px plum with text chip nearby
trail line
1px quiet smoke-gray
typography5 items
body
15-16px / 1.55, graphite, high contrast
decision name
semibold 14-16px, plain-language noun phrases
metadata
12-13px / 1.35, muted graphite, never below accessible contrast
micro label
11-12px uppercase or compact sentence case for rail labels only
ui family
Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, sans-serif
rules
color roles
Teal identifies only the followed trail/current path; remove teal from inactive or merely related items.Plum identifies convergence knots as small dots/chips with adjacent text labels.Amber remains semantic warning/feedback and must not be used for categories or decisions.
component rules
Trail Ledger: sticky rail with active teal segment, quiet gray inactive segments, labeled knot chips, and backtrack actions.Knot Chip: small plum marker plus semibold name; opens a panel, never a full decorative card by itself.Compare Drawer: side drawer for two to four sources/versions using small multiples and evidence annotations.Source Bundle Card: saved context packet with source count, included decisions, provenance, and restore action.Audit Trail Footer: always visible at document end and reachable from knots; includes timestamps, source changes, decision owner, and unresolved warnings.Relationship Preview: inline, one-hop previews only; graph view is optional diagnostics.
content rules
Name every knot as a decision or convergence, e.g. “Eligibility rule conflict,” not “Knot 4.”Use concise trail step labels under 42 characters where possible.Expose provenance in the visible layout, with hover used only for supplemental detail.
layout
breakpoints

mobile < 720px, tablet 720-1080px, desktop > 1080px.

density

Dense but breathable. Source, decision, and audit metadata are compact rows and chips; primary text retains generous line height and quiet margins.

grid
Desktop pairs a 220-280px trail ledger rail with a 680-780px main text column and an optional 320-420px compare/source drawer. Tablet compresses the ledger into a sticky top/side strip; mobile uses a collapsible Trail button plus inline knot summaries.
responsive

Preserve current-trail visibility at all sizes. Compare drawer becomes a bottom sheet on mobile; source bundle cards stack below the active passage.

whitespace

Use stone negative space to separate reasoning phases. Do not fill every intersection; absence is a pacing tool.

guidance
do
  • Use deep teal only for the currently followed trail, active rail segment, active source row, or current focus outline.
  • Use plum as small knot dots, pills, or chips marking a named convergence; never use plum as large panel fill.
  • Keep warning amber reserved for semantic feedback such as stale source, unresolved conflict, failed citation, or risky assumption.
  • Place a compact trail ledger beside the main text with numbered steps, source initials, timestamps, and named knots.
  • Make each knot open into a focused convergence panel with Decision, Sources, Assumptions, Alternatives, and Audit entries.
  • Use source bundle cards to preserve saved contexts: title, source count, decision coverage, last touched time, and primary confidence/status.
  • Offer lightweight relationship previews inline as short source-to-decision snippets or small multiples, not as a sprawling graph.
  • Keep labels literal: Trail Ledger, Knot, Compare, Source Bundle, Audit Trail, Related Decisions, Backtrack.
avoid
  • Do not make the graph view the home screen; if present, label it Diagnostic Map and keep it secondary.
  • Do not use thread, loom, warp, or weft as primary navigation labels.
  • Do not make colored dots unlabeled or rely on hover to reveal their meaning.
  • Do not render breadcrumb chains as long slash-separated strings.
  • Do not let amber compete visually with plum knots; warnings should be smaller or text-led when near knots.
  • Do not use decorative Japanese patterns, faux calligraphy, or icon fonts as the main information carrier.
katagami spec
# AYA Knot-and-Trail Decision Map

## Philosophy

AYA Knot-and-Trail Decision Map represents complex source reasoning as a calm linear reading trail with named convergence knots. It borrows from katagami restraint, loom ordering, and Tufte-style evidence trails without turning the interface into a decorative graph or literal weaving metaphor.

### Values

- Linear comprehension first: the current trail is always readable as a sequence before it is explorable as a network.
- Knots are explicit decisions or convergences, named in language, and visually small enough to annotate flow rather than dominate it.
- Source provenance stays visible in compact ledgers, bundle cards, and audit footers rather than hidden behind hover-only affordances.
- Ma and shibui guide pacing: stone surfaces, quiet rails, and deliberate gaps make dense reasoning feel navigable.
- The loom is structural IA: warp-like source trails and weft-like document passages align content, but labels remain clear product language.

### Anti-Values

- No default graph canvas as the primary navigation model.
- No long breadcrumb strings that require parsing as prose.
- No unlabeled colored dots; every chip, knot, and state needs text or accessible labeling.
- No metaphor labels that replace clear IA terms such as Sources, Compare, Trail, Decision, Audit, or Bundle.
- No hiding provenance, timestamps, or source relationships behind hover only.

## Tokens

### Color

- **Border Quiet**: #D7D5CE
- **Knot Plum**: #7B4A68
- **Surface Base**: #FDFCF9
- **Surface Stone**: #F2F0EA
- **Text Muted**: #686C70
- **Text Primary**: #202226
- **Trail Active Teal**: #16706A
- **Trail Inactive**: #D7D5CE
- **Warning Amber**: #B7772B

### Radius

- **Card**: 10px
- **Chip**: 999px
- **Drawer**: 14px

### Spacing

- **Knot Chip Gap**: 6px
- **Rail Gap**: 12px
- **Reader Margin**: 48-88px desktop, 20-28px mobile
- **Section Gap**: 28-40px

### Stroke

- **Active Trail**: 2px deep teal
- **Focus**: 2px teal outline with 2px offset
- **Knot Dot**: 6-8px plum with text chip nearby
- **Trail Line**: 1px quiet smoke-gray

### Typography

- **Body**: 15-16px / 1.55, graphite, high contrast
- **Decision Name**: semibold 14-16px, plain-language noun phrases
- **Metadata**: 12-13px / 1.35, muted graphite, never below accessible contrast
- **Micro Label**: 11-12px uppercase or compact sentence case for rail labels only
- **Ui Family**: Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, sans-serif

## Rules

### Color Roles

- Teal identifies only the followed trail/current path; remove teal from inactive or merely related items.
- Plum identifies convergence knots as small dots/chips with adjacent text labels.
- Amber remains semantic warning/feedback and must not be used for categories or decisions.

### Component Rules

- Trail Ledger: sticky rail with active teal segment, quiet gray inactive segments, labeled knot chips, and backtrack actions.
- Knot Chip: small plum marker plus semibold name; opens a panel, never a full decorative card by itself.
- Compare Drawer: side drawer for two to four sources/versions using small multiples and evidence annotations.
- Source Bundle Card: saved context packet with source count, included decisions, provenance, and restore action.
- Audit Trail Footer: always visible at document end and reachable from knots; includes timestamps, source changes, decision owner, and unresolved warnings.
- Relationship Preview: inline, one-hop previews only; graph view is optional diagnostics.

### Content Rules

- Name every knot as a decision or convergence, e.g. “Eligibility rule conflict,” not “Knot 4.”
- Use concise trail step labels under 42 characters where possible.
- Expose provenance in the visible layout, with hover used only for supplemental detail.

## Layout

### Breakpoints

mobile < 720px, tablet 720-1080px, desktop > 1080px.

### Density

Dense but breathable. Source, decision, and audit metadata are compact rows and chips; primary text retains generous line height and quiet margins.

### Grid

Desktop pairs a 220-280px trail ledger rail with a 680-780px main text column and an optional 320-420px compare/source drawer. Tablet compresses the ledger into a sticky top/side strip; mobile uses a collapsible Trail button plus inline knot summaries.

### Responsive

Preserve current-trail visibility at all sizes. Compare drawer becomes a bottom sheet on mobile; source bundle cards stack below the active passage.

### Whitespace

Use stone negative space to separate reasoning phases. Do not fill every intersection; absence is a pacing tool.

## Guidance

### Do

- Use deep teal only for the currently followed trail, active rail segment, active source row, or current focus outline.
- Use plum as small knot dots, pills, or chips marking a named convergence; never use plum as large panel fill.
- Keep warning amber reserved for semantic feedback such as stale source, unresolved conflict, failed citation, or risky assumption.
- Place a compact trail ledger beside the main text with numbered steps, source initials, timestamps, and named knots.
- Make each knot open into a focused convergence panel with Decision, Sources, Assumptions, Alternatives, and Audit entries.
- Use source bundle cards to preserve saved contexts: title, source count, decision coverage, last touched time, and primary confidence/status.
- Offer lightweight relationship previews inline as short source-to-decision snippets or small multiples, not as a sprawling graph.
- Keep labels literal: Trail Ledger, Knot, Compare, Source Bundle, Audit Trail, Related Decisions, Backtrack.

### Don't

- Do not make the graph view the home screen; if present, label it Diagnostic Map and keep it secondary.
- Do not use thread, loom, warp, or weft as primary navigation labels.
- Do not make colored dots unlabeled or rely on hover to reveal their meaning.
- Do not render breadcrumb chains as long slash-separated strings.
- Do not let amber compete visually with plum knots; warnings should be smaller or text-led when near knots.
- Do not use decorative Japanese patterns, faux calligraphy, or icon fonts as the main information carrier.

### Accessibility

Meet WCAG AA contrast for all labels and body text. Teal, plum, and amber must be paired with text labels, shape, or position. Keyboard users must be able to step through trail items, open a knot, compare sources, and reach the audit footer without hover-only interactions.

### Usage Context

Best for AI research workspaces, legal/product decision records, source-grounded writing systems, policy review, design rationale tools, and any dense text interface where users must backtrack, compare, and audit decisions without being forced into a graph.
DESIGN.md
---
version: "alpha"
name: "AYA Knot-and-Trail Decision Map"
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"
spacing:
  knot_chip_gap: "6px"
  rail_gap: "12px"
  reader_margin: "48-88px desktop, 20-28px mobile"
  section_gap: "28-40px"
---

# AYA Knot-and-Trail Decision Map

## Overview

AYA Knot-and-Trail Decision Map represents complex source reasoning as a calm linear reading trail with named convergence knots. It borrows from katagami restraint, loom ordering, and Tufte-style evidence trails without turning the interface into a decorative graph or literal weaving metaphor.

### Values

- Linear comprehension first: the current trail is always readable as a sequence before it is explorable as a network.
- Knots are explicit decisions or convergences, named in language, and visually small enough to annotate flow rather than dominate it.
- Source provenance stays visible in compact ledgers, bundle cards, and audit footers rather than hidden behind hover-only affordances.
- Ma and shibui guide pacing: stone surfaces, quiet rails, and deliberate gaps make dense reasoning feel navigable.
- The loom is structural IA: warp-like source trails and weft-like document passages align content, but labels remain clear product language.

### Anti-Values

- No default graph canvas as the primary navigation model.
- No long breadcrumb strings that require parsing as prose.
- No unlabeled colored dots; every chip, knot, and state needs text or accessible labeling.
- No metaphor labels that replace clear IA terms such as Sources, Compare, Trail, Decision, Audit, or Bundle.
- No hiding provenance, timestamps, or source relationships behind hover only.

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

### Spacing Tokens

- **Knot Chip Gap**: `6px`
- **Rail Gap**: `12px`
- **Reader Margin**: `48-88px desktop, 20-28px mobile`
- **Section Gap**: `28-40px`

### Breakpoints

mobile < 720px, tablet 720-1080px, desktop > 1080px.

### Density

Dense but breathable. Source, decision, and audit metadata are compact rows and chips; primary text retains generous line height and quiet margins.

### Grid

Desktop pairs a 220-280px trail ledger rail with a 680-780px main text column and an optional 320-420px compare/source drawer. Tablet compresses the ledger into a sticky top/side strip; mobile uses a collapsible Trail button plus inline knot summaries.

### Responsive

Preserve current-trail visibility at all sizes. Compare drawer becomes a bottom sheet on mobile; source bundle cards stack below the active passage.

### Whitespace

Use stone negative space to separate reasoning phases. Do not fill every intersection; absence is a pacing tool.

## Components

### Color Roles

- Teal identifies only the followed trail/current path; remove teal from inactive or merely related items.
- Plum identifies convergence knots as small dots/chips with adjacent text labels.
- Amber remains semantic warning/feedback and must not be used for categories or decisions.

### Component Rules

- Trail Ledger: sticky rail with active teal segment, quiet gray inactive segments, labeled knot chips, and backtrack actions.
- Knot Chip: small plum marker plus semibold name; opens a panel, never a full decorative card by itself.
- Compare Drawer: side drawer for two to four sources/versions using small multiples and evidence annotations.
- Source Bundle Card: saved context packet with source count, included decisions, provenance, and restore action.
- Audit Trail Footer: always visible at document end and reachable from knots; includes timestamps, source changes, decision owner, and unresolved warnings.
- Relationship Preview: inline, one-hop previews only; graph view is optional diagnostics.

### Content Rules

- Name every knot as a decision or convergence, e.g. “Eligibility rule conflict,” not “Knot 4.”
- Use concise trail step labels under 42 characters where possible.
- Expose provenance in the visible layout, with hover used only for supplemental detail.

## 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-019ee038-f637-7041-a40f-d470a08984a7/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 deep teal only for the currently followed trail, active rail segment, active source row, or current focus outline.
- Do Use plum as small knot dots, pills, or chips marking a named convergence; never use plum as large panel fill.
- Do Keep warning amber reserved for semantic feedback such as stale source, unresolved conflict, failed citation, or risky assumption.
- Do Place a compact trail ledger beside the main text with numbered steps, source initials, timestamps, and named knots.
- Do Make each knot open into a focused convergence panel with Decision, Sources, Assumptions, Alternatives, and Audit entries.
- Do Use source bundle cards to preserve saved contexts: title, source count, decision coverage, last touched time, and primary confidence/status.
- Do Offer lightweight relationship previews inline as short source-to-decision snippets or small multiples, not as a sprawling graph.
- Do Keep labels literal: Trail Ledger, Knot, Compare, Source Bundle, Audit Trail, Related Decisions, Backtrack.
- Don't Do not make the graph view the home screen; if present, label it Diagnostic Map and keep it secondary.
- Don't Do not use thread, loom, warp, or weft as primary navigation labels.
- Don't Do not make colored dots unlabeled or rely on hover to reveal their meaning.
- Don't Do not render breadcrumb chains as long slash-separated strings.
- Don't Do not let amber compete visually with plum knots; warnings should be smaller or text-led when near knots.
- Don't Do not use decorative Japanese patterns, faux calligraphy, or icon fonts as the main information carrier.

### Accessibility

Meet WCAG AA contrast for all labels and body text. Teal, plum, and amber must be paired with text labels, shape, or position. Keyboard users must be able to step through trail items, open a knot, compare sources, and reach the audit footer without hover-only interactions.

### Usage Context

Best for AI research workspaces, legal/product decision records, source-grounded writing systems, policy review, design rationale tools, and any dense text interface where users must backtrack, compare, and audit decisions without being forced into a graph.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "aya-knot-and-trail-decision-map",
  "type": "registry:theme",
  "title": "AYA Knot-and-Trail Decision Map 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-019ee038-f637-7041-a40f-d470a08984a7",
    "slug": "aya-knot-and-trail-decision-map",
    "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": {
      "color": [
        "border_quiet",
        "knot_plum",
        "surface_base",
        "surface_stone",
        "text_muted",
        "text_primary",
        "trail_active_teal",
        "trail_inactive",
        "warning_amber"
      ],
      "radius": [
        "card",
        "chip",
        "drawer"
      ],
      "spacing": [
        "knot_chip_gap",
        "rail_gap",
        "reader_margin",
        "section_gap"
      ],
      "stroke": [
        "active_trail",
        "focus",
        "knot_dot",
        "trail_line"
      ],
      "typography": [
        "body",
        "decision_name",
        "metadata",
        "micro_label",
        "ui_family"
      ]
    }
  }
}
```
in the wild

embodiments

Design Language Preview

AYA Knot-and-Trail Decision Map

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

Spacing

  • knot_chip_gap6px
  • rail_gap12px
  • reader_margin48-88px desktop, 20-28px mobile
  • section_gap28-40px
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 AyaKnotAndTrailDecisionMapShadcnKit() {
  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 Knot-and-Trail Decision Map</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-knot-and-trail-decision-map",
  "type": "registry:theme",
  "title": "AYA Knot-and-Trail Decision Map 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-019ee038-f637-7041-a40f-d470a08984a7",
    "slug": "aya-knot-and-trail-decision-map",
    "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": {
      "color": [
        "border_quiet",
        "knot_plum",
        "surface_base",
        "surface_stone",
        "text_muted",
        "text_primary",
        "trail_active_teal",
        "trail_inactive",
        "warning_amber"
      ],
      "radius": [
        "card",
        "chip",
        "drawer"
      ],
      "spacing": [
        "knot_chip_gap",
        "rail_gap",
        "reader_margin",
        "section_gap"
      ],
      "stroke": [
        "active_trail",
        "focus",
        "knot_dot",
        "trail_line"
      ],
      "typography": [
        "body",
        "decision_name",
        "metadata",
        "micro_label",
        "ui_family"
      ]
    }
  }
}
component recipescompatibility fallback
# AYA Knot-and-Trail Decision Map shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019ee038-f637-7041-a40f-d470a08984a7`
Slug: `en-019ee038-f637-7041-a40f-d470a08984a7`

## Intent

AYA Knot-and-Trail Decision Map represents complex source reasoning as a calm linear reading trail with named convergence knots. It borrows from katagami restraint, loom ordering, and Tufte-style evidence trails without turning the interface into a decorative graph or literal weaving metaphor.

## 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": "15-16px / 1.55, graphite, high contrast",
  "decision_name": "semibold 14-16px, plain-language noun phrases",
  "metadata": "12-13px / 1.35, muted graphite, never below accessible contrast",
  "micro_label": "11-12px uppercase or compact sentence case for rail labels only",
  "ui_family": "Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, sans-serif"
}

## Visual character to preserve

- Make the source language's structural identity visible in every component state.

## ShadSync visual profile

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

## Signature component recipes

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

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

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

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

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

## Preview shots

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

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/en-019ee038-f637-7041-a40f-d470a08984a7/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 deep teal only for the currently followed trail, active rail segment, active source row, or current focus outline.; Use plum as small knot dots, pills, or chips marking a named convergence; never use plum as large panel fill.; Keep warning amber reserved for semantic feedback such as stale source, unresolved conflict, failed citation, or risky assumption.; Place a compact trail ledger beside the main text with numbered steps, source initials, timestamps, and named knots.; Make each knot open into a focused convergence panel with Decision, Sources, Assumptions, Alternatives, and Audit entries.; Use source bundle cards to preserve saved contexts: title, source count, decision coverage, last touched time, and primary confidence/status.; Offer lightweight relationship previews inline as short source-to-decision snippets or small multiples, not as a sprawling graph.; Keep labels literal: Trail Ledger, Knot, Compare, Source Bundle, Audit Trail, Related Decisions, Backtrack.
- Do not: Do not make the graph view the home screen; if present, label it Diagnostic Map and keep it secondary.; Do not use thread, loom, warp, or weft as primary navigation labels.; Do not make colored dots unlabeled or rely on hover to reveal their meaning.; Do not render breadcrumb chains as long slash-separated strings.; Do not let amber compete visually with plum knots; warnings should be smaller or text-led when near knots.; Do not use decorative Japanese patterns, faux calligraphy, or icon fonts as the main information carrier.

## 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 AyaKnotAndTrailDecisionMapShadcnKit() {
  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 Knot-and-Trail Decision Map</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 < 720px, tablet 720-1080px, desktop > 1080px.",
  "density": "Dense but breathable. Source, decision, and audit metadata are compact rows and chips; primary text retains generous line height and quiet margins.",
  "grid": "Desktop pairs a 220-280px trail ledger rail with a 680-780px main text column and an optional 320-420px compare/source drawer. Tablet compresses the ledger into a sticky top/side strip; mobile uses a collapsible Trail button plus inline knot summaries.",
  "responsive": "Preserve current-trail visibility at all sizes. Compare drawer becomes a bottom sheet on mobile; source bundle cards stack below the active passage.",
  "whitespace": "Use stone negative space to separate reasoning phases. Do not fill every intersection; absence is a pacing tool."
}
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-019ee038-f637-7041-a40f-d470a08984a7",
    "name": "AYA Knot-and-Trail Decision Map",
    "slug": "en-019ee038-f637-7041-a40f-d470a08984a7"
  },
  "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": [],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": false,
    "stickerBadges": false,
    "motion": "still",
    "density": "balanced",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "AYA Knot-and-Trail Decision Map 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 deep teal only for the currently followed trail, active rail segment, active source row, or current focus outline.",
      "Use plum as small knot dots, pills, or chips marking a named convergence; never use plum as large panel fill.",
      "Keep warning amber reserved for semantic feedback such as stale source, unresolved conflict, failed citation, or risky assumption.",
      "Place a compact trail ledger beside the main text with numbered steps, source initials, timestamps, and named knots.",
      "Make each knot open into a focused convergence panel with Decision, Sources, Assumptions, Alternatives, and Audit entries.",
      "Use source bundle cards to preserve saved contexts: title, source count, decision coverage, last touched time, and primary confidence/status.",
      "Offer lightweight relationship previews inline as short source-to-decision snippets or small multiples, not as a sprawling graph.",
      "Keep labels literal: Trail Ledger, Knot, Compare, Source Bundle, Audit Trail, Related Decisions, Backtrack."
    ],
    "dont": [
      "Do not make the graph view the home screen; if present, label it Diagnostic Map and keep it secondary.",
      "Do not use thread, loom, warp, or weft as primary navigation labels.",
      "Do not make colored dots unlabeled or rely on hover to reveal their meaning.",
      "Do not render breadcrumb chains as long slash-separated strings.",
      "Do not let amber compete visually with plum knots; warnings should be smaller or text-led when near knots.",
      "Do not use decorative Japanese patterns, faux calligraphy, or icon fonts as the main information carrier."
    ]
  }
}