back to gallery
design language·aya-sumi-indigo-operational-minimalism

AYA Sumi Indigo Operational Minimalism

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
Sumi Indigo Operational Minimalism defines AYA as a calm, text-led operational workspace: crisp neutral planes, graphite/sumi typography, pale ai-nezumi blue-grey surfaces, and indigo semantic accents turn metrics, status, provenance, and document analytics into quiet inline signals rather than dashboard spectacle.
values
Keep documents and decisions primary; operational data supports the reading flow as margin signals, inline chips, compact tables, and contextual panels.Make density precise but breathable through tokenized spacing, clear type hierarchy, hairline dividers, and short measure lengths for long-form work.Use color semantically and sparingly: indigo for primary action and focus, softened state colors for status, persimmon only for rare errors or unresolved warmth.Prefer keyboard-first workflows, visible focus states, deterministic component behavior, and enterprise-grade affordances over playful personality.Translate Japanese restraint through sumi ink weight, negative space, rhythm, and material quietness; never through decorative icons, motifs, or tourist references.
anti-values
×No generic SaaS gradients, neon accents, glassmorphism, oversized KPI cards, or dashboard-first layouts.×No playful mascots, decorative Japanese icons, waves, lanterns, fans, seals, or ornamental pattern borders.×No saturated traffic-light UI; state colors must be softened, labeled, and accessible.×No equal marketing card grids or empty hero sections; the language is for a working product surface.×No decorative analytics that compete with text, sources, or decisions.
tokens
borders3 items
accent width
2px
default width
1px
style
solid graphite/blue-grey hairlines; left-edge semantic ticks for status and active context
colors17 items
accent
#27466F
background
#F7F7F4
border
#D9DEDF
border_strong
#AEB8BC
error
#B05A45
focus
#2F5E9E
info
#3F6387
primary
#27466F
primary_hover
#203A5D
primary_soft
#E4EBF3
success
#557463
surface
#FFFFFF
surface_alt
#EEF2F4
surface_subtle
#F1F3F1
text
#1F2426
text_muted
#5F686D
warning
#9B7445
motion3 items
duration
120ms-180ms
easing
cubic-bezier(0.2, 0, 0, 1)
philosophy
Fast operational confirmation only: focus, drawer reveal, row expansion, and command palette transitions.
radii5 items
character
Small, consistent radii; no bubbly SaaS rounding.
lg
10px
md
6px
pill
999px
sm
4px
shadow3 items
md
0 8px 24px rgba(31,36,38,0.08)
philosophy
Use almost no shadow; depth comes from tint, rule, and hierarchy.
sm
0 1px 2px rgba(31,36,38,0.05)
spacing3 items
density
Compact 8-12px internal gaps, 16-24px module gaps, 32-48px document pauses.
tokens
4px, 8px, 12px, 16px, 24px, 32px, 48px
unit
4px
typography5 items
font family
Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, sans-serif
line height
1.35 for dense UI, 1.55 for document reading, 1.2 for labels
mono family
IBM Plex Mono, ui-monospace, SFMono-Regular, Menlo, monospace
scale
12px captions, 13px dense controls, 14px body/work rows, 16px document lead, 20-24px section titles
weight
400 body, 500 controls, 600 headings and key labels; avoid heavy display weights
rules
accessibility
Meet WCAG AA for text and controls; all status colors require text labels or shape cues; focus rings must be clearly visible on neutral and tinted surfaces; keyboard navigation and command palette access are first-class.
composition
Lead with an operational document/workspace view, not a dashboard. Place quiet status, source confidence, small metrics, and review state adjacent to the relevant paragraph, row, or decision. Use thin dividers, pale ai-nezumi panels, and compact rails to weave context around the primary text.
density
Keep dense controls legible: minimum 13px labels, 14px row text, 32px touch/click targets where practical, 8px chip padding, and clear hover/focus states. Avoid cramming unrelated metrics into cards.
hierarchy
Hierarchy is created by sumi/graphite text weight, alignment, row grouping, indigo focus/action states, and subtle blue-grey surfaces. Headings are modest; tables and annotations should feel designed for repeated expert use.
signature patterns
Inline operational chips: small rounded labels with text + semantic color tick, used for source status, confidence, review state, and workflow phase.Document-adjacent metric strips: 2-4 tiny measures placed in a margin or header row with labels first and numbers second; never large KPI cards.Ai-nezumi context panels: pale blue-grey side surfaces with hairline dividers, dense lists, source snippets, and keyboard-visible actions.Indigo command focus: command palette, active nav, selected rows, and primary actions use restrained indigo fill/outline plus a 2px accessible focus ring.Graphite rule lattice: tables, timelines, and provenance trails use fine dividers and aligned baselines to create calm operational structure.
layout
breakpoints

mobile <= 640px, tablet 641-1024px, desktop >= 1025px; rails collapse into drawers and document analytics become inline sections on narrow screens.

density
High information density with 14px rows, 32-40px toolbars, compact chips, and restrained panels; breathing room comes from grouped whitespace and calm surfaces rather than large cards.
grid
Desktop uses a document-centered 12-column workspace with a 240-280px navigation/context rail, a 640-760px primary text column, and a 280-360px inspector/analytics rail. Tables and comparison views may span full width but retain compact row rhythm.
responsive

Preserve document-first order: command bar, context/source trail, document body, inline metrics, then inspector details. Do not reorder into dashboard cards.

whitespace

Use 16-24px between functional groups and 32-48px around reading zones. Avoid empty landing-page expanses; every pause supports comprehension.

guidance
do
  • Use crisp neutral backgrounds, sumi/graphite typography, pale ai-nezumi panels, and indigo semantic accents.
  • Embed metrics inline beside documents, tables, source trails, and workflow rows.
  • Design status chips with labels, muted state colors, and small left-edge ticks or dots.
  • Prioritize keyboard-first interactions: command palette, skip links, row shortcuts, visible focus, and deterministic drawer behavior.
  • Keep surfaces quiet: hairline rules, subtle tints, minimal shadows, and compact typography.
  • Use persimmon only for rare error, unresolved, destructive, or attention states.
avoid
  • Do not create a dashboard-first home screen or oversized KPI-card grid.
  • Do not use neon, generic SaaS gradients, playful mascots, or decorative Japanese motifs/icons.
  • Do not rely on color alone for state or status.
  • Do not add decorative illustrations that compete with operational text.
  • Do not over-round components or use heavy shadows that make the workspace feel like consumer SaaS.
katagami spec
# AYA Sumi Indigo Operational Minimalism

## Philosophy

Sumi Indigo Operational Minimalism defines AYA as a calm, text-led operational workspace: crisp neutral planes, graphite/sumi typography, pale ai-nezumi blue-grey surfaces, and indigo semantic accents turn metrics, status, provenance, and document analytics into quiet inline signals rather than dashboard spectacle.

### Values

- Keep documents and decisions primary; operational data supports the reading flow as margin signals, inline chips, compact tables, and contextual panels.
- Make density precise but breathable through tokenized spacing, clear type hierarchy, hairline dividers, and short measure lengths for long-form work.
- Use color semantically and sparingly: indigo for primary action and focus, softened state colors for status, persimmon only for rare errors or unresolved warmth.
- Prefer keyboard-first workflows, visible focus states, deterministic component behavior, and enterprise-grade affordances over playful personality.
- Translate Japanese restraint through sumi ink weight, negative space, rhythm, and material quietness; never through decorative icons, motifs, or tourist references.

### Anti-Values

- No generic SaaS gradients, neon accents, glassmorphism, oversized KPI cards, or dashboard-first layouts.
- No playful mascots, decorative Japanese icons, waves, lanterns, fans, seals, or ornamental pattern borders.
- No saturated traffic-light UI; state colors must be softened, labeled, and accessible.
- No equal marketing card grids or empty hero sections; the language is for a working product surface.
- No decorative analytics that compete with text, sources, or decisions.

### Visual Character

- A crisp neutral canvas (#F7F7F4 to #FFFFFF) with sumi/graphite text, pale ai-nezumi blue-grey panels, and fine rule systems that organize information without heavy cards.
- Dense text rows, document excerpts, source trails, and compact analytics sit on the same baseline grid, with metrics embedded as small annotations rather than oversized KPI tiles.
- Status appears as low-chroma chips, left-edge ticks, table row flags, and short semantic labels paired with icons or text so color is never the only cue.
- Primary actions are indigo but mostly outline, text, or restrained filled controls; persimmon appears only for destructive/error warmth at small scale.
- Navigation and operations feel like an expert editor workspace: command palette, keyboard hints, side rail, source drawer, and narrow context panes around a document center.

## Tokens

### Borders

- **Accent Width**: 2px
- **Default Width**: 1px
- **Style**: solid graphite/blue-grey hairlines; left-edge semantic ticks for status and active context

### Colors

| Name | Value |
|------|-------|
| accent | `#27466F` |
| background | `#F7F7F4` |
| border | `#D9DEDF` |
| border_strong | `#AEB8BC` |
| error | `#B05A45` |
| focus | `#2F5E9E` |
| info | `#3F6387` |
| primary | `#27466F` |
| primary_hover | `#203A5D` |
| primary_soft | `#E4EBF3` |
| success | `#557463` |
| surface | `#FFFFFF` |
| surface_alt | `#EEF2F4` |
| surface_subtle | `#F1F3F1` |
| text | `#1F2426` |
| text_muted | `#5F686D` |
| warning | `#9B7445` |

### Motion

- **Duration**: 120ms-180ms
- **Easing**: cubic-bezier(0.2, 0, 0, 1)
- **Philosophy**: Fast operational confirmation only: focus, drawer reveal, row expansion, and command palette transitions.

### Radii

- **Character**: Small, consistent radii; no bubbly SaaS rounding.
- **Lg**: 10px
- **Md**: 6px
- **Pill**: 999px
- **Sm**: 4px

### Shadow

- **Md**: 0 8px 24px rgba(31,36,38,0.08)
- **Philosophy**: Use almost no shadow; depth comes from tint, rule, and hierarchy.
- **Sm**: 0 1px 2px rgba(31,36,38,0.05)

### Spacing

- **Density**: Compact 8-12px internal gaps, 16-24px module gaps, 32-48px document pauses.
- **Tokens**: ["4px","8px","12px","16px","24px","32px","48px"]
- **Unit**: 4px

### Typography

- **Font Family**: Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, sans-serif
- **Line Height**: 1.35 for dense UI, 1.55 for document reading, 1.2 for labels
- **Mono Family**: IBM Plex Mono, ui-monospace, SFMono-Regular, Menlo, monospace
- **Scale**: 12px captions, 13px dense controls, 14px body/work rows, 16px document lead, 20-24px section titles
- **Weight**: 400 body, 500 controls, 600 headings and key labels; avoid heavy display weights

## Rules

### Accessibility

Meet WCAG AA for text and controls; all status colors require text labels or shape cues; focus rings must be clearly visible on neutral and tinted surfaces; keyboard navigation and command palette access are first-class.

### Composition

Lead with an operational document/workspace view, not a dashboard. Place quiet status, source confidence, small metrics, and review state adjacent to the relevant paragraph, row, or decision. Use thin dividers, pale ai-nezumi panels, and compact rails to weave context around the primary text.

### Density

Keep dense controls legible: minimum 13px labels, 14px row text, 32px touch/click targets where practical, 8px chip padding, and clear hover/focus states. Avoid cramming unrelated metrics into cards.

### Hierarchy

Hierarchy is created by sumi/graphite text weight, alignment, row grouping, indigo focus/action states, and subtle blue-grey surfaces. Headings are modest; tables and annotations should feel designed for repeated expert use.

### Signature Patterns

- Inline operational chips: small rounded labels with text + semantic color tick, used for source status, confidence, review state, and workflow phase.
- Document-adjacent metric strips: 2-4 tiny measures placed in a margin or header row with labels first and numbers second; never large KPI cards.
- Ai-nezumi context panels: pale blue-grey side surfaces with hairline dividers, dense lists, source snippets, and keyboard-visible actions.
- Indigo command focus: command palette, active nav, selected rows, and primary actions use restrained indigo fill/outline plus a 2px accessible focus ring.
- Graphite rule lattice: tables, timelines, and provenance trails use fine dividers and aligned baselines to create calm operational structure.

## Layout

### Breakpoints

mobile <= 640px, tablet 641-1024px, desktop >= 1025px; rails collapse into drawers and document analytics become inline sections on narrow screens.

### Density

High information density with 14px rows, 32-40px toolbars, compact chips, and restrained panels; breathing room comes from grouped whitespace and calm surfaces rather than large cards.

### Grid

Desktop uses a document-centered 12-column workspace with a 240-280px navigation/context rail, a 640-760px primary text column, and a 280-360px inspector/analytics rail. Tables and comparison views may span full width but retain compact row rhythm.

### Responsive

Preserve document-first order: command bar, context/source trail, document body, inline metrics, then inspector details. Do not reorder into dashboard cards.

### Whitespace

Use 16-24px between functional groups and 32-48px around reading zones. Avoid empty landing-page expanses; every pause supports comprehension.

## Guidance

### Do

- Use crisp neutral backgrounds, sumi/graphite typography, pale ai-nezumi panels, and indigo semantic accents.
- Embed metrics inline beside documents, tables, source trails, and workflow rows.
- Design status chips with labels, muted state colors, and small left-edge ticks or dots.
- Prioritize keyboard-first interactions: command palette, skip links, row shortcuts, visible focus, and deterministic drawer behavior.
- Keep surfaces quiet: hairline rules, subtle tints, minimal shadows, and compact typography.
- Use persimmon only for rare error, unresolved, destructive, or attention states.

### Don't

- Do not create a dashboard-first home screen or oversized KPI-card grid.
- Do not use neon, generic SaaS gradients, playful mascots, or decorative Japanese motifs/icons.
- Do not rely on color alone for state or status.
- Do not add decorative illustrations that compete with operational text.
- Do not over-round components or use heavy shadows that make the workspace feel like consumer SaaS.

### Accessibility

Use high-contrast sumi text, restrained but visible indigo focus rings, state labels with non-color cues, and compact targets that remain operable by keyboard and pointer.

### Usage Context

Best for AYA-style knowledge workspaces, document review, research synthesis, source analysis, enterprise workflows, operational copilots, and tools where dense context must remain calm and readable.
DESIGN.md
---
version: "alpha"
name: "AYA Sumi Indigo Operational Minimalism"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#27466F"
  background: "#F7F7F4"
  border: "#D9DEDF"
  border_strong: "#AEB8BC"
  error: "#B05A45"
  focus: "#2F5E9E"
  info: "#3F6387"
  primary: "#27466F"
  primary_hover: "#203A5D"
  primary_soft: "#E4EBF3"
  success: "#557463"
  surface: "#FFFFFF"
  surface_alt: "#EEF2F4"
  surface_subtle: "#F1F3F1"
  text: "#1F2426"
  text_muted: "#5F686D"
  warning: "#9B7445"
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"
rounded:
  character: "0px"
  lg: "10px"
  md: "6px"
  pill: "999px"
  sm: "4px"
spacing:
  density: "Compact 8-12px internal gaps, 16-24px module gaps, 32-48px document pauses."
  unit: "4px"
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-focus:
    backgroundColor: "{colors.focus}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-primary_hover:
    backgroundColor: "{colors.primary_hover}"
  color-reference-primary_soft:
    backgroundColor: "{colors.primary_soft}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-surface_alt:
    backgroundColor: "{colors.surface_alt}"
  color-reference-surface_subtle:
    backgroundColor: "{colors.surface_subtle}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-text_muted:
    backgroundColor: "{colors.text_muted}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#ffffff"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: "12px"
  card-surface:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    padding: "16px"
  input-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    height: "44px"
---

# AYA Sumi Indigo Operational Minimalism

## Overview

Sumi Indigo Operational Minimalism defines AYA as a calm, text-led operational workspace: crisp neutral planes, graphite/sumi typography, pale ai-nezumi blue-grey surfaces, and indigo semantic accents turn metrics, status, provenance, and document analytics into quiet inline signals rather than dashboard spectacle.

### Values

- Keep documents and decisions primary; operational data supports the reading flow as margin signals, inline chips, compact tables, and contextual panels.
- Make density precise but breathable through tokenized spacing, clear type hierarchy, hairline dividers, and short measure lengths for long-form work.
- Use color semantically and sparingly: indigo for primary action and focus, softened state colors for status, persimmon only for rare errors or unresolved warmth.
- Prefer keyboard-first workflows, visible focus states, deterministic component behavior, and enterprise-grade affordances over playful personality.
- Translate Japanese restraint through sumi ink weight, negative space, rhythm, and material quietness; never through decorative icons, motifs, or tourist references.

### Anti-Values

- No generic SaaS gradients, neon accents, glassmorphism, oversized KPI cards, or dashboard-first layouts.
- No playful mascots, decorative Japanese icons, waves, lanterns, fans, seals, or ornamental pattern borders.
- No saturated traffic-light UI; state colors must be softened, labeled, and accessible.
- No equal marketing card grids or empty hero sections; the language is for a working product surface.
- No decorative analytics that compete with text, sources, or decisions.

### Visual Character

- A crisp neutral canvas (#F7F7F4 to #FFFFFF) with sumi/graphite text, pale ai-nezumi blue-grey panels, and fine rule systems that organize information without heavy cards.
- Dense text rows, document excerpts, source trails, and compact analytics sit on the same baseline grid, with metrics embedded as small annotations rather than oversized KPI tiles.
- Status appears as low-chroma chips, left-edge ticks, table row flags, and short semantic labels paired with icons or text so color is never the only cue.
- Primary actions are indigo but mostly outline, text, or restrained filled controls; persimmon appears only for destructive/error warmth at small scale.
- Navigation and operations feel like an expert editor workspace: command palette, keyboard hints, side rail, source drawer, and narrow context panes around a document center.

## 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 | `#27466F` |
| background | `#F7F7F4` |
| border | `#D9DEDF` |
| border_strong | `#AEB8BC` |
| error | `#B05A45` |
| focus | `#2F5E9E` |
| info | `#3F6387` |
| primary | `#27466F` |
| primary_hover | `#203A5D` |
| primary_soft | `#E4EBF3` |
| success | `#557463` |
| surface | `#FFFFFF` |
| surface_alt | `#EEF2F4` |
| surface_subtle | `#F1F3F1` |
| text | `#1F2426` |
| text_muted | `#5F686D` |
| warning | `#9B7445` |

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

- **Density**: `Compact 8-12px internal gaps, 16-24px module gaps, 32-48px document pauses.`
- **Unit**: `4px`

### Breakpoints

mobile <= 640px, tablet 641-1024px, desktop >= 1025px; rails collapse into drawers and document analytics become inline sections on narrow screens.

### Density

High information density with 14px rows, 32-40px toolbars, compact chips, and restrained panels; breathing room comes from grouped whitespace and calm surfaces rather than large cards.

### Grid

Desktop uses a document-centered 12-column workspace with a 240-280px navigation/context rail, a 640-760px primary text column, and a 280-360px inspector/analytics rail. Tables and comparison views may span full width but retain compact row rhythm.

### Responsive

Preserve document-first order: command bar, context/source trail, document body, inline metrics, then inspector details. Do not reorder into dashboard cards.

### Whitespace

Use 16-24px between functional groups and 32-48px around reading zones. Avoid empty landing-page expanses; every pause supports comprehension.

## Shapes

### Rounded

- **Character**: `0px`
- **Lg**: `10px`
- **Md**: `6px`
- **Pill**: `999px`
- **Sm**: `4px`

### Borders

- **Accent Width**: 2px
- **Default Width**: 1px
- **Style**: solid graphite/blue-grey hairlines; left-edge semantic ticks for status and active context

## Components

### Accessibility

Meet WCAG AA for text and controls; all status colors require text labels or shape cues; focus rings must be clearly visible on neutral and tinted surfaces; keyboard navigation and command palette access are first-class.

### Composition

Lead with an operational document/workspace view, not a dashboard. Place quiet status, source confidence, small metrics, and review state adjacent to the relevant paragraph, row, or decision. Use thin dividers, pale ai-nezumi panels, and compact rails to weave context around the primary text.

### Density

Keep dense controls legible: minimum 13px labels, 14px row text, 32px touch/click targets where practical, 8px chip padding, and clear hover/focus states. Avoid cramming unrelated metrics into cards.

### Hierarchy

Hierarchy is created by sumi/graphite text weight, alignment, row grouping, indigo focus/action states, and subtle blue-grey surfaces. Headings are modest; tables and annotations should feel designed for repeated expert use.

### Signature Patterns

- Inline operational chips: small rounded labels with text + semantic color tick, used for source status, confidence, review state, and workflow phase.
- Document-adjacent metric strips: 2-4 tiny measures placed in a margin or header row with labels first and numbers second; never large KPI cards.
- Ai-nezumi context panels: pale blue-grey side surfaces with hairline dividers, dense lists, source snippets, and keyboard-visible actions.
- Indigo command focus: command palette, active nav, selected rows, and primary actions use restrained indigo fill/outline plus a 2px accessible focus ring.
- Graphite rule lattice: tables, timelines, and provenance trails use fine dividers and aligned baselines to create calm operational structure.

## shadcn/ui Usage

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

DESIGN.md with shadcn: `/language/aya-sumi-indigo-operational-minimalism/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 crisp neutral backgrounds, sumi/graphite typography, pale ai-nezumi panels, and indigo semantic accents.
- Do Embed metrics inline beside documents, tables, source trails, and workflow rows.
- Do Design status chips with labels, muted state colors, and small left-edge ticks or dots.
- Do Prioritize keyboard-first interactions: command palette, skip links, row shortcuts, visible focus, and deterministic drawer behavior.
- Do Keep surfaces quiet: hairline rules, subtle tints, minimal shadows, and compact typography.
- Do Use persimmon only for rare error, unresolved, destructive, or attention states.
- Don't Do not create a dashboard-first home screen or oversized KPI-card grid.
- Don't Do not use neon, generic SaaS gradients, playful mascots, or decorative Japanese motifs/icons.
- Don't Do not rely on color alone for state or status.
- Don't Do not add decorative illustrations that compete with operational text.
- Don't Do not over-round components or use heavy shadows that make the workspace feel like consumer SaaS.

### Accessibility

Use high-contrast sumi text, restrained but visible indigo focus rings, state labels with non-color cues, and compact targets that remain operable by keyboard and pointer.

### Usage Context

Best for AYA-style knowledge workspaces, document review, research synthesis, source analysis, enterprise workflows, operational copilots, and tools where dense context must remain calm and readable.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "aya-sumi-indigo-operational-minimalism",
  "type": "registry:theme",
  "title": "AYA Sumi Indigo Operational Minimalism shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F7F4",
      "foreground": "#1F2426",
      "card": "#FFFFFF",
      "card-foreground": "#1F2426",
      "popover": "#FFFFFF",
      "popover-foreground": "#1F2426",
      "primary": "#27466F",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#f4f4f5",
      "muted-foreground": "#1F2426",
      "accent": "#27466F",
      "accent-foreground": "#ffffff",
      "destructive": "#B05A45",
      "border": "#D9DEDF",
      "input": "#D9DEDF",
      "ring": "#27466F",
      "chart-1": "#27466F",
      "chart-2": "#f4f4f5",
      "chart-3": "#27466F",
      "chart-4": "#557463",
      "chart-5": "#9B7445",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#1F2426",
      "sidebar-primary": "#27466F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#3F6387",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D9DEDF",
      "sidebar-ring": "#27466F",
      "radius": "6px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#27466F",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#27466F",
      "accent-foreground": "#ffffff",
      "destructive": "#B05A45",
      "border": "#303642",
      "input": "#303642",
      "ring": "#27466F",
      "chart-1": "#27466F",
      "chart-2": "#f4f4f5",
      "chart-3": "#27466F",
      "chart-4": "#557463",
      "chart-5": "#9B7445",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#27466F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#27466F",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#27466F",
      "radius": "6px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "aya-sumi-indigo-operational-minimalism",
    "slug": "aya-sumi-indigo-operational-minimalism",
    "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",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "border_strong",
        "error",
        "focus",
        "info",
        "primary",
        "primary_hover",
        "primary_soft",
        "success",
        "surface",
        "surface_alt",
        "surface_subtle",
        "text",
        "text_muted",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "character",
        "lg",
        "md",
        "pill",
        "sm"
      ],
      "shadow": [
        "md",
        "philosophy",
        "sm"
      ],
      "spacing": [
        "density",
        "tokens",
        "unit"
      ],
      "typography": [
        "font_family",
        "line_height",
        "mono_family",
        "scale",
        "weight"
      ]
    }
  }
}
```
in the wild

embodiments

Design Language Preview

AYA Sumi Indigo Operational Minimalism

Color Palette

primary
secondary
accent
background
surface
text
muted
border
error
success
warning
info

Typography

h1

Heading One

h2

Heading Two

h3

Heading Three

h4

Heading Four

body

Body text demonstrates the reading experience. Good typography is invisible — it lets the content speak without drawing attention to the letterforms themselves.

caption

Caption text for supplementary information and metadata.

code
const theme = applyTokens(designLanguage);
render(<App theme={theme} />);

Buttons

Form Controls

Navigation

tabs
Overview content area with contextual information about the design language.
segmented control
dropdown menu

Feedback & Status

badges
NewDefaultActivePendingErrorOutline
alerts
Info: A new version is available.
Success: Changes saved successfully.
Warning: Storage is almost full.
Error: Failed to process request.
progress
66% complete
tooltip
avatar
AKJDML

Containers & Overlays

card

Card Title

Cards group related content and actions. This example shows a basic content card with a title and description.

accordion

Design tokens are the atomic values of a design system — colors, spacing, typography, and other values stored as key-value pairs.

dialog
separator

Data Display

table
NameStatusCategoryScore
Neo BrutalismPublishedMaximalist94
Aero GlassDraftSpatial87
Signal UIReviewEnterprise91
stat cards
Languages
42
+12%
Elements
3,150
+8%
Usage
18.4k
+23%
DESIGN.md

at a glance

Palette

Typography

headline-lgInter · 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

Components

New
Card title

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

Spacing

  • densityCompact 8-12px internal gaps, 16-24px module gaps, 32-48px document pauses.
  • unit4px

Shape

character0px
lg10px
md6px
pill999px
sm4px
shadcn/ui

implementation kit

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

DESIGN.md with shadcn

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

advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #F7F7F4;
  --foreground: #1F2426;
  --card: #FFFFFF;
  --card-foreground: #1F2426;
  --popover: #FFFFFF;
  --popover-foreground: #1F2426;
  --primary: #27466F;
  --primary-foreground: #ffffff;
  --secondary: #f4f4f5;
  --secondary-foreground: #111111;
  --muted: #f4f4f5;
  --muted-foreground: #1F2426;
  --accent: #27466F;
  --accent-foreground: #ffffff;
  --destructive: #B05A45;
  --border: #D9DEDF;
  --input: #D9DEDF;
  --ring: #27466F;
  --chart-1: #27466F;
  --chart-2: #f4f4f5;
  --chart-3: #27466F;
  --chart-4: #557463;
  --chart-5: #9B7445;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #1F2426;
  --sidebar-primary: #27466F;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #3F6387;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D9DEDF;
  --sidebar-ring: #27466F;
  --radius: 6px;
}

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

export function AyaSumiIndigoOperationalMinimalismShadcnKit() {
  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 Operational Minimalism</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-operational-minimalism",
  "type": "registry:theme",
  "title": "AYA Sumi Indigo Operational Minimalism shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F7F4",
      "foreground": "#1F2426",
      "card": "#FFFFFF",
      "card-foreground": "#1F2426",
      "popover": "#FFFFFF",
      "popover-foreground": "#1F2426",
      "primary": "#27466F",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#f4f4f5",
      "muted-foreground": "#1F2426",
      "accent": "#27466F",
      "accent-foreground": "#ffffff",
      "destructive": "#B05A45",
      "border": "#D9DEDF",
      "input": "#D9DEDF",
      "ring": "#27466F",
      "chart-1": "#27466F",
      "chart-2": "#f4f4f5",
      "chart-3": "#27466F",
      "chart-4": "#557463",
      "chart-5": "#9B7445",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#1F2426",
      "sidebar-primary": "#27466F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#3F6387",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D9DEDF",
      "sidebar-ring": "#27466F",
      "radius": "6px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#27466F",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#27466F",
      "accent-foreground": "#ffffff",
      "destructive": "#B05A45",
      "border": "#303642",
      "input": "#303642",
      "ring": "#27466F",
      "chart-1": "#27466F",
      "chart-2": "#f4f4f5",
      "chart-3": "#27466F",
      "chart-4": "#557463",
      "chart-5": "#9B7445",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#27466F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#27466F",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#27466F",
      "radius": "6px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "aya-sumi-indigo-operational-minimalism",
    "slug": "aya-sumi-indigo-operational-minimalism",
    "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",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "border_strong",
        "error",
        "focus",
        "info",
        "primary",
        "primary_hover",
        "primary_soft",
        "success",
        "surface",
        "surface_alt",
        "surface_subtle",
        "text",
        "text_muted",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "character",
        "lg",
        "md",
        "pill",
        "sm"
      ],
      "shadow": [
        "md",
        "philosophy",
        "sm"
      ],
      "spacing": [
        "density",
        "tokens",
        "unit"
      ],
      "typography": [
        "font_family",
        "line_height",
        "mono_family",
        "scale",
        "weight"
      ]
    }
  }
}
component recipescompatibility fallback
# AYA Sumi Indigo Operational Minimalism shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `aya-sumi-indigo-operational-minimalism`
Slug: `aya-sumi-indigo-operational-minimalism`

## Intent

Sumi Indigo Operational Minimalism defines AYA as a calm, text-led operational workspace: crisp neutral planes, graphite/sumi typography, pale ai-nezumi blue-grey surfaces, and indigo semantic accents turn metrics, status, provenance, and document analytics into quiet inline signals rather than dashboard spectacle.

## 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": "#27466F",
  "background": "#F7F7F4",
  "border": "#D9DEDF",
  "border_strong": "#AEB8BC",
  "error": "#B05A45",
  "focus": "#2F5E9E",
  "info": "#3F6387",
  "primary": "#27466F",
  "primary_hover": "#203A5D",
  "primary_soft": "#E4EBF3",
  "success": "#557463",
  "surface": "#FFFFFF",
  "surface_alt": "#EEF2F4",
  "surface_subtle": "#F1F3F1",
  "text": "#1F2426",
  "text_muted": "#5F686D",
  "warning": "#9B7445"
}

Typography:

{
  "font_family": "Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, sans-serif",
  "line_height": "1.35 for dense UI, 1.55 for document reading, 1.2 for labels",
  "mono_family": "IBM Plex Mono, ui-monospace, SFMono-Regular, Menlo, monospace",
  "scale": "12px captions, 13px dense controls, 14px body/work rows, 16px document lead, 20-24px section titles",
  "weight": "400 body, 500 controls, 600 headings and key labels; avoid heavy display weights"
}

## Visual character to preserve

- A crisp neutral canvas (#F7F7F4 to #FFFFFF) with sumi/graphite text, pale ai-nezumi blue-grey panels, and fine rule systems that organize information without heavy cards.
- Dense text rows, document excerpts, source trails, and compact analytics sit on the same baseline grid, with metrics embedded as small annotations rather than oversized KPI tiles.
- Status appears as low-chroma chips, left-edge ticks, table row flags, and short semantic labels paired with icons or text so color is never the only cue.
- Primary actions are indigo but mostly outline, text, or restrained filled controls; persimmon appears only for destructive/error warmth at small scale.
- Navigation and operations feel like an expert editor workspace: command palette, keyboard hints, side rail, source drawer, and narrow context panes around a document center.

## ShadSync visual profile

{
  "family": "system",
  "material": "flat",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": false,
  "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-operational-minimalism/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 crisp neutral backgrounds, sumi/graphite typography, pale ai-nezumi panels, and indigo semantic accents.; Embed metrics inline beside documents, tables, source trails, and workflow rows.; Design status chips with labels, muted state colors, and small left-edge ticks or dots.; Prioritize keyboard-first interactions: command palette, skip links, row shortcuts, visible focus, and deterministic drawer behavior.; Keep surfaces quiet: hairline rules, subtle tints, minimal shadows, and compact typography.; Use persimmon only for rare error, unresolved, destructive, or attention states.
- Do not: Do not create a dashboard-first home screen or oversized KPI-card grid.; Do not use neon, generic SaaS gradients, playful mascots, or decorative Japanese motifs/icons.; Do not rely on color alone for state or status.; Do not add decorative illustrations that compete with operational text.; Do not over-round components or use heavy shadows that make the workspace feel like consumer SaaS.

## 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 AyaSumiIndigoOperationalMinimalismShadcnKit() {
  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 Operational Minimalism</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; rails collapse into drawers and document analytics become inline sections on narrow screens.",
  "density": "High information density with 14px rows, 32-40px toolbars, compact chips, and restrained panels; breathing room comes from grouped whitespace and calm surfaces rather than large cards.",
  "grid": "Desktop uses a document-centered 12-column workspace with a 240-280px navigation/context rail, a 640-760px primary text column, and a 280-360px inspector/analytics rail. Tables and comparison views may span full width but retain compact row rhythm.",
  "responsive": "Preserve document-first order: command bar, context/source trail, document body, inline metrics, then inspector details. Do not reorder into dashboard cards.",
  "whitespace": "Use 16-24px between functional groups and 32-48px around reading zones. Avoid empty landing-page expanses; every pause supports comprehension."
}
preview shotscompatibility fallback
{
  "artifact": "katagami:shadcn-preview-shots",
  "version": "preview-shots-v1",
  "generator": "katagami-ui-compatibility-projection",
  "generatedBy": "katagami-ui-projection",
  "requiresVisualProfile": true,
  "schema": "katagami:shadcn-preview-shots/renderable-v1",
  "renderable": true,
  "language": {
    "id": "aya-sumi-indigo-operational-minimalism",
    "name": "AYA Sumi Indigo Operational Minimalism",
    "slug": "aya-sumi-indigo-operational-minimalism"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "A crisp neutral canvas (#F7F7F4 to #FFFFFF) with sumi/graphite text, pale ai-nezumi blue-grey panels, and fine rule systems that organize information without heavy cards.",
    "Dense text rows, document excerpts, source trails, and compact analytics sit on the same baseline grid, with metrics embedded as small annotations rather than oversized KPI tiles.",
    "Status appears as low-chroma chips, left-edge ticks, table row flags, and short semantic labels paired with icons or text so color is never the only cue.",
    "Primary actions are indigo but mostly outline, text, or restrained filled controls; persimmon appears only for destructive/error warmth at small scale.",
    "Navigation and operations feel like an expert editor workspace: command palette, keyboard hints, side rail, source drawer, and narrow context panes around a document center."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": false,
    "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 Operational Minimalism 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 crisp neutral backgrounds, sumi/graphite typography, pale ai-nezumi panels, and indigo semantic accents.",
      "Embed metrics inline beside documents, tables, source trails, and workflow rows.",
      "Design status chips with labels, muted state colors, and small left-edge ticks or dots.",
      "Prioritize keyboard-first interactions: command palette, skip links, row shortcuts, visible focus, and deterministic drawer behavior.",
      "Keep surfaces quiet: hairline rules, subtle tints, minimal shadows, and compact typography.",
      "Use persimmon only for rare error, unresolved, destructive, or attention states."
    ],
    "dont": [
      "Do not create a dashboard-first home screen or oversized KPI-card grid.",
      "Do not use neon, generic SaaS gradients, playful mascots, or decorative Japanese motifs/icons.",
      "Do not rely on color alone for state or status.",
      "Do not add decorative illustrations that compete with operational text.",
      "Do not over-round components or use heavy shadows that make the workspace feel like consumer SaaS."
    ]
  }
}
related

More like this