back to gallery
design language·mission-control-review

Mission-Control Review

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
Mission-Control Review merges aerospace telemetry dashboards with Swiss editorial pacing, framing dense operational data as a long-form review surface rather than a consumer app. It privileges calm dark contrast, disciplined annotation, and publication-grade hierarchy over neon spectacle.
values
Operational clarity over cinematic clutterEditorial hierarchy that turns telemetry into readable narrativeHigh-contrast dark surfaces with accessibility-aware restraintEvidence-first annotation and timestamped decision making
anti-values
×Arcade cyberpunk glow without information structure×Soft generic SaaS cards that erase technical gravity×Overloaded color coding that sacrifices readability
tokens
colors12 items
primary
#9BE7FF
secondary
#7C8EA3
accent
#F6B756
background
#081017
surface
#101A24
text
#E7F1F7
muted
#8A9BAE
border
#233545
error
#FF6D6D
success
#79E3A0
warning
#F6B756
info
#67C6FF
typography8 items
heading font
Space Grotesk
body font
IBM Plex Sans
mono font
IBM Plex Mono
base size
16px
scale ratio
1.2
line height
1.5
letter spacing
0.01em
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600;700&family=Space+Grotesk:wght@500;700&display=swap
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
radii5 items
none
0
sm
6px
md
10px
lg
16px
full
9999px
shadows3 items
sm
0 0 0 1px rgba(103,198,255,0.08)
md
0 14px 40px rgba(0,0,0,0.28)
lg
0 28px 80px rgba(0,0,0,0.42)
surfaces3 items
treatment
gradient
card style
Dark graphite panels use subtle vertical gradients with translucent overlays, making information layers feel stacked like instrument glass over printed briefing stock.
bg pattern
grid
borders4 items
default width
1px
accent width
2px
style
solid
character
Borders are precise aerospace drafting lines: faint outer frames, brighter top rules, and occasional accent ticks that imply measured calibration rather than decoration.
motion3 items
duration
180ms
easing
cubic-bezier(0.22, 1, 0.36, 1)
philosophy
deliberate
rules
composition
Compose screens like review boards: a narrative headline zone, a central evidence field, and flanking telemetry columns that support the main decision thread without competing for dominance.
hierarchy
Use large grotesk titles and compact monospace labels so operators can instantly distinguish story-level conclusions from metric-level evidence and procedural metadata.
density

High density but heavily gridded; clusters can be tight as long as labels, separators, and contrast maintain scanability.

signature patterns
All major modules use a clipped top-right or bottom-left notch created with pseudo-elements so the dashboard feels engineered from technical review plates rather than soft rectangles.Section headers pair uppercase monospace overlines with a long horizontal rule that continues into the grid, turning every panel title into a measured coordinate reference.Numeric readouts are grouped into bordered telemetry strips with evenly spaced cells, thin separator lines, and tiny status dots that reinforce instrument-panel rhythm.Editorial annotations appear as narrow side notes with rule-connected pointers into charts and tables, making explanatory commentary part of the structural layout instead of floating helper text.
layout
grid
Desktop uses a 14-column grid with a persistent left dossier column, a dominant central review span, and a right telemetry rail; tablet collapses to 8 columns and mobile to a single stacked narrative stream.
breakpoints

Desktop 1440+, tablet 768-1023, mobile 375-767 with modules reflowing from spread-like composition to sequential report blocks.

whitespace
Whitespace is intentional and editorial: tight within telemetry strips, generous around chapter transitions, and used to separate evidence clusters from narrative conclusions.
guidance
do
  • Use accent color only to mark status, thresholds, and active coordinates.
  • Frame dense data with clear labels, rules, and timestamps before adding visual flair.
  • Let long-form annotations and summary findings coexist with charts inside the same grid logic.
avoid
  • Do not flood charts or panels with full-surface neon gradients.
  • Do not use rounded consumer-product cards or playful iconography.
  • Do not hide operational metadata behind overly minimal presentation.
katagami spec
# Mission-Control Review

## Philosophy

Mission-Control Review merges aerospace telemetry dashboards with Swiss editorial pacing, framing dense operational data as a long-form review surface rather than a consumer app. It privileges calm dark contrast, disciplined annotation, and publication-grade hierarchy over neon spectacle.

### Values

- Operational clarity over cinematic clutter
- Editorial hierarchy that turns telemetry into readable narrative
- High-contrast dark surfaces with accessibility-aware restraint
- Evidence-first annotation and timestamped decision making

### Anti-Values

- Arcade cyberpunk glow without information structure
- Soft generic SaaS cards that erase technical gravity
- Overloaded color coding that sacrifices readability

### Visual Character

- A strict multi-column Swiss grid sits on a charcoal field, with oversized left-aligned deck headings and narrow telemetry rails that make the page feel like a mission dossier spread.
- Every major panel uses hairline inner rules, top-edge status bars, and clipped corner notches so containers read like technical review sheets instead of generic rounded cards.
- Monospaced numeric clusters are paired with restrained grotesk headlines and serif-free annotation captions, creating a contrast between narrative hierarchy and instrument readouts.
- Accent color is used as measured signal ink—cyan, amber, and red appear in thin rules, coordinate ticks, and active indicators rather than filling large surfaces.
- Long-form notes, figure labels, and evidence callouts are integrated directly into the dashboard composition so the interface feels half editorial review document and half live console.

## Tokens

### Colors

| Name | Value |
|------|-------|
| primary | `#9BE7FF` |
| secondary | `#7C8EA3` |
| accent | `#F6B756` |
| background | `#081017` |
| surface | `#101A24` |
| text | `#E7F1F7` |
| muted | `#8A9BAE` |
| border | `#233545` |
| error | `#FF6D6D` |
| success | `#79E3A0` |
| warning | `#F6B756` |
| info | `#67C6FF` |

### Typography

- **Heading Font**: Space Grotesk
- **Body Font**: IBM Plex Sans
- **Mono Font**: IBM Plex Mono
- **Base Size**: 16px
- **Scale Ratio**: 1.2
- **Line Height**: 1.5
- **Letter Spacing**: 0.01em
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600;700&family=Space+Grotesk:wght@500;700&display=swap

### Spacing

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

### Radii

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

### Shadows

- **Sm**: 0 0 0 1px rgba(103,198,255,0.08)
- **Md**: 0 14px 40px rgba(0,0,0,0.28)
- **Lg**: 0 28px 80px rgba(0,0,0,0.42)

### Surfaces

- **Treatment**: gradient
- **Card Style**: Dark graphite panels use subtle vertical gradients with translucent overlays, making information layers feel stacked like instrument glass over printed briefing stock.
- **Bg Pattern**: grid

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Borders are precise aerospace drafting lines: faint outer frames, brighter top rules, and occasional accent ticks that imply measured calibration rather than decoration.

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.22, 1, 0.36, 1)
- **Philosophy**: deliberate

## Rules

### Composition

Compose screens like review boards: a narrative headline zone, a central evidence field, and flanking telemetry columns that support the main decision thread without competing for dominance.

### Hierarchy

Use large grotesk titles and compact monospace labels so operators can instantly distinguish story-level conclusions from metric-level evidence and procedural metadata.

### Density

High density but heavily gridded; clusters can be tight as long as labels, separators, and contrast maintain scanability.

### Signature Patterns

- All major modules use a clipped top-right or bottom-left notch created with pseudo-elements so the dashboard feels engineered from technical review plates rather than soft rectangles.
- Section headers pair uppercase monospace overlines with a long horizontal rule that continues into the grid, turning every panel title into a measured coordinate reference.
- Numeric readouts are grouped into bordered telemetry strips with evenly spaced cells, thin separator lines, and tiny status dots that reinforce instrument-panel rhythm.
- Editorial annotations appear as narrow side notes with rule-connected pointers into charts and tables, making explanatory commentary part of the structural layout instead of floating helper text.

## Layout

### Grid

Desktop uses a 14-column grid with a persistent left dossier column, a dominant central review span, and a right telemetry rail; tablet collapses to 8 columns and mobile to a single stacked narrative stream.

### Breakpoints

Desktop 1440+, tablet 768-1023, mobile 375-767 with modules reflowing from spread-like composition to sequential report blocks.

### Whitespace

Whitespace is intentional and editorial: tight within telemetry strips, generous around chapter transitions, and used to separate evidence clusters from narrative conclusions.

## Guidance

### Do

- Use accent color only to mark status, thresholds, and active coordinates.
- Frame dense data with clear labels, rules, and timestamps before adding visual flair.
- Let long-form annotations and summary findings coexist with charts inside the same grid logic.

### Don't

- Do not flood charts or panels with full-surface neon gradients.
- Do not use rounded consumer-product cards or playful iconography.
- Do not hide operational metadata behind overly minimal presentation.
DESIGN.md
---
version: "alpha"
name: "Mission-Control Review"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  primary: "#9BE7FF"
  secondary: "#7C8EA3"
  accent: "#F6B756"
  background: "#081017"
  surface: "#101A24"
  text: "#E7F1F7"
  muted: "#8A9BAE"
  border: "#233545"
  error: "#FF6D6D"
  success: "#79E3A0"
  warning: "#F6B756"
  info: "#67C6FF"
typography:
  headline-lg:
    fontFamily: "Space Grotesk"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "0.01em"
  headline-md:
    fontFamily: "Space Grotesk"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "0.01em"
  body-md:
    fontFamily: "IBM Plex Sans"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "0.01em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  none: "0px"
  sm: "6px"
  md: "10px"
  lg: "16px"
  full: "9999px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
components:
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  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"
---

# Mission-Control Review

## Overview

Mission-Control Review merges aerospace telemetry dashboards with Swiss editorial pacing, framing dense operational data as a long-form review surface rather than a consumer app. It privileges calm dark contrast, disciplined annotation, and publication-grade hierarchy over neon spectacle.

### Values

- Operational clarity over cinematic clutter
- Editorial hierarchy that turns telemetry into readable narrative
- High-contrast dark surfaces with accessibility-aware restraint
- Evidence-first annotation and timestamped decision making

### Anti-Values

- Arcade cyberpunk glow without information structure
- Soft generic SaaS cards that erase technical gravity
- Overloaded color coding that sacrifices readability

### Visual Character

- A strict multi-column Swiss grid sits on a charcoal field, with oversized left-aligned deck headings and narrow telemetry rails that make the page feel like a mission dossier spread.
- Every major panel uses hairline inner rules, top-edge status bars, and clipped corner notches so containers read like technical review sheets instead of generic rounded cards.
- Monospaced numeric clusters are paired with restrained grotesk headlines and serif-free annotation captions, creating a contrast between narrative hierarchy and instrument readouts.
- Accent color is used as measured signal ink—cyan, amber, and red appear in thin rules, coordinate ticks, and active indicators rather than filling large surfaces.
- Long-form notes, figure labels, and evidence callouts are integrated directly into the dashboard composition so the interface feels half editorial review document and half live console.

## Colors

Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.

| Token | Value |
|-------|-------|
| primary | `#9BE7FF` |
| secondary | `#7C8EA3` |
| accent | `#F6B756` |
| background | `#081017` |
| surface | `#101A24` |
| text | `#E7F1F7` |
| muted | `#8A9BAE` |
| border | `#233545` |
| error | `#FF6D6D` |
| success | `#79E3A0` |
| warning | `#F6B756` |
| info | `#67C6FF` |

## Typography

- **Headline-Lg**: Space Grotesk, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Space Grotesk, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans, 16px, weight 400, line-height 1.5.
- **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`

### Grid

Desktop uses a 14-column grid with a persistent left dossier column, a dominant central review span, and a right telemetry rail; tablet collapses to 8 columns and mobile to a single stacked narrative stream.

### Breakpoints

Desktop 1440+, tablet 768-1023, mobile 375-767 with modules reflowing from spread-like composition to sequential report blocks.

### Whitespace

Whitespace is intentional and editorial: tight within telemetry strips, generous around chapter transitions, and used to separate evidence clusters from narrative conclusions.

## Elevation & Depth

### Shadows

- **Sm**: 0 0 0 1px rgba(103,198,255,0.08)
- **Md**: 0 14px 40px rgba(0,0,0,0.28)
- **Lg**: 0 28px 80px rgba(0,0,0,0.42)

## Shapes

### Rounded

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

### Surfaces

- **Treatment**: gradient
- **Card Style**: Dark graphite panels use subtle vertical gradients with translucent overlays, making information layers feel stacked like instrument glass over printed briefing stock.
- **Bg Pattern**: grid

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Borders are precise aerospace drafting lines: faint outer frames, brighter top rules, and occasional accent ticks that imply measured calibration rather than decoration.

## Components

### Composition

Compose screens like review boards: a narrative headline zone, a central evidence field, and flanking telemetry columns that support the main decision thread without competing for dominance.

### Hierarchy

Use large grotesk titles and compact monospace labels so operators can instantly distinguish story-level conclusions from metric-level evidence and procedural metadata.

### Density

High density but heavily gridded; clusters can be tight as long as labels, separators, and contrast maintain scanability.

### Signature Patterns

- All major modules use a clipped top-right or bottom-left notch created with pseudo-elements so the dashboard feels engineered from technical review plates rather than soft rectangles.
- Section headers pair uppercase monospace overlines with a long horizontal rule that continues into the grid, turning every panel title into a measured coordinate reference.
- Numeric readouts are grouped into bordered telemetry strips with evenly spaced cells, thin separator lines, and tiny status dots that reinforce instrument-panel rhythm.
- Editorial annotations appear as narrow side notes with rule-connected pointers into charts and tables, making explanatory commentary part of the structural layout instead of floating helper text.

## 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-019d9eb6-89e6-7151-a8ff-dc0311b47d23/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 accent color only to mark status, thresholds, and active coordinates.
- Do Frame dense data with clear labels, rules, and timestamps before adding visual flair.
- Do Let long-form annotations and summary findings coexist with charts inside the same grid logic.
- Don't Do not flood charts or panels with full-surface neon gradients.
- Don't Do not use rounded consumer-product cards or playful iconography.
- Don't Do not hide operational metadata behind overly minimal presentation.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "mission-control-review",
  "type": "registry:theme",
  "title": "Mission-Control Review shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#081017",
      "foreground": "#E7F1F7",
      "card": "#101A24",
      "card-foreground": "#E7F1F7",
      "popover": "#101A24",
      "popover-foreground": "#E7F1F7",
      "primary": "#9BE7FF",
      "primary-foreground": "#111111",
      "secondary": "#7C8EA3",
      "secondary-foreground": "#ffffff",
      "muted": "#8A9BAE",
      "muted-foreground": "#E7F1F7",
      "accent": "#F6B756",
      "accent-foreground": "#111111",
      "destructive": "#FF6D6D",
      "border": "#233545",
      "input": "#233545",
      "ring": "#F6B756",
      "chart-1": "#9BE7FF",
      "chart-2": "#7C8EA3",
      "chart-3": "#F6B756",
      "chart-4": "#79E3A0",
      "chart-5": "#F6B756",
      "sidebar": "#101A24",
      "sidebar-foreground": "#E7F1F7",
      "sidebar-primary": "#9BE7FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#67C6FF",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#233545",
      "sidebar-ring": "#F6B756",
      "radius": "10px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#9BE7FF",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#F6B756",
      "accent-foreground": "#111111",
      "destructive": "#FF6D6D",
      "border": "#303642",
      "input": "#303642",
      "ring": "#F6B756",
      "chart-1": "#9BE7FF",
      "chart-2": "#7C8EA3",
      "chart-3": "#F6B756",
      "chart-4": "#79E3A0",
      "chart-5": "#F6B756",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#9BE7FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#F6B756",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#F6B756",
      "radius": "10px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019d9eb6-89e6-7151-a8ff-dc0311b47d23",
    "slug": "mission-control-review",
    "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": {
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · mission-control-review
DESIGN.md

at a glance

Palette

Typography

headline-lgSpace Grotesk · 28px · 700

The quick brown fox jumps

headline-mdSpace Grotesk · 23px · 600

The quick brown fox jumps

body-mdIBM Plex Sans · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

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

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl48px
  • 4xl64px

Shape

none0px
sm6px
md10px
lg16px
full9999px
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: #081017;
  --foreground: #E7F1F7;
  --card: #101A24;
  --card-foreground: #E7F1F7;
  --popover: #101A24;
  --popover-foreground: #E7F1F7;
  --primary: #9BE7FF;
  --primary-foreground: #111111;
  --secondary: #7C8EA3;
  --secondary-foreground: #ffffff;
  --muted: #8A9BAE;
  --muted-foreground: #E7F1F7;
  --accent: #F6B756;
  --accent-foreground: #111111;
  --destructive: #FF6D6D;
  --border: #233545;
  --input: #233545;
  --ring: #F6B756;
  --chart-1: #9BE7FF;
  --chart-2: #7C8EA3;
  --chart-3: #F6B756;
  --chart-4: #79E3A0;
  --chart-5: #F6B756;
  --sidebar: #101A24;
  --sidebar-foreground: #E7F1F7;
  --sidebar-primary: #9BE7FF;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #67C6FF;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #233545;
  --sidebar-ring: #F6B756;
  --radius: 10px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #9BE7FF;
  --primary-foreground: #111111;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #F6B756;
  --accent-foreground: #111111;
  --destructive: #FF6D6D;
  --border: #303642;
  --input: #303642;
  --ring: #F6B756;
  --chart-1: #9BE7FF;
  --chart-2: #7C8EA3;
  --chart-3: #F6B756;
  --chart-4: #79E3A0;
  --chart-5: #F6B756;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #9BE7FF;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #F6B756;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #F6B756;
  --radius: 10px;
}
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 MissionControlReviewShadcnKit() {
  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">Mission-Control Review</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": "mission-control-review",
  "type": "registry:theme",
  "title": "Mission-Control Review shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#081017",
      "foreground": "#E7F1F7",
      "card": "#101A24",
      "card-foreground": "#E7F1F7",
      "popover": "#101A24",
      "popover-foreground": "#E7F1F7",
      "primary": "#9BE7FF",
      "primary-foreground": "#111111",
      "secondary": "#7C8EA3",
      "secondary-foreground": "#ffffff",
      "muted": "#8A9BAE",
      "muted-foreground": "#E7F1F7",
      "accent": "#F6B756",
      "accent-foreground": "#111111",
      "destructive": "#FF6D6D",
      "border": "#233545",
      "input": "#233545",
      "ring": "#F6B756",
      "chart-1": "#9BE7FF",
      "chart-2": "#7C8EA3",
      "chart-3": "#F6B756",
      "chart-4": "#79E3A0",
      "chart-5": "#F6B756",
      "sidebar": "#101A24",
      "sidebar-foreground": "#E7F1F7",
      "sidebar-primary": "#9BE7FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#67C6FF",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#233545",
      "sidebar-ring": "#F6B756",
      "radius": "10px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#9BE7FF",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#F6B756",
      "accent-foreground": "#111111",
      "destructive": "#FF6D6D",
      "border": "#303642",
      "input": "#303642",
      "ring": "#F6B756",
      "chart-1": "#9BE7FF",
      "chart-2": "#7C8EA3",
      "chart-3": "#F6B756",
      "chart-4": "#79E3A0",
      "chart-5": "#F6B756",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#9BE7FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#F6B756",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#F6B756",
      "radius": "10px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019d9eb6-89e6-7151-a8ff-dc0311b47d23",
    "slug": "mission-control-review",
    "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": {
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ]
    }
  }
}
component recipescompatibility fallback
# Mission-Control Review shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019d9eb6-89e6-7151-a8ff-dc0311b47d23`
Slug: `mission-control-review`

## Intent

Mission-Control Review merges aerospace telemetry dashboards with Swiss editorial pacing, framing dense operational data as a long-form review surface rather than a consumer app. It privileges calm dark contrast, disciplined annotation, and publication-grade hierarchy over neon 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:

{
  "primary": "#9BE7FF",
  "secondary": "#7C8EA3",
  "accent": "#F6B756",
  "background": "#081017",
  "surface": "#101A24",
  "text": "#E7F1F7",
  "muted": "#8A9BAE",
  "border": "#233545",
  "error": "#FF6D6D",
  "success": "#79E3A0",
  "warning": "#F6B756",
  "info": "#67C6FF"
}

Typography:

{
  "heading_font": "Space Grotesk",
  "body_font": "IBM Plex Sans",
  "mono_font": "IBM Plex Mono",
  "base_size": "16px",
  "scale_ratio": 1.2,
  "line_height": 1.5,
  "letter_spacing": "0.01em",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600;700&family=Space+Grotesk:wght@500;700&display=swap"
}

## Visual character to preserve

- A strict multi-column Swiss grid sits on a charcoal field, with oversized left-aligned deck headings and narrow telemetry rails that make the page feel like a mission dossier spread.
- Every major panel uses hairline inner rules, top-edge status bars, and clipped corner notches so containers read like technical review sheets instead of generic rounded cards.
- Monospaced numeric clusters are paired with restrained grotesk headlines and serif-free annotation captions, creating a contrast between narrative hierarchy and instrument readouts.
- Accent color is used as measured signal ink—cyan, amber, and red appear in thin rules, coordinate ticks, and active indicators rather than filling large surfaces.
- Long-form notes, figure labels, and evidence callouts are integrated directly into the dashboard composition so the interface feels half editorial review document and half live console.

## ShadSync visual profile

{
  "family": "editorial",
  "material": "flat",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": false,
  "stickerBadges": false,
  "motion": "still",
  "density": "balanced",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.

### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.

### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.

### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.

### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.

## Preview shots

- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/mission-control-review/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 accent color only to mark status, thresholds, and active coordinates.; Frame dense data with clear labels, rules, and timestamps before adding visual flair.; Let long-form annotations and summary findings coexist with charts inside the same grid logic.
- Do not: Do not flood charts or panels with full-surface neon gradients.; Do not use rounded consumer-product cards or playful iconography.; Do not hide operational metadata behind overly minimal presentation.

## 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 MissionControlReviewShadcnKit() {
  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">Mission-Control Review</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

{
  "grid": "Desktop uses a 14-column grid with a persistent left dossier column, a dominant central review span, and a right telemetry rail; tablet collapses to 8 columns and mobile to a single stacked narrative stream.",
  "breakpoints": "Desktop 1440+, tablet 768-1023, mobile 375-767 with modules reflowing from spread-like composition to sequential report blocks.",
  "whitespace": "Whitespace is intentional and editorial: tight within telemetry strips, generous around chapter transitions, and used to separate evidence clusters from narrative conclusions."
}
preview shotscompatibility fallback
{
  "artifact": "katagami:shadcn-preview-shots",
  "version": "preview-shots-v1",
  "generator": "katagami-ui-compatibility-projection",
  "generatedBy": "katagami-ui-projection",
  "requiresVisualProfile": true,
  "schema": "katagami:shadcn-preview-shots/renderable-v1",
  "renderable": true,
  "language": {
    "id": "en-019d9eb6-89e6-7151-a8ff-dc0311b47d23",
    "name": "Mission-Control Review",
    "slug": "mission-control-review"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "A strict multi-column Swiss grid sits on a charcoal field, with oversized left-aligned deck headings and narrow telemetry rails that make the page feel like a mission dossier spread.",
    "Every major panel uses hairline inner rules, top-edge status bars, and clipped corner notches so containers read like technical review sheets instead of generic rounded cards.",
    "Monospaced numeric clusters are paired with restrained grotesk headlines and serif-free annotation captions, creating a contrast between narrative hierarchy and instrument readouts.",
    "Accent color is used as measured signal ink—cyan, amber, and red appear in thin rules, coordinate ticks, and active indicators rather than filling large surfaces.",
    "Long-form notes, figure labels, and evidence callouts are integrated directly into the dashboard composition so the interface feels half editorial review document and half live console."
  ],
  "visualProfile": {
    "family": "editorial",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": false,
    "stickerBadges": false,
    "motion": "still",
    "density": "balanced",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Mission-Control Review 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 accent color only to mark status, thresholds, and active coordinates.",
      "Frame dense data with clear labels, rules, and timestamps before adding visual flair.",
      "Let long-form annotations and summary findings coexist with charts inside the same grid logic."
    ],
    "dont": [
      "Do not flood charts or panels with full-surface neon gradients.",
      "Do not use rounded consumer-product cards or playful iconography.",
      "Do not hide operational metadata behind overly minimal presentation."
    ]
  }
}
related

More like this