back to gallery
design language·yokohama-android-cafe-terminal

Yokohama Android Cafe Terminal

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
Yokohama Android Cafe Terminal is a quiet interface language for humane machine rooms disguised as warm neighborhood cafes. It blends delicate black-and-white manga interiors, paper menu cards, softened terminal panes, and anime title-card timing into a system that feels inhabited rather than operated. The terminal is present, but it behaves like low furniture: shallow, muted, orderly, and never brighter than the room. The emotional center is slice-of-life science fiction: diagnostics that apologize, status lights that whisper, and command surfaces that leave room for a cup, a window, and a pause.
values
Quiet existential warmth: every technical surface should feel calm enough to read during rain in a cafe.Human-first diagnostics: machine states are written as considerate messages, not alarms or threat displays.Manga-room specificity: panels, window mullions, ruled counters, and speech-label fragments carry the visual story.Terminal restraint: command UI is flattened into low-contrast panes with espresso borders and tea-green text.Editorial anime rhythm: title labels, split cards, and episode metadata appear as calm typographic beats.Material softness: warm paper whites, espresso ink, and sparse amber/sage cues replace cyber-neon spectacle.
anti-values
×No neon cyberpunk glow fields, holographic gradients, or saturated RGB arcade accents.×No generic dashboard chrome, glassmorphism, or SaaS card piles without a lived-in scene.×No aggressive red-error language unless paired with humane recovery text and subdued color.×No decorative anime quotation that overwhelms the functional cafe-terminal structure.
tokens
borders4 items
accent width
2px
character
Faded manga ink: espresso-brown structural lines, double rules on title cards, and bracket corner ticks on terminal panes.
default width
1px
style
solid
colors12 items
accent
#8A9A82
background
#F4EFE4
border
#BBAE98
error
#8B4A3B
info
#7A8880
muted
#6D5444
primary
#4B372C
secondary
#6D5444
success
#6F8069
surface
#E8DDCB
text
#1E1B18
warning
#B08A55
motion3 items
duration
180ms
easing
cubic-bezier(0.2, 0.0, 0.1, 1)
philosophy
Only small status lights breathe and row focus slides by 2px; no sweeping scans, glitching, or spectacle motion.
radii5 items
full
9999px
lg
24px
md
16px
none
0px
sm
0px
shadows3 items
lg
0 22px 60px rgba(75,55,44,0.14)
md
0 10px 28px rgba(75,55,44,0.10)
sm
0 1px 0 rgba(30,27,24,0.12)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64, 96
surfaces3 items
bg pattern
Layered repeating-linear-gradients: horizontal paper rules at 24px and occasional vertical cafe-window mullions at wide intervals.
card style
Square or 16px-radius cards with 1px espresso-taupe borders, inner rule lines, and tiny metadata captions pinned to top rails.
treatment
Matte paper whites with faint manga hatch ruling; terminal areas use tea-stained panels instead of luminous dark glass.
typography8 items
base size
16px
body font
Noto Serif JP
google fonts url
https://fonts.googleapis.com/css2?family=Noto+Serif+JP:wght@400;500;700&family=Sono:wght@400;500;600&family=Zen+Kurenaido&display=swap
heading font
Zen Kurenaido
letter spacing
-0.02em
line height
1.58
mono font
Sono
scale ratio
1.22
rules
composition
Use a cafe-interior base grid: a wide manga window or counter panel, a narrow title-card spine, and terminal panes arranged like furniture below eye level. Prefer ruled rectangles and shallow shelves over floating modals. Every screen needs at least one inhabited cue such as a cup mark, menu rail, receipt, maintenance note, or window frame. Keep accent color to sage and amber status details only. Use black ink for hierarchy, espresso for structure, and paper negative space for the emotional tone.
density
Moderate density with compact diagnostics inside generous room-scale whitespace: terminal rows may be tight, but panels need breathing space like quiet tables in a cafe.
hierarchy
Primary hierarchy comes from placement and line weight before color. Headings use Zen Kurenaido in large, airy title-card settings; body copy uses Noto Serif JP for manga-cafe warmth; operational data uses Sono in small terminal rows. Important states get a label, a dot, and a border-weight shift, never color alone. Episode labels and bracket glyphs may mark sections, but they remain secondary to readable content.
signature patterns
Cafe-window manga grid: large paper panels divided by 1px espresso mullions with faint hatch gradients, used as the underlying composition rather than decoration.Low-furniture terminal panes: command blocks sit in muted tea surfaces with inset top rails, bracket corners, and sage monospace rows below the visual horizon.Humane diagnostic speech strips: machine statuses appear as small ruled manga captions with amber dots, recovery copy, and soft labels such as please wait or listening.Quiet anime title-card rhythm: tiny episode codes, vertical spines, and split-screen labels punctuate sections without using neon, bevels, or aggressive motion.
layout
breakpoints

Mobile 375px single-column with horizontal scroll avoided; tablet 768px two-column stack; desktop 1200px+ full cafe-counter composition.

density

Room-first moderate density: 40% negative space on desktop, with data clustered in shallow bands so the interface feels like an interior rather than a cockpit.

grid

Desktop uses a 12-column max-width 1280px grid with 24px gutters, combining a 7-column cafe scene, 3-column terminal stack, and 2-column vertical title spine.

responsive

At tablet the title spine becomes a top subtitle rail; at mobile terminal panes stack after the cafe panel and metadata labels remain visible but shorter.

whitespace

Whitespace should resemble table distance: 24px between related cards, 48px between scene zones, and wide paper margins around title cards and diagnostics.

guidance
do
  • Begin with warm paper white and espresso linework before adding any sage or amber status color.
  • Make terminal panes low contrast, matte, and physically placed inside the room grid like shelves or receipts.
  • Use tiny Y2K/anime labels as metadata: episode codes, bracket marks, spine captions, and quiet split-screen headings.
  • Write diagnostics in humane language with recovery hints, not terse machine panic.
  • Keep global letter spacing at -0.02em and use line height generously for calm reading.
  • Let ruled manga panels, window mullions, and counter rails create composition instead of shadows or gradients.
  • Pair every colored state with text, dot shape, or border change for accessibility.
avoid
  • Do not introduce cyan, magenta, laser green, or neon glow except as a single tiny status light if absolutely necessary.
  • Do not use generic dark terminal full-screen styling; the terminal must be softened into the cafe paper palette.
  • Do not crowd every panel with decorative manga marks; empty paper is part of the identity.
  • Do not rely on anime screenshots, character art, or literal franchise references.
  • Do not use glass blur, high-saturation gradients, or glossy cyberpunk surfaces.
  • Do not present errors as hostile alerts; soften them with plain-language next steps.
  • Do not mix many border radii; use square rules and occasional 16px/24px human surfaces only.
katagami spec
# Yokohama Android Cafe Terminal

## Philosophy

Yokohama Android Cafe Terminal is a quiet interface language for humane machine rooms disguised as warm neighborhood cafes. It blends delicate black-and-white manga interiors, paper menu cards, softened terminal panes, and anime title-card timing into a system that feels inhabited rather than operated. The terminal is present, but it behaves like low furniture: shallow, muted, orderly, and never brighter than the room. The emotional center is slice-of-life science fiction: diagnostics that apologize, status lights that whisper, and command surfaces that leave room for a cup, a window, and a pause.

### Values

- Quiet existential warmth: every technical surface should feel calm enough to read during rain in a cafe.
- Human-first diagnostics: machine states are written as considerate messages, not alarms or threat displays.
- Manga-room specificity: panels, window mullions, ruled counters, and speech-label fragments carry the visual story.
- Terminal restraint: command UI is flattened into low-contrast panes with espresso borders and tea-green text.
- Editorial anime rhythm: title labels, split cards, and episode metadata appear as calm typographic beats.
- Material softness: warm paper whites, espresso ink, and sparse amber/sage cues replace cyber-neon spectacle.

### Anti-Values

- No neon cyberpunk glow fields, holographic gradients, or saturated RGB arcade accents.
- No generic dashboard chrome, glassmorphism, or SaaS card piles without a lived-in scene.
- No aggressive red-error language unless paired with humane recovery text and subdued color.
- No decorative anime quotation that overwhelms the functional cafe-terminal structure.

### Visual Character

- A warm paper body grid overlaid with ultra-thin manga ruling lines using repeating-linear-gradient backgrounds and espresso 1px borders.
- Terminal panes are inset like cafe furniture: low-contrast #E8DDCB surfaces, square panel corners, monospace command rows, and no outer glow.
- Y2K and anime title motifs are reduced to tiny uppercase labels, bracket glyphs, episode numbers, and vertical spine captions rather than loud graphics.
- Diagnostics use humane speech-strip composition: small ruled cards with soft amber status dots, plain-language machine notes, and generous line height.
- The signature scene is built as a cafe counter floorplan with manga window panels, terminal receipts, menu rails, and quiet android maintenance cues.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Faded manga ink: espresso-brown structural lines, double rules on title cards, and bracket corner ticks on terminal panes.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#8A9A82` |
| background | `#F4EFE4` |
| border | `#BBAE98` |
| error | `#8B4A3B` |
| info | `#7A8880` |
| muted | `#6D5444` |
| primary | `#4B372C` |
| secondary | `#6D5444` |
| success | `#6F8069` |
| surface | `#E8DDCB` |
| text | `#1E1B18` |
| warning | `#B08A55` |

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.2, 0.0, 0.1, 1)
- **Philosophy**: Only small status lights breathe and row focus slides by 2px; no sweeping scans, glitching, or spectacle motion.

### Radii

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

### Shadows

- **Lg**: 0 22px 60px rgba(75,55,44,0.14)
- **Md**: 0 10px 28px rgba(75,55,44,0.10)
- **Sm**: 0 1px 0 rgba(30,27,24,0.12)

### Spacing

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

### Surfaces

- **Bg Pattern**: Layered repeating-linear-gradients: horizontal paper rules at 24px and occasional vertical cafe-window mullions at wide intervals.
- **Card Style**: Square or 16px-radius cards with 1px espresso-taupe borders, inner rule lines, and tiny metadata captions pinned to top rails.
- **Treatment**: Matte paper whites with faint manga hatch ruling; terminal areas use tea-stained panels instead of luminous dark glass.

### Typography

- **Base Size**: 16px
- **Body Font**: Noto Serif JP
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Noto+Serif+JP:wght@400;500;700&family=Sono:wght@400;500;600&family=Zen+Kurenaido&display=swap
- **Heading Font**: Zen Kurenaido
- **Letter Spacing**: -0.02em
- **Line Height**: 1.58
- **Mono Font**: Sono
- **Scale Ratio**: 1.22

## Rules

### Composition

Use a cafe-interior base grid: a wide manga window or counter panel, a narrow title-card spine, and terminal panes arranged like furniture below eye level. Prefer ruled rectangles and shallow shelves over floating modals. Every screen needs at least one inhabited cue such as a cup mark, menu rail, receipt, maintenance note, or window frame. Keep accent color to sage and amber status details only. Use black ink for hierarchy, espresso for structure, and paper negative space for the emotional tone.

### Density

Moderate density with compact diagnostics inside generous room-scale whitespace: terminal rows may be tight, but panels need breathing space like quiet tables in a cafe.

### Hierarchy

Primary hierarchy comes from placement and line weight before color. Headings use Zen Kurenaido in large, airy title-card settings; body copy uses Noto Serif JP for manga-cafe warmth; operational data uses Sono in small terminal rows. Important states get a label, a dot, and a border-weight shift, never color alone. Episode labels and bracket glyphs may mark sections, but they remain secondary to readable content.

### Signature Patterns

- Cafe-window manga grid: large paper panels divided by 1px espresso mullions with faint hatch gradients, used as the underlying composition rather than decoration.
- Low-furniture terminal panes: command blocks sit in muted tea surfaces with inset top rails, bracket corners, and sage monospace rows below the visual horizon.
- Humane diagnostic speech strips: machine statuses appear as small ruled manga captions with amber dots, recovery copy, and soft labels such as please wait or listening.
- Quiet anime title-card rhythm: tiny episode codes, vertical spines, and split-screen labels punctuate sections without using neon, bevels, or aggressive motion.

## Layout

### Breakpoints

Mobile 375px single-column with horizontal scroll avoided; tablet 768px two-column stack; desktop 1200px+ full cafe-counter composition.

### Density

Room-first moderate density: 40% negative space on desktop, with data clustered in shallow bands so the interface feels like an interior rather than a cockpit.

### Grid

Desktop uses a 12-column max-width 1280px grid with 24px gutters, combining a 7-column cafe scene, 3-column terminal stack, and 2-column vertical title spine.

### Responsive

At tablet the title spine becomes a top subtitle rail; at mobile terminal panes stack after the cafe panel and metadata labels remain visible but shorter.

### Whitespace

Whitespace should resemble table distance: 24px between related cards, 48px between scene zones, and wide paper margins around title cards and diagnostics.

## Guidance

### Do

- Begin with warm paper white and espresso linework before adding any sage or amber status color.
- Make terminal panes low contrast, matte, and physically placed inside the room grid like shelves or receipts.
- Use tiny Y2K/anime labels as metadata: episode codes, bracket marks, spine captions, and quiet split-screen headings.
- Write diagnostics in humane language with recovery hints, not terse machine panic.
- Keep global letter spacing at -0.02em and use line height generously for calm reading.
- Let ruled manga panels, window mullions, and counter rails create composition instead of shadows or gradients.
- Pair every colored state with text, dot shape, or border change for accessibility.

### Don't

- Do not introduce cyan, magenta, laser green, or neon glow except as a single tiny status light if absolutely necessary.
- Do not use generic dark terminal full-screen styling; the terminal must be softened into the cafe paper palette.
- Do not crowd every panel with decorative manga marks; empty paper is part of the identity.
- Do not rely on anime screenshots, character art, or literal franchise references.
- Do not use glass blur, high-saturation gradients, or glossy cyberpunk surfaces.
- Do not present errors as hostile alerts; soften them with plain-language next steps.
- Do not mix many border radii; use square rules and occasional 16px/24px human surfaces only.

### Accessibility

Maintain AA contrast for body and controls. Amber and sage are supplementary only; statuses include text labels and shape. Preserve visible focus outlines as espresso double rules. Respect reduced motion by disabling breathing status lights.

### Usage Context

Best for calm developer tools, AI companions, robotics dashboards, maintenance consoles, creative coding notebooks, and contemplative product surfaces where machines should feel patient and domestic.
DESIGN.md
---
version: "alpha"
name: "Yokohama Android Cafe Terminal"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#8A9A82"
  background: "#F4EFE4"
  border: "#BBAE98"
  error: "#8B4A3B"
  info: "#7A8880"
  muted: "#6D5444"
  primary: "#4B372C"
  secondary: "#6D5444"
  success: "#6F8069"
  surface: "#E8DDCB"
  text: "#1E1B18"
  warning: "#B08A55"
typography:
  headline-lg:
    fontFamily: "Zen Kurenaido"
    fontSize: "1.816rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Zen Kurenaido"
    fontSize: "1.488rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "Noto Serif JP"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.58
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "Sono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "24px"
  md: "16px"
  none: "0px"
  sm: "0px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
  step-8: "96px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  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"
---

# Yokohama Android Cafe Terminal

## Overview

Yokohama Android Cafe Terminal is a quiet interface language for humane machine rooms disguised as warm neighborhood cafes. It blends delicate black-and-white manga interiors, paper menu cards, softened terminal panes, and anime title-card timing into a system that feels inhabited rather than operated. The terminal is present, but it behaves like low furniture: shallow, muted, orderly, and never brighter than the room. The emotional center is slice-of-life science fiction: diagnostics that apologize, status lights that whisper, and command surfaces that leave room for a cup, a window, and a pause.

### Values

- Quiet existential warmth: every technical surface should feel calm enough to read during rain in a cafe.
- Human-first diagnostics: machine states are written as considerate messages, not alarms or threat displays.
- Manga-room specificity: panels, window mullions, ruled counters, and speech-label fragments carry the visual story.
- Terminal restraint: command UI is flattened into low-contrast panes with espresso borders and tea-green text.
- Editorial anime rhythm: title labels, split cards, and episode metadata appear as calm typographic beats.
- Material softness: warm paper whites, espresso ink, and sparse amber/sage cues replace cyber-neon spectacle.

### Anti-Values

- No neon cyberpunk glow fields, holographic gradients, or saturated RGB arcade accents.
- No generic dashboard chrome, glassmorphism, or SaaS card piles without a lived-in scene.
- No aggressive red-error language unless paired with humane recovery text and subdued color.
- No decorative anime quotation that overwhelms the functional cafe-terminal structure.

### Visual Character

- A warm paper body grid overlaid with ultra-thin manga ruling lines using repeating-linear-gradient backgrounds and espresso 1px borders.
- Terminal panes are inset like cafe furniture: low-contrast #E8DDCB surfaces, square panel corners, monospace command rows, and no outer glow.
- Y2K and anime title motifs are reduced to tiny uppercase labels, bracket glyphs, episode numbers, and vertical spine captions rather than loud graphics.
- Diagnostics use humane speech-strip composition: small ruled cards with soft amber status dots, plain-language machine notes, and generous line height.
- The signature scene is built as a cafe counter floorplan with manga window panels, terminal receipts, menu rails, and quiet android maintenance cues.

## 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 | `#8A9A82` |
| background | `#F4EFE4` |
| border | `#BBAE98` |
| error | `#8B4A3B` |
| info | `#7A8880` |
| muted | `#6D5444` |
| primary | `#4B372C` |
| secondary | `#6D5444` |
| success | `#6F8069` |
| surface | `#E8DDCB` |
| text | `#1E1B18` |
| warning | `#B08A55` |

## Typography

- **Headline-Lg**: Zen Kurenaido, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Zen Kurenaido, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Noto Serif JP, 16px, weight 400, line-height 1.58.
- **Label-Md**: Sono, 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**: `48px`
- **4xl**: `64px`
- **Step-8**: `96px`

### Breakpoints

Mobile 375px single-column with horizontal scroll avoided; tablet 768px two-column stack; desktop 1200px+ full cafe-counter composition.

### Density

Room-first moderate density: 40% negative space on desktop, with data clustered in shallow bands so the interface feels like an interior rather than a cockpit.

### Grid

Desktop uses a 12-column max-width 1280px grid with 24px gutters, combining a 7-column cafe scene, 3-column terminal stack, and 2-column vertical title spine.

### Responsive

At tablet the title spine becomes a top subtitle rail; at mobile terminal panes stack after the cafe panel and metadata labels remain visible but shorter.

### Whitespace

Whitespace should resemble table distance: 24px between related cards, 48px between scene zones, and wide paper margins around title cards and diagnostics.

## Elevation & Depth

### Shadows

- **Lg**: 0 22px 60px rgba(75,55,44,0.14)
- **Md**: 0 10px 28px rgba(75,55,44,0.10)
- **Sm**: 0 1px 0 rgba(30,27,24,0.12)

## Shapes

### Rounded

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

### Surfaces

- **Bg Pattern**: Layered repeating-linear-gradients: horizontal paper rules at 24px and occasional vertical cafe-window mullions at wide intervals.
- **Card Style**: Square or 16px-radius cards with 1px espresso-taupe borders, inner rule lines, and tiny metadata captions pinned to top rails.
- **Treatment**: Matte paper whites with faint manga hatch ruling; terminal areas use tea-stained panels instead of luminous dark glass.

### Borders

- **Accent Width**: 2px
- **Character**: Faded manga ink: espresso-brown structural lines, double rules on title cards, and bracket corner ticks on terminal panes.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use a cafe-interior base grid: a wide manga window or counter panel, a narrow title-card spine, and terminal panes arranged like furniture below eye level. Prefer ruled rectangles and shallow shelves over floating modals. Every screen needs at least one inhabited cue such as a cup mark, menu rail, receipt, maintenance note, or window frame. Keep accent color to sage and amber status details only. Use black ink for hierarchy, espresso for structure, and paper negative space for the emotional tone.

### Density

Moderate density with compact diagnostics inside generous room-scale whitespace: terminal rows may be tight, but panels need breathing space like quiet tables in a cafe.

### Hierarchy

Primary hierarchy comes from placement and line weight before color. Headings use Zen Kurenaido in large, airy title-card settings; body copy uses Noto Serif JP for manga-cafe warmth; operational data uses Sono in small terminal rows. Important states get a label, a dot, and a border-weight shift, never color alone. Episode labels and bracket glyphs may mark sections, but they remain secondary to readable content.

### Signature Patterns

- Cafe-window manga grid: large paper panels divided by 1px espresso mullions with faint hatch gradients, used as the underlying composition rather than decoration.
- Low-furniture terminal panes: command blocks sit in muted tea surfaces with inset top rails, bracket corners, and sage monospace rows below the visual horizon.
- Humane diagnostic speech strips: machine statuses appear as small ruled manga captions with amber dots, recovery copy, and soft labels such as please wait or listening.
- Quiet anime title-card rhythm: tiny episode codes, vertical spines, and split-screen labels punctuate sections without using neon, bevels, or aggressive motion.

## 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/yokohama-android-cafe-terminal/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 Begin with warm paper white and espresso linework before adding any sage or amber status color.
- Do Make terminal panes low contrast, matte, and physically placed inside the room grid like shelves or receipts.
- Do Use tiny Y2K/anime labels as metadata: episode codes, bracket marks, spine captions, and quiet split-screen headings.
- Do Write diagnostics in humane language with recovery hints, not terse machine panic.
- Do Keep global letter spacing at -0.02em and use line height generously for calm reading.
- Do Let ruled manga panels, window mullions, and counter rails create composition instead of shadows or gradients.
- Do Pair every colored state with text, dot shape, or border change for accessibility.
- Don't Do not introduce cyan, magenta, laser green, or neon glow except as a single tiny status light if absolutely necessary.
- Don't Do not use generic dark terminal full-screen styling; the terminal must be softened into the cafe paper palette.
- Don't Do not crowd every panel with decorative manga marks; empty paper is part of the identity.
- Don't Do not rely on anime screenshots, character art, or literal franchise references.
- Don't Do not use glass blur, high-saturation gradients, or glossy cyberpunk surfaces.
- Don't Do not present errors as hostile alerts; soften them with plain-language next steps.
- Don't Do not mix many border radii; use square rules and occasional 16px/24px human surfaces only.

### Accessibility

Maintain AA contrast for body and controls. Amber and sage are supplementary only; statuses include text labels and shape. Preserve visible focus outlines as espresso double rules. Respect reduced motion by disabling breathing status lights.

### Usage Context

Best for calm developer tools, AI companions, robotics dashboards, maintenance consoles, creative coding notebooks, and contemplative product surfaces where machines should feel patient and domestic.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "yokohama-android-cafe-terminal",
  "type": "registry:theme",
  "title": "Yokohama Android Cafe Terminal shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F4EFE4",
      "foreground": "#1E1B18",
      "card": "#E8DDCB",
      "card-foreground": "#1E1B18",
      "popover": "#E8DDCB",
      "popover-foreground": "#1E1B18",
      "primary": "#4B372C",
      "primary-foreground": "#ffffff",
      "secondary": "#6D5444",
      "secondary-foreground": "#ffffff",
      "muted": "#6D5444",
      "muted-foreground": "#1E1B18",
      "accent": "#8A9A82",
      "accent-foreground": "#ffffff",
      "destructive": "#8B4A3B",
      "border": "#BBAE98",
      "input": "#BBAE98",
      "ring": "#8A9A82",
      "chart-1": "#4B372C",
      "chart-2": "#6D5444",
      "chart-3": "#8A9A82",
      "chart-4": "#6F8069",
      "chart-5": "#B08A55",
      "sidebar": "#E8DDCB",
      "sidebar-foreground": "#1E1B18",
      "sidebar-primary": "#4B372C",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#7A8880",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#BBAE98",
      "sidebar-ring": "#8A9A82",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#4B372C",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#8A9A82",
      "accent-foreground": "#ffffff",
      "destructive": "#8B4A3B",
      "border": "#303642",
      "input": "#303642",
      "ring": "#8A9A82",
      "chart-1": "#4B372C",
      "chart-2": "#6D5444",
      "chart-3": "#8A9A82",
      "chart-4": "#6F8069",
      "chart-5": "#B08A55",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#4B372C",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#8A9A82",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#8A9A82",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "yokohama-android-cafe-terminal",
    "slug": "yokohama-android-cafe-terminal",
    "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",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · yokohama-android-cafe-terminal
DESIGN.md

at a glance

Palette

Typography

headline-lgZen Kurenaido · 29px · 700

The quick brown fox jumps

headline-mdZen Kurenaido · 24px · 600

The quick brown fox jumps

body-mdNoto Serif JP · 16px · 400

The quick brown fox jumps

label-mdSono · 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
  • 3xl48px
  • 4xl64px
  • step-896px

Shape

full9999px
lg24px
md16px
none0px
sm0px
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: #F4EFE4;
  --foreground: #1E1B18;
  --card: #E8DDCB;
  --card-foreground: #1E1B18;
  --popover: #E8DDCB;
  --popover-foreground: #1E1B18;
  --primary: #4B372C;
  --primary-foreground: #ffffff;
  --secondary: #6D5444;
  --secondary-foreground: #ffffff;
  --muted: #6D5444;
  --muted-foreground: #1E1B18;
  --accent: #8A9A82;
  --accent-foreground: #ffffff;
  --destructive: #8B4A3B;
  --border: #BBAE98;
  --input: #BBAE98;
  --ring: #8A9A82;
  --chart-1: #4B372C;
  --chart-2: #6D5444;
  --chart-3: #8A9A82;
  --chart-4: #6F8069;
  --chart-5: #B08A55;
  --sidebar: #E8DDCB;
  --sidebar-foreground: #1E1B18;
  --sidebar-primary: #4B372C;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #7A8880;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #BBAE98;
  --sidebar-ring: #8A9A82;
  --radius: 16px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #4B372C;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #8A9A82;
  --accent-foreground: #ffffff;
  --destructive: #8B4A3B;
  --border: #303642;
  --input: #303642;
  --ring: #8A9A82;
  --chart-1: #4B372C;
  --chart-2: #6D5444;
  --chart-3: #8A9A82;
  --chart-4: #6F8069;
  --chart-5: #B08A55;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #4B372C;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #8A9A82;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #8A9A82;
  --radius: 16px;
}
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 YokohamaAndroidCafeTerminalShadcnKit() {
  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">Yokohama Android Cafe Terminal</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": "yokohama-android-cafe-terminal",
  "type": "registry:theme",
  "title": "Yokohama Android Cafe Terminal shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F4EFE4",
      "foreground": "#1E1B18",
      "card": "#E8DDCB",
      "card-foreground": "#1E1B18",
      "popover": "#E8DDCB",
      "popover-foreground": "#1E1B18",
      "primary": "#4B372C",
      "primary-foreground": "#ffffff",
      "secondary": "#6D5444",
      "secondary-foreground": "#ffffff",
      "muted": "#6D5444",
      "muted-foreground": "#1E1B18",
      "accent": "#8A9A82",
      "accent-foreground": "#ffffff",
      "destructive": "#8B4A3B",
      "border": "#BBAE98",
      "input": "#BBAE98",
      "ring": "#8A9A82",
      "chart-1": "#4B372C",
      "chart-2": "#6D5444",
      "chart-3": "#8A9A82",
      "chart-4": "#6F8069",
      "chart-5": "#B08A55",
      "sidebar": "#E8DDCB",
      "sidebar-foreground": "#1E1B18",
      "sidebar-primary": "#4B372C",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#7A8880",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#BBAE98",
      "sidebar-ring": "#8A9A82",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#4B372C",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#8A9A82",
      "accent-foreground": "#ffffff",
      "destructive": "#8B4A3B",
      "border": "#303642",
      "input": "#303642",
      "ring": "#8A9A82",
      "chart-1": "#4B372C",
      "chart-2": "#6D5444",
      "chart-3": "#8A9A82",
      "chart-4": "#6F8069",
      "chart-5": "#B08A55",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#4B372C",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#8A9A82",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#8A9A82",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "yokohama-android-cafe-terminal",
    "slug": "yokohama-android-cafe-terminal",
    "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",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
component recipescompatibility fallback
# Yokohama Android Cafe Terminal shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `yokohama-android-cafe-terminal`
Slug: `yokohama-android-cafe-terminal`

## Intent

Yokohama Android Cafe Terminal is a quiet interface language for humane machine rooms disguised as warm neighborhood cafes. It blends delicate black-and-white manga interiors, paper menu cards, softened terminal panes, and anime title-card timing into a system that feels inhabited rather than operated. The terminal is present, but it behaves like low furniture: shallow, muted, orderly, and never brighter than the room. The emotional center is slice-of-life science fiction: diagnostics that apologize, status lights that whisper, and command surfaces that leave room for a cup, a window, and a pause.

## 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": "#8A9A82",
  "background": "#F4EFE4",
  "border": "#BBAE98",
  "error": "#8B4A3B",
  "info": "#7A8880",
  "muted": "#6D5444",
  "primary": "#4B372C",
  "secondary": "#6D5444",
  "success": "#6F8069",
  "surface": "#E8DDCB",
  "text": "#1E1B18",
  "warning": "#B08A55"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Noto Serif JP",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Noto+Serif+JP:wght@400;500;700&family=Sono:wght@400;500;600&family=Zen+Kurenaido&display=swap",
  "heading_font": "Zen Kurenaido",
  "letter_spacing": "-0.02em",
  "line_height": 1.58,
  "mono_font": "Sono",
  "scale_ratio": 1.22
}

## Visual character to preserve

- A warm paper body grid overlaid with ultra-thin manga ruling lines using repeating-linear-gradient backgrounds and espresso 1px borders.
- Terminal panes are inset like cafe furniture: low-contrast #E8DDCB surfaces, square panel corners, monospace command rows, and no outer glow.
- Y2K and anime title motifs are reduced to tiny uppercase labels, bracket glyphs, episode numbers, and vertical spine captions rather than loud graphics.
- Diagnostics use humane speech-strip composition: small ruled cards with soft amber status dots, plain-language machine notes, and generous line height.
- The signature scene is built as a cafe counter floorplan with manga window panels, terminal receipts, menu rails, and quiet android maintenance cues.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "stickerBadges": false,
  "motion": "still",
  "density": "balanced",
  "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/yokohama-android-cafe-terminal/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: Begin with warm paper white and espresso linework before adding any sage or amber status color.; Make terminal panes low contrast, matte, and physically placed inside the room grid like shelves or receipts.; Use tiny Y2K/anime labels as metadata: episode codes, bracket marks, spine captions, and quiet split-screen headings.; Write diagnostics in humane language with recovery hints, not terse machine panic.; Keep global letter spacing at -0.02em and use line height generously for calm reading.; Let ruled manga panels, window mullions, and counter rails create composition instead of shadows or gradients.; Pair every colored state with text, dot shape, or border change for accessibility.
- Do not: Do not introduce cyan, magenta, laser green, or neon glow except as a single tiny status light if absolutely necessary.; Do not use generic dark terminal full-screen styling; the terminal must be softened into the cafe paper palette.; Do not crowd every panel with decorative manga marks; empty paper is part of the identity.; Do not rely on anime screenshots, character art, or literal franchise references.; Do not use glass blur, high-saturation gradients, or glossy cyberpunk surfaces.; Do not present errors as hostile alerts; soften them with plain-language next steps.; Do not mix many border radii; use square rules and occasional 16px/24px human surfaces only.

## 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 YokohamaAndroidCafeTerminalShadcnKit() {
  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">Yokohama Android Cafe Terminal</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 375px single-column with horizontal scroll avoided; tablet 768px two-column stack; desktop 1200px+ full cafe-counter composition.",
  "density": "Room-first moderate density: 40% negative space on desktop, with data clustered in shallow bands so the interface feels like an interior rather than a cockpit.",
  "grid": "Desktop uses a 12-column max-width 1280px grid with 24px gutters, combining a 7-column cafe scene, 3-column terminal stack, and 2-column vertical title spine.",
  "responsive": "At tablet the title spine becomes a top subtitle rail; at mobile terminal panes stack after the cafe panel and metadata labels remain visible but shorter.",
  "whitespace": "Whitespace should resemble table distance: 24px between related cards, 48px between scene zones, and wide paper margins around title cards and diagnostics."
}
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": "yokohama-android-cafe-terminal",
    "name": "Yokohama Android Cafe Terminal",
    "slug": "yokohama-android-cafe-terminal"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "A warm paper body grid overlaid with ultra-thin manga ruling lines using repeating-linear-gradient backgrounds and espresso 1px borders.",
    "Terminal panes are inset like cafe furniture: low-contrast #E8DDCB surfaces, square panel corners, monospace command rows, and no outer glow.",
    "Y2K and anime title motifs are reduced to tiny uppercase labels, bracket glyphs, episode numbers, and vertical spine captions rather than loud graphics.",
    "Diagnostics use humane speech-strip composition: small ruled cards with soft amber status dots, plain-language machine notes, and generous line height.",
    "The signature scene is built as a cafe counter floorplan with manga window panels, terminal receipts, menu rails, and quiet android maintenance cues."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": false,
    "motion": "still",
    "density": "balanced",
    "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": "Yokohama Android Cafe Terminal 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": [
      "Begin with warm paper white and espresso linework before adding any sage or amber status color.",
      "Make terminal panes low contrast, matte, and physically placed inside the room grid like shelves or receipts.",
      "Use tiny Y2K/anime labels as metadata: episode codes, bracket marks, spine captions, and quiet split-screen headings.",
      "Write diagnostics in humane language with recovery hints, not terse machine panic.",
      "Keep global letter spacing at -0.02em and use line height generously for calm reading.",
      "Let ruled manga panels, window mullions, and counter rails create composition instead of shadows or gradients.",
      "Pair every colored state with text, dot shape, or border change for accessibility."
    ],
    "dont": [
      "Do not introduce cyan, magenta, laser green, or neon glow except as a single tiny status light if absolutely necessary.",
      "Do not use generic dark terminal full-screen styling; the terminal must be softened into the cafe paper palette.",
      "Do not crowd every panel with decorative manga marks; empty paper is part of the identity.",
      "Do not rely on anime screenshots, character art, or literal franchise references.",
      "Do not use glass blur, high-saturation gradients, or glossy cyberpunk surfaces.",
      "Do not present errors as hostile alerts; soften them with plain-language next steps.",
      "Do not mix many border radii; use square rules and occasional 16px/24px human surfaces only."
    ]
  }
}
related

More like this