back to gallery
design language·aya-washi-text-workspace

AYA Washi Text Workspace

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
Washi Text Workspace defines AYA as a quiet, paper-like, text-first product surface: generous editorial spacing, fine rules, warm whites, paper greys, sumi text, pale indigo interaction fields, and tiny persimmon provenance cues. It turns context, metrics, status, and sources into marginal annotations and inline signals rather than dashboard chrome.
values
Make reading, synthesis, and decision trails the primary experience; all analytics should sit adjacent to the text they explain.Use Japanese-inspired restraint through negative space, rhythm, material quietness, and careful line weight, never through literal motifs.Prefer editorial order over SaaS spectacle: modest headings, precise columns, measured gutters, and hairline dividers.Let color behave like annotation, not decoration: pale indigo for hover/focus/selection, persimmon only for rare attention and provenance.Support dense work without visual noise by using compact marginal signals, source trails, and calm typography.
anti-values
×No literal Japanese motifs, tourist katagami patterns, decorative waves, lantern/red-black cliches, seals, fans, or ornamental borders.×No dashboard-first KPI grids, heavy cards, glossy widgets, busy chrome, saturated fills, or generic SaaS gradients.×No over-rounded consumer components, thick shadows, gamified badges, or decorative illustrations competing with text.×No status systems that depend on color alone or place metrics away from their document context.
tokens
color12 items
danger muted
#A65A4F
indigo field
#EEF2F8
indigo focus
#425A7A
ink faint
#8C8679
ink muted
#5F5A50
paper
#FBFAF6
paper alt
#F6F4EE
paper rule
#DDD8CD
persimmon attention
#B9683B
success muted
#6E7F63
sumi
#181714
warning muted
#A47A3A
radius3 items
large
10px max for panels; avoid pill-heavy styling except tiny tags
medium
6px
small
3px
shadow2 items
default
none
lifted
0 1px 2px rgba(24,23,20,0.06) only for transient popovers
spacing5 items
base
4px
group gap
16-24px
rail gutter
20-28px
reading margin
32-64px depending on viewport
row
32-40px compact rows
stroke3 items
attention tick
2px persimmon left rule for rare provenance or unresolved items
focus
1.5-2px indigo outline with 2px offset
hairline
1px solid #DDD8CD
typography6 items
body
Inter, Source Sans 3, system-ui, sans-serif
body size
14-16px for reading; 13-14px for dense rows; 11-12px for marginal metadata
editorial serif optional
Source Serif 4 or a similarly quiet serif for long-form excerpts only
line height
1.45-1.65 for paragraphs, 1.25-1.35 for tables and chips
mono
IBM Plex Mono, ui-monospace, monospace
weight
Use 400/500 for most text; reserve 600 for section anchors and active labels.
rules
accessibility
Maintain WCAG AA contrast for all text and controls. Preserve keyboard navigation, visible focus, readable line lengths, non-color status cues, and deterministic command/drawer behavior.
composition
Lead with the working text surface. Use hairline dividers, marginalia columns, compact tables, source snippets, and inline metrics to weave context around the document without dashboard cards.
hierarchy

Create hierarchy through type size, weight, indentation, rule weight, and proximity. Use color mainly for state and focus, not decoration.

interaction
Hover and selection states are pale indigo paper tints. Focus must be highly visible but quiet. Popovers and drawers should feel like paper overlays with hairlines and minimal shadow.
signature patterns
Marginal source slips: small paper-grey annotations aligned to a paragraph, with source name, confidence, and timestamp.Inline metric notches: tiny label-number pairs embedded in a row header or margin rather than separated into KPI cards.Pale indigo reading focus: selected text blocks, active rows, and command results receive a quiet blue-grey wash with sumi text unchanged.Persimmon provenance pin: a rare dot or left tick marking unresolved, cited, or attention-worthy material.Fine-rule context map: navigation appears as a textual outline with small counts and state ticks, not icon-heavy chrome.
status
Status indicators are short labels with a dot, tick, left rule, or icon plus text. Never rely on color alone. Keep them compact and adjacent to the relevant row or paragraph.
layout
breakpoints

mobile <= 640px, tablet 641-1024px, desktop >= 1025px.

density

Editorially dense but not cramped: compact rows and chips are balanced with generous outer margins and clear group spacing.

grid
Document-centered workspace: 680-780px primary reading column, 220-280px context/navigation rail, and 280-340px inspector or source rail. Analytical content stays near the relevant text as marginal strips, inline tables, or source drawers.
responsive
On narrow screens, preserve document order: title/context trail, body text, inline metrics, provenance, then inspector details. Rails become drawers; metrics become caption rows, not cards.
whitespace

Whitespace acts like paper margin. Leave pauses around reading zones, section breaks, and decision summaries; avoid empty marketing expanses.

guidance
do
  • Use warm paper surfaces, sumi text, fine rules, and generous editorial margins.
  • Place metrics, provenance, and status inline or in the margin beside the content they explain.
  • Use pale indigo for hover, focus, command, and selection states.
  • Use persimmon only as a tiny attention/provenance accent.
  • Keep navigation textual, compact, and context-map oriented.
avoid
  • Do not use literal Japanese decoration, tourist motifs, waves, lantern palettes, or ornamental borders.
  • Do not create dashboard chrome, heavy cards, glossy panels, or saturated chart blocks.
  • Do not make analytics larger than the document they support.
  • Do not use color without labels, shape, or text cues.
  • Do not add decorative patterning that reduces reading calm.
katagami spec
# AYA Washi Text Workspace

## Philosophy

Washi Text Workspace defines AYA as a quiet, paper-like, text-first product surface: generous editorial spacing, fine rules, warm whites, paper greys, sumi text, pale indigo interaction fields, and tiny persimmon provenance cues. It turns context, metrics, status, and sources into marginal annotations and inline signals rather than dashboard chrome.

### Values

- Make reading, synthesis, and decision trails the primary experience; all analytics should sit adjacent to the text they explain.
- Use Japanese-inspired restraint through negative space, rhythm, material quietness, and careful line weight, never through literal motifs.
- Prefer editorial order over SaaS spectacle: modest headings, precise columns, measured gutters, and hairline dividers.
- Let color behave like annotation, not decoration: pale indigo for hover/focus/selection, persimmon only for rare attention and provenance.
- Support dense work without visual noise by using compact marginal signals, source trails, and calm typography.

### Anti-Values

- No literal Japanese motifs, tourist katagami patterns, decorative waves, lantern/red-black cliches, seals, fans, or ornamental borders.
- No dashboard-first KPI grids, heavy cards, glossy widgets, busy chrome, saturated fills, or generic SaaS gradients.
- No over-rounded consumer components, thick shadows, gamified badges, or decorative illustrations competing with text.
- No status systems that depend on color alone or place metrics away from their document context.

### Visual Character

- Warm washi whites and quiet paper greys form a nearly flat canvas, with sumi blacks for text and fine grey rules for structure.
- The main workspace resembles an edited document table: generous margins, compact annotations, and restrained context rails.
- Interactive states appear as very pale indigo washes, thin focus outlines, and subtle row tints rather than saturated blocks.
- Persimmon is a small provenance/attention mark: a dot, left tick, source stamp, or rare alert accent, never a large fill.
- Information density is high but calm because signals are narrow, aligned, typographic, and close to the related paragraph or row.

## Tokens

### Color

- **Danger Muted**: #A65A4F
- **Indigo Field**: #EEF2F8
- **Indigo Focus**: #425A7A
- **Ink Faint**: #8C8679
- **Ink Muted**: #5F5A50
- **Paper**: #FBFAF6
- **Paper Alt**: #F6F4EE
- **Paper Rule**: #DDD8CD
- **Persimmon Attention**: #B9683B
- **Success Muted**: #6E7F63
- **Sumi**: #181714
- **Warning Muted**: #A47A3A

### Radius

- **Large**: 10px max for panels; avoid pill-heavy styling except tiny tags
- **Medium**: 6px
- **Small**: 3px

### Shadow

- **Default**: none
- **Lifted**: 0 1px 2px rgba(24,23,20,0.06) only for transient popovers

### Spacing

- **Base**: 4px
- **Group Gap**: 16-24px
- **Rail Gutter**: 20-28px
- **Reading Margin**: 32-64px depending on viewport
- **Row**: 32-40px compact rows

### Stroke

- **Attention Tick**: 2px persimmon left rule for rare provenance or unresolved items
- **Focus**: 1.5-2px indigo outline with 2px offset
- **Hairline**: 1px solid #DDD8CD

### Typography

- **Body**: Inter, Source Sans 3, system-ui, sans-serif
- **Body Size**: 14-16px for reading; 13-14px for dense rows; 11-12px for marginal metadata
- **Editorial Serif Optional**: Source Serif 4 or a similarly quiet serif for long-form excerpts only
- **Line Height**: 1.45-1.65 for paragraphs, 1.25-1.35 for tables and chips
- **Mono**: IBM Plex Mono, ui-monospace, monospace
- **Weight**: Use 400/500 for most text; reserve 600 for section anchors and active labels.

## Rules

### Accessibility

Maintain WCAG AA contrast for all text and controls. Preserve keyboard navigation, visible focus, readable line lengths, non-color status cues, and deterministic command/drawer behavior.

### Composition

Lead with the working text surface. Use hairline dividers, marginalia columns, compact tables, source snippets, and inline metrics to weave context around the document without dashboard cards.

### Hierarchy

Create hierarchy through type size, weight, indentation, rule weight, and proximity. Use color mainly for state and focus, not decoration.

### Interaction

Hover and selection states are pale indigo paper tints. Focus must be highly visible but quiet. Popovers and drawers should feel like paper overlays with hairlines and minimal shadow.

### Signature Patterns

- Marginal source slips: small paper-grey annotations aligned to a paragraph, with source name, confidence, and timestamp.
- Inline metric notches: tiny label-number pairs embedded in a row header or margin rather than separated into KPI cards.
- Pale indigo reading focus: selected text blocks, active rows, and command results receive a quiet blue-grey wash with sumi text unchanged.
- Persimmon provenance pin: a rare dot or left tick marking unresolved, cited, or attention-worthy material.
- Fine-rule context map: navigation appears as a textual outline with small counts and state ticks, not icon-heavy chrome.

### Status

Status indicators are short labels with a dot, tick, left rule, or icon plus text. Never rely on color alone. Keep them compact and adjacent to the relevant row or paragraph.

## Layout

### Breakpoints

mobile <= 640px, tablet 641-1024px, desktop >= 1025px.

### Density

Editorially dense but not cramped: compact rows and chips are balanced with generous outer margins and clear group spacing.

### Grid

Document-centered workspace: 680-780px primary reading column, 220-280px context/navigation rail, and 280-340px inspector or source rail. Analytical content stays near the relevant text as marginal strips, inline tables, or source drawers.

### Responsive

On narrow screens, preserve document order: title/context trail, body text, inline metrics, provenance, then inspector details. Rails become drawers; metrics become caption rows, not cards.

### Whitespace

Whitespace acts like paper margin. Leave pauses around reading zones, section breaks, and decision summaries; avoid empty marketing expanses.

## Guidance

### Do

- Use warm paper surfaces, sumi text, fine rules, and generous editorial margins.
- Place metrics, provenance, and status inline or in the margin beside the content they explain.
- Use pale indigo for hover, focus, command, and selection states.
- Use persimmon only as a tiny attention/provenance accent.
- Keep navigation textual, compact, and context-map oriented.

### Don't

- Do not use literal Japanese decoration, tourist motifs, waves, lantern palettes, or ornamental borders.
- Do not create dashboard chrome, heavy cards, glossy panels, or saturated chart blocks.
- Do not make analytics larger than the document they support.
- Do not use color without labels, shape, or text cues.
- Do not add decorative patterning that reduces reading calm.

### Accessibility

High contrast sumi text on warm paper, visible indigo focus rings, labels for all status colors, comfortable line length, keyboard-first command and navigation patterns.

### Usage Context

Best for AYA knowledge work, research synthesis, source review, writing systems, context mapping, document-adjacent analytics, and expert workflows where lots of information must remain readable.
DESIGN.md
---
version: "alpha"
name: "AYA Washi Text Workspace"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
typography:
  headline-lg:
    fontFamily: "Inter"
    fontSize: "1.953rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Inter"
    fontSize: "1.563rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "Inter"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "Inter"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
spacing:
  base: "4px"
  group_gap: "16-24px"
  rail_gutter: "20-28px"
  reading_margin: "32-64px depending on viewport"
  row: "32-40px compact rows"
---

# AYA Washi Text Workspace

## Overview

Washi Text Workspace defines AYA as a quiet, paper-like, text-first product surface: generous editorial spacing, fine rules, warm whites, paper greys, sumi text, pale indigo interaction fields, and tiny persimmon provenance cues. It turns context, metrics, status, and sources into marginal annotations and inline signals rather than dashboard chrome.

### Values

- Make reading, synthesis, and decision trails the primary experience; all analytics should sit adjacent to the text they explain.
- Use Japanese-inspired restraint through negative space, rhythm, material quietness, and careful line weight, never through literal motifs.
- Prefer editorial order over SaaS spectacle: modest headings, precise columns, measured gutters, and hairline dividers.
- Let color behave like annotation, not decoration: pale indigo for hover/focus/selection, persimmon only for rare attention and provenance.
- Support dense work without visual noise by using compact marginal signals, source trails, and calm typography.

### Anti-Values

- No literal Japanese motifs, tourist katagami patterns, decorative waves, lantern/red-black cliches, seals, fans, or ornamental borders.
- No dashboard-first KPI grids, heavy cards, glossy widgets, busy chrome, saturated fills, or generic SaaS gradients.
- No over-rounded consumer components, thick shadows, gamified badges, or decorative illustrations competing with text.
- No status systems that depend on color alone or place metrics away from their document context.

### Visual Character

- Warm washi whites and quiet paper greys form a nearly flat canvas, with sumi blacks for text and fine grey rules for structure.
- The main workspace resembles an edited document table: generous margins, compact annotations, and restrained context rails.
- Interactive states appear as very pale indigo washes, thin focus outlines, and subtle row tints rather than saturated blocks.
- Persimmon is a small provenance/attention mark: a dot, left tick, source stamp, or rare alert accent, never a large fill.
- Information density is high but calm because signals are narrow, aligned, typographic, and close to the related paragraph or row.

## Typography

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

## Layout

### Spacing Tokens

- **Base**: `4px`
- **Group Gap**: `16-24px`
- **Rail Gutter**: `20-28px`
- **Reading Margin**: `32-64px depending on viewport`
- **Row**: `32-40px compact rows`

### Breakpoints

mobile <= 640px, tablet 641-1024px, desktop >= 1025px.

### Density

Editorially dense but not cramped: compact rows and chips are balanced with generous outer margins and clear group spacing.

### Grid

Document-centered workspace: 680-780px primary reading column, 220-280px context/navigation rail, and 280-340px inspector or source rail. Analytical content stays near the relevant text as marginal strips, inline tables, or source drawers.

### Responsive

On narrow screens, preserve document order: title/context trail, body text, inline metrics, provenance, then inspector details. Rails become drawers; metrics become caption rows, not cards.

### Whitespace

Whitespace acts like paper margin. Leave pauses around reading zones, section breaks, and decision summaries; avoid empty marketing expanses.

## Components

### Accessibility

Maintain WCAG AA contrast for all text and controls. Preserve keyboard navigation, visible focus, readable line lengths, non-color status cues, and deterministic command/drawer behavior.

### Composition

Lead with the working text surface. Use hairline dividers, marginalia columns, compact tables, source snippets, and inline metrics to weave context around the document without dashboard cards.

### Hierarchy

Create hierarchy through type size, weight, indentation, rule weight, and proximity. Use color mainly for state and focus, not decoration.

### Interaction

Hover and selection states are pale indigo paper tints. Focus must be highly visible but quiet. Popovers and drawers should feel like paper overlays with hairlines and minimal shadow.

### Signature Patterns

- Marginal source slips: small paper-grey annotations aligned to a paragraph, with source name, confidence, and timestamp.
- Inline metric notches: tiny label-number pairs embedded in a row header or margin rather than separated into KPI cards.
- Pale indigo reading focus: selected text blocks, active rows, and command results receive a quiet blue-grey wash with sumi text unchanged.
- Persimmon provenance pin: a rare dot or left tick marking unresolved, cited, or attention-worthy material.
- Fine-rule context map: navigation appears as a textual outline with small counts and state ticks, not icon-heavy chrome.

### Status

Status indicators are short labels with a dot, tick, left rule, or icon plus text. Never rely on color alone. Keep them compact and adjacent to the relevant row or paragraph.

## shadcn/ui Usage

When the target app uses shadcn/ui, copy DESIGN.md with shadcn instead of the plain DESIGN.md. It contains the same Katagami design-language source plus the shadcn/ui primitives, imports, theme variables, component recipes, and preview-shot guidance.

DESIGN.md with shadcn: `/language/en-019edd70-1f8b-72d1-bc87-343aa6ba22f6/DESIGN.with-shadcn.md`.

The shadcn page also exposes optional machine-readable files for automation, but the human-facing handoff is DESIGN.md with shadcn.

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

Use these primitives in shadcn apps:
- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Implementation rule for agents: import shadcn primitives from `@/components/ui/*`, apply the generated CSS variables first, then compose the language-specific recipes from the companion MD. Katagami remains the source of truth; shadcn names are the implementation surface.

## Do's and Don'ts

- Do Use warm paper surfaces, sumi text, fine rules, and generous editorial margins.
- Do Place metrics, provenance, and status inline or in the margin beside the content they explain.
- Do Use pale indigo for hover, focus, command, and selection states.
- Do Use persimmon only as a tiny attention/provenance accent.
- Do Keep navigation textual, compact, and context-map oriented.
- Don't Do not use literal Japanese decoration, tourist motifs, waves, lantern palettes, or ornamental borders.
- Don't Do not create dashboard chrome, heavy cards, glossy panels, or saturated chart blocks.
- Don't Do not make analytics larger than the document they support.
- Don't Do not use color without labels, shape, or text cues.
- Don't Do not add decorative patterning that reduces reading calm.

### Accessibility

High contrast sumi text on warm paper, visible indigo focus rings, labels for all status colors, comfortable line length, keyboard-first command and navigation patterns.

### Usage Context

Best for AYA knowledge work, research synthesis, source review, writing systems, context mapping, document-adjacent analytics, and expert workflows where lots of information must remain readable.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "aya-washi-text-workspace",
  "type": "registry:theme",
  "title": "AYA Washi Text Workspace shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#ffffff",
      "foreground": "#111111",
      "card": "#ffffff",
      "card-foreground": "#111111",
      "popover": "#ffffff",
      "popover-foreground": "#111111",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#f4f4f5",
      "muted-foreground": "#111111",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#e4e4e7",
      "input": "#e4e4e7",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#ffffff",
      "sidebar-foreground": "#111111",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#e4e4e7",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#303642",
      "input": "#303642",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edd70-1f8b-72d1-bc87-343aa6ba22f6",
    "slug": "aya-washi-text-workspace",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "color": [
        "danger_muted",
        "indigo_field",
        "indigo_focus",
        "ink_faint",
        "ink_muted",
        "paper",
        "paper_alt",
        "paper_rule",
        "persimmon_attention",
        "success_muted",
        "sumi",
        "warning_muted"
      ],
      "radius": [
        "large",
        "medium",
        "small"
      ],
      "shadow": [
        "default",
        "lifted"
      ],
      "spacing": [
        "base",
        "group_gap",
        "rail_gutter",
        "reading_margin",
        "row"
      ],
      "stroke": [
        "attention_tick",
        "focus",
        "hairline"
      ],
      "typography": [
        "body",
        "body_size",
        "editorial_serif_optional",
        "line_height",
        "mono",
        "weight"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · aya-washi-text-workspace
DESIGN.md

at a glance

Typography

headline-lgInter · 31px · 700

The quick brown fox jumps

headline-mdInter · 25px · 600

The quick brown fox jumps

body-mdInter · 16px · 400

The quick brown fox jumps

label-mdInter · 12px · 600

The quick brown fox jumps

Spacing

  • base4px
  • group_gap16-24px
  • rail_gutter20-28px
  • reading_margin32-64px depending on viewport
  • row32-40px compact rows
shadcn/ui

implementation kit

needs agent-authored kitcompatibility fallback
shadcn compatibility only
The generated theme variables are available, but the polished shadcn component recipes and shots have not been authored by the Katagami agent yet.
fallbackprimitives render
Compatibility proof
Local shadcn-style primitives accept the generated theme variables.
primaryaccentsurfacemutedwarningerror
table rhythm
buttonok
cardok
inputok
recommendedcompatibility fallback

DESIGN.md with shadcn

Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.

advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #ffffff;
  --foreground: #111111;
  --card: #ffffff;
  --card-foreground: #111111;
  --popover: #ffffff;
  --popover-foreground: #111111;
  --primary: #111111;
  --primary-foreground: #ffffff;
  --secondary: #f4f4f5;
  --secondary-foreground: #111111;
  --muted: #f4f4f5;
  --muted-foreground: #111111;
  --accent: #111111;
  --accent-foreground: #ffffff;
  --destructive: #dc2626;
  --border: #e4e4e7;
  --input: #e4e4e7;
  --ring: #111111;
  --chart-1: #111111;
  --chart-2: #f4f4f5;
  --chart-3: #111111;
  --chart-4: #16a34a;
  --chart-5: #d97706;
  --sidebar: #ffffff;
  --sidebar-foreground: #111111;
  --sidebar-primary: #111111;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #111111;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #e4e4e7;
  --sidebar-ring: #111111;
  --radius: 0.625rem;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #111111;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #111111;
  --accent-foreground: #ffffff;
  --destructive: #dc2626;
  --border: #303642;
  --input: #303642;
  --ring: #111111;
  --chart-1: #111111;
  --chart-2: #f4f4f5;
  --chart-3: #111111;
  --chart-4: #16a34a;
  --chart-5: #d97706;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #111111;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #111111;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #111111;
  --radius: 0.625rem;
}
tsx starter
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
  Card,
  CardContent,
  CardDescription,
  CardFooter,
  CardHeader,
  CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";

export function AyaWashiTextWorkspaceShadcnKit() {
  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 Washi Text Workspace</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-washi-text-workspace",
  "type": "registry:theme",
  "title": "AYA Washi Text Workspace shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#ffffff",
      "foreground": "#111111",
      "card": "#ffffff",
      "card-foreground": "#111111",
      "popover": "#ffffff",
      "popover-foreground": "#111111",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#f4f4f5",
      "muted-foreground": "#111111",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#e4e4e7",
      "input": "#e4e4e7",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#ffffff",
      "sidebar-foreground": "#111111",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#e4e4e7",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#303642",
      "input": "#303642",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edd70-1f8b-72d1-bc87-343aa6ba22f6",
    "slug": "aya-washi-text-workspace",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "color": [
        "danger_muted",
        "indigo_field",
        "indigo_focus",
        "ink_faint",
        "ink_muted",
        "paper",
        "paper_alt",
        "paper_rule",
        "persimmon_attention",
        "success_muted",
        "sumi",
        "warning_muted"
      ],
      "radius": [
        "large",
        "medium",
        "small"
      ],
      "shadow": [
        "default",
        "lifted"
      ],
      "spacing": [
        "base",
        "group_gap",
        "rail_gutter",
        "reading_margin",
        "row"
      ],
      "stroke": [
        "attention_tick",
        "focus",
        "hairline"
      ],
      "typography": [
        "body",
        "body_size",
        "editorial_serif_optional",
        "line_height",
        "mono",
        "weight"
      ]
    }
  }
}
component recipescompatibility fallback
# AYA Washi Text Workspace shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019edd70-1f8b-72d1-bc87-343aa6ba22f6`
Slug: `aya-washi-text-workspace`

## Intent

Washi Text Workspace defines AYA as a quiet, paper-like, text-first product surface: generous editorial spacing, fine rules, warm whites, paper greys, sumi text, pale indigo interaction fields, and tiny persimmon provenance cues. It turns context, metrics, status, and sources into marginal annotations and inline signals rather than dashboard chrome.

## Required primitives

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

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

## Token cues

Colors:

Defined by the Katagami source fields.

Typography:

{
  "body": "Inter, Source Sans 3, system-ui, sans-serif",
  "body_size": "14-16px for reading; 13-14px for dense rows; 11-12px for marginal metadata",
  "editorial_serif_optional": "Source Serif 4 or a similarly quiet serif for long-form excerpts only",
  "line_height": "1.45-1.65 for paragraphs, 1.25-1.35 for tables and chips",
  "mono": "IBM Plex Mono, ui-monospace, monospace",
  "weight": "Use 400/500 for most text; reserve 600 for section anchors and active labels."
}

## Visual character to preserve

- Warm washi whites and quiet paper greys form a nearly flat canvas, with sumi blacks for text and fine grey rules for structure.
- The main workspace resembles an edited document table: generous margins, compact annotations, and restrained context rails.
- Interactive states appear as very pale indigo washes, thin focus outlines, and subtle row tints rather than saturated blocks.
- Persimmon is a small provenance/attention mark: a dot, left tick, source stamp, or rare alert accent, never a large fill.
- Information density is high but calm because signals are narrow, aligned, typographic, and close to the related paragraph or row.

## ShadSync visual profile

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

## Signature component recipes

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

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

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

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

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

## Preview shots

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

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/aya-washi-text-workspace/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use warm paper surfaces, sumi text, fine rules, and generous editorial margins.; Place metrics, provenance, and status inline or in the margin beside the content they explain.; Use pale indigo for hover, focus, command, and selection states.; Use persimmon only as a tiny attention/provenance accent.; Keep navigation textual, compact, and context-map oriented.
- Do not: Do not use literal Japanese decoration, tourist motifs, waves, lantern palettes, or ornamental borders.; Do not create dashboard chrome, heavy cards, glossy panels, or saturated chart blocks.; Do not make analytics larger than the document they support.; Do not use color without labels, shape, or text cues.; Do not add decorative patterning that reduces reading calm.

## 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 AyaWashiTextWorkspaceShadcnKit() {
  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 Washi Text Workspace</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 641-1024px, desktop >= 1025px.",
  "density": "Editorially dense but not cramped: compact rows and chips are balanced with generous outer margins and clear group spacing.",
  "grid": "Document-centered workspace: 680-780px primary reading column, 220-280px context/navigation rail, and 280-340px inspector or source rail. Analytical content stays near the relevant text as marginal strips, inline tables, or source drawers.",
  "responsive": "On narrow screens, preserve document order: title/context trail, body text, inline metrics, provenance, then inspector details. Rails become drawers; metrics become caption rows, not cards.",
  "whitespace": "Whitespace acts like paper margin. Leave pauses around reading zones, section breaks, and decision summaries; avoid empty marketing expanses."
}
preview shotscompatibility fallback
{
  "artifact": "katagami:shadcn-preview-shots",
  "version": "preview-shots-v1",
  "generator": "katagami-ui-compatibility-projection",
  "generatedBy": "katagami-ui-projection",
  "requiresVisualProfile": true,
  "schema": "katagami:shadcn-preview-shots/renderable-v1",
  "renderable": true,
  "language": {
    "id": "en-019edd70-1f8b-72d1-bc87-343aa6ba22f6",
    "name": "AYA Washi Text Workspace",
    "slug": "aya-washi-text-workspace"
  },
  "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": [
    "Warm washi whites and quiet paper greys form a nearly flat canvas, with sumi blacks for text and fine grey rules for structure.",
    "The main workspace resembles an edited document table: generous margins, compact annotations, and restrained context rails.",
    "Interactive states appear as very pale indigo washes, thin focus outlines, and subtle row tints rather than saturated blocks.",
    "Persimmon is a small provenance/attention mark: a dot, left tick, source stamp, or rare alert accent, never a large fill.",
    "Information density is high but calm because signals are narrow, aligned, typographic, and close to the related paragraph or row."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": true,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "AYA Washi Text Workspace launch room",
        "description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
        "primaryAction": "Apply theme",
        "secondaryAction": "Review states",
        "stats": [
          {
            "label": "components",
            "value": "16",
            "tone": "accent"
          },
          {
            "label": "states",
            "value": "ready"
          },
          {
            "label": "density",
            "value": "balanced",
            "tone": "warning"
          }
        ],
        "rows": [
          {
            "label": "Primary flow",
            "value": "mapped",
            "status": "active"
          },
          {
            "label": "Token coverage",
            "value": "semantic",
            "status": "synced"
          },
          {
            "label": "Responsive proof",
            "value": "queued",
            "status": "review"
          }
        ],
        "statuses": [
          "Active",
          "Synced",
          "Draft"
        ]
      }
    },
    {
      "id": "detail-editor",
      "title": "Detail editor",
      "viewport": "tablet",
      "primitives": [
        "button",
        "card",
        "input",
        "textarea",
        "select",
        "checkbox",
        "switch",
        "slider",
        "dialog",
        "sheet"
      ],
      "composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
      "mustShow": [
        "focus ring",
        "error or destructive state",
        "dialog or sheet treatment",
        "written guidance content"
      ],
      "avoid": [
        "unstyled browser controls",
        "floating cards inside cards",
        "missing labels"
      ],
      "scene": {
        "eyebrow": "editing flow",
        "headline": "Language recipe editor",
        "description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
        "primaryAction": "Save recipe",
        "secondaryAction": "Open sheet",
        "fields": [
          {
            "label": "Component family",
            "value": "Narrative cards"
          },
          {
            "label": "State treatment",
            "value": "Visible focus + validation"
          },
          {
            "label": "Motion",
            "value": "Small lift, no opacity-only fade"
          }
        ],
        "statuses": [
          "Focus",
          "Invalid",
          "Confirmed"
        ]
      }
    },
    {
      "id": "data-operations",
      "title": "Data operations",
      "viewport": "mobile",
      "primitives": [
        "button",
        "tabs",
        "badge",
        "dropdown-menu",
        "table",
        "tooltip",
        "separator"
      ],
      "composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
      "mustShow": [
        "responsive reflow",
        "dense row styling",
        "menu affordance",
        "status badge system"
      ],
      "avoid": [
        "desktop-only tables",
        "text overflow",
        "default shadcn spacing without Katagami character"
      ],
      "scene": {
        "eyebrow": "operations",
        "headline": "Compact review queue",
        "description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
        "primaryAction": "Resolve",
        "secondaryAction": "Filter",
        "rows": [
          {
            "label": "Button hierarchy",
            "value": "approved",
            "status": "ok"
          },
          {
            "label": "Table rhythm",
            "value": "needs pass",
            "status": "watch"
          },
          {
            "label": "Empty state",
            "value": "designed",
            "status": "done"
          }
        ],
        "statuses": [
          "Queued",
          "Blocked",
          "Done"
        ]
      }
    }
  ],
  "componentRecipes": [
    {
      "primitive": "button",
      "intent": "Prove action hierarchy, focus, disabled, and destructive states."
    },
    {
      "primitive": "card",
      "intent": "Carry the language surface, border, elevation, and density rules."
    },
    {
      "primitive": "input",
      "intent": "Show labels, focus rings, validation, and spacing rhythm."
    },
    {
      "primitive": "textarea",
      "intent": "Show longer guidance, validation copy, and writing density."
    },
    {
      "primitive": "select",
      "intent": "Show filtering, selection contrast, and menu trigger styling."
    },
    {
      "primitive": "dialog",
      "intent": "Show centered decision states and overlay treatment."
    },
    {
      "primitive": "sheet",
      "intent": "Show contextual side panels and responsive editing."
    },
    {
      "primitive": "tabs",
      "intent": "Show navigational structure and active/inactive contrast."
    },
    {
      "primitive": "badge",
      "intent": "Show compact status vocabulary and semantic colors."
    },
    {
      "primitive": "separator",
      "intent": "Show section rhythm without generic gray dividers."
    },
    {
      "primitive": "checkbox",
      "intent": "Show binary selection with visible focus and checked states."
    },
    {
      "primitive": "switch",
      "intent": "Show settings toggles and on/off contrast."
    },
    {
      "primitive": "slider",
      "intent": "Show numeric adjustment with track/thumb styling."
    },
    {
      "primitive": "tooltip",
      "intent": "Show concise explanation styling above compact controls."
    },
    {
      "primitive": "dropdown-menu",
      "intent": "Show action menus, destructive items, and grouped choices."
    },
    {
      "primitive": "table",
      "intent": "Show dense operational data, separators, row states, and responsive behavior."
    }
  ],
  "qualityRules": {
    "do": [
      "Use warm paper surfaces, sumi text, fine rules, and generous editorial margins.",
      "Place metrics, provenance, and status inline or in the margin beside the content they explain.",
      "Use pale indigo for hover, focus, command, and selection states.",
      "Use persimmon only as a tiny attention/provenance accent.",
      "Keep navigation textual, compact, and context-map oriented."
    ],
    "dont": [
      "Do not use literal Japanese decoration, tourist motifs, waves, lantern palettes, or ornamental borders.",
      "Do not create dashboard chrome, heavy cards, glossy panels, or saturated chart blocks.",
      "Do not make analytics larger than the document they support.",
      "Do not use color without labels, shape, or text cues.",
      "Do not add decorative patterning that reduces reading calm."
    ]
  }
}