Graphite Cockpit 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
- thin pale graphite rules, black manga cuts, and safety-orange slivers only where maintenance intervention is implied
- default width
- 1px
- style
- solid
colors12 items
motion3 items
- duration
- 4800ms
- easing
- cubic-bezier(0.37, 0, 0.24, 1)
- philosophy
- nearly static cockpit observation with one slow breath cadence on pressure and life-support indicators
radii5 items
- full
- 9999px
- lg
- 4px
- md
- 2px
- none
- 0
- sm
- 1px
shadows3 items
- lg
- 0 34px 90px rgba(0,0,0,0.55)
- md
- 0 16px 40px rgba(0,0,0,0.38)
- sm
- 0 1px 0 rgba(236,229,216,0.08)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- subtle panel seams, bearing arcs, range ladders, and sparse calibration marks aligned to mechanical axes
- card style
- hard-edged clipped technical panel, no rounded SaaS container, with corner registration ticks
- treatment
- matte graphite plates over ink-black void with translucent cockpit glass films and warm paper gutters
typography8 items
- base size
- 16px
- body font
- IBM Plex Sans Condensed
- google fonts url
- https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans+Condensed:wght@400;500;600&family=Teko:wght@500;600;700&display=swap
- heading font
- Teko
- letter spacing
- -0.015em
- line height
- 1.45
- mono font
- IBM Plex Mono
- scale ratio
- 1.2
rules
Compose screens as a cockpit cross-section: asymmetrical black/white manga panels frame a central mechanical anatomy diagram, with data attached by leader lines rather than floating cards.
Medium-low density with deliberate blank voids; every line must feel registered to a mechanical surface, hinge, seal, or diagnostic channel.
Primary hierarchy belongs to silhouette, joint overlays, and failure thresholds; labels are small, compressed, tabular, and secondary unless orange marks a physical intervention point.
layout
desktop 1200px, tablet 760px, mobile 360px with diagram-first stacking
Twelve-column desktop grid collapsed into staggered cockpit plates; central negative-space diagram spans columns 4-9 while diagnostics dock to edges.
Use large ink-black voids and warm off-white gutters as silence around the machine; keep HUD labels small and never fill every gap.
guidance
- Reserve orange for intervention balloons, lock warnings, and risk slivers only.
- Align telemetry to mechanical joints, panel seams, and pressure seals.
- Use hard cuts, manga gutters, compressed type, and sparse pale-blue HUD lines.
- Let the cockpit feel unoccupied, as if the machine is observing its own body.
- Do not use green matrix rain, neon magenta/cyan cyberpunk glow, or city-at-night backdrops.
- Do not create generic analytics dashboards, SaaS cards, or rounded friendly components.
- Do not use fake kanji, fan-art character portraits, or noisy maximal FUI decoration.
- Do not make orange decorative; it must imply mechanical intervention or risk.
katagami spec
# Graphite Cockpit Notation ## Philosophy A minimal mecha cockpit notation system where a graphite-black machine quietly reports its own anatomy through sparse HUD overlays, exploded limb schematics, pressure seals, and orange intervention callouts rather than cyberpunk spectacle. ### Values - machine self-report over human heroics - manga-panel restraint with technical anatomy - risk-color scarcity and functional orange - negative space as cockpit silence - Y2K hardware labels without nostalgic gimmickry ### Anti-Values - green matrix rain or generic hacker dashboards - neon city cyberpunk glow - fan-art character busts - SaaS card grids and rounded friendliness - maximal fake-FUI noise ### Visual Character - Use asymmetric clipped cockpit plates with hard black borders and warm off-white manga gutters to divide the page into irregular technical panels. - Place a central exploded mecha limb silhouette in negative space with thin pale-blue leader lines, numbered orange balloons, and registration cross marks. - Build HUD information as sparse bearing arcs, range ladders, pressure-seal ticks, and actuator telemetry aligned to joints instead of generic dashboard cards. - Layer low-opacity graphite glass reflections and horizontal scan calibration rules over matte surfaces while keeping animation limited to slow life-support breathing. - Render terminal prompts as compact monospaced self-report lines, serial numbers, lock-pin states, and boot diagnostics embedded into panel edges. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: thin pale graphite rules, black manga cuts, and safety-orange slivers only where maintenance intervention is implied - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#E66A2C` | | background | `#08090A` | | border | `#3A3F42` | | error | `#FF6D3A` | | info | `#BFD8EA` | | muted | `#8C9296` | | primary | `#ECE5D8` | | secondary | `#AFC6D8` | | success | `#9AB59C` | | surface | `#16181B` | | text | `#F1EADF` | | warning | `#D8903F` | ### Motion - **Duration**: 4800ms - **Easing**: cubic-bezier(0.37, 0, 0.24, 1) - **Philosophy**: nearly static cockpit observation with one slow breath cadence on pressure and life-support indicators ### Radii - **Full**: 9999px - **Lg**: 4px - **Md**: 2px - **None**: 0 - **Sm**: 1px ### Shadows - **Lg**: 0 34px 90px rgba(0,0,0,0.55) - **Md**: 0 16px 40px rgba(0,0,0,0.38) - **Sm**: 0 1px 0 rgba(236,229,216,0.08) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: subtle panel seams, bearing arcs, range ladders, and sparse calibration marks aligned to mechanical axes - **Card Style**: hard-edged clipped technical panel, no rounded SaaS container, with corner registration ticks - **Treatment**: matte graphite plates over ink-black void with translucent cockpit glass films and warm paper gutters ### Typography - **Base Size**: 16px - **Body Font**: IBM Plex Sans Condensed - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans+Condensed:wght@400;500;600&family=Teko:wght@500;600;700&display=swap - **Heading Font**: Teko - **Letter Spacing**: -0.015em - **Line Height**: 1.45 - **Mono Font**: IBM Plex Mono - **Scale Ratio**: 1.2 ## Rules ### Composition Compose screens as a cockpit cross-section: asymmetrical black/white manga panels frame a central mechanical anatomy diagram, with data attached by leader lines rather than floating cards. ### Density Medium-low density with deliberate blank voids; every line must feel registered to a mechanical surface, hinge, seal, or diagnostic channel. ### Hierarchy Primary hierarchy belongs to silhouette, joint overlays, and failure thresholds; labels are small, compressed, tabular, and secondary unless orange marks a physical intervention point. ### Signature Patterns - Clipped polygon cockpit plates created with CSS clip-path and overprinted with corner registration ticks via pseudo-elements. - Exploded-view anatomy drawn from CSS bars, circles, and SVG-like div lines, annotated with pale leader rules and numbered orange balloons. - Bearing arcs and range ladders built from repeating-linear-gradients and conic-gradient masks instead of generic chart widgets. - Maintenance warning slivers as narrow orange edge strips that interrupt graphite panels only at lock-pin or pressure-seal states. - Terminal self-report microcopy placed vertically and along panel edges using monospaced tabular numerals and tiny calibration ticks. ## Layout ### Breakpoints desktop 1200px, tablet 760px, mobile 360px with diagram-first stacking ### Grid Twelve-column desktop grid collapsed into staggered cockpit plates; central negative-space diagram spans columns 4-9 while diagnostics dock to edges. ### Whitespace Use large ink-black voids and warm off-white gutters as silence around the machine; keep HUD labels small and never fill every gap. ## Guidance ### Do - Reserve orange for intervention balloons, lock warnings, and risk slivers only. - Align telemetry to mechanical joints, panel seams, and pressure seals. - Use hard cuts, manga gutters, compressed type, and sparse pale-blue HUD lines. - Let the cockpit feel unoccupied, as if the machine is observing its own body. ### Don't - Do not use green matrix rain, neon magenta/cyan cyberpunk glow, or city-at-night backdrops. - Do not create generic analytics dashboards, SaaS cards, or rounded friendly components. - Do not use fake kanji, fan-art character portraits, or noisy maximal FUI decoration. - Do not make orange decorative; it must imply mechanical intervention or risk. ### Accessibility Maintain strong contrast between warm off-white text and graphite surfaces; pair orange warnings with explicit labels and keep tiny microcopy non-essential.
DESIGN.md
---
version: "alpha"
name: "Graphite Cockpit Notation"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#E66A2C"
background: "#08090A"
border: "#3A3F42"
error: "#FF6D3A"
info: "#BFD8EA"
muted: "#8C9296"
primary: "#ECE5D8"
secondary: "#AFC6D8"
success: "#9AB59C"
surface: "#16181B"
text: "#F1EADF"
warning: "#D8903F"
typography:
headline-lg:
fontFamily: "Teko"
fontSize: "1.728rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.015em"
headline-md:
fontFamily: "Teko"
fontSize: "1.44rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.015em"
body-md:
fontFamily: "IBM Plex Sans Condensed"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.45
letterSpacing: "-0.015em"
label-md:
fontFamily: "IBM Plex Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "4px"
md: "2px"
none: "0px"
sm: "1px"
spacing:
base: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
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: "#000000"
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"
---
# Graphite Cockpit Notation
## Overview
A minimal mecha cockpit notation system where a graphite-black machine quietly reports its own anatomy through sparse HUD overlays, exploded limb schematics, pressure seals, and orange intervention callouts rather than cyberpunk spectacle.
### Values
- machine self-report over human heroics
- manga-panel restraint with technical anatomy
- risk-color scarcity and functional orange
- negative space as cockpit silence
- Y2K hardware labels without nostalgic gimmickry
### Anti-Values
- green matrix rain or generic hacker dashboards
- neon city cyberpunk glow
- fan-art character busts
- SaaS card grids and rounded friendliness
- maximal fake-FUI noise
### Visual Character
- Use asymmetric clipped cockpit plates with hard black borders and warm off-white manga gutters to divide the page into irregular technical panels.
- Place a central exploded mecha limb silhouette in negative space with thin pale-blue leader lines, numbered orange balloons, and registration cross marks.
- Build HUD information as sparse bearing arcs, range ladders, pressure-seal ticks, and actuator telemetry aligned to joints instead of generic dashboard cards.
- Layer low-opacity graphite glass reflections and horizontal scan calibration rules over matte surfaces while keeping animation limited to slow life-support breathing.
- Render terminal prompts as compact monospaced self-report lines, serial numbers, lock-pin states, and boot diagnostics embedded into panel edges.
## 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 | `#E66A2C` |
| background | `#08090A` |
| border | `#3A3F42` |
| error | `#FF6D3A` |
| info | `#BFD8EA` |
| muted | `#8C9296` |
| primary | `#ECE5D8` |
| secondary | `#AFC6D8` |
| success | `#9AB59C` |
| surface | `#16181B` |
| text | `#F1EADF` |
| warning | `#D8903F` |
## Typography
- **Headline-Lg**: Teko, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Teko, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans Condensed, 16px, weight 400, line-height 1.45.
- **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`
### Breakpoints
desktop 1200px, tablet 760px, mobile 360px with diagram-first stacking
### Grid
Twelve-column desktop grid collapsed into staggered cockpit plates; central negative-space diagram spans columns 4-9 while diagnostics dock to edges.
### Whitespace
Use large ink-black voids and warm off-white gutters as silence around the machine; keep HUD labels small and never fill every gap.
## Elevation & Depth
### Shadows
- **Lg**: 0 34px 90px rgba(0,0,0,0.55)
- **Md**: 0 16px 40px rgba(0,0,0,0.38)
- **Sm**: 0 1px 0 rgba(236,229,216,0.08)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `4px`
- **Md**: `2px`
- **None**: `0px`
- **Sm**: `1px`
### Surfaces
- **Bg Pattern**: subtle panel seams, bearing arcs, range ladders, and sparse calibration marks aligned to mechanical axes
- **Card Style**: hard-edged clipped technical panel, no rounded SaaS container, with corner registration ticks
- **Treatment**: matte graphite plates over ink-black void with translucent cockpit glass films and warm paper gutters
### Borders
- **Accent Width**: 2px
- **Character**: thin pale graphite rules, black manga cuts, and safety-orange slivers only where maintenance intervention is implied
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Compose screens as a cockpit cross-section: asymmetrical black/white manga panels frame a central mechanical anatomy diagram, with data attached by leader lines rather than floating cards.
### Density
Medium-low density with deliberate blank voids; every line must feel registered to a mechanical surface, hinge, seal, or diagnostic channel.
### Hierarchy
Primary hierarchy belongs to silhouette, joint overlays, and failure thresholds; labels are small, compressed, tabular, and secondary unless orange marks a physical intervention point.
### Signature Patterns
- Clipped polygon cockpit plates created with CSS clip-path and overprinted with corner registration ticks via pseudo-elements.
- Exploded-view anatomy drawn from CSS bars, circles, and SVG-like div lines, annotated with pale leader rules and numbered orange balloons.
- Bearing arcs and range ladders built from repeating-linear-gradients and conic-gradient masks instead of generic chart widgets.
- Maintenance warning slivers as narrow orange edge strips that interrupt graphite panels only at lock-pin or pressure-seal states.
- Terminal self-report microcopy placed vertically and along panel edges using monospaced tabular numerals and tiny calibration ticks.
## 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-019e05eb-1008-72c0-ae28-b09a449fe2a5/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 Reserve orange for intervention balloons, lock warnings, and risk slivers only.
- Do Align telemetry to mechanical joints, panel seams, and pressure seals.
- Do Use hard cuts, manga gutters, compressed type, and sparse pale-blue HUD lines.
- Do Let the cockpit feel unoccupied, as if the machine is observing its own body.
- Don't Do not use green matrix rain, neon magenta/cyan cyberpunk glow, or city-at-night backdrops.
- Don't Do not create generic analytics dashboards, SaaS cards, or rounded friendly components.
- Don't Do not use fake kanji, fan-art character portraits, or noisy maximal FUI decoration.
- Don't Do not make orange decorative; it must imply mechanical intervention or risk.
### Accessibility
Maintain strong contrast between warm off-white text and graphite surfaces; pair orange warnings with explicit labels and keep tiny microcopy non-essential.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "graphite-cockpit-notation",
"type": "registry:theme",
"title": "Graphite Cockpit Notation shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#08090A",
"foreground": "#F1EADF",
"card": "#16181B",
"card-foreground": "#F1EADF",
"popover": "#16181B",
"popover-foreground": "#F1EADF",
"primary": "#ECE5D8",
"primary-foreground": "#111111",
"secondary": "#AFC6D8",
"secondary-foreground": "#111111",
"muted": "#8C9296",
"muted-foreground": "#F1EADF",
"accent": "#E66A2C",
"accent-foreground": "#ffffff",
"destructive": "#FF6D3A",
"border": "#3A3F42",
"input": "#3A3F42",
"ring": "#E66A2C",
"chart-1": "#ECE5D8",
"chart-2": "#AFC6D8",
"chart-3": "#E66A2C",
"chart-4": "#9AB59C",
"chart-5": "#D8903F",
"sidebar": "#16181B",
"sidebar-foreground": "#F1EADF",
"sidebar-primary": "#ECE5D8",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#BFD8EA",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#3A3F42",
"sidebar-ring": "#E66A2C",
"radius": "2px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#ECE5D8",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#E66A2C",
"accent-foreground": "#ffffff",
"destructive": "#FF6D3A",
"border": "#303642",
"input": "#303642",
"ring": "#E66A2C",
"chart-1": "#ECE5D8",
"chart-2": "#AFC6D8",
"chart-3": "#E66A2C",
"chart-4": "#9AB59C",
"chart-5": "#D8903F",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#ECE5D8",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#E66A2C",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#E66A2C",
"radius": "2px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e05eb-1008-72c0-ae28-b09a449fe2a5",
"slug": "graphite-cockpit-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
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: #08090A;
--foreground: #F1EADF;
--card: #16181B;
--card-foreground: #F1EADF;
--popover: #16181B;
--popover-foreground: #F1EADF;
--primary: #ECE5D8;
--primary-foreground: #111111;
--secondary: #AFC6D8;
--secondary-foreground: #111111;
--muted: #8C9296;
--muted-foreground: #F1EADF;
--accent: #E66A2C;
--accent-foreground: #ffffff;
--destructive: #FF6D3A;
--border: #3A3F42;
--input: #3A3F42;
--ring: #E66A2C;
--chart-1: #ECE5D8;
--chart-2: #AFC6D8;
--chart-3: #E66A2C;
--chart-4: #9AB59C;
--chart-5: #D8903F;
--sidebar: #16181B;
--sidebar-foreground: #F1EADF;
--sidebar-primary: #ECE5D8;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #BFD8EA;
--sidebar-accent-foreground: #111111;
--sidebar-border: #3A3F42;
--sidebar-ring: #E66A2C;
--radius: 2px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #ECE5D8;
--primary-foreground: #111111;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #E66A2C;
--accent-foreground: #ffffff;
--destructive: #FF6D3A;
--border: #303642;
--input: #303642;
--ring: #E66A2C;
--chart-1: #ECE5D8;
--chart-2: #AFC6D8;
--chart-3: #E66A2C;
--chart-4: #9AB59C;
--chart-5: #D8903F;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #ECE5D8;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #E66A2C;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #E66A2C;
--radius: 2px;
}
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 GraphiteCockpitNotationShadcnKit() {
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">Graphite Cockpit 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",
"name": "graphite-cockpit-notation",
"type": "registry:theme",
"title": "Graphite Cockpit Notation shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#08090A",
"foreground": "#F1EADF",
"card": "#16181B",
"card-foreground": "#F1EADF",
"popover": "#16181B",
"popover-foreground": "#F1EADF",
"primary": "#ECE5D8",
"primary-foreground": "#111111",
"secondary": "#AFC6D8",
"secondary-foreground": "#111111",
"muted": "#8C9296",
"muted-foreground": "#F1EADF",
"accent": "#E66A2C",
"accent-foreground": "#ffffff",
"destructive": "#FF6D3A",
"border": "#3A3F42",
"input": "#3A3F42",
"ring": "#E66A2C",
"chart-1": "#ECE5D8",
"chart-2": "#AFC6D8",
"chart-3": "#E66A2C",
"chart-4": "#9AB59C",
"chart-5": "#D8903F",
"sidebar": "#16181B",
"sidebar-foreground": "#F1EADF",
"sidebar-primary": "#ECE5D8",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#BFD8EA",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#3A3F42",
"sidebar-ring": "#E66A2C",
"radius": "2px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#ECE5D8",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#E66A2C",
"accent-foreground": "#ffffff",
"destructive": "#FF6D3A",
"border": "#303642",
"input": "#303642",
"ring": "#E66A2C",
"chart-1": "#ECE5D8",
"chart-2": "#AFC6D8",
"chart-3": "#E66A2C",
"chart-4": "#9AB59C",
"chart-5": "#D8903F",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#ECE5D8",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#E66A2C",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#E66A2C",
"radius": "2px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e05eb-1008-72c0-ae28-b09a449fe2a5",
"slug": "graphite-cockpit-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"
]
}
}
}
# Graphite Cockpit Notation shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e05eb-1008-72c0-ae28-b09a449fe2a5`
Slug: `graphite-cockpit-notation`
## Intent
A minimal mecha cockpit notation system where a graphite-black machine quietly reports its own anatomy through sparse HUD overlays, exploded limb schematics, pressure seals, and orange intervention callouts rather than cyberpunk spectacle.
## Required primitives
- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table
Install with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.
## Token cues
Colors:
{
"accent": "#E66A2C",
"background": "#08090A",
"border": "#3A3F42",
"error": "#FF6D3A",
"info": "#BFD8EA",
"muted": "#8C9296",
"primary": "#ECE5D8",
"secondary": "#AFC6D8",
"success": "#9AB59C",
"surface": "#16181B",
"text": "#F1EADF",
"warning": "#D8903F"
}
Typography:
{
"base_size": "16px",
"body_font": "IBM Plex Sans Condensed",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans+Condensed:wght@400;500;600&family=Teko:wght@500;600;700&display=swap",
"heading_font": "Teko",
"letter_spacing": "-0.015em",
"line_height": 1.45,
"mono_font": "IBM Plex Mono",
"scale_ratio": 1.2
}
## Visual character to preserve
- Use asymmetric clipped cockpit plates with hard black borders and warm off-white manga gutters to divide the page into irregular technical panels.
- Place a central exploded mecha limb silhouette in negative space with thin pale-blue leader lines, numbered orange balloons, and registration cross marks.
- Build HUD information as sparse bearing arcs, range ladders, pressure-seal ticks, and actuator telemetry aligned to joints instead of generic dashboard cards.
- Layer low-opacity graphite glass reflections and horizontal scan calibration rules over matte surfaces while keeping animation limited to slow life-support breathing.
- Render terminal prompts as compact monospaced self-report lines, serial numbers, lock-pin states, and boot diagnostics embedded into panel edges.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "blob",
"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/graphite-cockpit-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: Reserve orange for intervention balloons, lock warnings, and risk slivers only.; Align telemetry to mechanical joints, panel seams, and pressure seals.; Use hard cuts, manga gutters, compressed type, and sparse pale-blue HUD lines.; Let the cockpit feel unoccupied, as if the machine is observing its own body.
- Do not: Do not use green matrix rain, neon magenta/cyan cyberpunk glow, or city-at-night backdrops.; Do not create generic analytics dashboards, SaaS cards, or rounded friendly components.; Do not use fake kanji, fan-art character portraits, or noisy maximal FUI decoration.; Do not make orange decorative; it must imply mechanical intervention or risk.
## 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 GraphiteCockpitNotationShadcnKit() {
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">Graphite Cockpit 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, tablet 760px, mobile 360px with diagram-first stacking",
"grid": "Twelve-column desktop grid collapsed into staggered cockpit plates; central negative-space diagram spans columns 4-9 while diagnostics dock to edges.",
"whitespace": "Use large ink-black voids and warm off-white gutters as silence around the machine; keep HUD labels small and never fill every gap."
}
{
"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-019e05eb-1008-72c0-ae28-b09a449fe2a5",
"name": "Graphite Cockpit Notation",
"slug": "graphite-cockpit-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": [
"Use asymmetric clipped cockpit plates with hard black borders and warm off-white manga gutters to divide the page into irregular technical panels.",
"Place a central exploded mecha limb silhouette in negative space with thin pale-blue leader lines, numbered orange balloons, and registration cross marks.",
"Build HUD information as sparse bearing arcs, range ladders, pressure-seal ticks, and actuator telemetry aligned to joints instead of generic dashboard cards.",
"Layer low-opacity graphite glass reflections and horizontal scan calibration rules over matte surfaces while keeping animation limited to slow life-support breathing.",
"Render terminal prompts as compact monospaced self-report lines, serial numbers, lock-pin states, and boot diagnostics embedded into panel edges."
],
"visualProfile": {
"family": "brutalist",
"material": "ink",
"contour": "blob",
"border": "solid",
"underlay": false,
"grain": false,
"stickerBadges": false,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "Graphite Cockpit 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": [
"Reserve orange for intervention balloons, lock warnings, and risk slivers only.",
"Align telemetry to mechanical joints, panel seams, and pressure seals.",
"Use hard cuts, manga gutters, compressed type, and sparse pale-blue HUD lines.",
"Let the cockpit feel unoccupied, as if the machine is observing its own body."
],
"dont": [
"Do not use green matrix rain, neon magenta/cyan cyberpunk glow, or city-at-night backdrops.",
"Do not create generic analytics dashboards, SaaS cards, or rounded friendly components.",
"Do not use fake kanji, fan-art character portraits, or noisy maximal FUI decoration.",
"Do not make orange decorative; it must imply mechanical intervention or risk."
]
}
}