back to gallery
design language·aya-sumi-indigo-paper-system

AYA Sumi Indigo Paper System

A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.

Download DESIGN.md

Portable DESIGN.md source of truth for most agents and apps.

the spec

specification

philosophy
summary
A restrained application design language for AYA, built from the feeling of black ink on warm rice paper with one continuous indigo thread for orientation, interaction, and continuity. The interface is designed for long-form reading, contextual weaving, and occasional data views without becoming dashboard-heavy. Most hierarchy comes from typography, paper surfaces, hairline rules, whitespace, and density changes; color appears only as a narrow signal. Indigo marks the active path, selected context, links, focus, and a single highlighted data series. A muted gold thread is reserved for provenance, verified milestones, and rare ceremonial annotations, never for primary action. The result should feel calm, precise, Japanese-inspired, and product-ready rather than themed or decorative.
values
near-monochrome clarity for text-heavy workflowsindigo as a connective thread rather than a decorative brand washwarm paper surfaces that reduce glare and support sustained readingkatagami-like negative space, cut lines, and implied pattern over ornamentcomponent restraint: rules, underlines, notches, and borders before filled colorhigh-contrast accessible text and focus states despite the quiet palettedata views that remain editorial and sparse, never saturated dashboards
anti-values
×blue SaaS dashboards with indigo spread across every tile×decorative gradients, glassmorphism, or glossy luxury gold×colored card backgrounds used as structural hierarchy×rainbow chart legends or multiple competing accent hues×low-contrast beige minimalism that compromises reading×literal Japanese motifs pasted on top of generic UI components
tokens
borders4 items
accent width
2px
character
Mist-colored hairlines, ruled ledger dividers, and indigo thread accents used as linework rather than decoration.
default width
1px
style
solid
colors14 items
accent
#B89B4D
background
#F7F3EA
border
#E7E1D6
border_strong
#D2C7B8
error
#9F3A32
info
#1F4E79
muted
#6E6A63
primary
#1F4E79
primary_strong
#173F63
success
#4F6F52
surface
#FBF9F3
surface_subtle
#F2EDE3
text
#171717
warning
#9A6A1F
motion3 items
duration
150ms
easing
cubic-bezier(0.2, 0, 0, 1)
philosophy
Motion is quiet and tactile: indigo threads draw in, paper panels settle by 1px, and focus rings clarify without bounce.
radii5 items
full
9999px
lg
16px
md
8px
none
0
sm
2px
shadows3 items
lg
0 24px 60px rgba(23,23,23,0.08)
md
0 10px 28px rgba(23,23,23,0.06)
sm
0 1px 2px rgba(23,23,23,0.04)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 40, 48, 64, 80, 104
surfaces3 items
bg pattern
Optional katagami-inspired micro-dot or cut-line pattern at very low contrast in margins only, never behind dense text.
card style
Off-white paper panels with 1px mist borders, 16px radius at most, and little to no shadow.
treatment
Warm matte paper canvas with lightly raised paper panels and sparse ruled sections.
typography9 items
base size
16px
body font
Noto Sans
display font
Noto Serif JP
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600;700&family=Noto+Sans:wght@400;500;600;700&family=Noto+Serif+JP:wght@500;600;700&display=swap
heading font
IBM Plex Sans
letter spacing
-0.01em
line height
1.62
mono font
IBM Plex Mono
scale ratio
1.2
rules
composition
Use a paper workspace with a centered 640-760px reading measure for primary text and modular side-context rails for sources, metadata, and woven threads. App-wide navigation may sit as a slim left rail or top strip, but active location is shown by a 2px indigo stitch/underline. Data views should use ruled tables, compact ledgers, and margin summaries instead of colored cards. Keep page chrome quiet so text and contextual relationships carry the experience.
density
Default density is calm editorial-product density: generous line height for reading, 24-32px section padding, compact but legible tables, and clear pauses between context clusters. Increase density through alignment, rules, and typography; do not add boxes or colored fills to make information look important.
hierarchy
Text hierarchy starts with sumi values, weight, size, and whitespace. Indigo is reserved for primary action, current navigation, links, selected rows, keyboard focus, and one key chart series. Gold thread is a ceremonial micro-accent for verified provenance, milestones, or premium annotations. Semantic success, warning, and error colors are muted and always accompanied by labels or icons.
signature patterns
The Indigo Thread: active nav, selected context, and primary path use a 2px indigo line, underline, or left stitch rather than a filled blue surface.Paper Ledger Rows: tables use warm ruled dividers, tabular numerals, and a tiny indigo notch for the selected row.Katagami Margin Notes: side annotations sit in cutout-like paper modules with dashed or hairline connectors back to the source text.Gold Knot Verification: verified provenance or completed milestones get a 6-8px muted gold dot/seal paired with text, never a gold CTA.Ink Wash State: hover and selected backgrounds are extremely pale indigo washes under 5% color area, with the line remaining the main signal.
layout
breakpoints
Mobile <= 640px stacks navigation, reading content, and context notes; tablet 641-1024px keeps the reading column first with collapsible context; desktop >= 1025px exposes the full woven workspace.
density

Editorial application density: roomy text, compact metadata, restrained controls, and sparse ledgers for data-heavy moments.

grid
Desktop uses a quiet 12-column workspace: optional 220px navigation rail, 640-760px central reading column, and a 280-340px context rail. Gutters follow the 8px spacing scale with 32px default page padding.
responsive

On small screens, context rails become inline expandable paper notes and data tables become ledger cards with the indigo stitch preserved for selection.

whitespace

Whitespace acts as ma: a functional pause around reading passages, source clusters, and decision points. Use paper margins before adding panels.

guidance
do
  • Let typography, whitespace, and ruled structure create hierarchy before using color.
  • Use indigo only for active path, focus, selected state, links, primary action, and one key data series.
  • Keep gold as a small provenance or milestone signal paired with a label.
  • Prefer underlines, left stitches, notches, and hairlines over filled colored panels.
  • Use warm off-white paper surfaces to support long reading and reduce glare.
  • Make data views feel like ledgers: sparse, aligned, tabular, and text-first.
  • Style all controls with custom borders, hover states, and visible focus treatment.
avoid
  • Do not fill dashboards with saturated indigo tiles or blue chart palettes.
  • Do not use gold as luxury gloss, gradients, large fills, or primary CTAs.
  • Do not paste literal Japanese ornament into components; translate motifs into spacing, line, and restraint.
  • Do not allow color area to exceed roughly 5% of a normal work screen.
  • Do not rely on pale beige or gray text that fails contrast.
  • Do not use browser-default form controls or generic rounded SaaS cards.
  • Do not make every source, category, or thread a different color.
katagami spec
# AYA Sumi Indigo Paper System

## Philosophy

A restrained application design language for AYA, built from the feeling of black ink on warm rice paper with one continuous indigo thread for orientation, interaction, and continuity. The interface is designed for long-form reading, contextual weaving, and occasional data views without becoming dashboard-heavy. Most hierarchy comes from typography, paper surfaces, hairline rules, whitespace, and density changes; color appears only as a narrow signal. Indigo marks the active path, selected context, links, focus, and a single highlighted data series. A muted gold thread is reserved for provenance, verified milestones, and rare ceremonial annotations, never for primary action. The result should feel calm, precise, Japanese-inspired, and product-ready rather than themed or decorative.

### Values

- near-monochrome clarity for text-heavy workflows
- indigo as a connective thread rather than a decorative brand wash
- warm paper surfaces that reduce glare and support sustained reading
- katagami-like negative space, cut lines, and implied pattern over ornament
- component restraint: rules, underlines, notches, and borders before filled color
- high-contrast accessible text and focus states despite the quiet palette
- data views that remain editorial and sparse, never saturated dashboards

### Anti-Values

- blue SaaS dashboards with indigo spread across every tile
- decorative gradients, glassmorphism, or glossy luxury gold
- colored card backgrounds used as structural hierarchy
- rainbow chart legends or multiple competing accent hues
- low-contrast beige minimalism that compromises reading
- literal Japanese motifs pasted on top of generic UI components

### Visual Character

- Warm rice-paper canvas with raised paper panels separated by mist hairlines and quiet ruled sections.
- Active navigation uses a 2px indigo thread, underline, or left stitch rather than a filled blue pill.
- Long text areas use generous leading, narrow reading measures, and margin notes that feel like editorial annotations.
- Data tables are sparse ruled ledgers with tabular numerals and one indigo highlight series when emphasis is needed.
- Gold appears as a tiny knot, dot, seal, or hairline for verified provenance and completed milestones only.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Mist-colored hairlines, ruled ledger dividers, and indigo thread accents used as linework rather than decoration.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#B89B4D` |
| background | `#F7F3EA` |
| border | `#E7E1D6` |
| border_strong | `#D2C7B8` |
| error | `#9F3A32` |
| info | `#1F4E79` |
| muted | `#6E6A63` |
| primary | `#1F4E79` |
| primary_strong | `#173F63` |
| success | `#4F6F52` |
| surface | `#FBF9F3` |
| surface_subtle | `#F2EDE3` |
| text | `#171717` |
| warning | `#9A6A1F` |

### Motion

- **Duration**: 150ms
- **Easing**: cubic-bezier(0.2, 0, 0, 1)
- **Philosophy**: Motion is quiet and tactile: indigo threads draw in, paper panels settle by 1px, and focus rings clarify without bounce.

### Radii

- **Full**: 9999px
- **Lg**: 16px
- **Md**: 8px
- **None**: 0
- **Sm**: 2px

### Shadows

- **Lg**: 0 24px 60px rgba(23,23,23,0.08)
- **Md**: 0 10px 28px rgba(23,23,23,0.06)
- **Sm**: 0 1px 2px rgba(23,23,23,0.04)

### Spacing

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

### Surfaces

- **Bg Pattern**: Optional katagami-inspired micro-dot or cut-line pattern at very low contrast in margins only, never behind dense text.
- **Card Style**: Off-white paper panels with 1px mist borders, 16px radius at most, and little to no shadow.
- **Treatment**: Warm matte paper canvas with lightly raised paper panels and sparse ruled sections.

### Typography

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

## Rules

### Composition

Use a paper workspace with a centered 640-760px reading measure for primary text and modular side-context rails for sources, metadata, and woven threads. App-wide navigation may sit as a slim left rail or top strip, but active location is shown by a 2px indigo stitch/underline. Data views should use ruled tables, compact ledgers, and margin summaries instead of colored cards. Keep page chrome quiet so text and contextual relationships carry the experience.

### Density

Default density is calm editorial-product density: generous line height for reading, 24-32px section padding, compact but legible tables, and clear pauses between context clusters. Increase density through alignment, rules, and typography; do not add boxes or colored fills to make information look important.

### Hierarchy

Text hierarchy starts with sumi values, weight, size, and whitespace. Indigo is reserved for primary action, current navigation, links, selected rows, keyboard focus, and one key chart series. Gold thread is a ceremonial micro-accent for verified provenance, milestones, or premium annotations. Semantic success, warning, and error colors are muted and always accompanied by labels or icons.

### Signature Patterns

- The Indigo Thread: active nav, selected context, and primary path use a 2px indigo line, underline, or left stitch rather than a filled blue surface.
- Paper Ledger Rows: tables use warm ruled dividers, tabular numerals, and a tiny indigo notch for the selected row.
- Katagami Margin Notes: side annotations sit in cutout-like paper modules with dashed or hairline connectors back to the source text.
- Gold Knot Verification: verified provenance or completed milestones get a 6-8px muted gold dot/seal paired with text, never a gold CTA.
- Ink Wash State: hover and selected backgrounds are extremely pale indigo washes under 5% color area, with the line remaining the main signal.

## Layout

### Breakpoints

Mobile <= 640px stacks navigation, reading content, and context notes; tablet 641-1024px keeps the reading column first with collapsible context; desktop >= 1025px exposes the full woven workspace.

### Density

Editorial application density: roomy text, compact metadata, restrained controls, and sparse ledgers for data-heavy moments.

### Grid

Desktop uses a quiet 12-column workspace: optional 220px navigation rail, 640-760px central reading column, and a 280-340px context rail. Gutters follow the 8px spacing scale with 32px default page padding.

### Responsive

On small screens, context rails become inline expandable paper notes and data tables become ledger cards with the indigo stitch preserved for selection.

### Whitespace

Whitespace acts as ma: a functional pause around reading passages, source clusters, and decision points. Use paper margins before adding panels.

## Guidance

### Do

- Let typography, whitespace, and ruled structure create hierarchy before using color.
- Use indigo only for active path, focus, selected state, links, primary action, and one key data series.
- Keep gold as a small provenance or milestone signal paired with a label.
- Prefer underlines, left stitches, notches, and hairlines over filled colored panels.
- Use warm off-white paper surfaces to support long reading and reduce glare.
- Make data views feel like ledgers: sparse, aligned, tabular, and text-first.
- Style all controls with custom borders, hover states, and visible focus treatment.

### Don't

- Do not fill dashboards with saturated indigo tiles or blue chart palettes.
- Do not use gold as luxury gloss, gradients, large fills, or primary CTAs.
- Do not paste literal Japanese ornament into components; translate motifs into spacing, line, and restraint.
- Do not allow color area to exceed roughly 5% of a normal work screen.
- Do not rely on pale beige or gray text that fails contrast.
- Do not use browser-default form controls or generic rounded SaaS cards.
- Do not make every source, category, or thread a different color.

### Accessibility

Sumi text on paper surfaces must meet WCAG AA; indigo focus rings are at least 2px and visible against warm paper; gold is never the sole status indicator; muted semantic colors always include text labels or iconography.

### Usage Context

Best for AYA/Katagami workflows involving long-form text, research synthesis, source threading, provenance review, calm analytics, knowledge work, and contextual dashboards that should feel precise rather than busy.
DESIGN.md
---
version: "alpha"
name: "AYA Sumi Indigo Paper System"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#B89B4D"
  background: "#F7F3EA"
  border: "#E7E1D6"
  border_strong: "#D2C7B8"
  error: "#9F3A32"
  info: "#1F4E79"
  muted: "#6E6A63"
  primary: "#1F4E79"
  primary_strong: "#173F63"
  success: "#4F6F52"
  surface: "#FBF9F3"
  surface_subtle: "#F2EDE3"
  text: "#171717"
  warning: "#9A6A1F"
typography:
  headline-lg:
    fontFamily: "IBM Plex Sans"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.01em"
  headline-md:
    fontFamily: "IBM Plex Sans"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.01em"
  body-md:
    fontFamily: "Noto Sans"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.62
    letterSpacing: "-0.01em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "16px"
  md: "8px"
  none: "0px"
  sm: "2px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "40px"
  4xl: "48px"
  step-8: "64px"
  step-9: "80px"
  step-10: "104px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-border_strong:
    backgroundColor: "{colors.border_strong}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-primary_strong:
    backgroundColor: "{colors.primary_strong}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-surface_subtle:
    backgroundColor: "{colors.surface_subtle}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#ffffff"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  card-surface:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  input-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    height: "44px"
---

# AYA Sumi Indigo Paper System

## Overview

A restrained application design language for AYA, built from the feeling of black ink on warm rice paper with one continuous indigo thread for orientation, interaction, and continuity. The interface is designed for long-form reading, contextual weaving, and occasional data views without becoming dashboard-heavy. Most hierarchy comes from typography, paper surfaces, hairline rules, whitespace, and density changes; color appears only as a narrow signal. Indigo marks the active path, selected context, links, focus, and a single highlighted data series. A muted gold thread is reserved for provenance, verified milestones, and rare ceremonial annotations, never for primary action. The result should feel calm, precise, Japanese-inspired, and product-ready rather than themed or decorative.

### Values

- near-monochrome clarity for text-heavy workflows
- indigo as a connective thread rather than a decorative brand wash
- warm paper surfaces that reduce glare and support sustained reading
- katagami-like negative space, cut lines, and implied pattern over ornament
- component restraint: rules, underlines, notches, and borders before filled color
- high-contrast accessible text and focus states despite the quiet palette
- data views that remain editorial and sparse, never saturated dashboards

### Anti-Values

- blue SaaS dashboards with indigo spread across every tile
- decorative gradients, glassmorphism, or glossy luxury gold
- colored card backgrounds used as structural hierarchy
- rainbow chart legends or multiple competing accent hues
- low-contrast beige minimalism that compromises reading
- literal Japanese motifs pasted on top of generic UI components

### Visual Character

- Warm rice-paper canvas with raised paper panels separated by mist hairlines and quiet ruled sections.
- Active navigation uses a 2px indigo thread, underline, or left stitch rather than a filled blue pill.
- Long text areas use generous leading, narrow reading measures, and margin notes that feel like editorial annotations.
- Data tables are sparse ruled ledgers with tabular numerals and one indigo highlight series when emphasis is needed.
- Gold appears as a tiny knot, dot, seal, or hairline for verified provenance and completed milestones only.

## 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 | `#B89B4D` |
| background | `#F7F3EA` |
| border | `#E7E1D6` |
| border_strong | `#D2C7B8` |
| error | `#9F3A32` |
| info | `#1F4E79` |
| muted | `#6E6A63` |
| primary | `#1F4E79` |
| primary_strong | `#173F63` |
| success | `#4F6F52` |
| surface | `#FBF9F3` |
| surface_subtle | `#F2EDE3` |
| text | `#171717` |
| warning | `#9A6A1F` |

## Typography

- **Headline-Lg**: IBM Plex Sans, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: IBM Plex Sans, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: Noto Sans, 16px, weight 400, line-height 1.62.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

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

### Breakpoints

Mobile <= 640px stacks navigation, reading content, and context notes; tablet 641-1024px keeps the reading column first with collapsible context; desktop >= 1025px exposes the full woven workspace.

### Density

Editorial application density: roomy text, compact metadata, restrained controls, and sparse ledgers for data-heavy moments.

### Grid

Desktop uses a quiet 12-column workspace: optional 220px navigation rail, 640-760px central reading column, and a 280-340px context rail. Gutters follow the 8px spacing scale with 32px default page padding.

### Responsive

On small screens, context rails become inline expandable paper notes and data tables become ledger cards with the indigo stitch preserved for selection.

### Whitespace

Whitespace acts as ma: a functional pause around reading passages, source clusters, and decision points. Use paper margins before adding panels.

## Elevation & Depth

### Shadows

- **Lg**: 0 24px 60px rgba(23,23,23,0.08)
- **Md**: 0 10px 28px rgba(23,23,23,0.06)
- **Sm**: 0 1px 2px rgba(23,23,23,0.04)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `16px`
- **Md**: `8px`
- **None**: `0px`
- **Sm**: `2px`

### Surfaces

- **Bg Pattern**: Optional katagami-inspired micro-dot or cut-line pattern at very low contrast in margins only, never behind dense text.
- **Card Style**: Off-white paper panels with 1px mist borders, 16px radius at most, and little to no shadow.
- **Treatment**: Warm matte paper canvas with lightly raised paper panels and sparse ruled sections.

### Borders

- **Accent Width**: 2px
- **Character**: Mist-colored hairlines, ruled ledger dividers, and indigo thread accents used as linework rather than decoration.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use a paper workspace with a centered 640-760px reading measure for primary text and modular side-context rails for sources, metadata, and woven threads. App-wide navigation may sit as a slim left rail or top strip, but active location is shown by a 2px indigo stitch/underline. Data views should use ruled tables, compact ledgers, and margin summaries instead of colored cards. Keep page chrome quiet so text and contextual relationships carry the experience.

### Density

Default density is calm editorial-product density: generous line height for reading, 24-32px section padding, compact but legible tables, and clear pauses between context clusters. Increase density through alignment, rules, and typography; do not add boxes or colored fills to make information look important.

### Hierarchy

Text hierarchy starts with sumi values, weight, size, and whitespace. Indigo is reserved for primary action, current navigation, links, selected rows, keyboard focus, and one key chart series. Gold thread is a ceremonial micro-accent for verified provenance, milestones, or premium annotations. Semantic success, warning, and error colors are muted and always accompanied by labels or icons.

### Signature Patterns

- The Indigo Thread: active nav, selected context, and primary path use a 2px indigo line, underline, or left stitch rather than a filled blue surface.
- Paper Ledger Rows: tables use warm ruled dividers, tabular numerals, and a tiny indigo notch for the selected row.
- Katagami Margin Notes: side annotations sit in cutout-like paper modules with dashed or hairline connectors back to the source text.
- Gold Knot Verification: verified provenance or completed milestones get a 6-8px muted gold dot/seal paired with text, never a gold CTA.
- Ink Wash State: hover and selected backgrounds are extremely pale indigo washes under 5% color area, with the line remaining the main signal.

## 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-019ee039-d1ea-77d1-8244-17614ca1809a/DESIGN.with-shadcn.md`.

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

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

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

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

## Do's and Don'ts

- Do Let typography, whitespace, and ruled structure create hierarchy before using color.
- Do Use indigo only for active path, focus, selected state, links, primary action, and one key data series.
- Do Keep gold as a small provenance or milestone signal paired with a label.
- Do Prefer underlines, left stitches, notches, and hairlines over filled colored panels.
- Do Use warm off-white paper surfaces to support long reading and reduce glare.
- Do Make data views feel like ledgers: sparse, aligned, tabular, and text-first.
- Do Style all controls with custom borders, hover states, and visible focus treatment.
- Don't Do not fill dashboards with saturated indigo tiles or blue chart palettes.
- Don't Do not use gold as luxury gloss, gradients, large fills, or primary CTAs.
- Don't Do not paste literal Japanese ornament into components; translate motifs into spacing, line, and restraint.
- Don't Do not allow color area to exceed roughly 5% of a normal work screen.
- Don't Do not rely on pale beige or gray text that fails contrast.
- Don't Do not use browser-default form controls or generic rounded SaaS cards.
- Don't Do not make every source, category, or thread a different color.

### Accessibility

Sumi text on paper surfaces must meet WCAG AA; indigo focus rings are at least 2px and visible against warm paper; gold is never the sole status indicator; muted semantic colors always include text labels or iconography.

### Usage Context

Best for AYA/Katagami workflows involving long-form text, research synthesis, source threading, provenance review, calm analytics, knowledge work, and contextual dashboards that should feel precise rather than busy.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "aya-sumi-indigo-paper-system",
  "type": "registry:theme",
  "title": "AYA Sumi Indigo Paper System shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F3EA",
      "foreground": "#171717",
      "card": "#FBF9F3",
      "card-foreground": "#171717",
      "popover": "#FBF9F3",
      "popover-foreground": "#171717",
      "primary": "#1F4E79",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#6E6A63",
      "muted-foreground": "#171717",
      "accent": "#B89B4D",
      "accent-foreground": "#ffffff",
      "destructive": "#9F3A32",
      "border": "#E7E1D6",
      "input": "#E7E1D6",
      "ring": "#B89B4D",
      "chart-1": "#1F4E79",
      "chart-2": "#f4f4f5",
      "chart-3": "#B89B4D",
      "chart-4": "#4F6F52",
      "chart-5": "#9A6A1F",
      "sidebar": "#FBF9F3",
      "sidebar-foreground": "#171717",
      "sidebar-primary": "#1F4E79",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#1F4E79",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#E7E1D6",
      "sidebar-ring": "#B89B4D",
      "radius": "8px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1F4E79",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#B89B4D",
      "accent-foreground": "#ffffff",
      "destructive": "#9F3A32",
      "border": "#303642",
      "input": "#303642",
      "ring": "#B89B4D",
      "chart-1": "#1F4E79",
      "chart-2": "#f4f4f5",
      "chart-3": "#B89B4D",
      "chart-4": "#4F6F52",
      "chart-5": "#9A6A1F",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1F4E79",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#B89B4D",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#B89B4D",
      "radius": "8px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019ee039-d1ea-77d1-8244-17614ca1809a",
    "slug": "aya-sumi-indigo-paper-system",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "border_strong",
        "error",
        "info",
        "muted",
        "primary",
        "primary_strong",
        "success",
        "surface",
        "surface_subtle",
        "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_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

Design Language Preview

AYA Sumi Indigo Paper System

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-lgIBM Plex Sans · 28px · 700

The quick brown fox jumps

headline-mdIBM Plex Sans · 23px · 600

The quick brown fox jumps

body-mdNoto Sans · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

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

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl40px
  • 4xl48px
  • step-864px
  • step-980px
  • step-10104px

Shape

full9999px
lg16px
md8px
none0px
sm2px
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: #F7F3EA;
  --foreground: #171717;
  --card: #FBF9F3;
  --card-foreground: #171717;
  --popover: #FBF9F3;
  --popover-foreground: #171717;
  --primary: #1F4E79;
  --primary-foreground: #ffffff;
  --secondary: #f4f4f5;
  --secondary-foreground: #111111;
  --muted: #6E6A63;
  --muted-foreground: #171717;
  --accent: #B89B4D;
  --accent-foreground: #ffffff;
  --destructive: #9F3A32;
  --border: #E7E1D6;
  --input: #E7E1D6;
  --ring: #B89B4D;
  --chart-1: #1F4E79;
  --chart-2: #f4f4f5;
  --chart-3: #B89B4D;
  --chart-4: #4F6F52;
  --chart-5: #9A6A1F;
  --sidebar: #FBF9F3;
  --sidebar-foreground: #171717;
  --sidebar-primary: #1F4E79;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #1F4E79;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #E7E1D6;
  --sidebar-ring: #B89B4D;
  --radius: 8px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #1F4E79;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #B89B4D;
  --accent-foreground: #ffffff;
  --destructive: #9F3A32;
  --border: #303642;
  --input: #303642;
  --ring: #B89B4D;
  --chart-1: #1F4E79;
  --chart-2: #f4f4f5;
  --chart-3: #B89B4D;
  --chart-4: #4F6F52;
  --chart-5: #9A6A1F;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #1F4E79;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #B89B4D;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #B89B4D;
  --radius: 8px;
}
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 AyaSumiIndigoPaperSystemShadcnKit() {
  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 Sumi Indigo Paper System</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-sumi-indigo-paper-system",
  "type": "registry:theme",
  "title": "AYA Sumi Indigo Paper System shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F3EA",
      "foreground": "#171717",
      "card": "#FBF9F3",
      "card-foreground": "#171717",
      "popover": "#FBF9F3",
      "popover-foreground": "#171717",
      "primary": "#1F4E79",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#6E6A63",
      "muted-foreground": "#171717",
      "accent": "#B89B4D",
      "accent-foreground": "#ffffff",
      "destructive": "#9F3A32",
      "border": "#E7E1D6",
      "input": "#E7E1D6",
      "ring": "#B89B4D",
      "chart-1": "#1F4E79",
      "chart-2": "#f4f4f5",
      "chart-3": "#B89B4D",
      "chart-4": "#4F6F52",
      "chart-5": "#9A6A1F",
      "sidebar": "#FBF9F3",
      "sidebar-foreground": "#171717",
      "sidebar-primary": "#1F4E79",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#1F4E79",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#E7E1D6",
      "sidebar-ring": "#B89B4D",
      "radius": "8px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1F4E79",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#B89B4D",
      "accent-foreground": "#ffffff",
      "destructive": "#9F3A32",
      "border": "#303642",
      "input": "#303642",
      "ring": "#B89B4D",
      "chart-1": "#1F4E79",
      "chart-2": "#f4f4f5",
      "chart-3": "#B89B4D",
      "chart-4": "#4F6F52",
      "chart-5": "#9A6A1F",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1F4E79",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#B89B4D",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#B89B4D",
      "radius": "8px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019ee039-d1ea-77d1-8244-17614ca1809a",
    "slug": "aya-sumi-indigo-paper-system",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "border_strong",
        "error",
        "info",
        "muted",
        "primary",
        "primary_strong",
        "success",
        "surface",
        "surface_subtle",
        "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_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
component recipescompatibility fallback
# AYA Sumi Indigo Paper System shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019ee039-d1ea-77d1-8244-17614ca1809a`
Slug: `aya-sumi-indigo-paper-system`

## Intent

A restrained application design language for AYA, built from the feeling of black ink on warm rice paper with one continuous indigo thread for orientation, interaction, and continuity. The interface is designed for long-form reading, contextual weaving, and occasional data views without becoming dashboard-heavy. Most hierarchy comes from typography, paper surfaces, hairline rules, whitespace, and density changes; color appears only as a narrow signal. Indigo marks the active path, selected context, links, focus, and a single highlighted data series. A muted gold thread is reserved for provenance, verified milestones, and rare ceremonial annotations, never for primary action. The result should feel calm, precise, Japanese-inspired, and product-ready rather than themed or decorative.

## 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": "#B89B4D",
  "background": "#F7F3EA",
  "border": "#E7E1D6",
  "border_strong": "#D2C7B8",
  "error": "#9F3A32",
  "info": "#1F4E79",
  "muted": "#6E6A63",
  "primary": "#1F4E79",
  "primary_strong": "#173F63",
  "success": "#4F6F52",
  "surface": "#FBF9F3",
  "surface_subtle": "#F2EDE3",
  "text": "#171717",
  "warning": "#9A6A1F"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Noto Sans",
  "display_font": "Noto Serif JP",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600;700&family=Noto+Sans:wght@400;500;600;700&family=Noto+Serif+JP:wght@500;600;700&display=swap",
  "heading_font": "IBM Plex Sans",
  "letter_spacing": "-0.01em",
  "line_height": 1.62,
  "mono_font": "IBM Plex Mono",
  "scale_ratio": 1.2
}

## Visual character to preserve

- Warm rice-paper canvas with raised paper panels separated by mist hairlines and quiet ruled sections.
- Active navigation uses a 2px indigo thread, underline, or left stitch rather than a filled blue pill.
- Long text areas use generous leading, narrow reading measures, and margin notes that feel like editorial annotations.
- Data tables are sparse ruled ledgers with tabular numerals and one indigo highlight series when emphasis is needed.
- Gold appears as a tiny knot, dot, seal, or hairline for verified provenance and completed milestones only.

## ShadSync visual profile

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

## Signature component recipes

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

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

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

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

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

## Preview shots

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

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/aya-sumi-indigo-paper-system/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Let typography, whitespace, and ruled structure create hierarchy before using color.; Use indigo only for active path, focus, selected state, links, primary action, and one key data series.; Keep gold as a small provenance or milestone signal paired with a label.; Prefer underlines, left stitches, notches, and hairlines over filled colored panels.; Use warm off-white paper surfaces to support long reading and reduce glare.; Make data views feel like ledgers: sparse, aligned, tabular, and text-first.; Style all controls with custom borders, hover states, and visible focus treatment.
- Do not: Do not fill dashboards with saturated indigo tiles or blue chart palettes.; Do not use gold as luxury gloss, gradients, large fills, or primary CTAs.; Do not paste literal Japanese ornament into components; translate motifs into spacing, line, and restraint.; Do not allow color area to exceed roughly 5% of a normal work screen.; Do not rely on pale beige or gray text that fails contrast.; Do not use browser-default form controls or generic rounded SaaS cards.; Do not make every source, category, or thread a different color.

## 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 AyaSumiIndigoPaperSystemShadcnKit() {
  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 Sumi Indigo Paper System</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 stacks navigation, reading content, and context notes; tablet 641-1024px keeps the reading column first with collapsible context; desktop >= 1025px exposes the full woven workspace.",
  "density": "Editorial application density: roomy text, compact metadata, restrained controls, and sparse ledgers for data-heavy moments.",
  "grid": "Desktop uses a quiet 12-column workspace: optional 220px navigation rail, 640-760px central reading column, and a 280-340px context rail. Gutters follow the 8px spacing scale with 32px default page padding.",
  "responsive": "On small screens, context rails become inline expandable paper notes and data tables become ledger cards with the indigo stitch preserved for selection.",
  "whitespace": "Whitespace acts as ma: a functional pause around reading passages, source clusters, and decision points. Use paper margins before adding panels."
}
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-019ee039-d1ea-77d1-8244-17614ca1809a",
    "name": "AYA Sumi Indigo Paper System",
    "slug": "aya-sumi-indigo-paper-system"
  },
  "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 rice-paper canvas with raised paper panels separated by mist hairlines and quiet ruled sections.",
    "Active navigation uses a 2px indigo thread, underline, or left stitch rather than a filled blue pill.",
    "Long text areas use generous leading, narrow reading measures, and margin notes that feel like editorial annotations.",
    "Data tables are sparse ruled ledgers with tabular numerals and one indigo highlight series when emphasis is needed.",
    "Gold appears as a tiny knot, dot, seal, or hairline for verified provenance and completed milestones only."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "pebble",
    "border": "dashed",
    "underlay": false,
    "grain": true,
    "stickerBadges": false,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "AYA Sumi Indigo Paper System launch room",
        "description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
        "primaryAction": "Apply theme",
        "secondaryAction": "Review states",
        "stats": [
          {
            "label": "components",
            "value": "16",
            "tone": "accent"
          },
          {
            "label": "states",
            "value": "ready"
          },
          {
            "label": "density",
            "value": "balanced",
            "tone": "warning"
          }
        ],
        "rows": [
          {
            "label": "Primary flow",
            "value": "mapped",
            "status": "active"
          },
          {
            "label": "Token coverage",
            "value": "semantic",
            "status": "synced"
          },
          {
            "label": "Responsive proof",
            "value": "queued",
            "status": "review"
          }
        ],
        "statuses": [
          "Active",
          "Synced",
          "Draft"
        ]
      }
    },
    {
      "id": "detail-editor",
      "title": "Detail editor",
      "viewport": "tablet",
      "primitives": [
        "button",
        "card",
        "input",
        "textarea",
        "select",
        "checkbox",
        "switch",
        "slider",
        "dialog",
        "sheet"
      ],
      "composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
      "mustShow": [
        "focus ring",
        "error or destructive state",
        "dialog or sheet treatment",
        "written guidance content"
      ],
      "avoid": [
        "unstyled browser controls",
        "floating cards inside cards",
        "missing labels"
      ],
      "scene": {
        "eyebrow": "editing flow",
        "headline": "Language recipe editor",
        "description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
        "primaryAction": "Save recipe",
        "secondaryAction": "Open sheet",
        "fields": [
          {
            "label": "Component family",
            "value": "Narrative cards"
          },
          {
            "label": "State treatment",
            "value": "Visible focus + validation"
          },
          {
            "label": "Motion",
            "value": "Small lift, no opacity-only fade"
          }
        ],
        "statuses": [
          "Focus",
          "Invalid",
          "Confirmed"
        ]
      }
    },
    {
      "id": "data-operations",
      "title": "Data operations",
      "viewport": "mobile",
      "primitives": [
        "button",
        "tabs",
        "badge",
        "dropdown-menu",
        "table",
        "tooltip",
        "separator"
      ],
      "composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
      "mustShow": [
        "responsive reflow",
        "dense row styling",
        "menu affordance",
        "status badge system"
      ],
      "avoid": [
        "desktop-only tables",
        "text overflow",
        "default shadcn spacing without Katagami character"
      ],
      "scene": {
        "eyebrow": "operations",
        "headline": "Compact review queue",
        "description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
        "primaryAction": "Resolve",
        "secondaryAction": "Filter",
        "rows": [
          {
            "label": "Button hierarchy",
            "value": "approved",
            "status": "ok"
          },
          {
            "label": "Table rhythm",
            "value": "needs pass",
            "status": "watch"
          },
          {
            "label": "Empty state",
            "value": "designed",
            "status": "done"
          }
        ],
        "statuses": [
          "Queued",
          "Blocked",
          "Done"
        ]
      }
    }
  ],
  "componentRecipes": [
    {
      "primitive": "button",
      "intent": "Prove action hierarchy, focus, disabled, and destructive states."
    },
    {
      "primitive": "card",
      "intent": "Carry the language surface, border, elevation, and density rules."
    },
    {
      "primitive": "input",
      "intent": "Show labels, focus rings, validation, and spacing rhythm."
    },
    {
      "primitive": "textarea",
      "intent": "Show longer guidance, validation copy, and writing density."
    },
    {
      "primitive": "select",
      "intent": "Show filtering, selection contrast, and menu trigger styling."
    },
    {
      "primitive": "dialog",
      "intent": "Show centered decision states and overlay treatment."
    },
    {
      "primitive": "sheet",
      "intent": "Show contextual side panels and responsive editing."
    },
    {
      "primitive": "tabs",
      "intent": "Show navigational structure and active/inactive contrast."
    },
    {
      "primitive": "badge",
      "intent": "Show compact status vocabulary and semantic colors."
    },
    {
      "primitive": "separator",
      "intent": "Show section rhythm without generic gray dividers."
    },
    {
      "primitive": "checkbox",
      "intent": "Show binary selection with visible focus and checked states."
    },
    {
      "primitive": "switch",
      "intent": "Show settings toggles and on/off contrast."
    },
    {
      "primitive": "slider",
      "intent": "Show numeric adjustment with track/thumb styling."
    },
    {
      "primitive": "tooltip",
      "intent": "Show concise explanation styling above compact controls."
    },
    {
      "primitive": "dropdown-menu",
      "intent": "Show action menus, destructive items, and grouped choices."
    },
    {
      "primitive": "table",
      "intent": "Show dense operational data, separators, row states, and responsive behavior."
    }
  ],
  "qualityRules": {
    "do": [
      "Let typography, whitespace, and ruled structure create hierarchy before using color.",
      "Use indigo only for active path, focus, selected state, links, primary action, and one key data series.",
      "Keep gold as a small provenance or milestone signal paired with a label.",
      "Prefer underlines, left stitches, notches, and hairlines over filled colored panels.",
      "Use warm off-white paper surfaces to support long reading and reduce glare.",
      "Make data views feel like ledgers: sparse, aligned, tabular, and text-first.",
      "Style all controls with custom borders, hover states, and visible focus treatment."
    ],
    "dont": [
      "Do not fill dashboards with saturated indigo tiles or blue chart palettes.",
      "Do not use gold as luxury gloss, gradients, large fills, or primary CTAs.",
      "Do not paste literal Japanese ornament into components; translate motifs into spacing, line, and restraint.",
      "Do not allow color area to exceed roughly 5% of a normal work screen.",
      "Do not rely on pale beige or gray text that fails contrast.",
      "Do not use browser-default form controls or generic rounded SaaS cards.",
      "Do not make every source, category, or thread a different color."
    ]
  }
}
related

More like this