A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.
Portable DESIGN.md source of truth for most agents and apps.
Compose screens like review boards: a narrative headline zone, a central evidence field, and supporting telemetry rails, oriented by a left datum rail of coordinate ticks. Let the conclusion stay dominant; rails support the decision thread without competing. Never box navigation into a pill or floating card.
Use large Space Grotesk deck titles for story-level conclusions and compact IBM Plex Mono for metric-level readouts, coordinates, and procedural metadata, so operators distinguish narrative from instrument at a glance. Cyan reads; amber marks thresholds and active coordinates; red flags a real fault.
High density but heavily gridded: telemetry strips and ledgers can be tight as long as labels, separators, status dots, and contrast keep them scannable; every dense cluster has a quieter band or annotation nearby.
A left datum coordinate rail; clipped-notch technical plates with a 2px cyan top status bar; section headers of amber mono coordinate overline + title + rule into the grid; telemetry strips of evenly spaced readout cells with signal-ink status dots; and rule-connected editorial annotations inside the grid.
A persistent left datum rail (or sidebar nav on the dashboard) plus a dominant central content stack; content caps and centres around 1320-1480px and only the landing hero spans 100vw.
Intentional and editorial: tight within telemetry strips and ticks, generous around section transitions and above every title, used to separate evidence clusters from narrative conclusions.
Light and spacious at the masthead and hero, denser through telemetry strips, ledgers, and command forms, quieter again at the audit footer.
Renders from ~390px mobile to 2560px+ ultra-wide; tablet drops the datum rail to a top bar, mobile collapses to a single stacked stream, hides non-essential nav and table columns, makes controls full width, and never overflows horizontally; grids shrink with minmax(0,1fr) + min-width:0.
datum
Spacecraft and orbital subjects rendered as mission-control review plates in the Datum technique: the subject crisp and dominant on a deep charcoal field over a faint blueprint grid, dressed with hairline cyan dimension rules and calibration ticks, amber coordinate crosshairs, sparse monospace readouts and status dots in the margins, and clipped corner notches framing the plate.
One full-bleed landing hero in the Datum technique composed with a calm left third for the overlay; elsewhere keep imagery to plate previews and feature studies with leader-line callouts. End every prompt with NO text, NO letters, NO logos.
# Apsis ## Philosophy Apsis is a review-board language for operational telemetry. It reads dense flight data like a long-form dossier rather than a consumer app: a narrative headline zone, a central evidence field, and supporting telemetry rails. Every reading carries a coordinate; every finding carries a rule. It privileges calm dark contrast, disciplined annotation, and publication-grade hierarchy over neon spectacle. A faithful refinement of Mission-Control Review — same idea, same charcoal field and signal-ink palette family — brought up to standard in its radius system, accent discipline, button and form systems, and no-JS motion gate. ### Values - Operational clarity over cinematic clutter - Editorial hierarchy that turns telemetry into a readable narrative - Every reading located: a coordinate rail and per-section coordinates orient the page - Evidence-first annotation, rule-connected to the chart or table it explains - High-contrast charcoal surfaces with accessibility-aware restraint - Accent spent only as signal ink — cyan reads, amber marks thresholds, red flags a real fault ### Anti-Values - Arcade cyberpunk glow without information structure - White or muddy pastel grounds, gradient washes, neon spectacle - Soft generic SaaS cards that erase the technical gravity - Floating helper text divorced from the evidence it explains - Accent colour spent on decoration rather than a real status - The oversized italic-serif AI-startup default headline ### Visual Character - A continuous left datum rail carries coordinate ticks (LAT / REV / LON) down the page, giving every section a fixed location in the flight. - Every major module is a clipped-notch plate — squared corners with one clipped notch and a 2px cyan top status bar — so containers read like engineered review sheets, never soft consumer cards. - Section headers pair an amber monospace coordinate overline with the title and a horizontal rule that continues into the grid, turning each panel title into a measured coordinate reference. - Numeric readouts cluster into telemetry strips with evenly spaced cells, thin separators, and tiny signal-ink status dots for instrument-panel rhythm; Space Grotesk decks carry conclusions while IBM Plex Mono carries readouts. - Editorial annotations sit inside the grid, rule-connected by a left signal-ink rule to the chart or table they explain — commentary as structure, not floating helper text. ## Tokens ### Colors | Name | Value | |------|-------| | bg | `#081017` | | surface | `#101A24` | | surface_2 | `#16242F` | | recess | `#050B11` | | text | `#E7F1F7` | | muted | `#8A9BAE` | | border | `#233545` | | rule | `#1B2A38` | | accent | `#9BE7FF` | | accent_2 | `#F6B756` | | on_accent | `#061019` | | success | `#79E3A0` | | warning | `#F6B756` | | error | `#FF6D6D` | | info | `#67C6FF` | ### Typography - **Base Size**: 17px - **Body Font**: IBM Plex Sans - **Heading Font**: Space Grotesk - **Mono Font**: IBM Plex Mono - **Heading Weight**: 600 - **Heading Transform**: none - **Letter Spacing**: -0.02em - **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;600;700&display=swap ### Radii - **None**: 0 - **Sm**: 0 - **Md**: 16px - **Lg**: 24px - **Full**: 9999px ### Shadows - **Sm**: inset 0 0 0 1px rgba(155,231,255,0.06) - **Md**: 0 24px 60px rgba(0,0,0,0.42) - **Lg**: 0 48px 120px rgba(0,0,0,0.55) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Treatment**: flat clipped-notch technical plates over a charcoal field; a 2px cyan status bar across each plate top; no glass, no gradient washes - **Card Style**: Squared plates with one clipped corner notch (top-right or bottom-left) built with clip-path, a faint vertical surface gradient (#16242F to #101A24), a hairline #233545 border, and a 2px cyan top status bar — engineered review sheets, never rounded consumer cards. - **Bg Pattern**: faint 64px blueprint grid over a deep charcoal #081017 field ### Borders - **Default Width**: 1px - **Accent Width**: 0 - **Style**: solid - **Character**: Precise aerospace drafting hairlines (#233545) for structure only; colour is carried by signal-ink status dots and the cyan top status bar, never by an accent edge on a card. ### Motion - **Duration**: 180ms - **Easing**: cubic-bezier(0.22, 1, 0.36, 1) - **Philosophy**: Deliberate. The settled, fully-rendered page is the default and is visible with no JavaScript; reveals are layered on top behind an .mtn class on <html> and respect prefers-reduced-motion. ## Rules ### Composition Compose screens like review boards: a narrative headline zone, a central evidence field, and supporting telemetry rails, oriented by a left datum rail of coordinate ticks. Let the conclusion stay dominant; rails support the decision thread without competing. Never box navigation into a pill or floating card. ### Hierarchy Use large Space Grotesk deck titles for story-level conclusions and compact IBM Plex Mono for metric-level readouts, coordinates, and procedural metadata, so operators distinguish narrative from instrument at a glance. Cyan reads; amber marks thresholds and active coordinates; red flags a real fault. ### Density High density but heavily gridded: telemetry strips and ledgers can be tight as long as labels, separators, status dots, and contrast keep them scannable; every dense cluster has a quieter band or annotation nearby. ### Signature A left datum coordinate rail; clipped-notch technical plates with a 2px cyan top status bar; section headers of amber mono coordinate overline + title + rule into the grid; telemetry strips of evenly spaced readout cells with signal-ink status dots; and rule-connected editorial annotations inside the grid. ## Layout ### Grid A persistent left datum rail (or sidebar nav on the dashboard) plus a dominant central content stack; content caps and centres around 1320-1480px and only the landing hero spans 100vw. ### Whitespace Intentional and editorial: tight within telemetry strips and ticks, generous around section transitions and above every title, used to separate evidence clusters from narrative conclusions. ### Density Light and spacious at the masthead and hero, denser through telemetry strips, ledgers, and command forms, quieter again at the audit footer. ### Responsive Renders from ~390px mobile to 2560px+ ultra-wide; tablet drops the datum rail to a top bar, mobile collapses to a single stacked stream, hides non-essential nav and table columns, makes controls full width, and never overflows horizontally; grids shrink with minmax(0,1fr) + min-width:0. ### Breakpoints - **Mobile**: 390px - **Tablet**: 768px - **Desktop**: 1200px - **Reflow**: 1100px and 960px and 680px ## Guidance ### Do - Orient the page with a left datum rail and per-section amber coordinates; give every reading a location. - Build modules as clipped-notch plates with a cyan top status bar; pad above every title. - Lead with the narrative conclusion in Space Grotesk; set readouts, coordinates, and timestamps in IBM Plex Mono. - Keep cyan as the read, amber for thresholds and active coordinates, red for a real fault; hold accents like highlighters. - Group numbers into telemetry strips with evenly spaced cells and signal-ink status dots. - Rule-connect annotations into the chart or table they explain; let findings live inside the grid. - Explicitly style every form control with a visible cyan focus ring; render the settled state with no JavaScript. ### Don't - Do not default to a white or muddy ground, or flood panels with neon gradients. - Do not use rounded consumer-product cards, in-between radii, or nested cards. - Do not give a plate a lone accent edge; colour rides the top status bar and status dots, not a side edge. - Do not box navigation into a pill or floating rounded card. - Do not spend accent on decoration, hide operational metadata behind minimalism, or use the oversized italic-serif AI-default headline. - Do not use emoji on buttons or symbol glyphs in copy; use inline SVG primitives. ### Accessibility High-contrast light text and signal ink on charcoal, all clearing WCAG AA; status carried by colour AND label/shape; mono readouts stay 14.5px+, body 17px+; visible 2px cyan focus rings with offset; touch targets at least 44px; every form control explicitly styled with no browser defaults; the fully-rendered state is visible with no JavaScript and motion respects prefers-reduced-motion. ## Imagery Direction ### Pairs With datum ### Summary Spacecraft and orbital subjects rendered as mission-control review plates in the Datum technique: the subject crisp and dominant on a deep charcoal field over a faint blueprint grid, dressed with hairline cyan dimension rules and calibration ticks, amber coordinate crosshairs, sparse monospace readouts and status dots in the margins, and clipped corner notches framing the plate. ### Subjects - orbital spacecraft / deep-space orbiter - high-gain dish antenna and solar arrays - launch vehicle stack in section - orbital trajectory / apsis diagram - ground-station antenna - reaction-wheel and thruster assemblies ### Usage One full-bleed landing hero in the Datum technique composed with a calm left third for the overlay; elsewhere keep imagery to plate previews and feature studies with leader-line callouts. End every prompt with NO text, NO letters, NO logos.
---
version: "alpha"
name: "Apsis"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
bg: "#081017"
surface: "#101A24"
surface_2: "#16242F"
recess: "#050B11"
text: "#E7F1F7"
muted: "#8A9BAE"
border: "#233545"
rule: "#1B2A38"
accent: "#9BE7FF"
accent_2: "#F6B756"
on_accent: "#061019"
success: "#79E3A0"
warning: "#F6B756"
error: "#FF6D6D"
info: "#67C6FF"
typography:
headline-lg:
fontFamily: "Space Grotesk"
fontSize: "2.075rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.02em"
headline-md:
fontFamily: "Space Grotesk"
fontSize: "1.66rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.02em"
body-md:
fontFamily: "IBM Plex Sans"
fontSize: "17px"
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: "0px"
md: "16px"
lg: "24px"
full: "9999px"
spacing:
base: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
components:
color-reference-bg:
backgroundColor: "{colors.bg}"
color-reference-surface:
backgroundColor: "{colors.surface}"
color-reference-surface_2:
backgroundColor: "{colors.surface_2}"
color-reference-recess:
backgroundColor: "{colors.recess}"
color-reference-text:
backgroundColor: "{colors.text}"
color-reference-muted:
backgroundColor: "{colors.muted}"
color-reference-border:
backgroundColor: "{colors.border}"
color-reference-rule:
backgroundColor: "{colors.rule}"
color-reference-accent:
backgroundColor: "{colors.accent}"
color-reference-accent_2:
backgroundColor: "{colors.accent_2}"
color-reference-on_accent:
backgroundColor: "{colors.on_accent}"
color-reference-success:
backgroundColor: "{colors.success}"
color-reference-warning:
backgroundColor: "{colors.warning}"
color-reference-error:
backgroundColor: "{colors.error}"
color-reference-info:
backgroundColor: "{colors.info}"
button-primary:
backgroundColor: "{colors.accent}"
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"
---
# Apsis
## Overview
Apsis is a review-board language for operational telemetry. It reads dense flight data like a long-form dossier rather than a consumer app: a narrative headline zone, a central evidence field, and supporting telemetry rails. Every reading carries a coordinate; every finding carries a rule. It privileges calm dark contrast, disciplined annotation, and publication-grade hierarchy over neon spectacle. A faithful refinement of Mission-Control Review — same idea, same charcoal field and signal-ink palette family — brought up to standard in its radius system, accent discipline, button and form systems, and no-JS motion gate.
### Values
- Operational clarity over cinematic clutter
- Editorial hierarchy that turns telemetry into a readable narrative
- Every reading located: a coordinate rail and per-section coordinates orient the page
- Evidence-first annotation, rule-connected to the chart or table it explains
- High-contrast charcoal surfaces with accessibility-aware restraint
- Accent spent only as signal ink — cyan reads, amber marks thresholds, red flags a real fault
### Anti-Values
- Arcade cyberpunk glow without information structure
- White or muddy pastel grounds, gradient washes, neon spectacle
- Soft generic SaaS cards that erase the technical gravity
- Floating helper text divorced from the evidence it explains
- Accent colour spent on decoration rather than a real status
- The oversized italic-serif AI-startup default headline
### Visual Character
- A continuous left datum rail carries coordinate ticks (LAT / REV / LON) down the page, giving every section a fixed location in the flight.
- Every major module is a clipped-notch plate — squared corners with one clipped notch and a 2px cyan top status bar — so containers read like engineered review sheets, never soft consumer cards.
- Section headers pair an amber monospace coordinate overline with the title and a horizontal rule that continues into the grid, turning each panel title into a measured coordinate reference.
- Numeric readouts cluster into telemetry strips with evenly spaced cells, thin separators, and tiny signal-ink status dots for instrument-panel rhythm; Space Grotesk decks carry conclusions while IBM Plex Mono carries readouts.
- Editorial annotations sit inside the grid, rule-connected by a left signal-ink rule to the chart or table they explain — commentary as structure, not floating helper text.
## Colors
Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.
| Token | Value |
|-------|-------|
| bg | `#081017` |
| surface | `#101A24` |
| surface_2 | `#16242F` |
| recess | `#050B11` |
| text | `#E7F1F7` |
| muted | `#8A9BAE` |
| border | `#233545` |
| rule | `#1B2A38` |
| accent | `#9BE7FF` |
| accent_2 | `#F6B756` |
| on_accent | `#061019` |
| success | `#79E3A0` |
| warning | `#F6B756` |
| error | `#FF6D6D` |
| info | `#67C6FF` |
## Typography
- **Headline-Lg**: Space Grotesk, 2.075rem, weight 700, line-height 1.1.
- **Headline-Md**: Space Grotesk, 1.66rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans, 17px, 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
A persistent left datum rail (or sidebar nav on the dashboard) plus a dominant central content stack; content caps and centres around 1320-1480px and only the landing hero spans 100vw.
### Whitespace
Intentional and editorial: tight within telemetry strips and ticks, generous around section transitions and above every title, used to separate evidence clusters from narrative conclusions.
### Density
Light and spacious at the masthead and hero, denser through telemetry strips, ledgers, and command forms, quieter again at the audit footer.
### Responsive
Renders from ~390px mobile to 2560px+ ultra-wide; tablet drops the datum rail to a top bar, mobile collapses to a single stacked stream, hides non-essential nav and table columns, makes controls full width, and never overflows horizontally; grids shrink with minmax(0,1fr) + min-width:0.
### Breakpoints
- **Mobile**: 390px
- **Tablet**: 768px
- **Desktop**: 1200px
- **Reflow**: 1100px and 960px and 680px
## Elevation & Depth
### Shadows
- **Sm**: inset 0 0 0 1px rgba(155,231,255,0.06)
- **Md**: 0 24px 60px rgba(0,0,0,0.42)
- **Lg**: 0 48px 120px rgba(0,0,0,0.55)
## Shapes
### Rounded
- **None**: `0px`
- **Sm**: `0px`
- **Md**: `16px`
- **Lg**: `24px`
- **Full**: `9999px`
### Surfaces
- **Treatment**: flat clipped-notch technical plates over a charcoal field; a 2px cyan status bar across each plate top; no glass, no gradient washes
- **Card Style**: Squared plates with one clipped corner notch (top-right or bottom-left) built with clip-path, a faint vertical surface gradient (#16242F to #101A24), a hairline #233545 border, and a 2px cyan top status bar — engineered review sheets, never rounded consumer cards.
- **Bg Pattern**: faint 64px blueprint grid over a deep charcoal #081017 field
### Borders
- **Default Width**: 1px
- **Accent Width**: 0
- **Style**: solid
- **Character**: Precise aerospace drafting hairlines (#233545) for structure only; colour is carried by signal-ink status dots and the cyan top status bar, never by an accent edge on a card.
## Components
### Composition
Compose screens like review boards: a narrative headline zone, a central evidence field, and supporting telemetry rails, oriented by a left datum rail of coordinate ticks. Let the conclusion stay dominant; rails support the decision thread without competing. Never box navigation into a pill or floating card.
### Hierarchy
Use large Space Grotesk deck titles for story-level conclusions and compact IBM Plex Mono for metric-level readouts, coordinates, and procedural metadata, so operators distinguish narrative from instrument at a glance. Cyan reads; amber marks thresholds and active coordinates; red flags a real fault.
### Density
High density but heavily gridded: telemetry strips and ledgers can be tight as long as labels, separators, status dots, and contrast keep them scannable; every dense cluster has a quieter band or annotation nearby.
### Signature
A left datum coordinate rail; clipped-notch technical plates with a 2px cyan top status bar; section headers of amber mono coordinate overline + title + rule into the grid; telemetry strips of evenly spaced readout cells with signal-ink status dots; and rule-connected editorial annotations inside the grid.
## 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-019ef9d9-e63a-7a40-8f99-2194688f7650/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 Orient the page with a left datum rail and per-section amber coordinates; give every reading a location.
- Do Build modules as clipped-notch plates with a cyan top status bar; pad above every title.
- Do Lead with the narrative conclusion in Space Grotesk; set readouts, coordinates, and timestamps in IBM Plex Mono.
- Do Keep cyan as the read, amber for thresholds and active coordinates, red for a real fault; hold accents like highlighters.
- Do Group numbers into telemetry strips with evenly spaced cells and signal-ink status dots.
- Do Rule-connect annotations into the chart or table they explain; let findings live inside the grid.
- Do Explicitly style every form control with a visible cyan focus ring; render the settled state with no JavaScript.
- Don't Do not default to a white or muddy ground, or flood panels with neon gradients.
- Don't Do not use rounded consumer-product cards, in-between radii, or nested cards.
- Don't Do not give a plate a lone accent edge; colour rides the top status bar and status dots, not a side edge.
- Don't Do not box navigation into a pill or floating rounded card.
- Don't Do not spend accent on decoration, hide operational metadata behind minimalism, or use the oversized italic-serif AI-default headline.
- Don't Do not use emoji on buttons or symbol glyphs in copy; use inline SVG primitives.
### Accessibility
High-contrast light text and signal ink on charcoal, all clearing WCAG AA; status carried by colour AND label/shape; mono readouts stay 14.5px+, body 17px+; visible 2px cyan focus rings with offset; touch targets at least 44px; every form control explicitly styled with no browser defaults; the fully-rendered state is visible with no JavaScript and motion respects prefers-reduced-motion.
## Imagery Direction
### Pairs With
datum
### Summary
Spacecraft and orbital subjects rendered as mission-control review plates in the Datum technique: the subject crisp and dominant on a deep charcoal field over a faint blueprint grid, dressed with hairline cyan dimension rules and calibration ticks, amber coordinate crosshairs, sparse monospace readouts and status dots in the margins, and clipped corner notches framing the plate.
### Subjects
- orbital spacecraft / deep-space orbiter
- high-gain dish antenna and solar arrays
- launch vehicle stack in section
- orbital trajectory / apsis diagram
- ground-station antenna
- reaction-wheel and thruster assemblies
### Usage
One full-bleed landing hero in the Datum technique composed with a calm left third for the overlay; elsewhere keep imagery to plate previews and feature studies with leader-line callouts. End every prompt with NO text, NO letters, NO logos.
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "apsis",
"type": "registry:theme",
"title": "Apsis shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#081017",
"foreground": "#E7F1F7",
"card": "#101A24",
"card-foreground": "#E7F1F7",
"popover": "#101A24",
"popover-foreground": "#E7F1F7",
"primary": "#E7F1F7",
"primary-foreground": "#111111",
"secondary": "#f4f4f5",
"secondary-foreground": "#111111",
"muted": "#8A9BAE",
"muted-foreground": "#E7F1F7",
"accent": "#9BE7FF",
"accent-foreground": "#111111",
"destructive": "#FF6D6D",
"border": "#233545",
"input": "#233545",
"ring": "#9BE7FF",
"chart-1": "#E7F1F7",
"chart-2": "#f4f4f5",
"chart-3": "#9BE7FF",
"chart-4": "#79E3A0",
"chart-5": "#F6B756",
"sidebar": "#101A24",
"sidebar-foreground": "#E7F1F7",
"sidebar-primary": "#E7F1F7",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#67C6FF",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#233545",
"sidebar-ring": "#9BE7FF",
"radius": "16px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#E7F1F7",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#9BE7FF",
"accent-foreground": "#111111",
"destructive": "#FF6D6D",
"border": "#303642",
"input": "#303642",
"ring": "#9BE7FF",
"chart-1": "#E7F1F7",
"chart-2": "#f4f4f5",
"chart-3": "#9BE7FF",
"chart-4": "#79E3A0",
"chart-5": "#F6B756",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#E7F1F7",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#9BE7FF",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#9BE7FF",
"radius": "16px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019ef9d9-e63a-7a40-8f99-2194688f7650",
"slug": "apsis",
"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",
"accent_2",
"bg",
"border",
"error",
"info",
"muted",
"on_accent",
"recess",
"rule",
"success",
"surface",
"surface_2",
"text",
"warning"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"heading_transform",
"heading_weight",
"letter_spacing",
"mono_font"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"spacing": [
"base",
"scale"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"motion": [
"duration",
"easing",
"philosophy"
]
}
}
}
```The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Agent-generated
Keep Apsisand swap a palette and an art style onto it — the landing & dashboard recolor live. The Studio does the same with all three lanes free.
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.
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #081017;
--foreground: #E7F1F7;
--card: #101A24;
--card-foreground: #E7F1F7;
--popover: #101A24;
--popover-foreground: #E7F1F7;
--primary: #E7F1F7;
--primary-foreground: #111111;
--secondary: #f4f4f5;
--secondary-foreground: #111111;
--muted: #8A9BAE;
--muted-foreground: #E7F1F7;
--accent: #9BE7FF;
--accent-foreground: #111111;
--destructive: #FF6D6D;
--border: #233545;
--input: #233545;
--ring: #9BE7FF;
--chart-1: #E7F1F7;
--chart-2: #f4f4f5;
--chart-3: #9BE7FF;
--chart-4: #79E3A0;
--chart-5: #F6B756;
--sidebar: #101A24;
--sidebar-foreground: #E7F1F7;
--sidebar-primary: #E7F1F7;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #67C6FF;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #233545;
--sidebar-ring: #9BE7FF;
--radius: 16px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #E7F1F7;
--primary-foreground: #111111;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #9BE7FF;
--accent-foreground: #111111;
--destructive: #FF6D6D;
--border: #303642;
--input: #303642;
--ring: #9BE7FF;
--chart-1: #E7F1F7;
--chart-2: #f4f4f5;
--chart-3: #9BE7FF;
--chart-4: #79E3A0;
--chart-5: #F6B756;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #E7F1F7;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #9BE7FF;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #9BE7FF;
--radius: 16px;
}
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
Card,
CardContent,
CardDescription,
CardFooter,
CardHeader,
CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";
export function ApsisShadcnKit() {
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">Apsis</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "apsis",
"type": "registry:theme",
"cssVars": {
"theme": {
"font-sans": "IBM Plex Sans, system-ui, sans-serif",
"font-mono": "IBM Plex Mono, ui-monospace, monospace",
"font-display": "Space Grotesk, system-ui, sans-serif",
"radius": "0rem"
},
"dark": {
"background": "#081017",
"foreground": "#E7F1F7",
"card": "#101A24",
"card-foreground": "#E7F1F7",
"popover": "#16242F",
"popover-foreground": "#E7F1F7",
"primary": "#9BE7FF",
"primary-foreground": "#061019",
"secondary": "#16242F",
"secondary-foreground": "#E7F1F7",
"muted": "#101A24",
"muted-foreground": "#8A9BAE",
"accent": "#F6B756",
"accent-foreground": "#061019",
"destructive": "#FF6D6D",
"destructive-foreground": "#061019",
"border": "#233545",
"input": "#050B11",
"ring": "#9BE7FF",
"chart-1": "#9BE7FF",
"chart-2": "#F6B756",
"chart-3": "#79E3A0",
"chart-4": "#67C6FF",
"chart-5": "#FF6D6D",
"sidebar": "#081017",
"sidebar-foreground": "#8A9BAE",
"sidebar-primary": "#9BE7FF",
"sidebar-primary-foreground": "#061019",
"sidebar-accent": "#16242F",
"sidebar-accent-foreground": "#E7F1F7",
"sidebar-border": "#233545",
"sidebar-ring": "#9BE7FF"
}
},
"visualProfile": {
"mode": "dark",
"ground": "#081017",
"material": "flat clipped-notch technical plates on a charcoal blueprint-grid field; a 2px cyan status bar across the top of each plate; never glass, never gradient washes",
"radius": "0 (squared plates; pills and status dots at 9999)",
"border": "1px hairline #233545 drafting lines; colour carried by signal-ink status dots and the cyan top bar, never an accent edge",
"corner": "one clipped notch (top-right or bottom-left) per plate via clip-path",
"accentUsage": "cyan as primary signal ink, amber for coordinates/thresholds, red for a real fault only; accents like highlighters, never fills",
"typography": "Space Grotesk display, IBM Plex Sans body 17px+, IBM Plex Mono for readouts/labels/coordinates",
"elevation": "no decorative shadow; depth from the recessed input wells and the charcoal field",
"motion": "deliberate cubic-bezier(.22,1,.36,1); settled state visible with no JS"
}
}
# Apsis shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019ef9d9-e63a-7a40-8f99-2194688f7650`
Slug: `apsis`
## Intent
Apsis is a review-board language for operational telemetry. It reads dense flight data like a long-form dossier rather than a consumer app: a narrative headline zone, a central evidence field, and supporting telemetry rails. Every reading carries a coordinate; every finding carries a rule. It privileges calm dark contrast, disciplined annotation, and publication-grade hierarchy over neon spectacle. A faithful refinement of Mission-Control Review — same idea, same charcoal field and signal-ink palette family — brought up to standard in its radius system, accent discipline, button and form systems, and no-JS motion gate.
## 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:
{
"bg": "#081017",
"surface": "#101A24",
"surface_2": "#16242F",
"recess": "#050B11",
"text": "#E7F1F7",
"muted": "#8A9BAE",
"border": "#233545",
"rule": "#1B2A38",
"accent": "#9BE7FF",
"accent_2": "#F6B756",
"on_accent": "#061019",
"success": "#79E3A0",
"warning": "#F6B756",
"error": "#FF6D6D",
"info": "#67C6FF"
}
Typography:
{
"base_size": "17px",
"body_font": "IBM Plex Sans",
"heading_font": "Space Grotesk",
"mono_font": "IBM Plex Mono",
"heading_weight": "600",
"heading_transform": "none",
"letter_spacing": "-0.02em",
"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;600;700&display=swap"
}
## Visual character to preserve
- A continuous left datum rail carries coordinate ticks (LAT / REV / LON) down the page, giving every section a fixed location in the flight.
- Every major module is a clipped-notch plate — squared corners with one clipped notch and a 2px cyan top status bar — so containers read like engineered review sheets, never soft consumer cards.
- Section headers pair an amber monospace coordinate overline with the title and a horizontal rule that continues into the grid, turning each panel title into a measured coordinate reference.
- Numeric readouts cluster into telemetry strips with evenly spaced cells, thin separators, and tiny signal-ink status dots for instrument-panel rhythm; Space Grotesk decks carry conclusions while IBM Plex Mono carries readouts.
- Editorial annotations sit inside the grid, rule-connected by a left signal-ink rule to the chart or table they explain — commentary as structure, not floating helper text.
## ShadSync visual profile
{
"family": "editorial",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": true,
"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/apsis/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: Orient the page with a left datum rail and per-section amber coordinates; give every reading a location.; Build modules as clipped-notch plates with a cyan top status bar; pad above every title.; Lead with the narrative conclusion in Space Grotesk; set readouts, coordinates, and timestamps in IBM Plex Mono.; Keep cyan as the read, amber for thresholds and active coordinates, red for a real fault; hold accents like highlighters.; Group numbers into telemetry strips with evenly spaced cells and signal-ink status dots.; Rule-connect annotations into the chart or table they explain; let findings live inside the grid.; Explicitly style every form control with a visible cyan focus ring; render the settled state with no JavaScript.
- Do not: Do not default to a white or muddy ground, or flood panels with neon gradients.; Do not use rounded consumer-product cards, in-between radii, or nested cards.; Do not give a plate a lone accent edge; colour rides the top status bar and status dots, not a side edge.; Do not box navigation into a pill or floating rounded card.; Do not spend accent on decoration, hide operational metadata behind minimalism, or use the oversized italic-serif AI-default headline.; Do not use emoji on buttons or symbol glyphs in copy; use inline SVG primitives.
## 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 ApsisShadcnKit() {
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">Apsis</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": "A persistent left datum rail (or sidebar nav on the dashboard) plus a dominant central content stack; content caps and centres around 1320-1480px and only the landing hero spans 100vw.",
"whitespace": "Intentional and editorial: tight within telemetry strips and ticks, generous around section transitions and above every title, used to separate evidence clusters from narrative conclusions.",
"density": "Light and spacious at the masthead and hero, denser through telemetry strips, ledgers, and command forms, quieter again at the audit footer.",
"responsive": "Renders from ~390px mobile to 2560px+ ultra-wide; tablet drops the datum rail to a top bar, mobile collapses to a single stacked stream, hides non-essential nav and table columns, makes controls full width, and never overflows horizontally; grids shrink with minmax(0,1fr) + min-width:0.",
"breakpoints": {
"mobile": "390px",
"tablet": "768px",
"desktop": "1200px",
"reflow": "1100px and 960px and 680px"
}
}
{
"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-019ef9d9-e63a-7a40-8f99-2194688f7650",
"name": "Apsis",
"slug": "apsis"
},
"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 continuous left datum rail carries coordinate ticks (LAT / REV / LON) down the page, giving every section a fixed location in the flight.",
"Every major module is a clipped-notch plate — squared corners with one clipped notch and a 2px cyan top status bar — so containers read like engineered review sheets, never soft consumer cards.",
"Section headers pair an amber monospace coordinate overline with the title and a horizontal rule that continues into the grid, turning each panel title into a measured coordinate reference.",
"Numeric readouts cluster into telemetry strips with evenly spaced cells, thin separators, and tiny signal-ink status dots for instrument-panel rhythm; Space Grotesk decks carry conclusions while IBM Plex Mono carries readouts.",
"Editorial annotations sit inside the grid, rule-connected by a left signal-ink rule to the chart or table they explain — commentary as structure, not floating helper text."
],
"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": "Apsis 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": [
"Orient the page with a left datum rail and per-section amber coordinates; give every reading a location.",
"Build modules as clipped-notch plates with a cyan top status bar; pad above every title.",
"Lead with the narrative conclusion in Space Grotesk; set readouts, coordinates, and timestamps in IBM Plex Mono.",
"Keep cyan as the read, amber for thresholds and active coordinates, red for a real fault; hold accents like highlighters.",
"Group numbers into telemetry strips with evenly spaced cells and signal-ink status dots.",
"Rule-connect annotations into the chart or table they explain; let findings live inside the grid.",
"Explicitly style every form control with a visible cyan focus ring; render the settled state with no JavaScript."
],
"dont": [
"Do not default to a white or muddy ground, or flood panels with neon gradients.",
"Do not use rounded consumer-product cards, in-between radii, or nested cards.",
"Do not give a plate a lone accent edge; colour rides the top status bar and status dots, not a side edge.",
"Do not box navigation into a pill or floating rounded card.",
"Do not spend accent on decoration, hide operational metadata behind minimalism, or use the oversized italic-serif AI-default headline.",
"Do not use emoji on buttons or symbol glyphs in copy; use inline SVG primitives."
]
}
}