Silent Gantry Notation
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.
specification
philosophy
tokens
borders4 items
- accent width
- 2px
- character
- black manga gutters, pale HUD hairlines, and amber callout rules used only for mechanical attention
- default width
- 1px
- style
- solid with occasional dotted leader lines for exploded notation
colors12 items
motion3 items
- duration
- 180ms
- easing
- cubic-bezier(0.2, 0, 0.1, 1)
- philosophy
- subtle LCD state changes and scanline calibration only; no continuous animated spectacle in static embodiment
radii5 items
- full
- 9999px
- lg
- 24px
- md
- 16px
- none
- 0
- sm
- 0
shadows3 items
- lg
- 0 40px 120px rgba(0,0,0,0.62)
- md
- 0 18px 50px rgba(0,0,0,0.38)
- sm
- 0 1px 0 rgba(255,255,255,0.08)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64, 96, 128
surfaces3 items
- bg pattern
- deep black field with sparse panel registration ticks and low-contrast hardware seam lines
- card style
- square or 16px-radius panels with 1px technical borders, inset labels, and no decorative drop shadows on light panels
- treatment
- matte graphite shells interrupted by warm off-white manga sheets and desaturated LCD gray fields
typography8 items
- base size
- 16px
- body font
- IBM Plex Sans Condensed
- google fonts url
- https://fonts.googleapis.com/css2?family=Azeret+Mono:wght@500;700&family=IBM+Plex+Sans+Condensed:wght@400;500;600&family=Share+Tech+Mono&display=swap
- heading font
- Azeret Mono
- letter spacing
- -0.02em
- line height
- 1.48
- mono font
- Share Tech Mono
- scale ratio
- 1.22
rules
Use a scene-first cockpit diagnostic layout: one large off-center aperture, two or three manga-document panels, a narrow terminal rail, and generous black negative space. Align annotations to a strict orthogonal grid, but let dotted leaders cross the aperture like technical drawings. Keep the mecha diagram distant and segmented rather than centered like a poster.
Medium-low density with local high-density annotation clusters: most of the screen remains quiet, while exact cockpit systems, vector arcs, and diagnostic fields cluster only where the operator would scan.
Primary hierarchy belongs to mission state and aperture scale; secondary hierarchy belongs to panel titles, terminal bands, and amber mechanical callouts. Use condensed sans for operational labels, square monospace for serial fragments, and compact uppercase captions with negative tracking applied consistently.
layout
- desktop
- 1200px and up asymmetric 12-column frame
- mobile
- 375px single-column stacked panels
- tablet
- 768px two-zone cockpit then diagnostics
A 60/40 split between void and instrumentation keeps the interface readable while preserving the existential cockpit mood.
Desktop uses a 12-column grid, 24px gutters, max-width 1360px; the aperture spans seven columns while document panels stack across the remaining five.
On tablet the terminal rail moves below the aperture; on mobile the manga panels become sequential frames with annotations simplified but not removed.
Black negative space is an active layout material; keep at least one empty quadrant or long dark corridor visible at every viewport.
guidance
- Use thick black gutters to make manga structure visible before any UI details are noticed.
- Keep HUD arcs one-pixel thin, pale, and clipped by the cockpit aperture.
- Group cockpit controls into labeled operational clusters that reduce scan effort.
- Use amber only for mechanical callout numbers, warnings, and leader endpoints.
- Let off-white panels feel like printed technical sheets rather than glossy cards.
- Include terminal text that reads like mission state, serial diagnostics, or calibration logs.
- Preserve empty black space to communicate scale and quiet machine distance.
- Do not use green matrix rain, neon cyberpunk gradients, or saturated glow effects.
- Do not fill the scene with generic dashboard widgets or SaaS metric cards.
- Do not add anime characters, pilots, mascots, or heroic mecha poster poses.
- Do not make HUD elements decorative if they do not support orientation or status.
- Do not mix many accent colors; amber and pale blue-white are enough.
- Do not round every surface; square hardware edges are the default.
- Do not use unreadable fake microtext as texture.
katagami spec
# Silent Gantry Notation ## Philosophy Silent Gantry Notation is a restrained cockpit language for mission-critical machine proximity: black-and-white manga panel structure holds a distant mecha diagnostic frame, while pale HUD arcs and sparse amber callouts describe systems without turning the interface into spectacle. It treats the pilot screen as a place of quiet operational doubt, using absence, scale, and measured annotation to make the machine feel present but not anthropomorphic. ### Values - Restraint before information density: only the marks required for orientation, state, and consequence remain visible. - Human-centered cockpit readability: grouped instruments, predictable scan paths, and high contrast labels support operator task performance. - Manga panel discipline: warm off-white frames and black gutters create narrative sequencing without character illustration. - Machine-body distance: the mecha appears as segmented silhouette, exploded annotation, and telemetry rather than as heroic fan art. - Late-1990s hardware materiality: graphite bezels, small serial labels, LCD fields, and terminal fragments ground the speculative interface. - HUD restraint: arcs, reticles, and vectors are thin, pale, and subordinate to status hierarchy rather than decorative glow. ### Anti-Values - No green matrix rain, generic hacker dashboards, saturated cyberpunk glow, or decorative neon atmosphere. - No crowded SaaS card grids, marketing component catalogs, or arbitrary rounded white panels. - No character fan art, mascot cockpit pilots, or anime spectacle that overwhelms the operational interface. - No fake complexity through unreadable microtext; every terminal fragment and label must look placed for a reason. ### Visual Character - Asymmetric manga-panel grid with thick black gutters, warm off-white data sheets, and one dominant matte graphite cockpit aperture. - Thin pale blue-white HUD arcs built from CSS borders and pseudo-elements, never glowing more than a one-pixel technical overlay. - Exploded mecha notation using dotted leader lines, small amber-orange numbered callouts, and separated graphite component silhouettes. - Terminal fragments in compact monospace bands with Y2K serial labels, square LCD insets, and hardware tab captions. - Large zones of deliberate empty black space around the machine diagram to express scale, silence, and human-machine distance. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: black manga gutters, pale HUD hairlines, and amber callout rules used only for mechanical attention - **Default Width**: 1px - **Style**: solid with occasional dotted leader lines for exploded notation ### Colors | Name | Value | |------|-------| | accent | `#D9822B` | | background | `#050607` | | border | `#C8C0B2` | | error | `#B84A3A` | | info | `#BFDDE8` | | muted | `#8E9498` | | primary | `#0A0B0D` | | secondary | `#2B2F33` | | success | `#7C8F75` | | surface | `#F1EDE2` | | text | `#F6F1E7` | | warning | `#D9822B` | ### Motion - **Duration**: 180ms - **Easing**: cubic-bezier(0.2, 0, 0.1, 1) - **Philosophy**: subtle LCD state changes and scanline calibration only; no continuous animated spectacle in static embodiment ### Radii - **Full**: 9999px - **Lg**: 24px - **Md**: 16px - **None**: 0 - **Sm**: 0 ### Shadows - **Lg**: 0 40px 120px rgba(0,0,0,0.62) - **Md**: 0 18px 50px rgba(0,0,0,0.38) - **Sm**: 0 1px 0 rgba(255,255,255,0.08) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64,96,128] ### Surfaces - **Bg Pattern**: deep black field with sparse panel registration ticks and low-contrast hardware seam lines - **Card Style**: square or 16px-radius panels with 1px technical borders, inset labels, and no decorative drop shadows on light panels - **Treatment**: matte graphite shells interrupted by warm off-white manga sheets and desaturated LCD gray fields ### Typography - **Base Size**: 16px - **Body Font**: IBM Plex Sans Condensed - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Azeret+Mono:wght@500;700&family=IBM+Plex+Sans+Condensed:wght@400;500;600&family=Share+Tech+Mono&display=swap - **Heading Font**: Azeret Mono - **Letter Spacing**: -0.02em - **Line Height**: 1.48 - **Mono Font**: Share Tech Mono - **Scale Ratio**: 1.22 ## Rules ### Composition Use a scene-first cockpit diagnostic layout: one large off-center aperture, two or three manga-document panels, a narrow terminal rail, and generous black negative space. Align annotations to a strict orthogonal grid, but let dotted leaders cross the aperture like technical drawings. Keep the mecha diagram distant and segmented rather than centered like a poster. ### Density Medium-low density with local high-density annotation clusters: most of the screen remains quiet, while exact cockpit systems, vector arcs, and diagnostic fields cluster only where the operator would scan. ### Hierarchy Primary hierarchy belongs to mission state and aperture scale; secondary hierarchy belongs to panel titles, terminal bands, and amber mechanical callouts. Use condensed sans for operational labels, square monospace for serial fragments, and compact uppercase captions with negative tracking applied consistently. ### Signature Patterns - Manga gutter cockpit frame: thick black structural gutters divide warm paper panels from a single dark machine aperture. - Hairline HUD aperture arcs: CSS border-radius rings, clipped corners, and crosshair ticks float in pale blue-white over graphite. - Exploded amber leader notation: dotted lines connect numbered orange tabs to separated mecha component silhouettes. - Y2K hardware label rail: tiny serial plates, LCD rectangles, and terminal strings sit inside graphite tabs along panel edges. - Negative-space machine distance: large unfilled black areas isolate the pilot system from the machine body diagram. ## Layout ### Breakpoints - **Desktop**: 1200px and up asymmetric 12-column frame - **Mobile**: 375px single-column stacked panels - **Tablet**: 768px two-zone cockpit then diagnostics ### Density A 60/40 split between void and instrumentation keeps the interface readable while preserving the existential cockpit mood. ### Grid Desktop uses a 12-column grid, 24px gutters, max-width 1360px; the aperture spans seven columns while document panels stack across the remaining five. ### Responsive On tablet the terminal rail moves below the aperture; on mobile the manga panels become sequential frames with annotations simplified but not removed. ### Whitespace Black negative space is an active layout material; keep at least one empty quadrant or long dark corridor visible at every viewport. ## Guidance ### Do - Use thick black gutters to make manga structure visible before any UI details are noticed. - Keep HUD arcs one-pixel thin, pale, and clipped by the cockpit aperture. - Group cockpit controls into labeled operational clusters that reduce scan effort. - Use amber only for mechanical callout numbers, warnings, and leader endpoints. - Let off-white panels feel like printed technical sheets rather than glossy cards. - Include terminal text that reads like mission state, serial diagnostics, or calibration logs. - Preserve empty black space to communicate scale and quiet machine distance. ### Don't - Do not use green matrix rain, neon cyberpunk gradients, or saturated glow effects. - Do not fill the scene with generic dashboard widgets or SaaS metric cards. - Do not add anime characters, pilots, mascots, or heroic mecha poster poses. - Do not make HUD elements decorative if they do not support orientation or status. - Do not mix many accent colors; amber and pale blue-white are enough. - Do not round every surface; square hardware edges are the default. - Do not use unreadable fake microtext as texture. ### Accessibility Maintain high contrast between text and matte graphite, keep terminal sizes at 12px or larger, never rely on amber alone for state, and preserve clear reading order when panels stack. ### Usage Context Best for speculative cockpit systems, robotics control, aerospace mission displays, technical narrative tools, and editorial products about machine embodiment.
DESIGN.md
---
version: "alpha"
name: "Silent Gantry Notation"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#D9822B"
background: "#050607"
border: "#C8C0B2"
error: "#B84A3A"
info: "#BFDDE8"
muted: "#8E9498"
primary: "#0A0B0D"
secondary: "#2B2F33"
success: "#7C8F75"
surface: "#F1EDE2"
text: "#F6F1E7"
warning: "#D9822B"
typography:
headline-lg:
fontFamily: "Azeret Mono"
fontSize: "1.816rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.02em"
headline-md:
fontFamily: "Azeret Mono"
fontSize: "1.488rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.02em"
body-md:
fontFamily: "IBM Plex Sans Condensed"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.48
letterSpacing: "-0.02em"
label-md:
fontFamily: "Share Tech Mono"
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"
step-9: "128px"
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"
---
# Silent Gantry Notation
## Overview
Silent Gantry Notation is a restrained cockpit language for mission-critical machine proximity: black-and-white manga panel structure holds a distant mecha diagnostic frame, while pale HUD arcs and sparse amber callouts describe systems without turning the interface into spectacle. It treats the pilot screen as a place of quiet operational doubt, using absence, scale, and measured annotation to make the machine feel present but not anthropomorphic.
### Values
- Restraint before information density: only the marks required for orientation, state, and consequence remain visible.
- Human-centered cockpit readability: grouped instruments, predictable scan paths, and high contrast labels support operator task performance.
- Manga panel discipline: warm off-white frames and black gutters create narrative sequencing without character illustration.
- Machine-body distance: the mecha appears as segmented silhouette, exploded annotation, and telemetry rather than as heroic fan art.
- Late-1990s hardware materiality: graphite bezels, small serial labels, LCD fields, and terminal fragments ground the speculative interface.
- HUD restraint: arcs, reticles, and vectors are thin, pale, and subordinate to status hierarchy rather than decorative glow.
### Anti-Values
- No green matrix rain, generic hacker dashboards, saturated cyberpunk glow, or decorative neon atmosphere.
- No crowded SaaS card grids, marketing component catalogs, or arbitrary rounded white panels.
- No character fan art, mascot cockpit pilots, or anime spectacle that overwhelms the operational interface.
- No fake complexity through unreadable microtext; every terminal fragment and label must look placed for a reason.
### Visual Character
- Asymmetric manga-panel grid with thick black gutters, warm off-white data sheets, and one dominant matte graphite cockpit aperture.
- Thin pale blue-white HUD arcs built from CSS borders and pseudo-elements, never glowing more than a one-pixel technical overlay.
- Exploded mecha notation using dotted leader lines, small amber-orange numbered callouts, and separated graphite component silhouettes.
- Terminal fragments in compact monospace bands with Y2K serial labels, square LCD insets, and hardware tab captions.
- Large zones of deliberate empty black space around the machine diagram to express scale, silence, and human-machine distance.
## 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 | `#D9822B` |
| background | `#050607` |
| border | `#C8C0B2` |
| error | `#B84A3A` |
| info | `#BFDDE8` |
| muted | `#8E9498` |
| primary | `#0A0B0D` |
| secondary | `#2B2F33` |
| success | `#7C8F75` |
| surface | `#F1EDE2` |
| text | `#F6F1E7` |
| warning | `#D9822B` |
## Typography
- **Headline-Lg**: Azeret Mono, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Azeret Mono, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans Condensed, 16px, weight 400, line-height 1.48.
- **Label-Md**: Share Tech 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`
- **Step-9**: `128px`
### Breakpoints
- **Desktop**: 1200px and up asymmetric 12-column frame
- **Mobile**: 375px single-column stacked panels
- **Tablet**: 768px two-zone cockpit then diagnostics
### Density
A 60/40 split between void and instrumentation keeps the interface readable while preserving the existential cockpit mood.
### Grid
Desktop uses a 12-column grid, 24px gutters, max-width 1360px; the aperture spans seven columns while document panels stack across the remaining five.
### Responsive
On tablet the terminal rail moves below the aperture; on mobile the manga panels become sequential frames with annotations simplified but not removed.
### Whitespace
Black negative space is an active layout material; keep at least one empty quadrant or long dark corridor visible at every viewport.
## Elevation & Depth
### Shadows
- **Lg**: 0 40px 120px rgba(0,0,0,0.62)
- **Md**: 0 18px 50px rgba(0,0,0,0.38)
- **Sm**: 0 1px 0 rgba(255,255,255,0.08)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `24px`
- **Md**: `16px`
- **None**: `0px`
- **Sm**: `0px`
### Surfaces
- **Bg Pattern**: deep black field with sparse panel registration ticks and low-contrast hardware seam lines
- **Card Style**: square or 16px-radius panels with 1px technical borders, inset labels, and no decorative drop shadows on light panels
- **Treatment**: matte graphite shells interrupted by warm off-white manga sheets and desaturated LCD gray fields
### Borders
- **Accent Width**: 2px
- **Character**: black manga gutters, pale HUD hairlines, and amber callout rules used only for mechanical attention
- **Default Width**: 1px
- **Style**: solid with occasional dotted leader lines for exploded notation
## Components
### Composition
Use a scene-first cockpit diagnostic layout: one large off-center aperture, two or three manga-document panels, a narrow terminal rail, and generous black negative space. Align annotations to a strict orthogonal grid, but let dotted leaders cross the aperture like technical drawings. Keep the mecha diagram distant and segmented rather than centered like a poster.
### Density
Medium-low density with local high-density annotation clusters: most of the screen remains quiet, while exact cockpit systems, vector arcs, and diagnostic fields cluster only where the operator would scan.
### Hierarchy
Primary hierarchy belongs to mission state and aperture scale; secondary hierarchy belongs to panel titles, terminal bands, and amber mechanical callouts. Use condensed sans for operational labels, square monospace for serial fragments, and compact uppercase captions with negative tracking applied consistently.
### Signature Patterns
- Manga gutter cockpit frame: thick black structural gutters divide warm paper panels from a single dark machine aperture.
- Hairline HUD aperture arcs: CSS border-radius rings, clipped corners, and crosshair ticks float in pale blue-white over graphite.
- Exploded amber leader notation: dotted lines connect numbered orange tabs to separated mecha component silhouettes.
- Y2K hardware label rail: tiny serial plates, LCD rectangles, and terminal strings sit inside graphite tabs along panel edges.
- Negative-space machine distance: large unfilled black areas isolate the pilot system from the machine body diagram.
## 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-019e07eb-20b2-7ba1-9e99-d97c57d1d6d9/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 thick black gutters to make manga structure visible before any UI details are noticed.
- Do Keep HUD arcs one-pixel thin, pale, and clipped by the cockpit aperture.
- Do Group cockpit controls into labeled operational clusters that reduce scan effort.
- Do Use amber only for mechanical callout numbers, warnings, and leader endpoints.
- Do Let off-white panels feel like printed technical sheets rather than glossy cards.
- Do Include terminal text that reads like mission state, serial diagnostics, or calibration logs.
- Do Preserve empty black space to communicate scale and quiet machine distance.
- Don't Do not use green matrix rain, neon cyberpunk gradients, or saturated glow effects.
- Don't Do not fill the scene with generic dashboard widgets or SaaS metric cards.
- Don't Do not add anime characters, pilots, mascots, or heroic mecha poster poses.
- Don't Do not make HUD elements decorative if they do not support orientation or status.
- Don't Do not mix many accent colors; amber and pale blue-white are enough.
- Don't Do not round every surface; square hardware edges are the default.
- Don't Do not use unreadable fake microtext as texture.
### Accessibility
Maintain high contrast between text and matte graphite, keep terminal sizes at 12px or larger, never rely on amber alone for state, and preserve clear reading order when panels stack.
### Usage Context
Best for speculative cockpit systems, robotics control, aerospace mission displays, technical narrative tools, and editorial products about machine embodiment.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "silent-gantry-notation",
"type": "registry:theme",
"title": "Silent Gantry Notation shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#050607",
"foreground": "#F6F1E7",
"card": "#F1EDE2",
"card-foreground": "#F6F1E7",
"popover": "#F1EDE2",
"popover-foreground": "#F6F1E7",
"primary": "#0A0B0D",
"primary-foreground": "#ffffff",
"secondary": "#2B2F33",
"secondary-foreground": "#ffffff",
"muted": "#8E9498",
"muted-foreground": "#F6F1E7",
"accent": "#D9822B",
"accent-foreground": "#ffffff",
"destructive": "#B84A3A",
"border": "#C8C0B2",
"input": "#C8C0B2",
"ring": "#D9822B",
"chart-1": "#0A0B0D",
"chart-2": "#2B2F33",
"chart-3": "#D9822B",
"chart-4": "#7C8F75",
"chart-5": "#D9822B",
"sidebar": "#F1EDE2",
"sidebar-foreground": "#F6F1E7",
"sidebar-primary": "#0A0B0D",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#BFDDE8",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#C8C0B2",
"sidebar-ring": "#D9822B",
"radius": "16px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#0A0B0D",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#D9822B",
"accent-foreground": "#ffffff",
"destructive": "#B84A3A",
"border": "#303642",
"input": "#303642",
"ring": "#D9822B",
"chart-1": "#0A0B0D",
"chart-2": "#2B2F33",
"chart-3": "#D9822B",
"chart-4": "#7C8F75",
"chart-5": "#D9822B",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#0A0B0D",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#D9822B",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#D9822B",
"radius": "16px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e07eb-20b2-7ba1-9e99-d97c57d1d6d9",
"slug": "silent-gantry-notation",
"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"
]
}
}
}
```embodiments
at a glance
Typography
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Components
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
- step-9128px
Shape
implementation kit
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
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #050607;
--foreground: #F6F1E7;
--card: #F1EDE2;
--card-foreground: #F6F1E7;
--popover: #F1EDE2;
--popover-foreground: #F6F1E7;
--primary: #0A0B0D;
--primary-foreground: #ffffff;
--secondary: #2B2F33;
--secondary-foreground: #ffffff;
--muted: #8E9498;
--muted-foreground: #F6F1E7;
--accent: #D9822B;
--accent-foreground: #ffffff;
--destructive: #B84A3A;
--border: #C8C0B2;
--input: #C8C0B2;
--ring: #D9822B;
--chart-1: #0A0B0D;
--chart-2: #2B2F33;
--chart-3: #D9822B;
--chart-4: #7C8F75;
--chart-5: #D9822B;
--sidebar: #F1EDE2;
--sidebar-foreground: #F6F1E7;
--sidebar-primary: #0A0B0D;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #BFDDE8;
--sidebar-accent-foreground: #111111;
--sidebar-border: #C8C0B2;
--sidebar-ring: #D9822B;
--radius: 16px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #0A0B0D;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #D9822B;
--accent-foreground: #ffffff;
--destructive: #B84A3A;
--border: #303642;
--input: #303642;
--ring: #D9822B;
--chart-1: #0A0B0D;
--chart-2: #2B2F33;
--chart-3: #D9822B;
--chart-4: #7C8F75;
--chart-5: #D9822B;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #0A0B0D;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #D9822B;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #D9822B;
--radius: 16px;
}
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 SilentGantryNotationShadcnKit() {
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">Silent Gantry Notation</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>
);
}
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"cssVars": {
"dark": {
"accent": "#D9822B",
"accent-foreground": "#ffffff",
"background": "#0f1115",
"border": "#303642",
"card": "#181b22",
"card-foreground": "#f8fafc",
"chart-1": "#0A0B0D",
"chart-2": "#2B2F33",
"chart-3": "#D9822B",
"chart-4": "#7C8F75",
"chart-5": "#D9822B",
"destructive": "#B84A3A",
"foreground": "#f8fafc",
"input": "#303642",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#0A0B0D",
"primary-foreground": "#ffffff",
"radius": "16px",
"ring": "#D9822B",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"sidebar": "#181b22",
"sidebar-accent": "#D9822B",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#0A0B0D",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#D9822B"
},
"light": {
"accent": "#D9822B",
"accent-foreground": "#ffffff",
"background": "#050607",
"border": "#C8C0B2",
"card": "#F1EDE2",
"card-foreground": "#F6F1E7",
"chart-1": "#0A0B0D",
"chart-2": "#2B2F33",
"chart-3": "#D9822B",
"chart-4": "#7C8F75",
"chart-5": "#D9822B",
"destructive": "#B84A3A",
"foreground": "#F6F1E7",
"input": "#C8C0B2",
"muted": "#8E9498",
"muted-foreground": "#F6F1E7",
"popover": "#F1EDE2",
"popover-foreground": "#F6F1E7",
"primary": "#0A0B0D",
"primary-foreground": "#ffffff",
"radius": "16px",
"ring": "#D9822B",
"secondary": "#2B2F33",
"secondary-foreground": "#ffffff",
"sidebar": "#F1EDE2",
"sidebar-accent": "#BFDDE8",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#C8C0B2",
"sidebar-foreground": "#F6F1E7",
"sidebar-primary": "#0A0B0D",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#D9822B"
},
"theme": {}
},
"meta": {
"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",
"languageId": "en-019e07eb-20b2-7ba1-9e99-d97c57d1d6d9",
"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"
]
},
"slug": "silent-gantry-notation",
"source": "katagami"
},
"name": "silent-gantry-notation",
"title": "Silent Gantry Notation shadcn Theme",
"type": "registry:theme"
}
# Silent Gantry Notation shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e07eb-20b2-7ba1-9e99-d97c57d1d6d9`
Slug: `silent-gantry-notation`
## Intent
Silent Gantry Notation is a restrained cockpit language for mission-critical machine proximity: black-and-white manga panel structure holds a distant mecha diagnostic frame, while pale HUD arcs and sparse amber callouts describe systems without turning the interface into spectacle. It treats the pilot screen as a place of quiet operational doubt, using absence, scale, and measured annotation to make the machine feel present but not anthropomorphic.
## 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": "#D9822B",
"background": "#050607",
"border": "#C8C0B2",
"error": "#B84A3A",
"info": "#BFDDE8",
"muted": "#8E9498",
"primary": "#0A0B0D",
"secondary": "#2B2F33",
"success": "#7C8F75",
"surface": "#F1EDE2",
"text": "#F6F1E7",
"warning": "#D9822B"
}
Typography:
{
"base_size": "16px",
"body_font": "IBM Plex Sans Condensed",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Azeret+Mono:wght@500;700&family=IBM+Plex+Sans+Condensed:wght@400;500;600&family=Share+Tech+Mono&display=swap",
"heading_font": "Azeret Mono",
"letter_spacing": "-0.02em",
"line_height": 1.48,
"mono_font": "Share Tech Mono",
"scale_ratio": 1.22
}
## Visual character to preserve
- Asymmetric manga-panel grid with thick black gutters, warm off-white data sheets, and one dominant matte graphite cockpit aperture.
- Thin pale blue-white HUD arcs built from CSS borders and pseudo-elements, never glowing more than a one-pixel technical overlay.
- Exploded mecha notation using dotted leader lines, small amber-orange numbered callouts, and separated graphite component silhouettes.
- Terminal fragments in compact monospace bands with Y2K serial labels, square LCD insets, and hardware tab captions.
- Large zones of deliberate empty black space around the machine diagram to express scale, silence, and human-machine distance.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": true,
"stickerBadges": false,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
}
## Signature component recipes
### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.
### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.
### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.
### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.
### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.
## Preview shots
- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.
## Implementation contract
- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/silent-gantry-notation/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 thick black gutters to make manga structure visible before any UI details are noticed.; Keep HUD arcs one-pixel thin, pale, and clipped by the cockpit aperture.; Group cockpit controls into labeled operational clusters that reduce scan effort.; Use amber only for mechanical callout numbers, warnings, and leader endpoints.; Let off-white panels feel like printed technical sheets rather than glossy cards.; Include terminal text that reads like mission state, serial diagnostics, or calibration logs.; Preserve empty black space to communicate scale and quiet machine distance.
- Do not: Do not use green matrix rain, neon cyberpunk gradients, or saturated glow effects.; Do not fill the scene with generic dashboard widgets or SaaS metric cards.; Do not add anime characters, pilots, mascots, or heroic mecha poster poses.; Do not make HUD elements decorative if they do not support orientation or status.; Do not mix many accent colors; amber and pale blue-white are enough.; Do not round every surface; square hardware edges are the default.; Do not use unreadable fake microtext as texture.
## 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 SilentGantryNotationShadcnKit() {
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">Silent Gantry Notation</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": "1200px and up asymmetric 12-column frame",
"mobile": "375px single-column stacked panels",
"tablet": "768px two-zone cockpit then diagnostics"
},
"density": "A 60/40 split between void and instrumentation keeps the interface readable while preserving the existential cockpit mood.",
"grid": "Desktop uses a 12-column grid, 24px gutters, max-width 1360px; the aperture spans seven columns while document panels stack across the remaining five.",
"responsive": "On tablet the terminal rail moves below the aperture; on mobile the manga panels become sequential frames with annotations simplified but not removed.",
"whitespace": "Black negative space is an active layout material; keep at least one empty quadrant or long dark corridor visible at every viewport."
}
{
"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-019e07eb-20b2-7ba1-9e99-d97c57d1d6d9",
"name": "Silent Gantry Notation",
"slug": "silent-gantry-notation"
},
"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": [
"Asymmetric manga-panel grid with thick black gutters, warm off-white data sheets, and one dominant matte graphite cockpit aperture.",
"Thin pale blue-white HUD arcs built from CSS borders and pseudo-elements, never glowing more than a one-pixel technical overlay.",
"Exploded mecha notation using dotted leader lines, small amber-orange numbered callouts, and separated graphite component silhouettes.",
"Terminal fragments in compact monospace bands with Y2K serial labels, square LCD insets, and hardware tab captions.",
"Large zones of deliberate empty black space around the machine diagram to express scale, silence, and human-machine distance."
],
"visualProfile": {
"family": "paper-collage",
"material": "paper",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": true,
"stickerBadges": false,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "Silent Gantry Notation 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 thick black gutters to make manga structure visible before any UI details are noticed.",
"Keep HUD arcs one-pixel thin, pale, and clipped by the cockpit aperture.",
"Group cockpit controls into labeled operational clusters that reduce scan effort.",
"Use amber only for mechanical callout numbers, warnings, and leader endpoints.",
"Let off-white panels feel like printed technical sheets rather than glossy cards.",
"Include terminal text that reads like mission state, serial diagnostics, or calibration logs.",
"Preserve empty black space to communicate scale and quiet machine distance."
],
"dont": [
"Do not use green matrix rain, neon cyberpunk gradients, or saturated glow effects.",
"Do not fill the scene with generic dashboard widgets or SaaS metric cards.",
"Do not add anime characters, pilots, mascots, or heroic mecha poster poses.",
"Do not make HUD elements decorative if they do not support orientation or status.",
"Do not mix many accent colors; amber and pale blue-white are enough.",
"Do not round every surface; square hardware edges are the default.",
"Do not use unreadable fake microtext as texture."
]
}
}