back to gallery
design language·porcelain-android-service-ritual

Porcelain Android Service Ritual

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
Porcelain Android Service Ritual is a quiet interface language for human-scale robotic care: not a hacker console, not fan-art anime, but a service kiosk that feels like a ceramic appliance trained to ask permission. It blends black-and-white manga panel discipline with late-1990s consumer computing hardware cues: rounded access doors, tiny teal service LEDs, keyed ritual steps, and terminal text used as labels rather than spectacle. The system treats interaction as consent choreography, with every panel, light, and confirmation mark making the robot legible, maintainable, and humble.
values
Ritualized consent before automationHuman-scale robotics care instead of spectaclePorcelain restraint with exact black lineworkMachine-readable affordances that stay calmService maintenance honesty: ports, seams, and status lights are visibleLate-90s hardware softness without translucent toy excessExistential quiet: interfaces acknowledge dependence without drama
anti-values
×Neon cyberpunk glow or green matrix rain×Generic hacker dashboards filled with meaningless charts×Character illustration, mascot fan art, or anime faces×SaaS card-grid sameness and default startup dashboards×Aggressive military robotics styling
tokens
borders4 items
accent width
2px
character
rice-paper black technical linework with occasional double-rule service seams
default width
1px
style
solid
colors12 items
accent
#5F9C9A
background
#FBF7EF
border
#26231E
error
#A44738
info
#4F7F93
muted
#6F6960
primary
#11100E
secondary
#F4EFE6
success
#5F9C9A
surface
#FFFDF7
text
#141311
warning
#B9833D
motion3 items
duration
180ms
easing
cubic-bezier(0.2, 0.8, 0.2, 1)
philosophy
mechanical but gentle: LEDs tick, panels acknowledge, nothing sweeps or pulses like a cyberpunk display
radii5 items
full
9999px
lg
24px
md
24px
none
0
sm
16px
shadows3 items
lg
0 28px 70px rgba(60,48,34,0.16)
md
0 14px 30px rgba(60,48,34,0.10)
sm
0 1px 0 rgba(20,19,17,0.16)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64, 96
surfaces3 items
bg pattern
barely visible graphite hatch grid at 32px intervals, clipped by manga panel gutters
card style
rounded ceramic service plates with black hairline seams, amber maintenance tabs, and inset label wells
treatment
warm porcelain surfaces, subtle off-white radial highlight, no saturated gradients
typography8 items
base size
16px
body font
IBM Plex Sans JP
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans+JP:wght@400;500;600;700&family=Zen+Kaku+Gothic+New:wght@500;700;900&display=swap
heading font
Zen Kaku Gothic New
letter spacing
-0.02em
line height
1.52
mono font
IBM Plex Mono
scale ratio
1.22
rules
composition
Use a kiosk-scene composition: one large porcelain robot terminal body, a narrow ritual sidebar, and two lower maintenance panels. Align everything to a strict 12-column grid, then interrupt it with black manga gutters and rounded hardware seams. Avoid floating SaaS cards; every module must look physically attached to the service appliance.
density
Medium-high density is acceptable when it resembles labeled hardware, but whitespace must pool around the main consent action and robot status so the kiosk feels caring rather than overloaded.
hierarchy
Primary hierarchy comes from panel scale, black rule weight, and numbered ritual order. Headings are compact and heavy; body copy is calm and service-like; monospaced text appears only for machine labels, checksums, keypad values, or consent state.
signature patterns
Porcelain shell panels: off-white rounded rectangles with 1px black seams, inner highlight rings, and tiny screw dots at cardinal points.Consent ladder: numbered black capsules connected by fine vertical rules, each paired with a muted teal LED state and short human-readable permission text.Manga service gutters: thick black dividers slice the appliance into scene panels, with small callout tabs crossing panel edges like printed annotations.Checksum keypad rail: bottom-aligned monospaced keys and amber maintenance stamps turn terminal language into a tactile ritual instead of a hacker dashboard.Graphite hatch shadows: restrained diagonal line textures sit inside shadow zones to suggest ceramic volume without decorative illustration.
layout
breakpoints

Desktop 1200+, tablet 768-1199 collapses into two columns, mobile under 640 stacks status, consent, keypad, and maintenance in one column.

density

Medium density with many small hardware labels, counterbalanced by a single quiet central consent area and generous exterior porcelain margins.

grid

Desktop uses 12 columns at max-width 1280px with 24px gutters; kiosk body spans 8 columns, ritual rail spans 3, status strip spans full width.

responsive

Preserve the physical appliance metaphor on all sizes: panels stack as attached modules, gutters remain visible, and LEDs stay adjacent to labels.

whitespace

Use 24px and 32px interior breathing room around important ritual states; use narrow 8px gaps only for keypad and machine-readable labels.

guidance
do
  • Use warm porcelain whites and rice-paper black as the dominant identity.
  • Make service status legible with small muted teal LEDs placed beside text labels.
  • Show robotic affordances such as access seams, ports, keypads, checksums, and maintenance tabs.
  • Write interface copy as permission ritual: request, inspect, consent, assist, log.
  • Keep terminal motifs compact and tactile instead of filling the screen with code.
  • Use manga structure through gutters, callout tabs, and black panel rhythm rather than characters.
avoid
  • Do not use green matrix rain, neon cyberpunk glow, or saturated purple-blue palettes.
  • Do not create generic analytics dashboards, SaaS card grids, or meaningless graphs.
  • Do not use character art, android faces, fan-art references, or narrative illustration.
  • Do not overdecorate with many accent colors; teal and small amber are enough.
  • Do not hide hardware function behind abstract glassmorphism.
  • Do not let status LEDs become ambient glow or sci-fi spectacle.
katagami spec
# Porcelain Android Service Ritual

## Philosophy

Porcelain Android Service Ritual is a quiet interface language for human-scale robotic care: not a hacker console, not fan-art anime, but a service kiosk that feels like a ceramic appliance trained to ask permission. It blends black-and-white manga panel discipline with late-1990s consumer computing hardware cues: rounded access doors, tiny teal service LEDs, keyed ritual steps, and terminal text used as labels rather than spectacle. The system treats interaction as consent choreography, with every panel, light, and confirmation mark making the robot legible, maintainable, and humble.

### Values

- Ritualized consent before automation
- Human-scale robotics care instead of spectacle
- Porcelain restraint with exact black linework
- Machine-readable affordances that stay calm
- Service maintenance honesty: ports, seams, and status lights are visible
- Late-90s hardware softness without translucent toy excess
- Existential quiet: interfaces acknowledge dependence without drama

### Anti-Values

- Neon cyberpunk glow or green matrix rain
- Generic hacker dashboards filled with meaningless charts
- Character illustration, mascot fan art, or anime faces
- SaaS card-grid sameness and default startup dashboards
- Aggressive military robotics styling

### Visual Character

- Warm porcelain white page field with nested rounded technical panels outlined by 1px rice-paper black rules.
- Small muted teal LED dots and bars appear only beside service status, never as ambient neon glow.
- Manga-like black gutters divide the screen into ritual panels with numbered consent steps and speech-label callouts.
- Terminal motifs are compressed into keypad rows, monospaced inspection labels, and checksum stamps rather than full dashboards.
- Soft graphite hatching and faint warm gray shadows describe ceramic curvature while keeping the palette nearly monochrome.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: rice-paper black technical linework with occasional double-rule service seams
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#5F9C9A` |
| background | `#FBF7EF` |
| border | `#26231E` |
| error | `#A44738` |
| info | `#4F7F93` |
| muted | `#6F6960` |
| primary | `#11100E` |
| secondary | `#F4EFE6` |
| success | `#5F9C9A` |
| surface | `#FFFDF7` |
| text | `#141311` |
| warning | `#B9833D` |

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1)
- **Philosophy**: mechanical but gentle: LEDs tick, panels acknowledge, nothing sweeps or pulses like a cyberpunk display

### Radii

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

### Shadows

- **Lg**: 0 28px 70px rgba(60,48,34,0.16)
- **Md**: 0 14px 30px rgba(60,48,34,0.10)
- **Sm**: 0 1px 0 rgba(20,19,17,0.16)

### Spacing

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

### Surfaces

- **Bg Pattern**: barely visible graphite hatch grid at 32px intervals, clipped by manga panel gutters
- **Card Style**: rounded ceramic service plates with black hairline seams, amber maintenance tabs, and inset label wells
- **Treatment**: warm porcelain surfaces, subtle off-white radial highlight, no saturated gradients

### Typography

- **Base Size**: 16px
- **Body Font**: IBM Plex Sans JP
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans+JP:wght@400;500;600;700&family=Zen+Kaku+Gothic+New:wght@500;700;900&display=swap
- **Heading Font**: Zen Kaku Gothic New
- **Letter Spacing**: -0.02em
- **Line Height**: 1.52
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.22

## Rules

### Composition

Use a kiosk-scene composition: one large porcelain robot terminal body, a narrow ritual sidebar, and two lower maintenance panels. Align everything to a strict 12-column grid, then interrupt it with black manga gutters and rounded hardware seams. Avoid floating SaaS cards; every module must look physically attached to the service appliance.

### Density

Medium-high density is acceptable when it resembles labeled hardware, but whitespace must pool around the main consent action and robot status so the kiosk feels caring rather than overloaded.

### Hierarchy

Primary hierarchy comes from panel scale, black rule weight, and numbered ritual order. Headings are compact and heavy; body copy is calm and service-like; monospaced text appears only for machine labels, checksums, keypad values, or consent state.

### Signature Patterns

- Porcelain shell panels: off-white rounded rectangles with 1px black seams, inner highlight rings, and tiny screw dots at cardinal points.
- Consent ladder: numbered black capsules connected by fine vertical rules, each paired with a muted teal LED state and short human-readable permission text.
- Manga service gutters: thick black dividers slice the appliance into scene panels, with small callout tabs crossing panel edges like printed annotations.
- Checksum keypad rail: bottom-aligned monospaced keys and amber maintenance stamps turn terminal language into a tactile ritual instead of a hacker dashboard.
- Graphite hatch shadows: restrained diagonal line textures sit inside shadow zones to suggest ceramic volume without decorative illustration.

## Layout

### Breakpoints

Desktop 1200+, tablet 768-1199 collapses into two columns, mobile under 640 stacks status, consent, keypad, and maintenance in one column.

### Density

Medium density with many small hardware labels, counterbalanced by a single quiet central consent area and generous exterior porcelain margins.

### Grid

Desktop uses 12 columns at max-width 1280px with 24px gutters; kiosk body spans 8 columns, ritual rail spans 3, status strip spans full width.

### Responsive

Preserve the physical appliance metaphor on all sizes: panels stack as attached modules, gutters remain visible, and LEDs stay adjacent to labels.

### Whitespace

Use 24px and 32px interior breathing room around important ritual states; use narrow 8px gaps only for keypad and machine-readable labels.

## Guidance

### Do

- Use warm porcelain whites and rice-paper black as the dominant identity.
- Make service status legible with small muted teal LEDs placed beside text labels.
- Show robotic affordances such as access seams, ports, keypads, checksums, and maintenance tabs.
- Write interface copy as permission ritual: request, inspect, consent, assist, log.
- Keep terminal motifs compact and tactile instead of filling the screen with code.
- Use manga structure through gutters, callout tabs, and black panel rhythm rather than characters.

### Don't

- Do not use green matrix rain, neon cyberpunk glow, or saturated purple-blue palettes.
- Do not create generic analytics dashboards, SaaS card grids, or meaningless graphs.
- Do not use character art, android faces, fan-art references, or narrative illustration.
- Do not overdecorate with many accent colors; teal and small amber are enough.
- Do not hide hardware function behind abstract glassmorphism.
- Do not let status LEDs become ambient glow or sci-fi spectacle.

### Accessibility

Maintain strong text contrast on porcelain surfaces, pair every LED color with text and shape state, keep touch targets above 44px, and avoid relying on animation or hue alone to communicate service status.

### Usage Context

Best for speculative service robot kiosks, care-robot consent flows, appliance-like AI tools, maintenance consoles, and human-robot interaction prototypes that need warmth, restraint, and legibility.
DESIGN.md
---
version: "alpha"
name: "Porcelain Android Service Ritual"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#5F9C9A"
  background: "#FBF7EF"
  border: "#26231E"
  error: "#A44738"
  info: "#4F7F93"
  muted: "#6F6960"
  primary: "#11100E"
  secondary: "#F4EFE6"
  success: "#5F9C9A"
  surface: "#FFFDF7"
  text: "#141311"
  warning: "#B9833D"
typography:
  headline-lg:
    fontFamily: "Zen Kaku Gothic New"
    fontSize: "1.816rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Zen Kaku Gothic New"
    fontSize: "1.488rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "IBM Plex Sans JP"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.52
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "24px"
  md: "24px"
  none: "0px"
  sm: "16px"
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"
---

# Porcelain Android Service Ritual

## Overview

Porcelain Android Service Ritual is a quiet interface language for human-scale robotic care: not a hacker console, not fan-art anime, but a service kiosk that feels like a ceramic appliance trained to ask permission. It blends black-and-white manga panel discipline with late-1990s consumer computing hardware cues: rounded access doors, tiny teal service LEDs, keyed ritual steps, and terminal text used as labels rather than spectacle. The system treats interaction as consent choreography, with every panel, light, and confirmation mark making the robot legible, maintainable, and humble.

### Values

- Ritualized consent before automation
- Human-scale robotics care instead of spectacle
- Porcelain restraint with exact black linework
- Machine-readable affordances that stay calm
- Service maintenance honesty: ports, seams, and status lights are visible
- Late-90s hardware softness without translucent toy excess
- Existential quiet: interfaces acknowledge dependence without drama

### Anti-Values

- Neon cyberpunk glow or green matrix rain
- Generic hacker dashboards filled with meaningless charts
- Character illustration, mascot fan art, or anime faces
- SaaS card-grid sameness and default startup dashboards
- Aggressive military robotics styling

### Visual Character

- Warm porcelain white page field with nested rounded technical panels outlined by 1px rice-paper black rules.
- Small muted teal LED dots and bars appear only beside service status, never as ambient neon glow.
- Manga-like black gutters divide the screen into ritual panels with numbered consent steps and speech-label callouts.
- Terminal motifs are compressed into keypad rows, monospaced inspection labels, and checksum stamps rather than full dashboards.
- Soft graphite hatching and faint warm gray shadows describe ceramic curvature while keeping the palette nearly monochrome.

## 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 | `#5F9C9A` |
| background | `#FBF7EF` |
| border | `#26231E` |
| error | `#A44738` |
| info | `#4F7F93` |
| muted | `#6F6960` |
| primary | `#11100E` |
| secondary | `#F4EFE6` |
| success | `#5F9C9A` |
| surface | `#FFFDF7` |
| text | `#141311` |
| warning | `#B9833D` |

## Typography

- **Headline-Lg**: Zen Kaku Gothic New, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Zen Kaku Gothic New, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans JP, 16px, weight 400, line-height 1.52.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
- **Step-8**: `96px`

### Breakpoints

Desktop 1200+, tablet 768-1199 collapses into two columns, mobile under 640 stacks status, consent, keypad, and maintenance in one column.

### Density

Medium density with many small hardware labels, counterbalanced by a single quiet central consent area and generous exterior porcelain margins.

### Grid

Desktop uses 12 columns at max-width 1280px with 24px gutters; kiosk body spans 8 columns, ritual rail spans 3, status strip spans full width.

### Responsive

Preserve the physical appliance metaphor on all sizes: panels stack as attached modules, gutters remain visible, and LEDs stay adjacent to labels.

### Whitespace

Use 24px and 32px interior breathing room around important ritual states; use narrow 8px gaps only for keypad and machine-readable labels.

## Elevation & Depth

### Shadows

- **Lg**: 0 28px 70px rgba(60,48,34,0.16)
- **Md**: 0 14px 30px rgba(60,48,34,0.10)
- **Sm**: 0 1px 0 rgba(20,19,17,0.16)

## Shapes

### Rounded

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

### Surfaces

- **Bg Pattern**: barely visible graphite hatch grid at 32px intervals, clipped by manga panel gutters
- **Card Style**: rounded ceramic service plates with black hairline seams, amber maintenance tabs, and inset label wells
- **Treatment**: warm porcelain surfaces, subtle off-white radial highlight, no saturated gradients

### Borders

- **Accent Width**: 2px
- **Character**: rice-paper black technical linework with occasional double-rule service seams
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use a kiosk-scene composition: one large porcelain robot terminal body, a narrow ritual sidebar, and two lower maintenance panels. Align everything to a strict 12-column grid, then interrupt it with black manga gutters and rounded hardware seams. Avoid floating SaaS cards; every module must look physically attached to the service appliance.

### Density

Medium-high density is acceptable when it resembles labeled hardware, but whitespace must pool around the main consent action and robot status so the kiosk feels caring rather than overloaded.

### Hierarchy

Primary hierarchy comes from panel scale, black rule weight, and numbered ritual order. Headings are compact and heavy; body copy is calm and service-like; monospaced text appears only for machine labels, checksums, keypad values, or consent state.

### Signature Patterns

- Porcelain shell panels: off-white rounded rectangles with 1px black seams, inner highlight rings, and tiny screw dots at cardinal points.
- Consent ladder: numbered black capsules connected by fine vertical rules, each paired with a muted teal LED state and short human-readable permission text.
- Manga service gutters: thick black dividers slice the appliance into scene panels, with small callout tabs crossing panel edges like printed annotations.
- Checksum keypad rail: bottom-aligned monospaced keys and amber maintenance stamps turn terminal language into a tactile ritual instead of a hacker dashboard.
- Graphite hatch shadows: restrained diagonal line textures sit inside shadow zones to suggest ceramic volume without decorative illustration.

## shadcn/ui Usage

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

DESIGN.md with shadcn: `/language/en-019e07e9-958a-7151-a2be-2abe15e8af3e/DESIGN.with-shadcn.md`.

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

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

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

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

## Do's and Don'ts

- Do Use warm porcelain whites and rice-paper black as the dominant identity.
- Do Make service status legible with small muted teal LEDs placed beside text labels.
- Do Show robotic affordances such as access seams, ports, keypads, checksums, and maintenance tabs.
- Do Write interface copy as permission ritual: request, inspect, consent, assist, log.
- Do Keep terminal motifs compact and tactile instead of filling the screen with code.
- Do Use manga structure through gutters, callout tabs, and black panel rhythm rather than characters.
- Don't Do not use green matrix rain, neon cyberpunk glow, or saturated purple-blue palettes.
- Don't Do not create generic analytics dashboards, SaaS card grids, or meaningless graphs.
- Don't Do not use character art, android faces, fan-art references, or narrative illustration.
- Don't Do not overdecorate with many accent colors; teal and small amber are enough.
- Don't Do not hide hardware function behind abstract glassmorphism.
- Don't Do not let status LEDs become ambient glow or sci-fi spectacle.

### Accessibility

Maintain strong text contrast on porcelain surfaces, pair every LED color with text and shape state, keep touch targets above 44px, and avoid relying on animation or hue alone to communicate service status.

### Usage Context

Best for speculative service robot kiosks, care-robot consent flows, appliance-like AI tools, maintenance consoles, and human-robot interaction prototypes that need warmth, restraint, and legibility.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "porcelain-android-service-ritual",
  "type": "registry:theme",
  "title": "Porcelain Android Service Ritual shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FBF7EF",
      "foreground": "#141311",
      "card": "#FFFDF7",
      "card-foreground": "#141311",
      "popover": "#FFFDF7",
      "popover-foreground": "#141311",
      "primary": "#11100E",
      "primary-foreground": "#ffffff",
      "secondary": "#F4EFE6",
      "secondary-foreground": "#111111",
      "muted": "#6F6960",
      "muted-foreground": "#141311",
      "accent": "#5F9C9A",
      "accent-foreground": "#ffffff",
      "destructive": "#A44738",
      "border": "#26231E",
      "input": "#26231E",
      "ring": "#5F9C9A",
      "chart-1": "#11100E",
      "chart-2": "#F4EFE6",
      "chart-3": "#5F9C9A",
      "chart-4": "#5F9C9A",
      "chart-5": "#B9833D",
      "sidebar": "#FFFDF7",
      "sidebar-foreground": "#141311",
      "sidebar-primary": "#11100E",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#4F7F93",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#26231E",
      "sidebar-ring": "#5F9C9A",
      "radius": "24px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#11100E",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#5F9C9A",
      "accent-foreground": "#ffffff",
      "destructive": "#A44738",
      "border": "#303642",
      "input": "#303642",
      "ring": "#5F9C9A",
      "chart-1": "#11100E",
      "chart-2": "#F4EFE6",
      "chart-3": "#5F9C9A",
      "chart-4": "#5F9C9A",
      "chart-5": "#B9833D",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#11100E",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5F9C9A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#5F9C9A",
      "radius": "24px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e07e9-958a-7151-a2be-2abe15e8af3e",
    "slug": "porcelain-android-service-ritual",
    "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 · porcelain-android-service-ritual
DESIGN.md

at a glance

Palette

Typography

headline-lgZen Kaku Gothic New · 29px · 700

The quick brown fox jumps

headline-mdZen Kaku Gothic New · 24px · 600

The quick brown fox jumps

body-mdIBM Plex Sans JP · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

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

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl48px
  • 4xl64px
  • step-896px

Shape

full9999px
lg24px
md24px
none0px
sm16px
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: #FBF7EF;
  --foreground: #141311;
  --card: #FFFDF7;
  --card-foreground: #141311;
  --popover: #FFFDF7;
  --popover-foreground: #141311;
  --primary: #11100E;
  --primary-foreground: #ffffff;
  --secondary: #F4EFE6;
  --secondary-foreground: #111111;
  --muted: #6F6960;
  --muted-foreground: #141311;
  --accent: #5F9C9A;
  --accent-foreground: #ffffff;
  --destructive: #A44738;
  --border: #26231E;
  --input: #26231E;
  --ring: #5F9C9A;
  --chart-1: #11100E;
  --chart-2: #F4EFE6;
  --chart-3: #5F9C9A;
  --chart-4: #5F9C9A;
  --chart-5: #B9833D;
  --sidebar: #FFFDF7;
  --sidebar-foreground: #141311;
  --sidebar-primary: #11100E;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #4F7F93;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #26231E;
  --sidebar-ring: #5F9C9A;
  --radius: 24px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #11100E;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #5F9C9A;
  --accent-foreground: #ffffff;
  --destructive: #A44738;
  --border: #303642;
  --input: #303642;
  --ring: #5F9C9A;
  --chart-1: #11100E;
  --chart-2: #F4EFE6;
  --chart-3: #5F9C9A;
  --chart-4: #5F9C9A;
  --chart-5: #B9833D;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #11100E;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #5F9C9A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #5F9C9A;
  --radius: 24px;
}
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 PorcelainAndroidServiceRitualShadcnKit() {
  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">Porcelain Android Service Ritual</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": "porcelain-android-service-ritual",
  "type": "registry:theme",
  "title": "Porcelain Android Service Ritual shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FBF7EF",
      "foreground": "#141311",
      "card": "#FFFDF7",
      "card-foreground": "#141311",
      "popover": "#FFFDF7",
      "popover-foreground": "#141311",
      "primary": "#11100E",
      "primary-foreground": "#ffffff",
      "secondary": "#F4EFE6",
      "secondary-foreground": "#111111",
      "muted": "#6F6960",
      "muted-foreground": "#141311",
      "accent": "#5F9C9A",
      "accent-foreground": "#ffffff",
      "destructive": "#A44738",
      "border": "#26231E",
      "input": "#26231E",
      "ring": "#5F9C9A",
      "chart-1": "#11100E",
      "chart-2": "#F4EFE6",
      "chart-3": "#5F9C9A",
      "chart-4": "#5F9C9A",
      "chart-5": "#B9833D",
      "sidebar": "#FFFDF7",
      "sidebar-foreground": "#141311",
      "sidebar-primary": "#11100E",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#4F7F93",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#26231E",
      "sidebar-ring": "#5F9C9A",
      "radius": "24px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#11100E",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#5F9C9A",
      "accent-foreground": "#ffffff",
      "destructive": "#A44738",
      "border": "#303642",
      "input": "#303642",
      "ring": "#5F9C9A",
      "chart-1": "#11100E",
      "chart-2": "#F4EFE6",
      "chart-3": "#5F9C9A",
      "chart-4": "#5F9C9A",
      "chart-5": "#B9833D",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#11100E",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5F9C9A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#5F9C9A",
      "radius": "24px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e07e9-958a-7151-a2be-2abe15e8af3e",
    "slug": "porcelain-android-service-ritual",
    "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
# Porcelain Android Service Ritual shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e07e9-958a-7151-a2be-2abe15e8af3e`
Slug: `porcelain-android-service-ritual`

## Intent

Porcelain Android Service Ritual is a quiet interface language for human-scale robotic care: not a hacker console, not fan-art anime, but a service kiosk that feels like a ceramic appliance trained to ask permission. It blends black-and-white manga panel discipline with late-1990s consumer computing hardware cues: rounded access doors, tiny teal service LEDs, keyed ritual steps, and terminal text used as labels rather than spectacle. The system treats interaction as consent choreography, with every panel, light, and confirmation mark making the robot legible, maintainable, and humble.

## 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": "#5F9C9A",
  "background": "#FBF7EF",
  "border": "#26231E",
  "error": "#A44738",
  "info": "#4F7F93",
  "muted": "#6F6960",
  "primary": "#11100E",
  "secondary": "#F4EFE6",
  "success": "#5F9C9A",
  "surface": "#FFFDF7",
  "text": "#141311",
  "warning": "#B9833D"
}

Typography:

{
  "base_size": "16px",
  "body_font": "IBM Plex Sans JP",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans+JP:wght@400;500;600;700&family=Zen+Kaku+Gothic+New:wght@500;700;900&display=swap",
  "heading_font": "Zen Kaku Gothic New",
  "letter_spacing": "-0.02em",
  "line_height": 1.52,
  "mono_font": "IBM Plex Mono",
  "scale_ratio": 1.22
}

## Visual character to preserve

- Warm porcelain white page field with nested rounded technical panels outlined by 1px rice-paper black rules.
- Small muted teal LED dots and bars appear only beside service status, never as ambient neon glow.
- Manga-like black gutters divide the screen into ritual panels with numbered consent steps and speech-label callouts.
- Terminal motifs are compressed into keypad rows, monospaced inspection labels, and checksum stamps rather than full dashboards.
- Soft graphite hatching and faint warm gray shadows describe ceramic curvature while keeping the palette nearly monochrome.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": true,
  "stickerBadges": true,
  "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/porcelain-android-service-ritual/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use warm porcelain whites and rice-paper black as the dominant identity.; Make service status legible with small muted teal LEDs placed beside text labels.; Show robotic affordances such as access seams, ports, keypads, checksums, and maintenance tabs.; Write interface copy as permission ritual: request, inspect, consent, assist, log.; Keep terminal motifs compact and tactile instead of filling the screen with code.; Use manga structure through gutters, callout tabs, and black panel rhythm rather than characters.
- Do not: Do not use green matrix rain, neon cyberpunk glow, or saturated purple-blue palettes.; Do not create generic analytics dashboards, SaaS card grids, or meaningless graphs.; Do not use character art, android faces, fan-art references, or narrative illustration.; Do not overdecorate with many accent colors; teal and small amber are enough.; Do not hide hardware function behind abstract glassmorphism.; Do not let status LEDs become ambient glow or sci-fi spectacle.

## 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 PorcelainAndroidServiceRitualShadcnKit() {
  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">Porcelain Android Service Ritual</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": "Desktop 1200+, tablet 768-1199 collapses into two columns, mobile under 640 stacks status, consent, keypad, and maintenance in one column.",
  "density": "Medium density with many small hardware labels, counterbalanced by a single quiet central consent area and generous exterior porcelain margins.",
  "grid": "Desktop uses 12 columns at max-width 1280px with 24px gutters; kiosk body spans 8 columns, ritual rail spans 3, status strip spans full width.",
  "responsive": "Preserve the physical appliance metaphor on all sizes: panels stack as attached modules, gutters remain visible, and LEDs stay adjacent to labels.",
  "whitespace": "Use 24px and 32px interior breathing room around important ritual states; use narrow 8px gaps only for keypad and machine-readable labels."
}
preview shotscompatibility fallback
{
  "artifact": "katagami:shadcn-preview-shots",
  "version": "preview-shots-v1",
  "generator": "katagami-ui-compatibility-projection",
  "generatedBy": "katagami-ui-projection",
  "requiresVisualProfile": true,
  "schema": "katagami:shadcn-preview-shots/renderable-v1",
  "renderable": true,
  "language": {
    "id": "en-019e07e9-958a-7151-a2be-2abe15e8af3e",
    "name": "Porcelain Android Service Ritual",
    "slug": "porcelain-android-service-ritual"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "Warm porcelain white page field with nested rounded technical panels outlined by 1px rice-paper black rules.",
    "Small muted teal LED dots and bars appear only beside service status, never as ambient neon glow.",
    "Manga-like black gutters divide the screen into ritual panels with numbered consent steps and speech-label callouts.",
    "Terminal motifs are compressed into keypad rows, monospaced inspection labels, and checksum stamps rather than full dashboards.",
    "Soft graphite hatching and faint warm gray shadows describe ceramic curvature while keeping the palette nearly monochrome."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": true,
    "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": "Porcelain Android Service Ritual launch room",
        "description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
        "primaryAction": "Apply theme",
        "secondaryAction": "Review states",
        "stats": [
          {
            "label": "components",
            "value": "16",
            "tone": "accent"
          },
          {
            "label": "states",
            "value": "ready"
          },
          {
            "label": "density",
            "value": "balanced",
            "tone": "warning"
          }
        ],
        "rows": [
          {
            "label": "Primary flow",
            "value": "mapped",
            "status": "active"
          },
          {
            "label": "Token coverage",
            "value": "semantic",
            "status": "synced"
          },
          {
            "label": "Responsive proof",
            "value": "queued",
            "status": "review"
          }
        ],
        "statuses": [
          "Active",
          "Synced",
          "Draft"
        ]
      }
    },
    {
      "id": "detail-editor",
      "title": "Detail editor",
      "viewport": "tablet",
      "primitives": [
        "button",
        "card",
        "input",
        "textarea",
        "select",
        "checkbox",
        "switch",
        "slider",
        "dialog",
        "sheet"
      ],
      "composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
      "mustShow": [
        "focus ring",
        "error or destructive state",
        "dialog or sheet treatment",
        "written guidance content"
      ],
      "avoid": [
        "unstyled browser controls",
        "floating cards inside cards",
        "missing labels"
      ],
      "scene": {
        "eyebrow": "editing flow",
        "headline": "Language recipe editor",
        "description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
        "primaryAction": "Save recipe",
        "secondaryAction": "Open sheet",
        "fields": [
          {
            "label": "Component family",
            "value": "Narrative cards"
          },
          {
            "label": "State treatment",
            "value": "Visible focus + validation"
          },
          {
            "label": "Motion",
            "value": "Small lift, no opacity-only fade"
          }
        ],
        "statuses": [
          "Focus",
          "Invalid",
          "Confirmed"
        ]
      }
    },
    {
      "id": "data-operations",
      "title": "Data operations",
      "viewport": "mobile",
      "primitives": [
        "button",
        "tabs",
        "badge",
        "dropdown-menu",
        "table",
        "tooltip",
        "separator"
      ],
      "composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
      "mustShow": [
        "responsive reflow",
        "dense row styling",
        "menu affordance",
        "status badge system"
      ],
      "avoid": [
        "desktop-only tables",
        "text overflow",
        "default shadcn spacing without Katagami character"
      ],
      "scene": {
        "eyebrow": "operations",
        "headline": "Compact review queue",
        "description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
        "primaryAction": "Resolve",
        "secondaryAction": "Filter",
        "rows": [
          {
            "label": "Button hierarchy",
            "value": "approved",
            "status": "ok"
          },
          {
            "label": "Table rhythm",
            "value": "needs pass",
            "status": "watch"
          },
          {
            "label": "Empty state",
            "value": "designed",
            "status": "done"
          }
        ],
        "statuses": [
          "Queued",
          "Blocked",
          "Done"
        ]
      }
    }
  ],
  "componentRecipes": [
    {
      "primitive": "button",
      "intent": "Prove action hierarchy, focus, disabled, and destructive states."
    },
    {
      "primitive": "card",
      "intent": "Carry the language surface, border, elevation, and density rules."
    },
    {
      "primitive": "input",
      "intent": "Show labels, focus rings, validation, and spacing rhythm."
    },
    {
      "primitive": "textarea",
      "intent": "Show longer guidance, validation copy, and writing density."
    },
    {
      "primitive": "select",
      "intent": "Show filtering, selection contrast, and menu trigger styling."
    },
    {
      "primitive": "dialog",
      "intent": "Show centered decision states and overlay treatment."
    },
    {
      "primitive": "sheet",
      "intent": "Show contextual side panels and responsive editing."
    },
    {
      "primitive": "tabs",
      "intent": "Show navigational structure and active/inactive contrast."
    },
    {
      "primitive": "badge",
      "intent": "Show compact status vocabulary and semantic colors."
    },
    {
      "primitive": "separator",
      "intent": "Show section rhythm without generic gray dividers."
    },
    {
      "primitive": "checkbox",
      "intent": "Show binary selection with visible focus and checked states."
    },
    {
      "primitive": "switch",
      "intent": "Show settings toggles and on/off contrast."
    },
    {
      "primitive": "slider",
      "intent": "Show numeric adjustment with track/thumb styling."
    },
    {
      "primitive": "tooltip",
      "intent": "Show concise explanation styling above compact controls."
    },
    {
      "primitive": "dropdown-menu",
      "intent": "Show action menus, destructive items, and grouped choices."
    },
    {
      "primitive": "table",
      "intent": "Show dense operational data, separators, row states, and responsive behavior."
    }
  ],
  "qualityRules": {
    "do": [
      "Use warm porcelain whites and rice-paper black as the dominant identity.",
      "Make service status legible with small muted teal LEDs placed beside text labels.",
      "Show robotic affordances such as access seams, ports, keypads, checksums, and maintenance tabs.",
      "Write interface copy as permission ritual: request, inspect, consent, assist, log.",
      "Keep terminal motifs compact and tactile instead of filling the screen with code.",
      "Use manga structure through gutters, callout tabs, and black panel rhythm rather than characters."
    ],
    "dont": [
      "Do not use green matrix rain, neon cyberpunk glow, or saturated purple-blue palettes.",
      "Do not create generic analytics dashboards, SaaS card grids, or meaningless graphs.",
      "Do not use character art, android faces, fan-art references, or narrative illustration.",
      "Do not overdecorate with many accent colors; teal and small amber are enough.",
      "Do not hide hardware function behind abstract glassmorphism.",
      "Do not let status LEDs become ambient glow or sci-fi spectacle."
    ]
  }
}
related

More like this