back to gallery
design language·graphite-linear-seat-notation

Graphite Linear-Seat 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.

the spec

specification

philosophy
summary
Graphite Linear-Seat Notation treats a web interface as a cockpit service overlay for a body coupled to a machine shell. Its atmosphere comes from black-and-white manga panel discipline, late-90s hardware labels, and restrained diagnostic UI: the pilot is never illustrated, only inferred through seat geometry, reach arcs, harness scuffs, breath-fogged glass, and nervous-system calibration marks.
values
Human presence is implied through ergonomic absence: empty seat rails, restraint pressure marks, hand reach zones, breath residue, and calibration traces replace character art.Information feels bolted to hardware, not floated as cards; every label attaches to a rail, screw index, centerline, panel edge, or exploded actuator callout.Monochrome manga structure does the emotional work through gutters, hard cuts, graphite fields, halftone fog, and isolated empty compartments.Operational color is scarce and mechanical: pale blue-gray registration lines carry system alignment, while safety orange marks lock pins, service arrows, and numbered components.The system favors quiet precision over cyberpunk spectacle; small type, exact ticks, and diagrammatic restraint create tension without dense HUD chaos.Y2K hardware/software language appears as CRT mode labels, boot fragments, serial part codes, square LEDs, and compact terminal numerals rather than nostalgic decoration.
anti-values
×No green matrix rain, purple-cyan neon cyberpunk, command-center dashboard spectacle, or generic hacker terminal theatrics.×No franchise mecha fan art, heroic pilots, full-body character illustration, or glossy anime splash composition.×No rounded SaaS card grid, floating analytics widgets, gradient buttons, or friendly product-dashboard softness.×No dense game HUD clutter; telemetry must have air, alignment, and a reason to attach to the cockpit structure.
tokens
borders4 items
accent width
2px
character
Hard ink and bone hairlines: borders define manga gutters, panel seams, centerline reticles, and service callout stems; no rounded partial accent borders.
default width
1px
style
solid
colors12 items
accent
#c66f2e
background
#090a0b
border
#343537
error
#b85b35
info
#aab7bd
muted
#7b7f82
primary
#d8d0c2
secondary
#8e99a1
success
#9da58f
surface
#151719
text
#e7e0d2
warning
#c66f2e
motion3 items
duration
180ms
easing
cubic-bezier(0.16, 1, 0.3, 1)
philosophy
Motion should feel like a calibration relay settling: small tick translations, LED state changes, and line brightness shifts, never sweeping animated HUD spectacle.
radii5 items
full
9999px
lg
0
md
0
none
0
sm
0
shadows3 items
lg
0 34px 120px rgba(0,0,0,0.55)
md
0 18px 60px rgba(0,0,0,0.38)
sm
0 0 0 1px rgba(216,208,194,0.08)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64, 96, 128
surfaces3 items
bg pattern
Graphite field crossed by faint centerline rulers, sparse calibration ticks, manga hatch bands, and clipped CRT scan strips.
card style
Flat service panels with square corners, visible panel IDs, screw-index dots, attached leader lines, and orange callout tabs only where mechanically meaningful.
treatment
Matte graphite blocks with hard 1px ink borders, warm off-white gutters, subtle halftone/noise masks, and no glossy gradients.
typography8 items
base size
16px
body font
IBM Plex Sans Condensed
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Sans+Condensed:wght@400;500;600&family=Spline+Sans+Mono:wght@400;500;600&family=Teko:wght@500;600&display=swap
heading font
Teko
letter spacing
-0.02em
line height
1.55
mono font
Spline Sans Mono
scale ratio
1.22
rules
composition
Use a 12-column cockpit service sheet with one dominant linear-seat bay offset from center, a panoramic monitor arc crossing the top, one dense diagnostic edge rail, and one large empty graphite compartment. Avoid equal rows: the seat schematic must dominate, while callouts, boot strips, and actuator diagrams vary in weight and attachment.
density
Alternate 4px-to-8px telemetry clusters with 64px-to-128px voids. Dense information belongs near rails, screws, lock pins, and CRT strips; the central empty seat volume must remain readable and isolating.
hierarchy
The seat centerline and manga panel architecture establish primary hierarchy; oversized Teko headings act like manual section stamps, body copy stays narrow and subdued, and Spline Sans Mono telemetry remains tiny. Orange appears only on mechanical intervention points, not as general emphasis.
signature patterns
Linear-seat bay: a CSS-drawn empty pilot seat rectangle with centerline reticle, harness rub bands, reach-zone arcs, breath-fog panel, and pale blue-gray calibration ticks.Bolted callout rail: hardware-anchored information groups using screw dots, orange numbered tabs, angled leader lines, lock-pin chevrons, and square-corner exploded component boxes.Manga service gutters: warm off-white structural gutters cutting through matte graphite panels with halftone fog, hatch-line masks, and 1px black ink borders.CRT panoramic strip: segmented top monitors with tiny mode labels, scanline texture, inactive gray LEDs, boot fragments, and no glowing neon color fields.Exploded actuator notation: stacked wireframe component silhouettes offset from the main bay and connected by thin leaders, using numeric part codes instead of icons.
layout
breakpoints
Desktop >= 1180px keeps the cockpit cutaway spread; tablet 760-1179px becomes an 8-column sheet with the rail below the seat bay; mobile < 760px stacks panels while preserving horizontal CRT strips and centerline marks.
density

Medium-low overall density with deliberate high-density edge clusters; the interface breathes through black graphite voids and warm manga gutters.

grid

Desktop uses a 12-column max-width 1400px grid with 24px gutters, a dominant 6-column seat bay, a 3-column service rail, and overlapping monitor strips.

responsive
On tablet, callout stems shorten and exploded diagrams move under the seat bay; on mobile, nonessential boot fragments hide before typography or spacing compresses.
whitespace

Major voids use 64px, 96px, and 128px intervals; related telemetry and screw labels sit 4px to 12px apart so grouping contrast remains visible.

guidance
do
  • Use square-corner panels, hard manga gutters, graphite voids, and visible centerline rulers as the primary structure.
  • Attach every label to a tangible edge, rail, screw, diagram, seat axis, monitor strip, or callout stem.
  • Keep type compact: Teko for manual stamps, IBM Plex Sans Condensed for narrow instructions, Spline Sans Mono for serials and telemetry.
  • Use orange only for lock pins, service arrows, numbered annotations, and intervention states.
  • Imply the pilot through absent-body traces such as reach arcs, breath fog, harness abrasion, and sensor feedback.
  • Let one large empty graphite area remain underexplained to preserve isolation and pressure.
  • Build hover states as mechanical registration changes: small line shifts, LED toggles, or callout brightening.
avoid
  • Do not use green code rain, neon purple/cyan cyberpunk, glowing city grids, or generic hacker dashboards.
  • Do not use rounded SaaS cards, glossy surfaces, three equal feature cards, or analytics widgets.
  • Do not depict heroic characters, franchise mecha, anime splash art, or full pilots inside the cockpit.
  • Do not fill all voids with HUD decoration; silence and graphite space are part of the language.
  • Do not use gradients, rainbow accents, saturated color triads, or large colored backdrops.
  • Do not let labels float unattached; if a datum is not bolted to hardware, remove it.
  • Do not mix rounded radius values or place one-sided accent borders on rounded elements.
katagami spec
# Graphite Linear-Seat Notation

## Philosophy

Graphite Linear-Seat Notation treats a web interface as a cockpit service overlay for a body coupled to a machine shell. Its atmosphere comes from black-and-white manga panel discipline, late-90s hardware labels, and restrained diagnostic UI: the pilot is never illustrated, only inferred through seat geometry, reach arcs, harness scuffs, breath-fogged glass, and nervous-system calibration marks.

### Values

- Human presence is implied through ergonomic absence: empty seat rails, restraint pressure marks, hand reach zones, breath residue, and calibration traces replace character art.
- Information feels bolted to hardware, not floated as cards; every label attaches to a rail, screw index, centerline, panel edge, or exploded actuator callout.
- Monochrome manga structure does the emotional work through gutters, hard cuts, graphite fields, halftone fog, and isolated empty compartments.
- Operational color is scarce and mechanical: pale blue-gray registration lines carry system alignment, while safety orange marks lock pins, service arrows, and numbered components.
- The system favors quiet precision over cyberpunk spectacle; small type, exact ticks, and diagrammatic restraint create tension without dense HUD chaos.
- Y2K hardware/software language appears as CRT mode labels, boot fragments, serial part codes, square LEDs, and compact terminal numerals rather than nostalgic decoration.

### Anti-Values

- No green matrix rain, purple-cyan neon cyberpunk, command-center dashboard spectacle, or generic hacker terminal theatrics.
- No franchise mecha fan art, heroic pilots, full-body character illustration, or glossy anime splash composition.
- No rounded SaaS card grid, floating analytics widgets, gradient buttons, or friendly product-dashboard softness.
- No dense game HUD clutter; telemetry must have air, alignment, and a reason to attach to the cockpit structure.

### Visual Character

- Build pages from hard-edged manga gutters: warm off-white panel bands, near-black graphite compartments, 1px ink rules, and asymmetric cutaway rectangles instead of rounded cards.
- Use a central linear-seat schematic with vertical centerline reticles, seat orientation marks, reach-zone arcs, harness rub bands, and pale HUD calibration ticks drawn in CSS.
- Anchor information clusters to hardware rails with screw-index dots, orange lock-pin chevrons, numbered callout stems, and exploded actuator boxes connected by thin leader lines.
- Render panoramic monitor logic as stacked black CRT strips and multi-display mode labels wrapping the seat bay, with tiny monospaced boot fragments and inactive cool-gray LEDs.
- Reserve large empty graphite fields and off-white gutters as psychological pressure, letting dense diagnostic fragments occupy only bolted edge zones and service panels.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Hard ink and bone hairlines: borders define manga gutters, panel seams, centerline reticles, and service callout stems; no rounded partial accent borders.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#c66f2e` |
| background | `#090a0b` |
| border | `#343537` |
| error | `#b85b35` |
| info | `#aab7bd` |
| muted | `#7b7f82` |
| primary | `#d8d0c2` |
| secondary | `#8e99a1` |
| success | `#9da58f` |
| surface | `#151719` |
| text | `#e7e0d2` |
| warning | `#c66f2e` |

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.16, 1, 0.3, 1)
- **Philosophy**: Motion should feel like a calibration relay settling: small tick translations, LED state changes, and line brightness shifts, never sweeping animated HUD spectacle.

### Radii

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

### Shadows

- **Lg**: 0 34px 120px rgba(0,0,0,0.55)
- **Md**: 0 18px 60px rgba(0,0,0,0.38)
- **Sm**: 0 0 0 1px rgba(216,208,194,0.08)

### Spacing

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

### Surfaces

- **Bg Pattern**: Graphite field crossed by faint centerline rulers, sparse calibration ticks, manga hatch bands, and clipped CRT scan strips.
- **Card Style**: Flat service panels with square corners, visible panel IDs, screw-index dots, attached leader lines, and orange callout tabs only where mechanically meaningful.
- **Treatment**: Matte graphite blocks with hard 1px ink borders, warm off-white gutters, subtle halftone/noise masks, and no glossy gradients.

### Typography

- **Base Size**: 16px
- **Body Font**: IBM Plex Sans Condensed
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Sans+Condensed:wght@400;500;600&family=Spline+Sans+Mono:wght@400;500;600&family=Teko:wght@500;600&display=swap
- **Heading Font**: Teko
- **Letter Spacing**: -0.02em
- **Line Height**: 1.55
- **Mono Font**: Spline Sans Mono
- **Scale Ratio**: 1.22

## Rules

### Composition

Use a 12-column cockpit service sheet with one dominant linear-seat bay offset from center, a panoramic monitor arc crossing the top, one dense diagnostic edge rail, and one large empty graphite compartment. Avoid equal rows: the seat schematic must dominate, while callouts, boot strips, and actuator diagrams vary in weight and attachment.

### Density

Alternate 4px-to-8px telemetry clusters with 64px-to-128px voids. Dense information belongs near rails, screws, lock pins, and CRT strips; the central empty seat volume must remain readable and isolating.

### Hierarchy

The seat centerline and manga panel architecture establish primary hierarchy; oversized Teko headings act like manual section stamps, body copy stays narrow and subdued, and Spline Sans Mono telemetry remains tiny. Orange appears only on mechanical intervention points, not as general emphasis.

### Signature Patterns

- Linear-seat bay: a CSS-drawn empty pilot seat rectangle with centerline reticle, harness rub bands, reach-zone arcs, breath-fog panel, and pale blue-gray calibration ticks.
- Bolted callout rail: hardware-anchored information groups using screw dots, orange numbered tabs, angled leader lines, lock-pin chevrons, and square-corner exploded component boxes.
- Manga service gutters: warm off-white structural gutters cutting through matte graphite panels with halftone fog, hatch-line masks, and 1px black ink borders.
- CRT panoramic strip: segmented top monitors with tiny mode labels, scanline texture, inactive gray LEDs, boot fragments, and no glowing neon color fields.
- Exploded actuator notation: stacked wireframe component silhouettes offset from the main bay and connected by thin leaders, using numeric part codes instead of icons.

## Layout

### Breakpoints

Desktop >= 1180px keeps the cockpit cutaway spread; tablet 760-1179px becomes an 8-column sheet with the rail below the seat bay; mobile < 760px stacks panels while preserving horizontal CRT strips and centerline marks.

### Density

Medium-low overall density with deliberate high-density edge clusters; the interface breathes through black graphite voids and warm manga gutters.

### Grid

Desktop uses a 12-column max-width 1400px grid with 24px gutters, a dominant 6-column seat bay, a 3-column service rail, and overlapping monitor strips.

### Responsive

On tablet, callout stems shorten and exploded diagrams move under the seat bay; on mobile, nonessential boot fragments hide before typography or spacing compresses.

### Whitespace

Major voids use 64px, 96px, and 128px intervals; related telemetry and screw labels sit 4px to 12px apart so grouping contrast remains visible.

## Guidance

### Do

- Use square-corner panels, hard manga gutters, graphite voids, and visible centerline rulers as the primary structure.
- Attach every label to a tangible edge, rail, screw, diagram, seat axis, monitor strip, or callout stem.
- Keep type compact: Teko for manual stamps, IBM Plex Sans Condensed for narrow instructions, Spline Sans Mono for serials and telemetry.
- Use orange only for lock pins, service arrows, numbered annotations, and intervention states.
- Imply the pilot through absent-body traces such as reach arcs, breath fog, harness abrasion, and sensor feedback.
- Let one large empty graphite area remain underexplained to preserve isolation and pressure.
- Build hover states as mechanical registration changes: small line shifts, LED toggles, or callout brightening.

### Don't

- Do not use green code rain, neon purple/cyan cyberpunk, glowing city grids, or generic hacker dashboards.
- Do not use rounded SaaS cards, glossy surfaces, three equal feature cards, or analytics widgets.
- Do not depict heroic characters, franchise mecha, anime splash art, or full pilots inside the cockpit.
- Do not fill all voids with HUD decoration; silence and graphite space are part of the language.
- Do not use gradients, rainbow accents, saturated color triads, or large colored backdrops.
- Do not let labels float unattached; if a datum is not bolted to hardware, remove it.
- Do not mix rounded radius values or place one-sided accent borders on rounded elements.

### Accessibility

Maintain high contrast between warm off-white text and near-black fields, pair orange warnings with labels or numbers, keep critical telemetry above 12px, and provide visible square focus outlines using bone or orange hairlines.

### Usage Context

Best for fictional cockpit calibration tools, machine-body diagnostic interfaces, speculative hardware manuals, anime-inspired product microsites, and editorial systems about cybernetics without spectacle.
DESIGN.md
---
version: "alpha"
name: "Graphite Linear-Seat Notation"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#c66f2e"
  background: "#090a0b"
  border: "#343537"
  error: "#b85b35"
  info: "#aab7bd"
  muted: "#7b7f82"
  primary: "#d8d0c2"
  secondary: "#8e99a1"
  success: "#9da58f"
  surface: "#151719"
  text: "#e7e0d2"
  warning: "#c66f2e"
typography:
  headline-lg:
    fontFamily: "Teko"
    fontSize: "1.816rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Teko"
    fontSize: "1.488rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "IBM Plex Sans Condensed"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.55
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "Spline Sans Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "0px"
  md: "0px"
  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: "#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 Linear-Seat Notation

## Overview

Graphite Linear-Seat Notation treats a web interface as a cockpit service overlay for a body coupled to a machine shell. Its atmosphere comes from black-and-white manga panel discipline, late-90s hardware labels, and restrained diagnostic UI: the pilot is never illustrated, only inferred through seat geometry, reach arcs, harness scuffs, breath-fogged glass, and nervous-system calibration marks.

### Values

- Human presence is implied through ergonomic absence: empty seat rails, restraint pressure marks, hand reach zones, breath residue, and calibration traces replace character art.
- Information feels bolted to hardware, not floated as cards; every label attaches to a rail, screw index, centerline, panel edge, or exploded actuator callout.
- Monochrome manga structure does the emotional work through gutters, hard cuts, graphite fields, halftone fog, and isolated empty compartments.
- Operational color is scarce and mechanical: pale blue-gray registration lines carry system alignment, while safety orange marks lock pins, service arrows, and numbered components.
- The system favors quiet precision over cyberpunk spectacle; small type, exact ticks, and diagrammatic restraint create tension without dense HUD chaos.
- Y2K hardware/software language appears as CRT mode labels, boot fragments, serial part codes, square LEDs, and compact terminal numerals rather than nostalgic decoration.

### Anti-Values

- No green matrix rain, purple-cyan neon cyberpunk, command-center dashboard spectacle, or generic hacker terminal theatrics.
- No franchise mecha fan art, heroic pilots, full-body character illustration, or glossy anime splash composition.
- No rounded SaaS card grid, floating analytics widgets, gradient buttons, or friendly product-dashboard softness.
- No dense game HUD clutter; telemetry must have air, alignment, and a reason to attach to the cockpit structure.

### Visual Character

- Build pages from hard-edged manga gutters: warm off-white panel bands, near-black graphite compartments, 1px ink rules, and asymmetric cutaway rectangles instead of rounded cards.
- Use a central linear-seat schematic with vertical centerline reticles, seat orientation marks, reach-zone arcs, harness rub bands, and pale HUD calibration ticks drawn in CSS.
- Anchor information clusters to hardware rails with screw-index dots, orange lock-pin chevrons, numbered callout stems, and exploded actuator boxes connected by thin leader lines.
- Render panoramic monitor logic as stacked black CRT strips and multi-display mode labels wrapping the seat bay, with tiny monospaced boot fragments and inactive cool-gray LEDs.
- Reserve large empty graphite fields and off-white gutters as psychological pressure, letting dense diagnostic fragments occupy only bolted edge zones and service panels.

## 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 | `#c66f2e` |
| background | `#090a0b` |
| border | `#343537` |
| error | `#b85b35` |
| info | `#aab7bd` |
| muted | `#7b7f82` |
| primary | `#d8d0c2` |
| secondary | `#8e99a1` |
| success | `#9da58f` |
| surface | `#151719` |
| text | `#e7e0d2` |
| warning | `#c66f2e` |

## Typography

- **Headline-Lg**: Teko, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Teko, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans Condensed, 16px, weight 400, line-height 1.55.
- **Label-Md**: Spline Sans 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 >= 1180px keeps the cockpit cutaway spread; tablet 760-1179px becomes an 8-column sheet with the rail below the seat bay; mobile < 760px stacks panels while preserving horizontal CRT strips and centerline marks.

### Density

Medium-low overall density with deliberate high-density edge clusters; the interface breathes through black graphite voids and warm manga gutters.

### Grid

Desktop uses a 12-column max-width 1400px grid with 24px gutters, a dominant 6-column seat bay, a 3-column service rail, and overlapping monitor strips.

### Responsive

On tablet, callout stems shorten and exploded diagrams move under the seat bay; on mobile, nonessential boot fragments hide before typography or spacing compresses.

### Whitespace

Major voids use 64px, 96px, and 128px intervals; related telemetry and screw labels sit 4px to 12px apart so grouping contrast remains visible.

## Elevation & Depth

### Shadows

- **Lg**: 0 34px 120px rgba(0,0,0,0.55)
- **Md**: 0 18px 60px rgba(0,0,0,0.38)
- **Sm**: 0 0 0 1px rgba(216,208,194,0.08)

## Shapes

### Rounded

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

### Surfaces

- **Bg Pattern**: Graphite field crossed by faint centerline rulers, sparse calibration ticks, manga hatch bands, and clipped CRT scan strips.
- **Card Style**: Flat service panels with square corners, visible panel IDs, screw-index dots, attached leader lines, and orange callout tabs only where mechanically meaningful.
- **Treatment**: Matte graphite blocks with hard 1px ink borders, warm off-white gutters, subtle halftone/noise masks, and no glossy gradients.

### Borders

- **Accent Width**: 2px
- **Character**: Hard ink and bone hairlines: borders define manga gutters, panel seams, centerline reticles, and service callout stems; no rounded partial accent borders.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use a 12-column cockpit service sheet with one dominant linear-seat bay offset from center, a panoramic monitor arc crossing the top, one dense diagnostic edge rail, and one large empty graphite compartment. Avoid equal rows: the seat schematic must dominate, while callouts, boot strips, and actuator diagrams vary in weight and attachment.

### Density

Alternate 4px-to-8px telemetry clusters with 64px-to-128px voids. Dense information belongs near rails, screws, lock pins, and CRT strips; the central empty seat volume must remain readable and isolating.

### Hierarchy

The seat centerline and manga panel architecture establish primary hierarchy; oversized Teko headings act like manual section stamps, body copy stays narrow and subdued, and Spline Sans Mono telemetry remains tiny. Orange appears only on mechanical intervention points, not as general emphasis.

### Signature Patterns

- Linear-seat bay: a CSS-drawn empty pilot seat rectangle with centerline reticle, harness rub bands, reach-zone arcs, breath-fog panel, and pale blue-gray calibration ticks.
- Bolted callout rail: hardware-anchored information groups using screw dots, orange numbered tabs, angled leader lines, lock-pin chevrons, and square-corner exploded component boxes.
- Manga service gutters: warm off-white structural gutters cutting through matte graphite panels with halftone fog, hatch-line masks, and 1px black ink borders.
- CRT panoramic strip: segmented top monitors with tiny mode labels, scanline texture, inactive gray LEDs, boot fragments, and no glowing neon color fields.
- Exploded actuator notation: stacked wireframe component silhouettes offset from the main bay and connected by thin leaders, using numeric part codes instead of icons.

## 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/graphite-linear-seat-notation/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 square-corner panels, hard manga gutters, graphite voids, and visible centerline rulers as the primary structure.
- Do Attach every label to a tangible edge, rail, screw, diagram, seat axis, monitor strip, or callout stem.
- Do Keep type compact: Teko for manual stamps, IBM Plex Sans Condensed for narrow instructions, Spline Sans Mono for serials and telemetry.
- Do Use orange only for lock pins, service arrows, numbered annotations, and intervention states.
- Do Imply the pilot through absent-body traces such as reach arcs, breath fog, harness abrasion, and sensor feedback.
- Do Let one large empty graphite area remain underexplained to preserve isolation and pressure.
- Do Build hover states as mechanical registration changes: small line shifts, LED toggles, or callout brightening.
- Don't Do not use green code rain, neon purple/cyan cyberpunk, glowing city grids, or generic hacker dashboards.
- Don't Do not use rounded SaaS cards, glossy surfaces, three equal feature cards, or analytics widgets.
- Don't Do not depict heroic characters, franchise mecha, anime splash art, or full pilots inside the cockpit.
- Don't Do not fill all voids with HUD decoration; silence and graphite space are part of the language.
- Don't Do not use gradients, rainbow accents, saturated color triads, or large colored backdrops.
- Don't Do not let labels float unattached; if a datum is not bolted to hardware, remove it.
- Don't Do not mix rounded radius values or place one-sided accent borders on rounded elements.

### Accessibility

Maintain high contrast between warm off-white text and near-black fields, pair orange warnings with labels or numbers, keep critical telemetry above 12px, and provide visible square focus outlines using bone or orange hairlines.

### Usage Context

Best for fictional cockpit calibration tools, machine-body diagnostic interfaces, speculative hardware manuals, anime-inspired product microsites, and editorial systems about cybernetics without spectacle.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "graphite-linear-seat-notation",
  "type": "registry:theme",
  "title": "Graphite Linear-Seat Notation shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#090a0b",
      "foreground": "#e7e0d2",
      "card": "#151719",
      "card-foreground": "#e7e0d2",
      "popover": "#151719",
      "popover-foreground": "#e7e0d2",
      "primary": "#d8d0c2",
      "primary-foreground": "#111111",
      "secondary": "#8e99a1",
      "secondary-foreground": "#ffffff",
      "muted": "#7b7f82",
      "muted-foreground": "#e7e0d2",
      "accent": "#c66f2e",
      "accent-foreground": "#ffffff",
      "destructive": "#b85b35",
      "border": "#343537",
      "input": "#343537",
      "ring": "#c66f2e",
      "chart-1": "#d8d0c2",
      "chart-2": "#8e99a1",
      "chart-3": "#c66f2e",
      "chart-4": "#9da58f",
      "chart-5": "#c66f2e",
      "sidebar": "#151719",
      "sidebar-foreground": "#e7e0d2",
      "sidebar-primary": "#d8d0c2",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#aab7bd",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#343537",
      "sidebar-ring": "#c66f2e",
      "radius": "0"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#d8d0c2",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#c66f2e",
      "accent-foreground": "#ffffff",
      "destructive": "#b85b35",
      "border": "#303642",
      "input": "#303642",
      "ring": "#c66f2e",
      "chart-1": "#d8d0c2",
      "chart-2": "#8e99a1",
      "chart-3": "#c66f2e",
      "chart-4": "#9da58f",
      "chart-5": "#c66f2e",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#d8d0c2",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#c66f2e",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#c66f2e",
      "radius": "0"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "graphite-linear-seat-notation",
    "slug": "graphite-linear-seat-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"
      ]
    }
  }
}
```
in the wild

embodiments

Design Language Preview

Graphite Linear-Seat Notation

Color Palette

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

Typography

h1

Heading One

h2

Heading Two

h3

Heading Three

h4

Heading Four

body

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

caption

Caption text for supplementary information and metadata.

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

Buttons

Form Controls

Navigation

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

Feedback & Status

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

Containers & Overlays

card

Card Title

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

accordion

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

dialog
separator

Data Display

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

at a glance

Palette

Typography

headline-lgTeko · 29px · 700

The quick brown fox jumps

headline-mdTeko · 24px · 600

The quick brown fox jumps

body-mdIBM Plex Sans Condensed · 16px · 400

The quick brown fox jumps

label-mdSpline Sans Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

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

Spacing

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

Shape

full9999px
lg0px
md0px
none0px
sm0px
shadcn/ui

implementation kit

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

DESIGN.md with shadcn

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

advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #090a0b;
  --foreground: #e7e0d2;
  --card: #151719;
  --card-foreground: #e7e0d2;
  --popover: #151719;
  --popover-foreground: #e7e0d2;
  --primary: #d8d0c2;
  --primary-foreground: #111111;
  --secondary: #8e99a1;
  --secondary-foreground: #ffffff;
  --muted: #7b7f82;
  --muted-foreground: #e7e0d2;
  --accent: #c66f2e;
  --accent-foreground: #ffffff;
  --destructive: #b85b35;
  --border: #343537;
  --input: #343537;
  --ring: #c66f2e;
  --chart-1: #d8d0c2;
  --chart-2: #8e99a1;
  --chart-3: #c66f2e;
  --chart-4: #9da58f;
  --chart-5: #c66f2e;
  --sidebar: #151719;
  --sidebar-foreground: #e7e0d2;
  --sidebar-primary: #d8d0c2;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #aab7bd;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #343537;
  --sidebar-ring: #c66f2e;
  --radius: 0;
}

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

export function GraphiteLinearSeatNotationShadcnKit() {
  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 Linear-Seat 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>
  );
}
theme JSONcompatibility fallback
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "graphite-linear-seat-notation",
  "type": "registry:theme",
  "title": "Graphite Linear-Seat Notation shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#090a0b",
      "foreground": "#e7e0d2",
      "card": "#151719",
      "card-foreground": "#e7e0d2",
      "popover": "#151719",
      "popover-foreground": "#e7e0d2",
      "primary": "#d8d0c2",
      "primary-foreground": "#111111",
      "secondary": "#8e99a1",
      "secondary-foreground": "#ffffff",
      "muted": "#7b7f82",
      "muted-foreground": "#e7e0d2",
      "accent": "#c66f2e",
      "accent-foreground": "#ffffff",
      "destructive": "#b85b35",
      "border": "#343537",
      "input": "#343537",
      "ring": "#c66f2e",
      "chart-1": "#d8d0c2",
      "chart-2": "#8e99a1",
      "chart-3": "#c66f2e",
      "chart-4": "#9da58f",
      "chart-5": "#c66f2e",
      "sidebar": "#151719",
      "sidebar-foreground": "#e7e0d2",
      "sidebar-primary": "#d8d0c2",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#aab7bd",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#343537",
      "sidebar-ring": "#c66f2e",
      "radius": "0"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#d8d0c2",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#c66f2e",
      "accent-foreground": "#ffffff",
      "destructive": "#b85b35",
      "border": "#303642",
      "input": "#303642",
      "ring": "#c66f2e",
      "chart-1": "#d8d0c2",
      "chart-2": "#8e99a1",
      "chart-3": "#c66f2e",
      "chart-4": "#9da58f",
      "chart-5": "#c66f2e",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#d8d0c2",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#c66f2e",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#c66f2e",
      "radius": "0"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "graphite-linear-seat-notation",
    "slug": "graphite-linear-seat-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"
      ]
    }
  }
}
component recipescompatibility fallback
# Graphite Linear-Seat Notation shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `graphite-linear-seat-notation`
Slug: `graphite-linear-seat-notation`

## Intent

Graphite Linear-Seat Notation treats a web interface as a cockpit service overlay for a body coupled to a machine shell. Its atmosphere comes from black-and-white manga panel discipline, late-90s hardware labels, and restrained diagnostic UI: the pilot is never illustrated, only inferred through seat geometry, reach arcs, harness scuffs, breath-fogged glass, and nervous-system calibration marks.

## 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": "#c66f2e",
  "background": "#090a0b",
  "border": "#343537",
  "error": "#b85b35",
  "info": "#aab7bd",
  "muted": "#7b7f82",
  "primary": "#d8d0c2",
  "secondary": "#8e99a1",
  "success": "#9da58f",
  "surface": "#151719",
  "text": "#e7e0d2",
  "warning": "#c66f2e"
}

Typography:

{
  "base_size": "16px",
  "body_font": "IBM Plex Sans Condensed",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Sans+Condensed:wght@400;500;600&family=Spline+Sans+Mono:wght@400;500;600&family=Teko:wght@500;600&display=swap",
  "heading_font": "Teko",
  "letter_spacing": "-0.02em",
  "line_height": 1.55,
  "mono_font": "Spline Sans Mono",
  "scale_ratio": 1.22
}

## Visual character to preserve

- Build pages from hard-edged manga gutters: warm off-white panel bands, near-black graphite compartments, 1px ink rules, and asymmetric cutaway rectangles instead of rounded cards.
- Use a central linear-seat schematic with vertical centerline reticles, seat orientation marks, reach-zone arcs, harness rub bands, and pale HUD calibration ticks drawn in CSS.
- Anchor information clusters to hardware rails with screw-index dots, orange lock-pin chevrons, numbered callout stems, and exploded actuator boxes connected by thin leader lines.
- Render panoramic monitor logic as stacked black CRT strips and multi-display mode labels wrapping the seat bay, with tiny monospaced boot fragments and inactive cool-gray LEDs.
- Reserve large empty graphite fields and off-white gutters as psychological pressure, letting dense diagnostic fragments occupy only bolted edge zones and service panels.

## ShadSync visual profile

{
  "family": "brutalist",
  "material": "ink",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "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-linear-seat-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 square-corner panels, hard manga gutters, graphite voids, and visible centerline rulers as the primary structure.; Attach every label to a tangible edge, rail, screw, diagram, seat axis, monitor strip, or callout stem.; Keep type compact: Teko for manual stamps, IBM Plex Sans Condensed for narrow instructions, Spline Sans Mono for serials and telemetry.; Use orange only for lock pins, service arrows, numbered annotations, and intervention states.; Imply the pilot through absent-body traces such as reach arcs, breath fog, harness abrasion, and sensor feedback.; Let one large empty graphite area remain underexplained to preserve isolation and pressure.; Build hover states as mechanical registration changes: small line shifts, LED toggles, or callout brightening.
- Do not: Do not use green code rain, neon purple/cyan cyberpunk, glowing city grids, or generic hacker dashboards.; Do not use rounded SaaS cards, glossy surfaces, three equal feature cards, or analytics widgets.; Do not depict heroic characters, franchise mecha, anime splash art, or full pilots inside the cockpit.; Do not fill all voids with HUD decoration; silence and graphite space are part of the language.; Do not use gradients, rainbow accents, saturated color triads, or large colored backdrops.; Do not let labels float unattached; if a datum is not bolted to hardware, remove it.; Do not mix rounded radius values or place one-sided accent borders on rounded elements.

## 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 GraphiteLinearSeatNotationShadcnKit() {
  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 Linear-Seat 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 >= 1180px keeps the cockpit cutaway spread; tablet 760-1179px becomes an 8-column sheet with the rail below the seat bay; mobile < 760px stacks panels while preserving horizontal CRT strips and centerline marks.",
  "density": "Medium-low overall density with deliberate high-density edge clusters; the interface breathes through black graphite voids and warm manga gutters.",
  "grid": "Desktop uses a 12-column max-width 1400px grid with 24px gutters, a dominant 6-column seat bay, a 3-column service rail, and overlapping monitor strips.",
  "responsive": "On tablet, callout stems shorten and exploded diagrams move under the seat bay; on mobile, nonessential boot fragments hide before typography or spacing compresses.",
  "whitespace": "Major voids use 64px, 96px, and 128px intervals; related telemetry and screw labels sit 4px to 12px apart so grouping contrast remains visible."
}
preview shotscompatibility fallback
{
  "artifact": "katagami:shadcn-preview-shots",
  "version": "preview-shots-v1",
  "generator": "katagami-ui-compatibility-projection",
  "generatedBy": "katagami-ui-projection",
  "requiresVisualProfile": true,
  "schema": "katagami:shadcn-preview-shots/renderable-v1",
  "renderable": true,
  "language": {
    "id": "graphite-linear-seat-notation",
    "name": "Graphite Linear-Seat Notation",
    "slug": "graphite-linear-seat-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": [
    "Build pages from hard-edged manga gutters: warm off-white panel bands, near-black graphite compartments, 1px ink rules, and asymmetric cutaway rectangles instead of rounded cards.",
    "Use a central linear-seat schematic with vertical centerline reticles, seat orientation marks, reach-zone arcs, harness rub bands, and pale HUD calibration ticks drawn in CSS.",
    "Anchor information clusters to hardware rails with screw-index dots, orange lock-pin chevrons, numbered callout stems, and exploded actuator boxes connected by thin leader lines.",
    "Render panoramic monitor logic as stacked black CRT strips and multi-display mode labels wrapping the seat bay, with tiny monospaced boot fragments and inactive cool-gray LEDs.",
    "Reserve large empty graphite fields and off-white gutters as psychological pressure, letting dense diagnostic fragments occupy only bolted edge zones and service panels."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "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": "Graphite Linear-Seat 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 square-corner panels, hard manga gutters, graphite voids, and visible centerline rulers as the primary structure.",
      "Attach every label to a tangible edge, rail, screw, diagram, seat axis, monitor strip, or callout stem.",
      "Keep type compact: Teko for manual stamps, IBM Plex Sans Condensed for narrow instructions, Spline Sans Mono for serials and telemetry.",
      "Use orange only for lock pins, service arrows, numbered annotations, and intervention states.",
      "Imply the pilot through absent-body traces such as reach arcs, breath fog, harness abrasion, and sensor feedback.",
      "Let one large empty graphite area remain underexplained to preserve isolation and pressure.",
      "Build hover states as mechanical registration changes: small line shifts, LED toggles, or callout brightening."
    ],
    "dont": [
      "Do not use green code rain, neon purple/cyan cyberpunk, glowing city grids, or generic hacker dashboards.",
      "Do not use rounded SaaS cards, glossy surfaces, three equal feature cards, or analytics widgets.",
      "Do not depict heroic characters, franchise mecha, anime splash art, or full pilots inside the cockpit.",
      "Do not fill all voids with HUD decoration; silence and graphite space are part of the language.",
      "Do not use gradients, rainbow accents, saturated color triads, or large colored backdrops.",
      "Do not let labels float unattached; if a datum is not bolted to hardware, remove it.",
      "Do not mix rounded radius values or place one-sided accent borders on rounded elements."
    ]
  }
}
related

More like this