back to gallery
design language·cinematic-sci-fi-screen-graphics

Cinematic Sci-Fi Screen Graphics

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
A cinematic interface language built from starship bridge displays, tactical HUD overlays, and diegetic mission-control graphics. It favors luminous data planes on deep carbon surfaces, disciplined color coding, angular framing, and screen-space depth cues that feel operational rather than decorative.
values
Operational clarity under pressureLuminous depth with disciplined restraintColor as semantic alert routingInterfaces that feel embedded into the scene world
anti-values
×Playful rounded consumer-app softness×Neon overload without hierarchy×Flat generic dashboard cards
tokens
colors12 items
primary
#7FD6FF
secondary
#FFB45C
accent
#FF5E66
background
#08111B
surface
#101C29
text
#E7F4FF
muted
#7C97AC
border
#31506B
error
#FF5E66
success
#61F0BF
warning
#FFB45C
info
#7FD6FF
typography8 items
heading font
Orbitron
body font
Exo 2
mono font
IBM Plex Mono
base size
16px
scale ratio
1.25
line height
1.5
letter spacing
0.02em
google fonts url
https://fonts.googleapis.com/css2?family=Exo+2:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500;600&family=Orbitron:wght@500;600;700;800&display=swap
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
radii5 items
none
0
sm
6px
md
12px
lg
18px
full
9999px
shadows3 items
sm
0 0 0 1px rgba(127,214,255,0.08), 0 10px 24px rgba(1,8,15,0.28)
md
0 0 0 1px rgba(127,214,255,0.12), 0 18px 42px rgba(1,8,15,0.40)
lg
0 0 0 1px rgba(255,180,92,0.16), 0 26px 70px rgba(1,8,15,0.52)
surfaces3 items
treatment
glass
card style
Layer dark translucent panels over carbon gradients, with faint inset highlights, grid texture, and luminous corner seams that make each surface feel like diegetic display glass.
bg pattern
grid
borders4 items
default width
1px
accent width
2px
style
solid
character
Borders are fine technical traces with brighter illuminated corners and occasional amber or red segment markers, emphasizing instrumentation precision over heavy framing.
motion3 items
duration
220ms
easing
cubic-bezier(0.2, 0.8, 0.2, 1)
philosophy
deliberate
rules
composition
Compose the scene as a mission operations cockpit: one commanding tactical canvas, flanking diagnostic rails, and stacked subpanels that look synchronized by a central system rather than collected from a UI kit.
hierarchy
Use large uppercase coordinates, destination names, and mission statuses as the headline layer; medium metric cards as secondary structure; and dense monospace telemetry strips as tertiary detail.
density

High information density with disciplined spacing bands and breathing room around the primary tactical display.

signature patterns
Every major panel uses clip-path chamfers or pseudo-element notches so the silhouettes read as engineered sci-fi display hardware instead of default rounded cards.Panel frames combine a dim outer border with brighter top-left and bottom-right luminous line segments, creating directional edge lighting around each module.Charts, maps, and media areas are crossed by orbital arcs, vector paths, scanlines, or grid overlays rendered with layered gradients and absolutely positioned rule lines.Headings and key values are uppercase with expanded tracking, while all metadata, tabs, and switches use monospace labels in tiny sizes to mimic systems telemetry.Status feedback relies on narrow horizontal light bars, segmented pills, and pulsing beacon dots rather than filled success banners or generic toast cards.
layout
grid
Desktop uses a 12-column command deck with a large central tactical panel, narrow utility rail, and stacked side diagnostics; tablet collapses to two columns; mobile becomes a single scrolling operations feed with preserved panel hierarchy.
breakpoints

1440px command deck, 768px tablet operations stack, 375px single-column field console.

whitespace
Keep outer gutters generous and interior padding measured, using tighter telemetry spacing inside modules and wider separation between major systems to preserve cinematic readability.
guidance
do
  • Use dark layered surfaces with narrow luminous accents, not large flat color fills.
  • Treat red, amber, and blue as semantic signals tied to system meaning and urgency.
  • Build frames, separators, and overlays from line work, not shadows alone.
  • Design screens as believable diegetic mission interfaces with narrative context.
avoid
  • Do not use pillowy cards, pastel gradients, or soft mobile-fintech styling.
  • Do not let accent glows blur text or dominate the screen more than the data.
  • Do not rely on generic dashboard widgets without structural sci-fi framing.
  • Do not hide essential hierarchy inside equally weighted panels.
katagami spec
# Cinematic Sci-Fi Screen Graphics

## Philosophy

A cinematic interface language built from starship bridge displays, tactical HUD overlays, and diegetic mission-control graphics. It favors luminous data planes on deep carbon surfaces, disciplined color coding, angular framing, and screen-space depth cues that feel operational rather than decorative.

### Values

- Operational clarity under pressure
- Luminous depth with disciplined restraint
- Color as semantic alert routing
- Interfaces that feel embedded into the scene world

### Anti-Values

- Playful rounded consumer-app softness
- Neon overload without hierarchy
- Flat generic dashboard cards

### Visual Character

- Primary panels sit on deep navy and carbon fields with translucent gradient glass, while bright inner strokes and soft outer glow create the illusion of projected instrument screens floating above the hull.
- Modules use chamfered corners, clipped edge notches, and segmented frame lines so every container feels engineered from tactical display hardware rather than drawn as a soft rectangle.
- Typography pairs wide futuristic uppercase headings with compact technical monospace telemetry labels, creating a strong separation between cinematic command language and dense machine readouts.
- Amber, ice blue, and signal red appear as narrow beams, scanlines, status bars, and data traces against dark backgrounds, producing controlled luminous accents instead of filling large surfaces with color.
- Backgrounds carry subtle radar grids, orbital arcs, and faint vector noise so the screen always suggests spatial systems and sensor depth rather than a blank webpage canvas.

## Tokens

### Colors

| Name | Value |
|------|-------|
| primary | `#7FD6FF` |
| secondary | `#FFB45C` |
| accent | `#FF5E66` |
| background | `#08111B` |
| surface | `#101C29` |
| text | `#E7F4FF` |
| muted | `#7C97AC` |
| border | `#31506B` |
| error | `#FF5E66` |
| success | `#61F0BF` |
| warning | `#FFB45C` |
| info | `#7FD6FF` |

### Typography

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

### Spacing

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

### Radii

- **None**: 0
- **Sm**: 6px
- **Md**: 12px
- **Lg**: 18px
- **Full**: 9999px

### Shadows

- **Sm**: 0 0 0 1px rgba(127,214,255,0.08), 0 10px 24px rgba(1,8,15,0.28)
- **Md**: 0 0 0 1px rgba(127,214,255,0.12), 0 18px 42px rgba(1,8,15,0.40)
- **Lg**: 0 0 0 1px rgba(255,180,92,0.16), 0 26px 70px rgba(1,8,15,0.52)

### Surfaces

- **Treatment**: glass
- **Card Style**: Layer dark translucent panels over carbon gradients, with faint inset highlights, grid texture, and luminous corner seams that make each surface feel like diegetic display glass.
- **Bg Pattern**: grid

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Borders are fine technical traces with brighter illuminated corners and occasional amber or red segment markers, emphasizing instrumentation precision over heavy framing.

### Motion

- **Duration**: 220ms
- **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1)
- **Philosophy**: deliberate

## Rules

### Composition

Compose the scene as a mission operations cockpit: one commanding tactical canvas, flanking diagnostic rails, and stacked subpanels that look synchronized by a central system rather than collected from a UI kit.

### Hierarchy

Use large uppercase coordinates, destination names, and mission statuses as the headline layer; medium metric cards as secondary structure; and dense monospace telemetry strips as tertiary detail.

### Density

High information density with disciplined spacing bands and breathing room around the primary tactical display.

### Signature Patterns

- Every major panel uses clip-path chamfers or pseudo-element notches so the silhouettes read as engineered sci-fi display hardware instead of default rounded cards.
- Panel frames combine a dim outer border with brighter top-left and bottom-right luminous line segments, creating directional edge lighting around each module.
- Charts, maps, and media areas are crossed by orbital arcs, vector paths, scanlines, or grid overlays rendered with layered gradients and absolutely positioned rule lines.
- Headings and key values are uppercase with expanded tracking, while all metadata, tabs, and switches use monospace labels in tiny sizes to mimic systems telemetry.
- Status feedback relies on narrow horizontal light bars, segmented pills, and pulsing beacon dots rather than filled success banners or generic toast cards.

## Layout

### Grid

Desktop uses a 12-column command deck with a large central tactical panel, narrow utility rail, and stacked side diagnostics; tablet collapses to two columns; mobile becomes a single scrolling operations feed with preserved panel hierarchy.

### Breakpoints

1440px command deck, 768px tablet operations stack, 375px single-column field console.

### Whitespace

Keep outer gutters generous and interior padding measured, using tighter telemetry spacing inside modules and wider separation between major systems to preserve cinematic readability.

## Guidance

### Do

- Use dark layered surfaces with narrow luminous accents, not large flat color fills.
- Treat red, amber, and blue as semantic signals tied to system meaning and urgency.
- Build frames, separators, and overlays from line work, not shadows alone.
- Design screens as believable diegetic mission interfaces with narrative context.

### Don't

- Do not use pillowy cards, pastel gradients, or soft mobile-fintech styling.
- Do not let accent glows blur text or dominate the screen more than the data.
- Do not rely on generic dashboard widgets without structural sci-fi framing.
- Do not hide essential hierarchy inside equally weighted panels.
DESIGN.md
---
version: "alpha"
name: "Cinematic Sci-Fi Screen Graphics"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  primary: "#7FD6FF"
  secondary: "#FFB45C"
  accent: "#FF5E66"
  background: "#08111B"
  surface: "#101C29"
  text: "#E7F4FF"
  muted: "#7C97AC"
  border: "#31506B"
  error: "#FF5E66"
  success: "#61F0BF"
  warning: "#FFB45C"
  info: "#7FD6FF"
typography:
  headline-lg:
    fontFamily: "Orbitron"
    fontSize: "1.953rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "0.02em"
  headline-md:
    fontFamily: "Orbitron"
    fontSize: "1.563rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "0.02em"
  body-md:
    fontFamily: "Exo 2"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "0.02em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  none: "0px"
  sm: "6px"
  md: "12px"
  lg: "18px"
  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"
---

# Cinematic Sci-Fi Screen Graphics

## Overview

A cinematic interface language built from starship bridge displays, tactical HUD overlays, and diegetic mission-control graphics. It favors luminous data planes on deep carbon surfaces, disciplined color coding, angular framing, and screen-space depth cues that feel operational rather than decorative.

### Values

- Operational clarity under pressure
- Luminous depth with disciplined restraint
- Color as semantic alert routing
- Interfaces that feel embedded into the scene world

### Anti-Values

- Playful rounded consumer-app softness
- Neon overload without hierarchy
- Flat generic dashboard cards

### Visual Character

- Primary panels sit on deep navy and carbon fields with translucent gradient glass, while bright inner strokes and soft outer glow create the illusion of projected instrument screens floating above the hull.
- Modules use chamfered corners, clipped edge notches, and segmented frame lines so every container feels engineered from tactical display hardware rather than drawn as a soft rectangle.
- Typography pairs wide futuristic uppercase headings with compact technical monospace telemetry labels, creating a strong separation between cinematic command language and dense machine readouts.
- Amber, ice blue, and signal red appear as narrow beams, scanlines, status bars, and data traces against dark backgrounds, producing controlled luminous accents instead of filling large surfaces with color.
- Backgrounds carry subtle radar grids, orbital arcs, and faint vector noise so the screen always suggests spatial systems and sensor depth rather than a blank webpage canvas.

## 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 | `#7FD6FF` |
| secondary | `#FFB45C` |
| accent | `#FF5E66` |
| background | `#08111B` |
| surface | `#101C29` |
| text | `#E7F4FF` |
| muted | `#7C97AC` |
| border | `#31506B` |
| error | `#FF5E66` |
| success | `#61F0BF` |
| warning | `#FFB45C` |
| info | `#7FD6FF` |

## Typography

- **Headline-Lg**: Orbitron, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Orbitron, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Exo 2, 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 12-column command deck with a large central tactical panel, narrow utility rail, and stacked side diagnostics; tablet collapses to two columns; mobile becomes a single scrolling operations feed with preserved panel hierarchy.

### Breakpoints

1440px command deck, 768px tablet operations stack, 375px single-column field console.

### Whitespace

Keep outer gutters generous and interior padding measured, using tighter telemetry spacing inside modules and wider separation between major systems to preserve cinematic readability.

## Elevation & Depth

### Shadows

- **Sm**: 0 0 0 1px rgba(127,214,255,0.08), 0 10px 24px rgba(1,8,15,0.28)
- **Md**: 0 0 0 1px rgba(127,214,255,0.12), 0 18px 42px rgba(1,8,15,0.40)
- **Lg**: 0 0 0 1px rgba(255,180,92,0.16), 0 26px 70px rgba(1,8,15,0.52)

## Shapes

### Rounded

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

### Surfaces

- **Treatment**: glass
- **Card Style**: Layer dark translucent panels over carbon gradients, with faint inset highlights, grid texture, and luminous corner seams that make each surface feel like diegetic display glass.
- **Bg Pattern**: grid

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Borders are fine technical traces with brighter illuminated corners and occasional amber or red segment markers, emphasizing instrumentation precision over heavy framing.

## Components

### Composition

Compose the scene as a mission operations cockpit: one commanding tactical canvas, flanking diagnostic rails, and stacked subpanels that look synchronized by a central system rather than collected from a UI kit.

### Hierarchy

Use large uppercase coordinates, destination names, and mission statuses as the headline layer; medium metric cards as secondary structure; and dense monospace telemetry strips as tertiary detail.

### Density

High information density with disciplined spacing bands and breathing room around the primary tactical display.

### Signature Patterns

- Every major panel uses clip-path chamfers or pseudo-element notches so the silhouettes read as engineered sci-fi display hardware instead of default rounded cards.
- Panel frames combine a dim outer border with brighter top-left and bottom-right luminous line segments, creating directional edge lighting around each module.
- Charts, maps, and media areas are crossed by orbital arcs, vector paths, scanlines, or grid overlays rendered with layered gradients and absolutely positioned rule lines.
- Headings and key values are uppercase with expanded tracking, while all metadata, tabs, and switches use monospace labels in tiny sizes to mimic systems telemetry.
- Status feedback relies on narrow horizontal light bars, segmented pills, and pulsing beacon dots rather than filled success banners or generic toast cards.

## 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-019da326-645f-7e52-ba63-402e4c09ac9c/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 dark layered surfaces with narrow luminous accents, not large flat color fills.
- Do Treat red, amber, and blue as semantic signals tied to system meaning and urgency.
- Do Build frames, separators, and overlays from line work, not shadows alone.
- Do Design screens as believable diegetic mission interfaces with narrative context.
- Don't Do not use pillowy cards, pastel gradients, or soft mobile-fintech styling.
- Don't Do not let accent glows blur text or dominate the screen more than the data.
- Don't Do not rely on generic dashboard widgets without structural sci-fi framing.
- Don't Do not hide essential hierarchy inside equally weighted panels.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "cinematic-sci-fi-screen-graphics",
  "type": "registry:theme",
  "title": "Cinematic Sci-Fi Screen Graphics shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#08111B",
      "foreground": "#E7F4FF",
      "card": "#101C29",
      "card-foreground": "#E7F4FF",
      "popover": "#101C29",
      "popover-foreground": "#E7F4FF",
      "primary": "#7FD6FF",
      "primary-foreground": "#111111",
      "secondary": "#FFB45C",
      "secondary-foreground": "#111111",
      "muted": "#7C97AC",
      "muted-foreground": "#E7F4FF",
      "accent": "#FF5E66",
      "accent-foreground": "#ffffff",
      "destructive": "#FF5E66",
      "border": "#31506B",
      "input": "#31506B",
      "ring": "#FF5E66",
      "chart-1": "#7FD6FF",
      "chart-2": "#FFB45C",
      "chart-3": "#FF5E66",
      "chart-4": "#61F0BF",
      "chart-5": "#FFB45C",
      "sidebar": "#101C29",
      "sidebar-foreground": "#E7F4FF",
      "sidebar-primary": "#7FD6FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#7FD6FF",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#31506B",
      "sidebar-ring": "#FF5E66",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#7FD6FF",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#FF5E66",
      "accent-foreground": "#ffffff",
      "destructive": "#FF5E66",
      "border": "#303642",
      "input": "#303642",
      "ring": "#FF5E66",
      "chart-1": "#7FD6FF",
      "chart-2": "#FFB45C",
      "chart-3": "#FF5E66",
      "chart-4": "#61F0BF",
      "chart-5": "#FFB45C",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#7FD6FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#FF5E66",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#FF5E66",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019da326-645f-7e52-ba63-402e4c09ac9c",
    "slug": "cinematic-sci-fi-screen-graphics",
    "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 · cinematic-sci-fi-screen-graphics
DESIGN.md

at a glance

Palette

Typography

headline-lgOrbitron · 31px · 700

The quick brown fox jumps

headline-mdOrbitron · 25px · 600

The quick brown fox jumps

body-mdExo 2 · 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
md12px
lg18px
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.
primaryaccentsurfacemutedwarning
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: #08111B;
  --foreground: #E7F4FF;
  --card: #101C29;
  --card-foreground: #E7F4FF;
  --popover: #101C29;
  --popover-foreground: #E7F4FF;
  --primary: #7FD6FF;
  --primary-foreground: #111111;
  --secondary: #FFB45C;
  --secondary-foreground: #111111;
  --muted: #7C97AC;
  --muted-foreground: #E7F4FF;
  --accent: #FF5E66;
  --accent-foreground: #ffffff;
  --destructive: #FF5E66;
  --border: #31506B;
  --input: #31506B;
  --ring: #FF5E66;
  --chart-1: #7FD6FF;
  --chart-2: #FFB45C;
  --chart-3: #FF5E66;
  --chart-4: #61F0BF;
  --chart-5: #FFB45C;
  --sidebar: #101C29;
  --sidebar-foreground: #E7F4FF;
  --sidebar-primary: #7FD6FF;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #7FD6FF;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #31506B;
  --sidebar-ring: #FF5E66;
  --radius: 12px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #7FD6FF;
  --primary-foreground: #111111;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #FF5E66;
  --accent-foreground: #ffffff;
  --destructive: #FF5E66;
  --border: #303642;
  --input: #303642;
  --ring: #FF5E66;
  --chart-1: #7FD6FF;
  --chart-2: #FFB45C;
  --chart-3: #FF5E66;
  --chart-4: #61F0BF;
  --chart-5: #FFB45C;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #7FD6FF;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #FF5E66;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #FF5E66;
  --radius: 12px;
}
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 CinematicSciFiScreenGraphicsShadcnKit() {
  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">Cinematic Sci-Fi Screen Graphics</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": "cinematic-sci-fi-screen-graphics",
  "type": "registry:theme",
  "title": "Cinematic Sci-Fi Screen Graphics shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#08111B",
      "foreground": "#E7F4FF",
      "card": "#101C29",
      "card-foreground": "#E7F4FF",
      "popover": "#101C29",
      "popover-foreground": "#E7F4FF",
      "primary": "#7FD6FF",
      "primary-foreground": "#111111",
      "secondary": "#FFB45C",
      "secondary-foreground": "#111111",
      "muted": "#7C97AC",
      "muted-foreground": "#E7F4FF",
      "accent": "#FF5E66",
      "accent-foreground": "#ffffff",
      "destructive": "#FF5E66",
      "border": "#31506B",
      "input": "#31506B",
      "ring": "#FF5E66",
      "chart-1": "#7FD6FF",
      "chart-2": "#FFB45C",
      "chart-3": "#FF5E66",
      "chart-4": "#61F0BF",
      "chart-5": "#FFB45C",
      "sidebar": "#101C29",
      "sidebar-foreground": "#E7F4FF",
      "sidebar-primary": "#7FD6FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#7FD6FF",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#31506B",
      "sidebar-ring": "#FF5E66",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#7FD6FF",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#FF5E66",
      "accent-foreground": "#ffffff",
      "destructive": "#FF5E66",
      "border": "#303642",
      "input": "#303642",
      "ring": "#FF5E66",
      "chart-1": "#7FD6FF",
      "chart-2": "#FFB45C",
      "chart-3": "#FF5E66",
      "chart-4": "#61F0BF",
      "chart-5": "#FFB45C",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#7FD6FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#FF5E66",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#FF5E66",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019da326-645f-7e52-ba63-402e4c09ac9c",
    "slug": "cinematic-sci-fi-screen-graphics",
    "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
# Cinematic Sci-Fi Screen Graphics shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019da326-645f-7e52-ba63-402e4c09ac9c`
Slug: `cinematic-sci-fi-screen-graphics`

## Intent

A cinematic interface language built from starship bridge displays, tactical HUD overlays, and diegetic mission-control graphics. It favors luminous data planes on deep carbon surfaces, disciplined color coding, angular framing, and screen-space depth cues that feel operational rather than decorative.

## 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": "#7FD6FF",
  "secondary": "#FFB45C",
  "accent": "#FF5E66",
  "background": "#08111B",
  "surface": "#101C29",
  "text": "#E7F4FF",
  "muted": "#7C97AC",
  "border": "#31506B",
  "error": "#FF5E66",
  "success": "#61F0BF",
  "warning": "#FFB45C",
  "info": "#7FD6FF"
}

Typography:

{
  "heading_font": "Orbitron",
  "body_font": "Exo 2",
  "mono_font": "IBM Plex Mono",
  "base_size": "16px",
  "scale_ratio": 1.25,
  "line_height": 1.5,
  "letter_spacing": "0.02em",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Exo+2:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500;600&family=Orbitron:wght@500;600;700;800&display=swap"
}

## Visual character to preserve

- Primary panels sit on deep navy and carbon fields with translucent gradient glass, while bright inner strokes and soft outer glow create the illusion of projected instrument screens floating above the hull.
- Modules use chamfered corners, clipped edge notches, and segmented frame lines so every container feels engineered from tactical display hardware rather than drawn as a soft rectangle.
- Typography pairs wide futuristic uppercase headings with compact technical monospace telemetry labels, creating a strong separation between cinematic command language and dense machine readouts.
- Amber, ice blue, and signal red appear as narrow beams, scanlines, status bars, and data traces against dark backgrounds, producing controlled luminous accents instead of filling large surfaces with color.
- Backgrounds carry subtle radar grids, orbital arcs, and faint vector noise so the screen always suggests spatial systems and sensor depth rather than a blank webpage canvas.

## ShadSync visual profile

{
  "family": "system",
  "material": "flat",
  "contour": "pebble",
  "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/cinematic-sci-fi-screen-graphics/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 dark layered surfaces with narrow luminous accents, not large flat color fills.; Treat red, amber, and blue as semantic signals tied to system meaning and urgency.; Build frames, separators, and overlays from line work, not shadows alone.; Design screens as believable diegetic mission interfaces with narrative context.
- Do not: Do not use pillowy cards, pastel gradients, or soft mobile-fintech styling.; Do not let accent glows blur text or dominate the screen more than the data.; Do not rely on generic dashboard widgets without structural sci-fi framing.; Do not hide essential hierarchy inside equally weighted panels.

## 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 CinematicSciFiScreenGraphicsShadcnKit() {
  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">Cinematic Sci-Fi Screen Graphics</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 12-column command deck with a large central tactical panel, narrow utility rail, and stacked side diagnostics; tablet collapses to two columns; mobile becomes a single scrolling operations feed with preserved panel hierarchy.",
  "breakpoints": "1440px command deck, 768px tablet operations stack, 375px single-column field console.",
  "whitespace": "Keep outer gutters generous and interior padding measured, using tighter telemetry spacing inside modules and wider separation between major systems to preserve cinematic readability."
}
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-019da326-645f-7e52-ba63-402e4c09ac9c",
    "name": "Cinematic Sci-Fi Screen Graphics",
    "slug": "cinematic-sci-fi-screen-graphics"
  },
  "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": [
    "Primary panels sit on deep navy and carbon fields with translucent gradient glass, while bright inner strokes and soft outer glow create the illusion of projected instrument screens floating above the hull.",
    "Modules use chamfered corners, clipped edge notches, and segmented frame lines so every container feels engineered from tactical display hardware rather than drawn as a soft rectangle.",
    "Typography pairs wide futuristic uppercase headings with compact technical monospace telemetry labels, creating a strong separation between cinematic command language and dense machine readouts.",
    "Amber, ice blue, and signal red appear as narrow beams, scanlines, status bars, and data traces against dark backgrounds, producing controlled luminous accents instead of filling large surfaces with color.",
    "Backgrounds carry subtle radar grids, orbital arcs, and faint vector noise so the screen always suggests spatial systems and sensor depth rather than a blank webpage canvas."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "pebble",
    "border": "solid",
    "underlay": true,
    "grain": false,
    "stickerBadges": false,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Cinematic Sci-Fi Screen Graphics 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 dark layered surfaces with narrow luminous accents, not large flat color fills.",
      "Treat red, amber, and blue as semantic signals tied to system meaning and urgency.",
      "Build frames, separators, and overlays from line work, not shadows alone.",
      "Design screens as believable diegetic mission interfaces with narrative context."
    ],
    "dont": [
      "Do not use pillowy cards, pastel gradients, or soft mobile-fintech styling.",
      "Do not let accent glows blur text or dominate the screen more than the data.",
      "Do not rely on generic dashboard widgets without structural sci-fi framing.",
      "Do not hide essential hierarchy inside equally weighted panels."
    ]
  }
}
related

More like this