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

AYA Context Map Navigation

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 quiet knowledge-workspace navigation language that treats navigation as a context map rather than a dashboard. The interface is built from warm paper surfaces, sumi text, pale ash dividers, deliberate ma, and a single deep indigo path marker that shows where the user is, what surrounds the current document, and which sources, threads, tasks, and changes are related. It avoids widget grids and decorative analytics; instead it uses left and right rails, breadcrumbs, relationship trails, marginal signals, source clusters, and compact summaries to preserve orientation while keeping the document or primary work surface dominant.
values
orientation before instrumentation: show where the user is and what relates to the current work before showing metricsma as active structure: whitespace, pauses, and unboxed margins organize complexitydocument primacy: rails and summaries frame the work without competing with itsemantic restraint: indigo marks current path and focus, muted status dots mark state, persimmon appears only for warning or meaningful deltaprogressive disclosure: relationship depth is revealed in nested layers, not exposed as a permanent dashboardtext-first clarity with readable measures, generous line-height, and numeric details tuned for inline comprehension
anti-values
×colorful widget dashboards or KPI grids masquerading as navigation×boxed panels around every signal, badge, breadcrumb, or summary×dense graph visualizations that require interpretation before action×decorative Japanese motifs, fans, waves, red sun clichés, or ornamental patterning×low-contrast minimalism that hides affordances or status meaning×source lists that become side-channel inboxes instead of evidence context
tokens
borders4 items
accent width
2px
character
Pale ash hairlines and indigo path rails; dividers should feel like map notation, not containers.
default width
1px
style
solid
colors16 items
accent
#273A73
background
#FBFAF6
border
#DDD7CC
border_soft
#EAE5DA
error
#9B3F35
info
#4E6E88
muted
#6F6A63
primary
#273A73
secondary
#7A8F78
subtle
#9B958C
success
#6F8061
surface
#FFFFFF
surface_inset
#F8F6F0
surface_washi
#F5F1E8
text
#1E1B18
warning
#B86A3C
motion3 items
duration
150ms
easing
cubic-bezier(0.2, 0, 0, 1)
philosophy
Disclosure slides and fades are short and quiet; orientation markers settle rather than bounce.
radii5 items
full
9999px
lg
10px
md
6px
none
0
sm
3px
shadows3 items
lg
0 18px 48px rgba(30,27,24,0.08)
md
0 8px 24px rgba(30,27,24,0.06)
sm
0 1px 2px rgba(30,27,24,0.04)
spacing2 items
base
8px
scale
4, 8, 12, 16, 20, 24, 32, 40, 48, 64, 80, 96
surfaces3 items
bg pattern
None by default; optional barely visible vertical reference line in rails to reinforce the context-map metaphor.
card style
Use unboxed lists and rule-separated clusters first; only source previews or expanded summaries may receive a soft 10px white panel.
treatment
Warm paper-like shell, white document plane, washi side gutters, and ash dividers with almost no elevation.
typography8 items
base size
16px
body font
Inter
google fonts url
https://fonts.googleapis.com/css2?family=Inter:wght@400;450;500;600;700&family=IBM+Plex+Mono:wght@400;500;600&display=swap
heading font
Inter
letter spacing
-0.01em
line height
1.58
mono font
IBM Plex Mono
scale ratio
1.18
rules
composition
Compose screens as a context map around a primary document or workspace. The left rail shows project, collection, and document position; the center remains dominant; the right rail explains adjacent relationships: sources, linked threads, tasks, recent changes, and evidence clusters. Breadcrumbs connect these zones as a quiet sentence of orientation. Use lines, indentation, and spacing to imply relationships before adding panels.
density
Keep signals compact and marginal: small dots, ticks, count pairs, short timestamps, and one-line summaries. Expanded states may show nested context but should preserve empty pauses between layers. No rail should become a dashboard of widgets.
hierarchy
Build hierarchy with type weight, spacing, indentation, and ash dividers. Sumi text carries content; muted labels explain metadata; deep indigo is reserved for current path, keyboard focus, active breadcrumb, and selected relationship. Persimmon is rare and only marks warning, conflict, or significant delta.
signature patterns
Indigo current-path rail: a 2px vertical line in the left spine connects the active project, section, and document node.Quiet breadcrumb sentence: workspace / collection / document / current section with muted depth counts and an indigo active segment.Marginal signal stack: tiny status dots, source counts, task counts, and change ticks sit in the document margin without boxes.Source cluster fan: related evidence appears as a compact grouped list with ash connectors, provenance labels, and one-line relevance notes.Relationship trail: linked documents, threads, and tasks use indentation plus hairline connectors instead of graph nodes or colorful chips.Nested context disclosure: expanded items reveal summary, provenance, last change, and next action in a narrow inline layer, then collapse back to a single row.Orientation states: empty, loading, current, nearby, stale, conflicted, and focused states are all text-labeled and supported by restrained line or dot changes.
layout
breakpoints

mobile <= 640px, tablet 641px-1024px, desktop >= 1025px; very wide screens may add a second marginal column only for pinned evidence.

density
Low-to-medium density. Navigation rows are compact but separated by ma; context summaries are terse and text-led. Avoid dashboards, dense cards, or always-visible analytics panels.
grid
Desktop uses a three-zone context shell: 232-272px left spine, fluid central document/workspace with 680-860px readable measure, and 288-344px right context rail. Gutters use 24-40px breathing room and rails align to an 8px spacing rhythm.
responsive
On mobile, the left spine collapses into a breadcrumb/header trail and the right rail becomes a bottom context sheet with sources, threads, tasks, and changes in tabs. On tablet, keep the document primary and allow one rail open at a time.
whitespace
Whitespace is the primary grouping tool: leave pauses between project, document, source, thread, and change layers; keep margins active with compact signals instead of boxes.
guidance
do
  • Let the document or main workspace remain the visual anchor; rails should explain context, not compete with it.
  • Use whitespace and ash rules as the main organizational material.
  • Use deep indigo consistently for current path, selection, and focus states.
  • Show relationships through breadcrumbs, indentation, connectors, provenance labels, and compact summaries.
  • Keep right-rail modules text-led: sources, threads, tasks, changes, and nearby documents each need a reason to appear.
  • Use muted semantic dots sparingly and always pair them with labels or counts.
  • Prefer progressive disclosure to permanent panels when context depth increases.
avoid
  • Do not use colorful widget grids, large metric cards, rainbow category systems, or dashboard-like analytics chrome.
  • Do not box every signal; margins should feel active and spare.
  • Do not use decorative Japanese motifs or literal cultural ornament as a substitute for spatial discipline.
  • Do not turn relationship trails into busy network graphs.
  • Do not use persimmon for general emphasis or branding; reserve it for warning, conflict, or rare delta.
  • Do not make source clusters look like ads, cards, or notifications.
  • Do not hide orientation in hover-only interactions; current location and nearby context must be visible by default.
katagami spec
# AYA Context Map Navigation

## Philosophy

A quiet knowledge-workspace navigation language that treats navigation as a context map rather than a dashboard. The interface is built from warm paper surfaces, sumi text, pale ash dividers, deliberate ma, and a single deep indigo path marker that shows where the user is, what surrounds the current document, and which sources, threads, tasks, and changes are related. It avoids widget grids and decorative analytics; instead it uses left and right rails, breadcrumbs, relationship trails, marginal signals, source clusters, and compact summaries to preserve orientation while keeping the document or primary work surface dominant.

### Values

- orientation before instrumentation: show where the user is and what relates to the current work before showing metrics
- ma as active structure: whitespace, pauses, and unboxed margins organize complexity
- document primacy: rails and summaries frame the work without competing with it
- semantic restraint: indigo marks current path and focus, muted status dots mark state, persimmon appears only for warning or meaningful delta
- progressive disclosure: relationship depth is revealed in nested layers, not exposed as a permanent dashboard
- text-first clarity with readable measures, generous line-height, and numeric details tuned for inline comprehension

### Anti-Values

- colorful widget dashboards or KPI grids masquerading as navigation
- boxed panels around every signal, badge, breadcrumb, or summary
- dense graph visualizations that require interpretation before action
- decorative Japanese motifs, fans, waves, red sun clichés, or ornamental patterning
- low-contrast minimalism that hides affordances or status meaning
- source lists that become side-channel inboxes instead of evidence context

### Visual Character

- A warm white/washi workspace with slim pale ash rules and broad breathing room around the central document.
- The left rail behaves like a project/document spine with an indigo current-path line and subdued nested disclosure markers.
- The right rail is a context margin for sources, threads, tasks, and recent changes, using compact summaries rather than cards.
- Breadcrumbs read as quiet wayfinding sentences with separators, depth counts, and optional parent/peer trails.
- Relationship trails use hairline connectors, indentation, and small labeled knots rather than colorful nodes.
- Status appears as tiny muted semantic dots, ticks, or marginal glyphs paired with readable text labels.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Pale ash hairlines and indigo path rails; dividers should feel like map notation, not containers.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#273A73` |
| background | `#FBFAF6` |
| border | `#DDD7CC` |
| border_soft | `#EAE5DA` |
| error | `#9B3F35` |
| info | `#4E6E88` |
| muted | `#6F6A63` |
| primary | `#273A73` |
| secondary | `#7A8F78` |
| subtle | `#9B958C` |
| success | `#6F8061` |
| surface | `#FFFFFF` |
| surface_inset | `#F8F6F0` |
| surface_washi | `#F5F1E8` |
| text | `#1E1B18` |
| warning | `#B86A3C` |

### Motion

- **Duration**: 150ms
- **Easing**: cubic-bezier(0.2, 0, 0, 1)
- **Philosophy**: Disclosure slides and fades are short and quiet; orientation markers settle rather than bounce.

### Radii

- **Full**: 9999px
- **Lg**: 10px
- **Md**: 6px
- **None**: 0
- **Sm**: 3px

### Shadows

- **Lg**: 0 18px 48px rgba(30,27,24,0.08)
- **Md**: 0 8px 24px rgba(30,27,24,0.06)
- **Sm**: 0 1px 2px rgba(30,27,24,0.04)

### Spacing

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

### Surfaces

- **Bg Pattern**: None by default; optional barely visible vertical reference line in rails to reinforce the context-map metaphor.
- **Card Style**: Use unboxed lists and rule-separated clusters first; only source previews or expanded summaries may receive a soft 10px white panel.
- **Treatment**: Warm paper-like shell, white document plane, washi side gutters, and ash dividers with almost no elevation.

### Typography

- **Base Size**: 16px
- **Body Font**: Inter
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Inter:wght@400;450;500;600;700&family=IBM+Plex+Mono:wght@400;500;600&display=swap
- **Heading Font**: Inter
- **Letter Spacing**: -0.01em
- **Line Height**: 1.58
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.18

## Rules

### Composition

Compose screens as a context map around a primary document or workspace. The left rail shows project, collection, and document position; the center remains dominant; the right rail explains adjacent relationships: sources, linked threads, tasks, recent changes, and evidence clusters. Breadcrumbs connect these zones as a quiet sentence of orientation. Use lines, indentation, and spacing to imply relationships before adding panels.

### Density

Keep signals compact and marginal: small dots, ticks, count pairs, short timestamps, and one-line summaries. Expanded states may show nested context but should preserve empty pauses between layers. No rail should become a dashboard of widgets.

### Hierarchy

Build hierarchy with type weight, spacing, indentation, and ash dividers. Sumi text carries content; muted labels explain metadata; deep indigo is reserved for current path, keyboard focus, active breadcrumb, and selected relationship. Persimmon is rare and only marks warning, conflict, or significant delta.

### Signature Patterns

- Indigo current-path rail: a 2px vertical line in the left spine connects the active project, section, and document node.
- Quiet breadcrumb sentence: workspace / collection / document / current section with muted depth counts and an indigo active segment.
- Marginal signal stack: tiny status dots, source counts, task counts, and change ticks sit in the document margin without boxes.
- Source cluster fan: related evidence appears as a compact grouped list with ash connectors, provenance labels, and one-line relevance notes.
- Relationship trail: linked documents, threads, and tasks use indentation plus hairline connectors instead of graph nodes or colorful chips.
- Nested context disclosure: expanded items reveal summary, provenance, last change, and next action in a narrow inline layer, then collapse back to a single row.
- Orientation states: empty, loading, current, nearby, stale, conflicted, and focused states are all text-labeled and supported by restrained line or dot changes.

## Layout

### Breakpoints

mobile <= 640px, tablet 641px-1024px, desktop >= 1025px; very wide screens may add a second marginal column only for pinned evidence.

### Density

Low-to-medium density. Navigation rows are compact but separated by ma; context summaries are terse and text-led. Avoid dashboards, dense cards, or always-visible analytics panels.

### Grid

Desktop uses a three-zone context shell: 232-272px left spine, fluid central document/workspace with 680-860px readable measure, and 288-344px right context rail. Gutters use 24-40px breathing room and rails align to an 8px spacing rhythm.

### Responsive

On mobile, the left spine collapses into a breadcrumb/header trail and the right rail becomes a bottom context sheet with sources, threads, tasks, and changes in tabs. On tablet, keep the document primary and allow one rail open at a time.

### Whitespace

Whitespace is the primary grouping tool: leave pauses between project, document, source, thread, and change layers; keep margins active with compact signals instead of boxes.

## Guidance

### Do

- Let the document or main workspace remain the visual anchor; rails should explain context, not compete with it.
- Use whitespace and ash rules as the main organizational material.
- Use deep indigo consistently for current path, selection, and focus states.
- Show relationships through breadcrumbs, indentation, connectors, provenance labels, and compact summaries.
- Keep right-rail modules text-led: sources, threads, tasks, changes, and nearby documents each need a reason to appear.
- Use muted semantic dots sparingly and always pair them with labels or counts.
- Prefer progressive disclosure to permanent panels when context depth increases.

### Don't

- Do not use colorful widget grids, large metric cards, rainbow category systems, or dashboard-like analytics chrome.
- Do not box every signal; margins should feel active and spare.
- Do not use decorative Japanese motifs or literal cultural ornament as a substitute for spatial discipline.
- Do not turn relationship trails into busy network graphs.
- Do not use persimmon for general emphasis or branding; reserve it for warning, conflict, or rare delta.
- Do not make source clusters look like ads, cards, or notifications.
- Do not hide orientation in hover-only interactions; current location and nearby context must be visible by default.

### Accessibility

Maintain WCAG AA contrast for sumi text, muted labels, indigo focus, and semantic status. Pair every color dot with text, title, shape, or position. Ensure keyboard focus is a visible indigo outline or rail with sufficient offset. Keep hit targets at least 40px in dense rails and preserve readable 16px body text with generous line-height.

### Usage Context

Best for research workspaces, knowledge bases, document collaboration, legal or policy review, source-grounded AI tools, technical writing environments, and any product where users need to understand relationships among documents, evidence, threads, tasks, and changes without leaving the primary work surface.
DESIGN.md
---
version: "alpha"
name: "AYA Context Map Navigation"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#273A73"
  background: "#FBFAF6"
  border: "#DDD7CC"
  border_soft: "#EAE5DA"
  error: "#9B3F35"
  info: "#4E6E88"
  muted: "#6F6A63"
  primary: "#273A73"
  secondary: "#7A8F78"
  subtle: "#9B958C"
  success: "#6F8061"
  surface: "#FFFFFF"
  surface_inset: "#F8F6F0"
  surface_washi: "#F5F1E8"
  text: "#1E1B18"
  warning: "#B86A3C"
typography:
  headline-lg:
    fontFamily: "Inter"
    fontSize: "1.643rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.01em"
  headline-md:
    fontFamily: "Inter"
    fontSize: "1.392rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.01em"
  body-md:
    fontFamily: "Inter"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.58
    letterSpacing: "-0.01em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "10px"
  md: "6px"
  none: "0px"
  sm: "3px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "20px"
  2xl: "24px"
  3xl: "32px"
  4xl: "40px"
  step-8: "48px"
  step-9: "64px"
  step-10: "80px"
  step-11: "96px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-border_soft:
    backgroundColor: "{colors.border_soft}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-subtle:
    backgroundColor: "{colors.subtle}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-surface_inset:
    backgroundColor: "{colors.surface_inset}"
  color-reference-surface_washi:
    backgroundColor: "{colors.surface_washi}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#ffffff"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  card-surface:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  input-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    height: "44px"
---

# AYA Context Map Navigation

## Overview

A quiet knowledge-workspace navigation language that treats navigation as a context map rather than a dashboard. The interface is built from warm paper surfaces, sumi text, pale ash dividers, deliberate ma, and a single deep indigo path marker that shows where the user is, what surrounds the current document, and which sources, threads, tasks, and changes are related. It avoids widget grids and decorative analytics; instead it uses left and right rails, breadcrumbs, relationship trails, marginal signals, source clusters, and compact summaries to preserve orientation while keeping the document or primary work surface dominant.

### Values

- orientation before instrumentation: show where the user is and what relates to the current work before showing metrics
- ma as active structure: whitespace, pauses, and unboxed margins organize complexity
- document primacy: rails and summaries frame the work without competing with it
- semantic restraint: indigo marks current path and focus, muted status dots mark state, persimmon appears only for warning or meaningful delta
- progressive disclosure: relationship depth is revealed in nested layers, not exposed as a permanent dashboard
- text-first clarity with readable measures, generous line-height, and numeric details tuned for inline comprehension

### Anti-Values

- colorful widget dashboards or KPI grids masquerading as navigation
- boxed panels around every signal, badge, breadcrumb, or summary
- dense graph visualizations that require interpretation before action
- decorative Japanese motifs, fans, waves, red sun clichés, or ornamental patterning
- low-contrast minimalism that hides affordances or status meaning
- source lists that become side-channel inboxes instead of evidence context

### Visual Character

- A warm white/washi workspace with slim pale ash rules and broad breathing room around the central document.
- The left rail behaves like a project/document spine with an indigo current-path line and subdued nested disclosure markers.
- The right rail is a context margin for sources, threads, tasks, and recent changes, using compact summaries rather than cards.
- Breadcrumbs read as quiet wayfinding sentences with separators, depth counts, and optional parent/peer trails.
- Relationship trails use hairline connectors, indentation, and small labeled knots rather than colorful nodes.
- Status appears as tiny muted semantic dots, ticks, or marginal glyphs paired with readable text labels.

## Colors

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

| Token | Value |
|-------|-------|
| accent | `#273A73` |
| background | `#FBFAF6` |
| border | `#DDD7CC` |
| border_soft | `#EAE5DA` |
| error | `#9B3F35` |
| info | `#4E6E88` |
| muted | `#6F6A63` |
| primary | `#273A73` |
| secondary | `#7A8F78` |
| subtle | `#9B958C` |
| success | `#6F8061` |
| surface | `#FFFFFF` |
| surface_inset | `#F8F6F0` |
| surface_washi | `#F5F1E8` |
| text | `#1E1B18` |
| warning | `#B86A3C` |

## Typography

- **Headline-Lg**: Inter, 1.643rem, weight 700, line-height 1.1.
- **Headline-Md**: Inter, 1.392rem, weight 600, line-height 1.15.
- **Body-Md**: Inter, 16px, weight 400, line-height 1.58.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `20px`
- **2xl**: `24px`
- **3xl**: `32px`
- **4xl**: `40px`
- **Step-8**: `48px`
- **Step-9**: `64px`
- **Step-10**: `80px`
- **Step-11**: `96px`

### Breakpoints

mobile <= 640px, tablet 641px-1024px, desktop >= 1025px; very wide screens may add a second marginal column only for pinned evidence.

### Density

Low-to-medium density. Navigation rows are compact but separated by ma; context summaries are terse and text-led. Avoid dashboards, dense cards, or always-visible analytics panels.

### Grid

Desktop uses a three-zone context shell: 232-272px left spine, fluid central document/workspace with 680-860px readable measure, and 288-344px right context rail. Gutters use 24-40px breathing room and rails align to an 8px spacing rhythm.

### Responsive

On mobile, the left spine collapses into a breadcrumb/header trail and the right rail becomes a bottom context sheet with sources, threads, tasks, and changes in tabs. On tablet, keep the document primary and allow one rail open at a time.

### Whitespace

Whitespace is the primary grouping tool: leave pauses between project, document, source, thread, and change layers; keep margins active with compact signals instead of boxes.

## Elevation & Depth

### Shadows

- **Lg**: 0 18px 48px rgba(30,27,24,0.08)
- **Md**: 0 8px 24px rgba(30,27,24,0.06)
- **Sm**: 0 1px 2px rgba(30,27,24,0.04)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `10px`
- **Md**: `6px`
- **None**: `0px`
- **Sm**: `3px`

### Surfaces

- **Bg Pattern**: None by default; optional barely visible vertical reference line in rails to reinforce the context-map metaphor.
- **Card Style**: Use unboxed lists and rule-separated clusters first; only source previews or expanded summaries may receive a soft 10px white panel.
- **Treatment**: Warm paper-like shell, white document plane, washi side gutters, and ash dividers with almost no elevation.

### Borders

- **Accent Width**: 2px
- **Character**: Pale ash hairlines and indigo path rails; dividers should feel like map notation, not containers.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Compose screens as a context map around a primary document or workspace. The left rail shows project, collection, and document position; the center remains dominant; the right rail explains adjacent relationships: sources, linked threads, tasks, recent changes, and evidence clusters. Breadcrumbs connect these zones as a quiet sentence of orientation. Use lines, indentation, and spacing to imply relationships before adding panels.

### Density

Keep signals compact and marginal: small dots, ticks, count pairs, short timestamps, and one-line summaries. Expanded states may show nested context but should preserve empty pauses between layers. No rail should become a dashboard of widgets.

### Hierarchy

Build hierarchy with type weight, spacing, indentation, and ash dividers. Sumi text carries content; muted labels explain metadata; deep indigo is reserved for current path, keyboard focus, active breadcrumb, and selected relationship. Persimmon is rare and only marks warning, conflict, or significant delta.

### Signature Patterns

- Indigo current-path rail: a 2px vertical line in the left spine connects the active project, section, and document node.
- Quiet breadcrumb sentence: workspace / collection / document / current section with muted depth counts and an indigo active segment.
- Marginal signal stack: tiny status dots, source counts, task counts, and change ticks sit in the document margin without boxes.
- Source cluster fan: related evidence appears as a compact grouped list with ash connectors, provenance labels, and one-line relevance notes.
- Relationship trail: linked documents, threads, and tasks use indentation plus hairline connectors instead of graph nodes or colorful chips.
- Nested context disclosure: expanded items reveal summary, provenance, last change, and next action in a narrow inline layer, then collapse back to a single row.
- Orientation states: empty, loading, current, nearby, stale, conflicted, and focused states are all text-labeled and supported by restrained line or dot changes.

## 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/aya-context-map-navigation/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 Let the document or main workspace remain the visual anchor; rails should explain context, not compete with it.
- Do Use whitespace and ash rules as the main organizational material.
- Do Use deep indigo consistently for current path, selection, and focus states.
- Do Show relationships through breadcrumbs, indentation, connectors, provenance labels, and compact summaries.
- Do Keep right-rail modules text-led: sources, threads, tasks, changes, and nearby documents each need a reason to appear.
- Do Use muted semantic dots sparingly and always pair them with labels or counts.
- Do Prefer progressive disclosure to permanent panels when context depth increases.
- Don't Do not use colorful widget grids, large metric cards, rainbow category systems, or dashboard-like analytics chrome.
- Don't Do not box every signal; margins should feel active and spare.
- Don't Do not use decorative Japanese motifs or literal cultural ornament as a substitute for spatial discipline.
- Don't Do not turn relationship trails into busy network graphs.
- Don't Do not use persimmon for general emphasis or branding; reserve it for warning, conflict, or rare delta.
- Don't Do not make source clusters look like ads, cards, or notifications.
- Don't Do not hide orientation in hover-only interactions; current location and nearby context must be visible by default.

### Accessibility

Maintain WCAG AA contrast for sumi text, muted labels, indigo focus, and semantic status. Pair every color dot with text, title, shape, or position. Ensure keyboard focus is a visible indigo outline or rail with sufficient offset. Keep hit targets at least 40px in dense rails and preserve readable 16px body text with generous line-height.

### Usage Context

Best for research workspaces, knowledge bases, document collaboration, legal or policy review, source-grounded AI tools, technical writing environments, and any product where users need to understand relationships among documents, evidence, threads, tasks, and changes without leaving the primary work surface.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "aya-context-map-navigation",
  "type": "registry:theme",
  "title": "AYA Context Map Navigation shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FBFAF6",
      "foreground": "#1E1B18",
      "card": "#FFFFFF",
      "card-foreground": "#1E1B18",
      "popover": "#FFFFFF",
      "popover-foreground": "#1E1B18",
      "primary": "#273A73",
      "primary-foreground": "#ffffff",
      "secondary": "#7A8F78",
      "secondary-foreground": "#ffffff",
      "muted": "#6F6A63",
      "muted-foreground": "#1E1B18",
      "accent": "#273A73",
      "accent-foreground": "#ffffff",
      "destructive": "#9B3F35",
      "border": "#DDD7CC",
      "input": "#DDD7CC",
      "ring": "#273A73",
      "chart-1": "#273A73",
      "chart-2": "#7A8F78",
      "chart-3": "#273A73",
      "chart-4": "#6F8061",
      "chart-5": "#B86A3C",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#1E1B18",
      "sidebar-primary": "#273A73",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#4E6E88",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#DDD7CC",
      "sidebar-ring": "#273A73",
      "radius": "6px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#273A73",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#273A73",
      "accent-foreground": "#ffffff",
      "destructive": "#9B3F35",
      "border": "#303642",
      "input": "#303642",
      "ring": "#273A73",
      "chart-1": "#273A73",
      "chart-2": "#7A8F78",
      "chart-3": "#273A73",
      "chart-4": "#6F8061",
      "chart-5": "#B86A3C",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#273A73",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#273A73",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#273A73",
      "radius": "6px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "aya-context-map-navigation",
    "slug": "aya-context-map-navigation",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "border_soft",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "subtle",
        "success",
        "surface",
        "surface_inset",
        "surface_washi",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

Design Language Preview

AYA Context Map Navigation

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

Palette

Typography

headline-lgInter · 26px · 700

The quick brown fox jumps

headline-mdInter · 22px · 600

The quick brown fox jumps

body-mdInter · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

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

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl20px
  • 2xl24px
  • 3xl32px
  • 4xl40px
  • step-848px
  • step-964px
  • step-1080px
  • step-1196px

Shape

full9999px
lg10px
md6px
none0px
sm3px
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.
primarysurfacemutedwarningerror
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: #FBFAF6;
  --foreground: #1E1B18;
  --card: #FFFFFF;
  --card-foreground: #1E1B18;
  --popover: #FFFFFF;
  --popover-foreground: #1E1B18;
  --primary: #273A73;
  --primary-foreground: #ffffff;
  --secondary: #7A8F78;
  --secondary-foreground: #ffffff;
  --muted: #6F6A63;
  --muted-foreground: #1E1B18;
  --accent: #273A73;
  --accent-foreground: #ffffff;
  --destructive: #9B3F35;
  --border: #DDD7CC;
  --input: #DDD7CC;
  --ring: #273A73;
  --chart-1: #273A73;
  --chart-2: #7A8F78;
  --chart-3: #273A73;
  --chart-4: #6F8061;
  --chart-5: #B86A3C;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #1E1B18;
  --sidebar-primary: #273A73;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #4E6E88;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #DDD7CC;
  --sidebar-ring: #273A73;
  --radius: 6px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #273A73;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #273A73;
  --accent-foreground: #ffffff;
  --destructive: #9B3F35;
  --border: #303642;
  --input: #303642;
  --ring: #273A73;
  --chart-1: #273A73;
  --chart-2: #7A8F78;
  --chart-3: #273A73;
  --chart-4: #6F8061;
  --chart-5: #B86A3C;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #273A73;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #273A73;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #273A73;
  --radius: 6px;
}
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 AyaContextMapNavigationShadcnKit() {
  return (
    <section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
      <div className="flex items-start justify-between gap-4">
        <div>
          <Badge variant="outline">shadcn/ui</Badge>
          <h2 className="mt-3 text-2xl font-semibold tracking-tight">AYA Context Map Navigation</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

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

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
theme JSONcompatibility fallback
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "aya-context-map-navigation",
  "type": "registry:theme",
  "title": "AYA Context Map Navigation shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FBFAF6",
      "foreground": "#1E1B18",
      "card": "#FFFFFF",
      "card-foreground": "#1E1B18",
      "popover": "#FFFFFF",
      "popover-foreground": "#1E1B18",
      "primary": "#273A73",
      "primary-foreground": "#ffffff",
      "secondary": "#7A8F78",
      "secondary-foreground": "#ffffff",
      "muted": "#6F6A63",
      "muted-foreground": "#1E1B18",
      "accent": "#273A73",
      "accent-foreground": "#ffffff",
      "destructive": "#9B3F35",
      "border": "#DDD7CC",
      "input": "#DDD7CC",
      "ring": "#273A73",
      "chart-1": "#273A73",
      "chart-2": "#7A8F78",
      "chart-3": "#273A73",
      "chart-4": "#6F8061",
      "chart-5": "#B86A3C",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#1E1B18",
      "sidebar-primary": "#273A73",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#4E6E88",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#DDD7CC",
      "sidebar-ring": "#273A73",
      "radius": "6px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#273A73",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#273A73",
      "accent-foreground": "#ffffff",
      "destructive": "#9B3F35",
      "border": "#303642",
      "input": "#303642",
      "ring": "#273A73",
      "chart-1": "#273A73",
      "chart-2": "#7A8F78",
      "chart-3": "#273A73",
      "chart-4": "#6F8061",
      "chart-5": "#B86A3C",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#273A73",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#273A73",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#273A73",
      "radius": "6px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "aya-context-map-navigation",
    "slug": "aya-context-map-navigation",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "border_soft",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "subtle",
        "success",
        "surface",
        "surface_inset",
        "surface_washi",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
component recipescompatibility fallback
# AYA Context Map Navigation shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `aya-context-map-navigation`
Slug: `aya-context-map-navigation`

## Intent

A quiet knowledge-workspace navigation language that treats navigation as a context map rather than a dashboard. The interface is built from warm paper surfaces, sumi text, pale ash dividers, deliberate ma, and a single deep indigo path marker that shows where the user is, what surrounds the current document, and which sources, threads, tasks, and changes are related. It avoids widget grids and decorative analytics; instead it uses left and right rails, breadcrumbs, relationship trails, marginal signals, source clusters, and compact summaries to preserve orientation while keeping the document or primary work surface dominant.

## Required primitives

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

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

## Token cues

Colors:

{
  "accent": "#273A73",
  "background": "#FBFAF6",
  "border": "#DDD7CC",
  "border_soft": "#EAE5DA",
  "error": "#9B3F35",
  "info": "#4E6E88",
  "muted": "#6F6A63",
  "primary": "#273A73",
  "secondary": "#7A8F78",
  "subtle": "#9B958C",
  "success": "#6F8061",
  "surface": "#FFFFFF",
  "surface_inset": "#F8F6F0",
  "surface_washi": "#F5F1E8",
  "text": "#1E1B18",
  "warning": "#B86A3C"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Inter",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Inter:wght@400;450;500;600;700&family=IBM+Plex+Mono:wght@400;500;600&display=swap",
  "heading_font": "Inter",
  "letter_spacing": "-0.01em",
  "line_height": 1.58,
  "mono_font": "IBM Plex Mono",
  "scale_ratio": 1.18
}

## Visual character to preserve

- A warm white/washi workspace with slim pale ash rules and broad breathing room around the central document.
- The left rail behaves like a project/document spine with an indigo current-path line and subdued nested disclosure markers.
- The right rail is a context margin for sources, threads, tasks, and recent changes, using compact summaries rather than cards.
- Breadcrumbs read as quiet wayfinding sentences with separators, depth counts, and optional parent/peer trails.
- Relationship trails use hairline connectors, indentation, and small labeled knots rather than colorful nodes.
- Status appears as tiny muted semantic dots, ticks, or marginal glyphs paired with readable text labels.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": true,
  "stickerBadges": false,
  "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/aya-context-map-navigation/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: Let the document or main workspace remain the visual anchor; rails should explain context, not compete with it.; Use whitespace and ash rules as the main organizational material.; Use deep indigo consistently for current path, selection, and focus states.; Show relationships through breadcrumbs, indentation, connectors, provenance labels, and compact summaries.; Keep right-rail modules text-led: sources, threads, tasks, changes, and nearby documents each need a reason to appear.; Use muted semantic dots sparingly and always pair them with labels or counts.; Prefer progressive disclosure to permanent panels when context depth increases.
- Do not: Do not use colorful widget grids, large metric cards, rainbow category systems, or dashboard-like analytics chrome.; Do not box every signal; margins should feel active and spare.; Do not use decorative Japanese motifs or literal cultural ornament as a substitute for spatial discipline.; Do not turn relationship trails into busy network graphs.; Do not use persimmon for general emphasis or branding; reserve it for warning, conflict, or rare delta.; Do not make source clusters look like ads, cards, or notifications.; Do not hide orientation in hover-only interactions; current location and nearby context must be visible by default.

## 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 AyaContextMapNavigationShadcnKit() {
  return (
    <section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
      <div className="flex items-start justify-between gap-4">
        <div>
          <Badge variant="outline">shadcn/ui</Badge>
          <h2 className="mt-3 text-2xl font-semibold tracking-tight">AYA Context Map Navigation</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 <= 640px, tablet 641px-1024px, desktop >= 1025px; very wide screens may add a second marginal column only for pinned evidence.",
  "density": "Low-to-medium density. Navigation rows are compact but separated by ma; context summaries are terse and text-led. Avoid dashboards, dense cards, or always-visible analytics panels.",
  "grid": "Desktop uses a three-zone context shell: 232-272px left spine, fluid central document/workspace with 680-860px readable measure, and 288-344px right context rail. Gutters use 24-40px breathing room and rails align to an 8px spacing rhythm.",
  "responsive": "On mobile, the left spine collapses into a breadcrumb/header trail and the right rail becomes a bottom context sheet with sources, threads, tasks, and changes in tabs. On tablet, keep the document primary and allow one rail open at a time.",
  "whitespace": "Whitespace is the primary grouping tool: leave pauses between project, document, source, thread, and change layers; keep margins active with compact signals instead of boxes."
}
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": "aya-context-map-navigation",
    "name": "AYA Context Map Navigation",
    "slug": "aya-context-map-navigation"
  },
  "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 warm white/washi workspace with slim pale ash rules and broad breathing room around the central document.",
    "The left rail behaves like a project/document spine with an indigo current-path line and subdued nested disclosure markers.",
    "The right rail is a context margin for sources, threads, tasks, and recent changes, using compact summaries rather than cards.",
    "Breadcrumbs read as quiet wayfinding sentences with separators, depth counts, and optional parent/peer trails.",
    "Relationship trails use hairline connectors, indentation, and small labeled knots rather than colorful nodes.",
    "Status appears as tiny muted semantic dots, ticks, or marginal glyphs paired with readable text labels."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": false,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "AYA Context Map Navigation 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": [
      "Let the document or main workspace remain the visual anchor; rails should explain context, not compete with it.",
      "Use whitespace and ash rules as the main organizational material.",
      "Use deep indigo consistently for current path, selection, and focus states.",
      "Show relationships through breadcrumbs, indentation, connectors, provenance labels, and compact summaries.",
      "Keep right-rail modules text-led: sources, threads, tasks, changes, and nearby documents each need a reason to appear.",
      "Use muted semantic dots sparingly and always pair them with labels or counts.",
      "Prefer progressive disclosure to permanent panels when context depth increases."
    ],
    "dont": [
      "Do not use colorful widget grids, large metric cards, rainbow category systems, or dashboard-like analytics chrome.",
      "Do not box every signal; margins should feel active and spare.",
      "Do not use decorative Japanese motifs or literal cultural ornament as a substitute for spatial discipline.",
      "Do not turn relationship trails into busy network graphs.",
      "Do not use persimmon for general emphasis or branding; reserve it for warning, conflict, or rare delta.",
      "Do not make source clusters look like ads, cards, or notifications.",
      "Do not hide orientation in hover-only interactions; current location and nearby context must be visible by default."
    ]
  }
}