back to gallery
design language·layered-shoji-navigation

Layered Shoji 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
Layered Shoji Navigation is a calm, text-first product language for AYA Katagami: a workspace that reveals many documents, signals, and relationships as translucent planes rather than as a noisy analytics dashboard. Japanese craft references are translated into interface behavior—washi restraint, katagami-like precision, woven context, indigo current markers, and generous negative space—without literal patterns, icons, or tourist motifs.
values
Context before decoration: every surface exists to clarify provenance, relationships, and next action.Layered calm: off-white planes, blue-gray depth, and hairline separations create readable spatial hierarchy without heavy shadows or gradients.Text-first precision: titles, excerpts, metrics, timestamps, and marginal signals remain the primary visual material.Progressive disclosure as craft: relationships are revealed by sliding, expanding, and aligning nearby layers rather than by opening modal dashboards.Quiet navigation memory: the current location is marked with indigo tabs, threads, and map nodes that persist across document views.Sparse notification warmth: amber and persimmon appear only as tiny dots, counts, or risk markers—not as broad fills.
anti-values
×Literal Japanese motifs, brush textures, lanterns, fans, waves, red sun marks, cherry blossoms, or faux-calligraphy.×Dark dashboards, saturated charts, neon gradients, glassmorphism glare, or marketing-style hero effects.×Equal KPI-card grids that make the product feel like a generic dashboard instead of a document workspace.×Low-contrast gray-on-white text, excessive blur, or translucency that harms readability.×Color-only status communication or notification dots without labels, counts, or accessible text.
tokens
borders4 items
accent width
3px
character
Quiet blue-gray and warm-gray hairlines; indigo appears as thin current-location rails, node rings, and connector strokes.
default width
1px
style
solid
colors17 items
accent
#394A8A
accent_soft
#E6E9F4
background
#F7F5EF
border
#D9DDD9
border_subtle
#E8E6DE
error
#B85B45
info
#617487
muted
#858A90
notification
#D66B3D
primary
#242629
secondary
#5E6369
success
#5F7C63
surface
#FFFEFA
surface_alt
#F1F0EA
surface_depth
#E7EBEE
text
#242629
warning
#B98232
motion3 items
duration
160ms-240ms
easing
cubic-bezier(.2,.7,.2,1)
philosophy
Reveal relationships through small layer translations, connector fades, and height expansions; avoid bounce, parallax spectacle, or continuous animation.
radii5 items
full
9999px
lg
18px
md
12px
none
0
sm
8px
shadows3 items
lg
0 18px 54px rgba(42,50,58,0.08)
md
0 8px 24px rgba(42,50,58,0.06)
sm
0 1px 0 rgba(34,38,42,0.04)
spacing2 items
base
4px
scale
4, 8, 12, 16, 20, 24, 32, 40, 48, 64, 80
surfaces3 items
bg pattern
None by default; structure comes from spacing, ruled separators, and nested layers rather than decorative patterns.
card style
Compact document planes with warm-white fill, 1px hairline border, 12-18px radius, and a slightly cooler underlayer offset for depth.
treatment
Matte off-white layers with subtle tonal shifts; no visible texture unless it is below 3% opacity and never interferes with text.
typography9 items
base size
15px
body font
Inter
display letter spacing
-0.025em
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@450;500;600&family=Inter:wght@400;450;520;600;700&display=swap
heading font
Inter
letter spacing
-0.011em
line height
1.55
mono font
IBM Plex Mono
scale ratio
1.18
rules
composition
Compose screens as layered document workspaces, not dashboard grids: context map, active reading plane, adjacent relationship plane, and marginal signal strip. Let one document or cluster anchor the screen while supporting signals stay compact and secondary.
density
Pack metadata tightly inside cards but separate different cognitive layers with whitespace and plane changes. Prefer inline metrics, source badges, and short excerpts over large charts.
hierarchy
Hierarchy begins with text weight, alignment, and proximity. Use indigo only for current location, selected relationship, focus, and active connector lines. Use amber/persimmon only for rare unread, risk, or notification dots with labels.
signature patterns
Context-map rail: small labeled nodes grouped by document cluster, with the active node shown by an indigo ring and a 3px vertical thread.Shoji layer stack: active document cards sit on a warm-white plane with a cooler blue-gray underplane offset by 8px, creating depth without gradient or glass effects.Marginal signals: counts, freshness, confidence, and alerts appear in the right margin as tiny chips or dots aligned to the related excerpt line.Progressive disclosure seams: collapsed rows show a thin rule and summary; expansion slides the related layer down while preserving surrounding context.Relationship reveal: hovering or selecting a reference fades in one connector line and lightly tints the linked document card, never drawing a dense graph web.
layout
breakpoints
Below 900px, context map becomes a horizontal breadcrumb/thread strip above the document list; below 640px, relationship details collapse into inline disclosure rows.
density

Medium-high information density with compact cards, 12-16px row gaps, 8px metadata clusters, and generous 40-64px breathing room around major mode changes.

grid
Desktop uses a 72px global rail, a 260-320px context-map column, and a flexible document canvas with 12-column internal rhythm. Relationship panels may overlap the canvas edge by 12-24px to imply layered context.
responsive

Maintain readable excerpts and current-location markers on small screens; hide secondary metrics before hiding document titles or source provenance.

whitespace

Negative space is active: use blank margins to separate levels of context and keep reading lanes clear. Do not fill every column with widgets.

guidance
do
  • Start every screen with a readable document or context object, then layer signals around it.
  • Use off-white tonal steps and hairlines before using shadow; keep depth subtle and functional.
  • Mark current location persistently with indigo threads, tabs, node rings, or left borders.
  • Keep analytics document-adjacent: inline counts, confidence chips, source freshness, and marginal annotations.
  • Use progressive disclosure to reveal why items relate, preserving the user’s place in the map.
  • Translate Japanese craft into restraint, rhythm, layering, and precision—not imagery.
avoid
  • Do not use literal Japanese patterns, brush strokes, red circles, paper grain overlays, or ornamental icons.
  • Do not create a generic dashboard of equal metric cards or colorful chart panels.
  • Do not use gradients beyond quiet tonal layering between neutral surfaces.
  • Do not let translucency, blur, or low-contrast gray reduce legibility.
  • Do not show dense relationship graphs by default; reveal one relationship path at a time.
katagami spec
# Layered Shoji Navigation

## Philosophy

Layered Shoji Navigation is a calm, text-first product language for AYA Katagami: a workspace that reveals many documents, signals, and relationships as translucent planes rather than as a noisy analytics dashboard. Japanese craft references are translated into interface behavior—washi restraint, katagami-like precision, woven context, indigo current markers, and generous negative space—without literal patterns, icons, or tourist motifs.

### Values

- Context before decoration: every surface exists to clarify provenance, relationships, and next action.
- Layered calm: off-white planes, blue-gray depth, and hairline separations create readable spatial hierarchy without heavy shadows or gradients.
- Text-first precision: titles, excerpts, metrics, timestamps, and marginal signals remain the primary visual material.
- Progressive disclosure as craft: relationships are revealed by sliding, expanding, and aligning nearby layers rather than by opening modal dashboards.
- Quiet navigation memory: the current location is marked with indigo tabs, threads, and map nodes that persist across document views.
- Sparse notification warmth: amber and persimmon appear only as tiny dots, counts, or risk markers—not as broad fills.

### Anti-Values

- Literal Japanese motifs, brush textures, lanterns, fans, waves, red sun marks, cherry blossoms, or faux-calligraphy.
- Dark dashboards, saturated charts, neon gradients, glassmorphism glare, or marketing-style hero effects.
- Equal KPI-card grids that make the product feel like a generic dashboard instead of a document workspace.
- Low-contrast gray-on-white text, excessive blur, or translucency that harms readability.
- Color-only status communication or notification dots without labels, counts, or accessible text.

### Visual Character

- A near-white workspace made of translucent-feeling panels: porcelain, washi, mist, and rice-paper surfaces separated by blue-gray depth lines.
- Navigation behaves like a context map: a left rail or top strip shows document clusters, current path, sibling signals, and relationship nodes with minimal indigo marks.
- Document cards are compact, rectangular, and excerpt-led, with inline metrics in mono numerals and marginal annotations rather than chart-heavy modules.
- Surfaces overlap by 8-24px or sit on nested planes, suggesting shoji screens and stacked paper without literal grids, bamboo, waves, or Japanese ornament.
- Motion is calm and relational: layers slide a few pixels, reveal connectors, or crossfade labels to show why one document or signal belongs to another.

## Tokens

### Borders

- **Accent Width**: 3px
- **Character**: Quiet blue-gray and warm-gray hairlines; indigo appears as thin current-location rails, node rings, and connector strokes.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#394A8A` |
| accent_soft | `#E6E9F4` |
| background | `#F7F5EF` |
| border | `#D9DDD9` |
| border_subtle | `#E8E6DE` |
| error | `#B85B45` |
| info | `#617487` |
| muted | `#858A90` |
| notification | `#D66B3D` |
| primary | `#242629` |
| secondary | `#5E6369` |
| success | `#5F7C63` |
| surface | `#FFFEFA` |
| surface_alt | `#F1F0EA` |
| surface_depth | `#E7EBEE` |
| text | `#242629` |
| warning | `#B98232` |

### Motion

- **Duration**: 160ms-240ms
- **Easing**: cubic-bezier(.2,.7,.2,1)
- **Philosophy**: Reveal relationships through small layer translations, connector fades, and height expansions; avoid bounce, parallax spectacle, or continuous animation.

### Radii

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

### Shadows

- **Lg**: 0 18px 54px rgba(42,50,58,0.08)
- **Md**: 0 8px 24px rgba(42,50,58,0.06)
- **Sm**: 0 1px 0 rgba(34,38,42,0.04)

### Spacing

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

### Surfaces

- **Bg Pattern**: None by default; structure comes from spacing, ruled separators, and nested layers rather than decorative patterns.
- **Card Style**: Compact document planes with warm-white fill, 1px hairline border, 12-18px radius, and a slightly cooler underlayer offset for depth.
- **Treatment**: Matte off-white layers with subtle tonal shifts; no visible texture unless it is below 3% opacity and never interferes with text.

### Typography

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

## Rules

### Composition

Compose screens as layered document workspaces, not dashboard grids: context map, active reading plane, adjacent relationship plane, and marginal signal strip. Let one document or cluster anchor the screen while supporting signals stay compact and secondary.

### Density

Pack metadata tightly inside cards but separate different cognitive layers with whitespace and plane changes. Prefer inline metrics, source badges, and short excerpts over large charts.

### Hierarchy

Hierarchy begins with text weight, alignment, and proximity. Use indigo only for current location, selected relationship, focus, and active connector lines. Use amber/persimmon only for rare unread, risk, or notification dots with labels.

### Signature Patterns

- Context-map rail: small labeled nodes grouped by document cluster, with the active node shown by an indigo ring and a 3px vertical thread.
- Shoji layer stack: active document cards sit on a warm-white plane with a cooler blue-gray underplane offset by 8px, creating depth without gradient or glass effects.
- Marginal signals: counts, freshness, confidence, and alerts appear in the right margin as tiny chips or dots aligned to the related excerpt line.
- Progressive disclosure seams: collapsed rows show a thin rule and summary; expansion slides the related layer down while preserving surrounding context.
- Relationship reveal: hovering or selecting a reference fades in one connector line and lightly tints the linked document card, never drawing a dense graph web.

## Layout

### Breakpoints

Below 900px, context map becomes a horizontal breadcrumb/thread strip above the document list; below 640px, relationship details collapse into inline disclosure rows.

### Density

Medium-high information density with compact cards, 12-16px row gaps, 8px metadata clusters, and generous 40-64px breathing room around major mode changes.

### Grid

Desktop uses a 72px global rail, a 260-320px context-map column, and a flexible document canvas with 12-column internal rhythm. Relationship panels may overlap the canvas edge by 12-24px to imply layered context.

### Responsive

Maintain readable excerpts and current-location markers on small screens; hide secondary metrics before hiding document titles or source provenance.

### Whitespace

Negative space is active: use blank margins to separate levels of context and keep reading lanes clear. Do not fill every column with widgets.

## Guidance

### Do

- Start every screen with a readable document or context object, then layer signals around it.
- Use off-white tonal steps and hairlines before using shadow; keep depth subtle and functional.
- Mark current location persistently with indigo threads, tabs, node rings, or left borders.
- Keep analytics document-adjacent: inline counts, confidence chips, source freshness, and marginal annotations.
- Use progressive disclosure to reveal why items relate, preserving the user’s place in the map.
- Translate Japanese craft into restraint, rhythm, layering, and precision—not imagery.

### Don't

- Do not use literal Japanese patterns, brush strokes, red circles, paper grain overlays, or ornamental icons.
- Do not create a generic dashboard of equal metric cards or colorful chart panels.
- Do not use gradients beyond quiet tonal layering between neutral surfaces.
- Do not let translucency, blur, or low-contrast gray reduce legibility.
- Do not show dense relationship graphs by default; reveal one relationship path at a time.

### Accessibility

Body text must meet WCAG AA on all off-white planes; focus uses a visible 2px indigo outline plus offset. Notification dots require text/count labels. Motion must respect reduced-motion by replacing slides with instant expansion and opacity changes.

### Usage Context

Best for AYA-style research, document intelligence, knowledge work, legal/strategy review, context synthesis, and signal-heavy workspaces where users need calm comprehension across many sources.
DESIGN.md
---
version: "alpha"
name: "Layered Shoji Navigation"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#394A8A"
  accent_soft: "#E6E9F4"
  background: "#F7F5EF"
  border: "#D9DDD9"
  border_subtle: "#E8E6DE"
  error: "#B85B45"
  info: "#617487"
  muted: "#858A90"
  notification: "#D66B3D"
  primary: "#242629"
  secondary: "#5E6369"
  success: "#5F7C63"
  surface: "#FFFEFA"
  surface_alt: "#F1F0EA"
  surface_depth: "#E7EBEE"
  text: "#242629"
  warning: "#B98232"
typography:
  headline-lg:
    fontFamily: "Inter"
    fontSize: "1.54rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.011em"
  headline-md:
    fontFamily: "Inter"
    fontSize: "1.305rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.011em"
  body-md:
    fontFamily: "Inter"
    fontSize: "15px"
    fontWeight: 400
    lineHeight: 1.55
    letterSpacing: "-0.011em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "18px"
  md: "12px"
  none: "0px"
  sm: "8px"
spacing:
  base: "4px"
  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"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-accent_soft:
    backgroundColor: "{colors.accent_soft}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-border_subtle:
    backgroundColor: "{colors.border_subtle}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-notification:
    backgroundColor: "{colors.notification}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-surface_alt:
    backgroundColor: "{colors.surface_alt}"
  color-reference-surface_depth:
    backgroundColor: "{colors.surface_depth}"
  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"
---

# Layered Shoji Navigation

## Overview

Layered Shoji Navigation is a calm, text-first product language for AYA Katagami: a workspace that reveals many documents, signals, and relationships as translucent planes rather than as a noisy analytics dashboard. Japanese craft references are translated into interface behavior—washi restraint, katagami-like precision, woven context, indigo current markers, and generous negative space—without literal patterns, icons, or tourist motifs.

### Values

- Context before decoration: every surface exists to clarify provenance, relationships, and next action.
- Layered calm: off-white planes, blue-gray depth, and hairline separations create readable spatial hierarchy without heavy shadows or gradients.
- Text-first precision: titles, excerpts, metrics, timestamps, and marginal signals remain the primary visual material.
- Progressive disclosure as craft: relationships are revealed by sliding, expanding, and aligning nearby layers rather than by opening modal dashboards.
- Quiet navigation memory: the current location is marked with indigo tabs, threads, and map nodes that persist across document views.
- Sparse notification warmth: amber and persimmon appear only as tiny dots, counts, or risk markers—not as broad fills.

### Anti-Values

- Literal Japanese motifs, brush textures, lanterns, fans, waves, red sun marks, cherry blossoms, or faux-calligraphy.
- Dark dashboards, saturated charts, neon gradients, glassmorphism glare, or marketing-style hero effects.
- Equal KPI-card grids that make the product feel like a generic dashboard instead of a document workspace.
- Low-contrast gray-on-white text, excessive blur, or translucency that harms readability.
- Color-only status communication or notification dots without labels, counts, or accessible text.

### Visual Character

- A near-white workspace made of translucent-feeling panels: porcelain, washi, mist, and rice-paper surfaces separated by blue-gray depth lines.
- Navigation behaves like a context map: a left rail or top strip shows document clusters, current path, sibling signals, and relationship nodes with minimal indigo marks.
- Document cards are compact, rectangular, and excerpt-led, with inline metrics in mono numerals and marginal annotations rather than chart-heavy modules.
- Surfaces overlap by 8-24px or sit on nested planes, suggesting shoji screens and stacked paper without literal grids, bamboo, waves, or Japanese ornament.
- Motion is calm and relational: layers slide a few pixels, reveal connectors, or crossfade labels to show why one document or signal belongs to another.

## 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 | `#394A8A` |
| accent_soft | `#E6E9F4` |
| background | `#F7F5EF` |
| border | `#D9DDD9` |
| border_subtle | `#E8E6DE` |
| error | `#B85B45` |
| info | `#617487` |
| muted | `#858A90` |
| notification | `#D66B3D` |
| primary | `#242629` |
| secondary | `#5E6369` |
| success | `#5F7C63` |
| surface | `#FFFEFA` |
| surface_alt | `#F1F0EA` |
| surface_depth | `#E7EBEE` |
| text | `#242629` |
| warning | `#B98232` |

## Typography

- **Headline-Lg**: Inter, 1.54rem, weight 700, line-height 1.1.
- **Headline-Md**: Inter, 1.305rem, weight 600, line-height 1.15.
- **Body-Md**: Inter, 15px, weight 400, line-height 1.55.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **Base**: `4px`
- **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`

### Breakpoints

Below 900px, context map becomes a horizontal breadcrumb/thread strip above the document list; below 640px, relationship details collapse into inline disclosure rows.

### Density

Medium-high information density with compact cards, 12-16px row gaps, 8px metadata clusters, and generous 40-64px breathing room around major mode changes.

### Grid

Desktop uses a 72px global rail, a 260-320px context-map column, and a flexible document canvas with 12-column internal rhythm. Relationship panels may overlap the canvas edge by 12-24px to imply layered context.

### Responsive

Maintain readable excerpts and current-location markers on small screens; hide secondary metrics before hiding document titles or source provenance.

### Whitespace

Negative space is active: use blank margins to separate levels of context and keep reading lanes clear. Do not fill every column with widgets.

## Elevation & Depth

### Shadows

- **Lg**: 0 18px 54px rgba(42,50,58,0.08)
- **Md**: 0 8px 24px rgba(42,50,58,0.06)
- **Sm**: 0 1px 0 rgba(34,38,42,0.04)

## Shapes

### Rounded

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

### Surfaces

- **Bg Pattern**: None by default; structure comes from spacing, ruled separators, and nested layers rather than decorative patterns.
- **Card Style**: Compact document planes with warm-white fill, 1px hairline border, 12-18px radius, and a slightly cooler underlayer offset for depth.
- **Treatment**: Matte off-white layers with subtle tonal shifts; no visible texture unless it is below 3% opacity and never interferes with text.

### Borders

- **Accent Width**: 3px
- **Character**: Quiet blue-gray and warm-gray hairlines; indigo appears as thin current-location rails, node rings, and connector strokes.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Compose screens as layered document workspaces, not dashboard grids: context map, active reading plane, adjacent relationship plane, and marginal signal strip. Let one document or cluster anchor the screen while supporting signals stay compact and secondary.

### Density

Pack metadata tightly inside cards but separate different cognitive layers with whitespace and plane changes. Prefer inline metrics, source badges, and short excerpts over large charts.

### Hierarchy

Hierarchy begins with text weight, alignment, and proximity. Use indigo only for current location, selected relationship, focus, and active connector lines. Use amber/persimmon only for rare unread, risk, or notification dots with labels.

### Signature Patterns

- Context-map rail: small labeled nodes grouped by document cluster, with the active node shown by an indigo ring and a 3px vertical thread.
- Shoji layer stack: active document cards sit on a warm-white plane with a cooler blue-gray underplane offset by 8px, creating depth without gradient or glass effects.
- Marginal signals: counts, freshness, confidence, and alerts appear in the right margin as tiny chips or dots aligned to the related excerpt line.
- Progressive disclosure seams: collapsed rows show a thin rule and summary; expansion slides the related layer down while preserving surrounding context.
- Relationship reveal: hovering or selecting a reference fades in one connector line and lightly tints the linked document card, never drawing a dense graph web.

## 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/layered-shoji-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 Start every screen with a readable document or context object, then layer signals around it.
- Do Use off-white tonal steps and hairlines before using shadow; keep depth subtle and functional.
- Do Mark current location persistently with indigo threads, tabs, node rings, or left borders.
- Do Keep analytics document-adjacent: inline counts, confidence chips, source freshness, and marginal annotations.
- Do Use progressive disclosure to reveal why items relate, preserving the user’s place in the map.
- Do Translate Japanese craft into restraint, rhythm, layering, and precision—not imagery.
- Don't Do not use literal Japanese patterns, brush strokes, red circles, paper grain overlays, or ornamental icons.
- Don't Do not create a generic dashboard of equal metric cards or colorful chart panels.
- Don't Do not use gradients beyond quiet tonal layering between neutral surfaces.
- Don't Do not let translucency, blur, or low-contrast gray reduce legibility.
- Don't Do not show dense relationship graphs by default; reveal one relationship path at a time.

### Accessibility

Body text must meet WCAG AA on all off-white planes; focus uses a visible 2px indigo outline plus offset. Notification dots require text/count labels. Motion must respect reduced-motion by replacing slides with instant expansion and opacity changes.

### Usage Context

Best for AYA-style research, document intelligence, knowledge work, legal/strategy review, context synthesis, and signal-heavy workspaces where users need calm comprehension across many sources.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "layered-shoji-navigation",
  "type": "registry:theme",
  "title": "Layered Shoji Navigation shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F5EF",
      "foreground": "#242629",
      "card": "#FFFEFA",
      "card-foreground": "#242629",
      "popover": "#FFFEFA",
      "popover-foreground": "#242629",
      "primary": "#242629",
      "primary-foreground": "#ffffff",
      "secondary": "#5E6369",
      "secondary-foreground": "#ffffff",
      "muted": "#858A90",
      "muted-foreground": "#242629",
      "accent": "#394A8A",
      "accent-foreground": "#ffffff",
      "destructive": "#B85B45",
      "border": "#D9DDD9",
      "input": "#D9DDD9",
      "ring": "#394A8A",
      "chart-1": "#242629",
      "chart-2": "#5E6369",
      "chart-3": "#394A8A",
      "chart-4": "#5F7C63",
      "chart-5": "#B98232",
      "sidebar": "#FFFEFA",
      "sidebar-foreground": "#242629",
      "sidebar-primary": "#242629",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#617487",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D9DDD9",
      "sidebar-ring": "#394A8A",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#242629",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#394A8A",
      "accent-foreground": "#ffffff",
      "destructive": "#B85B45",
      "border": "#303642",
      "input": "#303642",
      "ring": "#394A8A",
      "chart-1": "#242629",
      "chart-2": "#5E6369",
      "chart-3": "#394A8A",
      "chart-4": "#5F7C63",
      "chart-5": "#B98232",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#242629",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#394A8A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#394A8A",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "layered-shoji-navigation",
    "slug": "layered-shoji-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",
        "accent_soft",
        "background",
        "border",
        "border_subtle",
        "error",
        "info",
        "muted",
        "notification",
        "primary",
        "secondary",
        "success",
        "surface",
        "surface_alt",
        "surface_depth",
        "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",
        "display_letter_spacing",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

Design Language Preview

Layered Shoji 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 · 25px · 700

The quick brown fox jumps

headline-mdInter · 21px · 600

The quick brown fox jumps

body-mdInter · 15px · 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

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

Shape

full9999px
lg18px
md12px
none0px
sm8px
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: #F7F5EF;
  --foreground: #242629;
  --card: #FFFEFA;
  --card-foreground: #242629;
  --popover: #FFFEFA;
  --popover-foreground: #242629;
  --primary: #242629;
  --primary-foreground: #ffffff;
  --secondary: #5E6369;
  --secondary-foreground: #ffffff;
  --muted: #858A90;
  --muted-foreground: #242629;
  --accent: #394A8A;
  --accent-foreground: #ffffff;
  --destructive: #B85B45;
  --border: #D9DDD9;
  --input: #D9DDD9;
  --ring: #394A8A;
  --chart-1: #242629;
  --chart-2: #5E6369;
  --chart-3: #394A8A;
  --chart-4: #5F7C63;
  --chart-5: #B98232;
  --sidebar: #FFFEFA;
  --sidebar-foreground: #242629;
  --sidebar-primary: #242629;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #617487;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D9DDD9;
  --sidebar-ring: #394A8A;
  --radius: 12px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #242629;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #394A8A;
  --accent-foreground: #ffffff;
  --destructive: #B85B45;
  --border: #303642;
  --input: #303642;
  --ring: #394A8A;
  --chart-1: #242629;
  --chart-2: #5E6369;
  --chart-3: #394A8A;
  --chart-4: #5F7C63;
  --chart-5: #B98232;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #242629;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #394A8A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #394A8A;
  --radius: 12px;
}
tsx starter
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
  Card,
  CardContent,
  CardDescription,
  CardFooter,
  CardHeader,
  CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";

export function LayeredShojiNavigationShadcnKit() {
  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">Layered Shoji 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": "layered-shoji-navigation",
  "type": "registry:theme",
  "title": "Layered Shoji Navigation shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F5EF",
      "foreground": "#242629",
      "card": "#FFFEFA",
      "card-foreground": "#242629",
      "popover": "#FFFEFA",
      "popover-foreground": "#242629",
      "primary": "#242629",
      "primary-foreground": "#ffffff",
      "secondary": "#5E6369",
      "secondary-foreground": "#ffffff",
      "muted": "#858A90",
      "muted-foreground": "#242629",
      "accent": "#394A8A",
      "accent-foreground": "#ffffff",
      "destructive": "#B85B45",
      "border": "#D9DDD9",
      "input": "#D9DDD9",
      "ring": "#394A8A",
      "chart-1": "#242629",
      "chart-2": "#5E6369",
      "chart-3": "#394A8A",
      "chart-4": "#5F7C63",
      "chart-5": "#B98232",
      "sidebar": "#FFFEFA",
      "sidebar-foreground": "#242629",
      "sidebar-primary": "#242629",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#617487",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D9DDD9",
      "sidebar-ring": "#394A8A",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#242629",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#394A8A",
      "accent-foreground": "#ffffff",
      "destructive": "#B85B45",
      "border": "#303642",
      "input": "#303642",
      "ring": "#394A8A",
      "chart-1": "#242629",
      "chart-2": "#5E6369",
      "chart-3": "#394A8A",
      "chart-4": "#5F7C63",
      "chart-5": "#B98232",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#242629",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#394A8A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#394A8A",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "layered-shoji-navigation",
    "slug": "layered-shoji-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",
        "accent_soft",
        "background",
        "border",
        "border_subtle",
        "error",
        "info",
        "muted",
        "notification",
        "primary",
        "secondary",
        "success",
        "surface",
        "surface_alt",
        "surface_depth",
        "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",
        "display_letter_spacing",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
component recipescompatibility fallback
# Layered Shoji Navigation shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `layered-shoji-navigation`
Slug: `layered-shoji-navigation`

## Intent

Layered Shoji Navigation is a calm, text-first product language for AYA Katagami: a workspace that reveals many documents, signals, and relationships as translucent planes rather than as a noisy analytics dashboard. Japanese craft references are translated into interface behavior—washi restraint, katagami-like precision, woven context, indigo current markers, and generous negative space—without literal patterns, icons, or tourist motifs.

## 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": "#394A8A",
  "accent_soft": "#E6E9F4",
  "background": "#F7F5EF",
  "border": "#D9DDD9",
  "border_subtle": "#E8E6DE",
  "error": "#B85B45",
  "info": "#617487",
  "muted": "#858A90",
  "notification": "#D66B3D",
  "primary": "#242629",
  "secondary": "#5E6369",
  "success": "#5F7C63",
  "surface": "#FFFEFA",
  "surface_alt": "#F1F0EA",
  "surface_depth": "#E7EBEE",
  "text": "#242629",
  "warning": "#B98232"
}

Typography:

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

## Visual character to preserve

- A near-white workspace made of translucent-feeling panels: porcelain, washi, mist, and rice-paper surfaces separated by blue-gray depth lines.
- Navigation behaves like a context map: a left rail or top strip shows document clusters, current path, sibling signals, and relationship nodes with minimal indigo marks.
- Document cards are compact, rectangular, and excerpt-led, with inline metrics in mono numerals and marginal annotations rather than chart-heavy modules.
- Surfaces overlap by 8-24px or sit on nested planes, suggesting shoji screens and stacked paper without literal grids, bamboo, waves, or Japanese ornament.
- Motion is calm and relational: layers slide a few pixels, reveal connectors, or crossfade labels to show why one document or signal belongs to another.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "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/layered-shoji-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: Start every screen with a readable document or context object, then layer signals around it.; Use off-white tonal steps and hairlines before using shadow; keep depth subtle and functional.; Mark current location persistently with indigo threads, tabs, node rings, or left borders.; Keep analytics document-adjacent: inline counts, confidence chips, source freshness, and marginal annotations.; Use progressive disclosure to reveal why items relate, preserving the user’s place in the map.; Translate Japanese craft into restraint, rhythm, layering, and precision—not imagery.
- Do not: Do not use literal Japanese patterns, brush strokes, red circles, paper grain overlays, or ornamental icons.; Do not create a generic dashboard of equal metric cards or colorful chart panels.; Do not use gradients beyond quiet tonal layering between neutral surfaces.; Do not let translucency, blur, or low-contrast gray reduce legibility.; Do not show dense relationship graphs by default; reveal one relationship path at a time.

## 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 LayeredShojiNavigationShadcnKit() {
  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">Layered Shoji 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": "Below 900px, context map becomes a horizontal breadcrumb/thread strip above the document list; below 640px, relationship details collapse into inline disclosure rows.",
  "density": "Medium-high information density with compact cards, 12-16px row gaps, 8px metadata clusters, and generous 40-64px breathing room around major mode changes.",
  "grid": "Desktop uses a 72px global rail, a 260-320px context-map column, and a flexible document canvas with 12-column internal rhythm. Relationship panels may overlap the canvas edge by 12-24px to imply layered context.",
  "responsive": "Maintain readable excerpts and current-location markers on small screens; hide secondary metrics before hiding document titles or source provenance.",
  "whitespace": "Negative space is active: use blank margins to separate levels of context and keep reading lanes clear. Do not fill every column with widgets."
}
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": "layered-shoji-navigation",
    "name": "Layered Shoji Navigation",
    "slug": "layered-shoji-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 near-white workspace made of translucent-feeling panels: porcelain, washi, mist, and rice-paper surfaces separated by blue-gray depth lines.",
    "Navigation behaves like a context map: a left rail or top strip shows document clusters, current path, sibling signals, and relationship nodes with minimal indigo marks.",
    "Document cards are compact, rectangular, and excerpt-led, with inline metrics in mono numerals and marginal annotations rather than chart-heavy modules.",
    "Surfaces overlap by 8-24px or sit on nested planes, suggesting shoji screens and stacked paper without literal grids, bamboo, waves, or Japanese ornament.",
    "Motion is calm and relational: layers slide a few pixels, reveal connectors, or crossfade labels to show why one document or signal belongs to another."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "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": "Layered Shoji 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": [
      "Start every screen with a readable document or context object, then layer signals around it.",
      "Use off-white tonal steps and hairlines before using shadow; keep depth subtle and functional.",
      "Mark current location persistently with indigo threads, tabs, node rings, or left borders.",
      "Keep analytics document-adjacent: inline counts, confidence chips, source freshness, and marginal annotations.",
      "Use progressive disclosure to reveal why items relate, preserving the user’s place in the map.",
      "Translate Japanese craft into restraint, rhythm, layering, and precision—not imagery."
    ],
    "dont": [
      "Do not use literal Japanese patterns, brush strokes, red circles, paper grain overlays, or ornamental icons.",
      "Do not create a generic dashboard of equal metric cards or colorful chart panels.",
      "Do not use gradients beyond quiet tonal layering between neutral surfaces.",
      "Do not let translucency, blur, or low-contrast gray reduce legibility.",
      "Do not show dense relationship graphs by default; reveal one relationship path at a time."
    ]
  }
}
related

More like this