back to gallerydo avoid
design language·retro-futurist-systems-journalism
Retro-Futurist Systems Journalism
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
Retro-Futurist Systems Journalism merges mission-control instrumentation, late-20th-century speculative interface fiction, and rigorous editorial page architecture into a dark, information-forward publishing system. It treats every screen as a spread from a future-facing investigative magazine: annotated, gridded, data-dense, and cinematic, yet disciplined enough that long-form reading, telemetry scanning, and evidence comparison can coexist without chaos.
values
Editorial legibility under data densityWorldbuilding through structured annotationCinematic futurism constrained by publishing disciplineHigh-contrast accessibility in dark environments
anti-values
×Pure neon spectacle without reading hierarchy×Soft consumer SaaS minimalism that erases narrative texture×Chaotic cyberpunk clutter with no rational grid
tokens
colors12 items
primary
#7ce7ff
secondary
#ffb86b
accent
#ff6b8f
background
#070b11
surface
#111923
text
#edf3f7
muted
#8e9aa7
border
#30404f
error
#ff6b6b
success
#79e2a2
warning
#f3c969
info
#69c8ff
typography8 items
- heading font
- Barlow Condensed
- body font
- Cormorant Garamond
- mono font
- Space Mono
- base size
- 16px
- scale ratio
- 1.25
- line height
- 1.55
- letter spacing
- 0.01em
- google fonts url
- https://fonts.googleapis.com/css2?family=Barlow+Condensed:wght@400;500;600;700&family=Cormorant+Garamond:wght@400;500;600;700&family=Space+Mono:wght@400;700&display=swap
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
radii5 items
- none
- 0
- sm
- 6px
- md
- 12px
- lg
- 20px
- full
- 9999px
shadows3 items
- sm
- 0 0 0 1px rgba(124,231,255,0.05), 0 8px 24px rgba(0,0,0,0.28)
- md
- 0 0 0 1px rgba(124,231,255,0.08), 0 16px 40px rgba(0,0,0,0.36)
- lg
- 0 0 0 1px rgba(124,231,255,0.12), 0 24px 72px rgba(0,0,0,0.45)
surfaces3 items
- treatment
- gradient
- card style
- Matte charcoal panels with subtle top-to-bottom tonal gradients, inset seams, fine grid overlays, and occasional radial illumination behind priority telemetry modules.
- bg pattern
- grid
borders4 items
- default width
- 1px
- accent width
- 4px
- style
- solid
- character
- Borders feel like technical drafting rules: mostly thin and cool-toned, interrupted by emphatic vertical accent rails and occasional clipped machine corners.
motion3 items
- duration
- 220ms
- easing
- cubic-bezier(0.22, 1, 0.36, 1)
- philosophy
- deliberate
rules
composition
Compose pages as editorial investigations rather than component inventories: a headline deck, evidence-led hero, telemetry summaries, analytical sidebars, and data modules all aligned to a visible multicolumn publishing grid.
hierarchy
Use condensed uppercase display type for navigation, labels, and numerical framing; reserve the serif face for summaries, notes, and long-form reading so information can scan quickly without losing narrative authority.
density
High density but never crowded: every zone contains multiple informational layers separated by rules, labels, spacing bands, and contrast shifts rather than empty minimalist whitespace.
signature patterns
Every major panel uses a heavy left accent rail paired with thin full-perimeter borders and at least two internal rule dividers, producing a dossier-like stack of indexed information.Section headers combine an overline metadata label in monospace, a condensed uppercase title, and a trailing horizontal rule that extends across the remaining grid column width.Selected cards and hero modules use clipped corner geometry with circular radar or reticle overlays created through pseudo-elements, signaling retro-futurist machinery without overwhelming readability.Tables, stat blocks, and annotation callouts include small uppercase index codes in monospace positioned at corners or margins, making the screen feel archived, cataloged, and editorialized.Interactive controls glow through border, shadow, and background shifts only at focus or hover, keeping the base state restrained and publication-like instead of permanently neon-saturated.
layout
grid
A 12-column desktop editorial grid with persistent gutters, collapsing to 8 columns on tablet and a single-column stack on mobile; key modules span 3, 4, 5, or 8 columns to preserve publication rhythm.
breakpoints
Desktop ≥ 1200px, tablet 768-1199px, mobile < 768px. Horizontal data areas may scroll within framed containers, but primary reading flow must re-stack without page-level overflow.
whitespace
Whitespace appears as calibrated bands between sections and within panels, more like magazine pacing than airy app minimalism; tight internal clusters are balanced by strong outer margins and separators.
guidance
- Use luminous cyan and amber as precise navigational accents against matte dark surfaces.
- Keep editorial reading zones intact with serif body copy and generous line height.
- Reveal the grid through rules, aligned edges, and consistent metadata placement.
- Layer annotations and telemetry so worldbuilding enriches rather than interrupts comprehension.
- Do not flood full surfaces with neon gradients that reduce reading contrast.
- Do not replace the serif reading voice with generic UI sans body copy everywhere.
- Do not use soft cards, playful rounding, or consumer-dashboard emptiness.
- Do not let decorative sci-fi chrome break the underlying editorial order.
katagami spec
# Retro-Futurist Systems Journalism ## Philosophy Retro-Futurist Systems Journalism merges mission-control instrumentation, late-20th-century speculative interface fiction, and rigorous editorial page architecture into a dark, information-forward publishing system. It treats every screen as a spread from a future-facing investigative magazine: annotated, gridded, data-dense, and cinematic, yet disciplined enough that long-form reading, telemetry scanning, and evidence comparison can coexist without chaos. ### Values - Editorial legibility under data density - Worldbuilding through structured annotation - Cinematic futurism constrained by publishing discipline - High-contrast accessibility in dark environments ### Anti-Values - Pure neon spectacle without reading hierarchy - Soft consumer SaaS minimalism that erases narrative texture - Chaotic cyberpunk clutter with no rational grid ### Visual Character - A dark graphite field carries razor-thin cyan grid lines and inset panel seams, making the full composition feel like a printed investigative spread overlaid on a mission-control plotting surface. - Display headlines use a condensed uppercase grotesk with generous tracking while long-form annotation uses a readable serif, creating a deliberate tension between newsroom authority and speculative instrumentation. - Every major module is framed by asymmetrical rule systems: one heavy vertical accent rail, multiple fine horizontal dividers, and corner metadata labels that simulate archival dossier indexing. - Data points, badges, and callouts glow with restrained amber and electric cyan against matte charcoal surfaces, using luminous accents as navigational punctuation rather than immersive full-screen neon wash. - Charts, cards, and article excerpts sit on a strict editorial grid with visible column logic, but selected panels break the rectangle through clipped corners and circular telemetry overlays to signal retro-futurist machinery. ## Tokens ### Colors | Name | Value | |------|-------| | primary | `#7ce7ff` | | secondary | `#ffb86b` | | accent | `#ff6b8f` | | background | `#070b11` | | surface | `#111923` | | text | `#edf3f7` | | muted | `#8e9aa7` | | border | `#30404f` | | error | `#ff6b6b` | | success | `#79e2a2` | | warning | `#f3c969` | | info | `#69c8ff` | ### Typography - **Heading Font**: Barlow Condensed - **Body Font**: Cormorant Garamond - **Mono Font**: Space Mono - **Base Size**: 16px - **Scale Ratio**: 1.25 - **Line Height**: 1.55 - **Letter Spacing**: 0.01em - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Barlow+Condensed:wght@400;500;600;700&family=Cormorant+Garamond:wght@400;500;600;700&family=Space+Mono:wght@400;700&display=swap ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Radii - **None**: 0 - **Sm**: 6px - **Md**: 12px - **Lg**: 20px - **Full**: 9999px ### Shadows - **Sm**: 0 0 0 1px rgba(124,231,255,0.05), 0 8px 24px rgba(0,0,0,0.28) - **Md**: 0 0 0 1px rgba(124,231,255,0.08), 0 16px 40px rgba(0,0,0,0.36) - **Lg**: 0 0 0 1px rgba(124,231,255,0.12), 0 24px 72px rgba(0,0,0,0.45) ### Surfaces - **Treatment**: gradient - **Card Style**: Matte charcoal panels with subtle top-to-bottom tonal gradients, inset seams, fine grid overlays, and occasional radial illumination behind priority telemetry modules. - **Bg Pattern**: grid ### Borders - **Default Width**: 1px - **Accent Width**: 4px - **Style**: solid - **Character**: Borders feel like technical drafting rules: mostly thin and cool-toned, interrupted by emphatic vertical accent rails and occasional clipped machine corners. ### Motion - **Duration**: 220ms - **Easing**: cubic-bezier(0.22, 1, 0.36, 1) - **Philosophy**: deliberate ## Rules ### Composition Compose pages as editorial investigations rather than component inventories: a headline deck, evidence-led hero, telemetry summaries, analytical sidebars, and data modules all aligned to a visible multicolumn publishing grid. ### Hierarchy Use condensed uppercase display type for navigation, labels, and numerical framing; reserve the serif face for summaries, notes, and long-form reading so information can scan quickly without losing narrative authority. ### Density High density but never crowded: every zone contains multiple informational layers separated by rules, labels, spacing bands, and contrast shifts rather than empty minimalist whitespace. ### Signature Patterns - Every major panel uses a heavy left accent rail paired with thin full-perimeter borders and at least two internal rule dividers, producing a dossier-like stack of indexed information. - Section headers combine an overline metadata label in monospace, a condensed uppercase title, and a trailing horizontal rule that extends across the remaining grid column width. - Selected cards and hero modules use clipped corner geometry with circular radar or reticle overlays created through pseudo-elements, signaling retro-futurist machinery without overwhelming readability. - Tables, stat blocks, and annotation callouts include small uppercase index codes in monospace positioned at corners or margins, making the screen feel archived, cataloged, and editorialized. - Interactive controls glow through border, shadow, and background shifts only at focus or hover, keeping the base state restrained and publication-like instead of permanently neon-saturated. ## Layout ### Grid A 12-column desktop editorial grid with persistent gutters, collapsing to 8 columns on tablet and a single-column stack on mobile; key modules span 3, 4, 5, or 8 columns to preserve publication rhythm. ### Breakpoints Desktop ≥ 1200px, tablet 768-1199px, mobile < 768px. Horizontal data areas may scroll within framed containers, but primary reading flow must re-stack without page-level overflow. ### Whitespace Whitespace appears as calibrated bands between sections and within panels, more like magazine pacing than airy app minimalism; tight internal clusters are balanced by strong outer margins and separators. ## Guidance ### Do - Use luminous cyan and amber as precise navigational accents against matte dark surfaces. - Keep editorial reading zones intact with serif body copy and generous line height. - Reveal the grid through rules, aligned edges, and consistent metadata placement. - Layer annotations and telemetry so worldbuilding enriches rather than interrupts comprehension. ### Don't - Do not flood full surfaces with neon gradients that reduce reading contrast. - Do not replace the serif reading voice with generic UI sans body copy everywhere. - Do not use soft cards, playful rounding, or consumer-dashboard emptiness. - Do not let decorative sci-fi chrome break the underlying editorial order.
DESIGN.md
---
version: "alpha"
name: "Retro-Futurist Systems Journalism"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
primary: "#7ce7ff"
secondary: "#ffb86b"
accent: "#ff6b8f"
background: "#070b11"
surface: "#111923"
text: "#edf3f7"
muted: "#8e9aa7"
border: "#30404f"
error: "#ff6b6b"
success: "#79e2a2"
warning: "#f3c969"
info: "#69c8ff"
typography:
headline-lg:
fontFamily: "Barlow Condensed"
fontSize: "1.953rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "0.01em"
headline-md:
fontFamily: "Barlow Condensed"
fontSize: "1.563rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "0.01em"
body-md:
fontFamily: "Cormorant Garamond"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.55
letterSpacing: "0.01em"
label-md:
fontFamily: "Space Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
none: "0px"
sm: "6px"
md: "12px"
lg: "20px"
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"
---
# Retro-Futurist Systems Journalism
## Overview
Retro-Futurist Systems Journalism merges mission-control instrumentation, late-20th-century speculative interface fiction, and rigorous editorial page architecture into a dark, information-forward publishing system. It treats every screen as a spread from a future-facing investigative magazine: annotated, gridded, data-dense, and cinematic, yet disciplined enough that long-form reading, telemetry scanning, and evidence comparison can coexist without chaos.
### Values
- Editorial legibility under data density
- Worldbuilding through structured annotation
- Cinematic futurism constrained by publishing discipline
- High-contrast accessibility in dark environments
### Anti-Values
- Pure neon spectacle without reading hierarchy
- Soft consumer SaaS minimalism that erases narrative texture
- Chaotic cyberpunk clutter with no rational grid
### Visual Character
- A dark graphite field carries razor-thin cyan grid lines and inset panel seams, making the full composition feel like a printed investigative spread overlaid on a mission-control plotting surface.
- Display headlines use a condensed uppercase grotesk with generous tracking while long-form annotation uses a readable serif, creating a deliberate tension between newsroom authority and speculative instrumentation.
- Every major module is framed by asymmetrical rule systems: one heavy vertical accent rail, multiple fine horizontal dividers, and corner metadata labels that simulate archival dossier indexing.
- Data points, badges, and callouts glow with restrained amber and electric cyan against matte charcoal surfaces, using luminous accents as navigational punctuation rather than immersive full-screen neon wash.
- Charts, cards, and article excerpts sit on a strict editorial grid with visible column logic, but selected panels break the rectangle through clipped corners and circular telemetry overlays to signal retro-futurist machinery.
## 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 | `#7ce7ff` |
| secondary | `#ffb86b` |
| accent | `#ff6b8f` |
| background | `#070b11` |
| surface | `#111923` |
| text | `#edf3f7` |
| muted | `#8e9aa7` |
| border | `#30404f` |
| error | `#ff6b6b` |
| success | `#79e2a2` |
| warning | `#f3c969` |
| info | `#69c8ff` |
## Typography
- **Headline-Lg**: Barlow Condensed, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Barlow Condensed, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Cormorant Garamond, 16px, weight 400, line-height 1.55.
- **Label-Md**: Space 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 12-column desktop editorial grid with persistent gutters, collapsing to 8 columns on tablet and a single-column stack on mobile; key modules span 3, 4, 5, or 8 columns to preserve publication rhythm.
### Breakpoints
Desktop ≥ 1200px, tablet 768-1199px, mobile < 768px. Horizontal data areas may scroll within framed containers, but primary reading flow must re-stack without page-level overflow.
### Whitespace
Whitespace appears as calibrated bands between sections and within panels, more like magazine pacing than airy app minimalism; tight internal clusters are balanced by strong outer margins and separators.
## Elevation & Depth
### Shadows
- **Sm**: 0 0 0 1px rgba(124,231,255,0.05), 0 8px 24px rgba(0,0,0,0.28)
- **Md**: 0 0 0 1px rgba(124,231,255,0.08), 0 16px 40px rgba(0,0,0,0.36)
- **Lg**: 0 0 0 1px rgba(124,231,255,0.12), 0 24px 72px rgba(0,0,0,0.45)
## Shapes
### Rounded
- **None**: `0px`
- **Sm**: `6px`
- **Md**: `12px`
- **Lg**: `20px`
- **Full**: `9999px`
### Surfaces
- **Treatment**: gradient
- **Card Style**: Matte charcoal panels with subtle top-to-bottom tonal gradients, inset seams, fine grid overlays, and occasional radial illumination behind priority telemetry modules.
- **Bg Pattern**: grid
### Borders
- **Default Width**: 1px
- **Accent Width**: 4px
- **Style**: solid
- **Character**: Borders feel like technical drafting rules: mostly thin and cool-toned, interrupted by emphatic vertical accent rails and occasional clipped machine corners.
## Components
### Composition
Compose pages as editorial investigations rather than component inventories: a headline deck, evidence-led hero, telemetry summaries, analytical sidebars, and data modules all aligned to a visible multicolumn publishing grid.
### Hierarchy
Use condensed uppercase display type for navigation, labels, and numerical framing; reserve the serif face for summaries, notes, and long-form reading so information can scan quickly without losing narrative authority.
### Density
High density but never crowded: every zone contains multiple informational layers separated by rules, labels, spacing bands, and contrast shifts rather than empty minimalist whitespace.
### Signature Patterns
- Every major panel uses a heavy left accent rail paired with thin full-perimeter borders and at least two internal rule dividers, producing a dossier-like stack of indexed information.
- Section headers combine an overline metadata label in monospace, a condensed uppercase title, and a trailing horizontal rule that extends across the remaining grid column width.
- Selected cards and hero modules use clipped corner geometry with circular radar or reticle overlays created through pseudo-elements, signaling retro-futurist machinery without overwhelming readability.
- Tables, stat blocks, and annotation callouts include small uppercase index codes in monospace positioned at corners or margins, making the screen feel archived, cataloged, and editorialized.
- Interactive controls glow through border, shadow, and background shifts only at focus or hover, keeping the base state restrained and publication-like instead of permanently neon-saturated.
## 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-019d9eb0-4bed-7622-a704-7975213d3095/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 luminous cyan and amber as precise navigational accents against matte dark surfaces.
- Do Keep editorial reading zones intact with serif body copy and generous line height.
- Do Reveal the grid through rules, aligned edges, and consistent metadata placement.
- Do Layer annotations and telemetry so worldbuilding enriches rather than interrupts comprehension.
- Don't Do not flood full surfaces with neon gradients that reduce reading contrast.
- Don't Do not replace the serif reading voice with generic UI sans body copy everywhere.
- Don't Do not use soft cards, playful rounding, or consumer-dashboard emptiness.
- Don't Do not let decorative sci-fi chrome break the underlying editorial order.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "retro-futurist-systems-journalism",
"type": "registry:theme",
"title": "Retro-Futurist Systems Journalism shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#070b11",
"foreground": "#edf3f7",
"card": "#111923",
"card-foreground": "#edf3f7",
"popover": "#111923",
"popover-foreground": "#edf3f7",
"primary": "#7ce7ff",
"primary-foreground": "#111111",
"secondary": "#ffb86b",
"secondary-foreground": "#111111",
"muted": "#8e9aa7",
"muted-foreground": "#edf3f7",
"accent": "#ff6b8f",
"accent-foreground": "#ffffff",
"destructive": "#ff6b6b",
"border": "#30404f",
"input": "#30404f",
"ring": "#ff6b8f",
"chart-1": "#7ce7ff",
"chart-2": "#ffb86b",
"chart-3": "#ff6b8f",
"chart-4": "#79e2a2",
"chart-5": "#f3c969",
"sidebar": "#111923",
"sidebar-foreground": "#edf3f7",
"sidebar-primary": "#7ce7ff",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#69c8ff",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#30404f",
"sidebar-ring": "#ff6b8f",
"radius": "12px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#7ce7ff",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#ff6b8f",
"accent-foreground": "#ffffff",
"destructive": "#ff6b6b",
"border": "#303642",
"input": "#303642",
"ring": "#ff6b8f",
"chart-1": "#7ce7ff",
"chart-2": "#ffb86b",
"chart-3": "#ff6b8f",
"chart-4": "#79e2a2",
"chart-5": "#f3c969",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#7ce7ff",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#ff6b8f",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#ff6b8f",
"radius": "12px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019d9eb0-4bed-7622-a704-7975213d3095",
"slug": "retro-futurist-systems-journalism",
"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 · retro-futurist-systems-journalism
DESIGN.md
at a glance
Typography
headline-lgBarlow Condensed · 31px · 700
The quick brown fox jumps
headline-mdBarlow Condensed · 25px · 600
The quick brown fox jumps
body-mdCormorant Garamond · 16px · 400
The quick brown fox jumps
label-mdSpace 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
lg20px
full9999px
shadcn/ui
implementation kit
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 tabletheme css
:root {
--background: #070b11;
--foreground: #edf3f7;
--card: #111923;
--card-foreground: #edf3f7;
--popover: #111923;
--popover-foreground: #edf3f7;
--primary: #7ce7ff;
--primary-foreground: #111111;
--secondary: #ffb86b;
--secondary-foreground: #111111;
--muted: #8e9aa7;
--muted-foreground: #edf3f7;
--accent: #ff6b8f;
--accent-foreground: #ffffff;
--destructive: #ff6b6b;
--border: #30404f;
--input: #30404f;
--ring: #ff6b8f;
--chart-1: #7ce7ff;
--chart-2: #ffb86b;
--chart-3: #ff6b8f;
--chart-4: #79e2a2;
--chart-5: #f3c969;
--sidebar: #111923;
--sidebar-foreground: #edf3f7;
--sidebar-primary: #7ce7ff;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #69c8ff;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #30404f;
--sidebar-ring: #ff6b8f;
--radius: 12px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #7ce7ff;
--primary-foreground: #111111;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #ff6b8f;
--accent-foreground: #ffffff;
--destructive: #ff6b6b;
--border: #303642;
--input: #303642;
--ring: #ff6b8f;
--chart-1: #7ce7ff;
--chart-2: #ffb86b;
--chart-3: #ff6b8f;
--chart-4: #79e2a2;
--chart-5: #f3c969;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #7ce7ff;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #ff6b8f;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #ff6b8f;
--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 RetroFuturistSystemsJournalismShadcnKit() {
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">Retro-Futurist Systems Journalism</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": "retro-futurist-systems-journalism",
"type": "registry:theme",
"title": "Retro-Futurist Systems Journalism shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#070b11",
"foreground": "#edf3f7",
"card": "#111923",
"card-foreground": "#edf3f7",
"popover": "#111923",
"popover-foreground": "#edf3f7",
"primary": "#7ce7ff",
"primary-foreground": "#111111",
"secondary": "#ffb86b",
"secondary-foreground": "#111111",
"muted": "#8e9aa7",
"muted-foreground": "#edf3f7",
"accent": "#ff6b8f",
"accent-foreground": "#ffffff",
"destructive": "#ff6b6b",
"border": "#30404f",
"input": "#30404f",
"ring": "#ff6b8f",
"chart-1": "#7ce7ff",
"chart-2": "#ffb86b",
"chart-3": "#ff6b8f",
"chart-4": "#79e2a2",
"chart-5": "#f3c969",
"sidebar": "#111923",
"sidebar-foreground": "#edf3f7",
"sidebar-primary": "#7ce7ff",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#69c8ff",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#30404f",
"sidebar-ring": "#ff6b8f",
"radius": "12px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#7ce7ff",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#ff6b8f",
"accent-foreground": "#ffffff",
"destructive": "#ff6b6b",
"border": "#303642",
"input": "#303642",
"ring": "#ff6b8f",
"chart-1": "#7ce7ff",
"chart-2": "#ffb86b",
"chart-3": "#ff6b8f",
"chart-4": "#79e2a2",
"chart-5": "#f3c969",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#7ce7ff",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#ff6b8f",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#ff6b8f",
"radius": "12px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019d9eb0-4bed-7622-a704-7975213d3095",
"slug": "retro-futurist-systems-journalism",
"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
# Retro-Futurist Systems Journalism shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019d9eb0-4bed-7622-a704-7975213d3095`
Slug: `retro-futurist-systems-journalism`
## Intent
Retro-Futurist Systems Journalism merges mission-control instrumentation, late-20th-century speculative interface fiction, and rigorous editorial page architecture into a dark, information-forward publishing system. It treats every screen as a spread from a future-facing investigative magazine: annotated, gridded, data-dense, and cinematic, yet disciplined enough that long-form reading, telemetry scanning, and evidence comparison can coexist without chaos.
## 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": "#7ce7ff",
"secondary": "#ffb86b",
"accent": "#ff6b8f",
"background": "#070b11",
"surface": "#111923",
"text": "#edf3f7",
"muted": "#8e9aa7",
"border": "#30404f",
"error": "#ff6b6b",
"success": "#79e2a2",
"warning": "#f3c969",
"info": "#69c8ff"
}
Typography:
{
"heading_font": "Barlow Condensed",
"body_font": "Cormorant Garamond",
"mono_font": "Space Mono",
"base_size": "16px",
"scale_ratio": 1.25,
"line_height": 1.55,
"letter_spacing": "0.01em",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Barlow+Condensed:wght@400;500;600;700&family=Cormorant+Garamond:wght@400;500;600;700&family=Space+Mono:wght@400;700&display=swap"
}
## Visual character to preserve
- A dark graphite field carries razor-thin cyan grid lines and inset panel seams, making the full composition feel like a printed investigative spread overlaid on a mission-control plotting surface.
- Display headlines use a condensed uppercase grotesk with generous tracking while long-form annotation uses a readable serif, creating a deliberate tension between newsroom authority and speculative instrumentation.
- Every major module is framed by asymmetrical rule systems: one heavy vertical accent rail, multiple fine horizontal dividers, and corner metadata labels that simulate archival dossier indexing.
- Data points, badges, and callouts glow with restrained amber and electric cyan against matte charcoal surfaces, using luminous accents as navigational punctuation rather than immersive full-screen neon wash.
- Charts, cards, and article excerpts sit on a strict editorial grid with visible column logic, but selected panels break the rectangle through clipped corners and circular telemetry overlays to signal retro-futurist machinery.
## ShadSync visual profile
{
"family": "editorial",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": false,
"stickerBadges": true,
"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/retro-futurist-systems-journalism/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 luminous cyan and amber as precise navigational accents against matte dark surfaces.; Keep editorial reading zones intact with serif body copy and generous line height.; Reveal the grid through rules, aligned edges, and consistent metadata placement.; Layer annotations and telemetry so worldbuilding enriches rather than interrupts comprehension.
- Do not: Do not flood full surfaces with neon gradients that reduce reading contrast.; Do not replace the serif reading voice with generic UI sans body copy everywhere.; Do not use soft cards, playful rounding, or consumer-dashboard emptiness.; Do not let decorative sci-fi chrome break the underlying editorial order.
## 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 RetroFuturistSystemsJournalismShadcnKit() {
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">Retro-Futurist Systems Journalism</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 12-column desktop editorial grid with persistent gutters, collapsing to 8 columns on tablet and a single-column stack on mobile; key modules span 3, 4, 5, or 8 columns to preserve publication rhythm.",
"breakpoints": "Desktop ≥ 1200px, tablet 768-1199px, mobile < 768px. Horizontal data areas may scroll within framed containers, but primary reading flow must re-stack without page-level overflow.",
"whitespace": "Whitespace appears as calibrated bands between sections and within panels, more like magazine pacing than airy app minimalism; tight internal clusters are balanced by strong outer margins and separators."
}
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-019d9eb0-4bed-7622-a704-7975213d3095",
"name": "Retro-Futurist Systems Journalism",
"slug": "retro-futurist-systems-journalism"
},
"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 dark graphite field carries razor-thin cyan grid lines and inset panel seams, making the full composition feel like a printed investigative spread overlaid on a mission-control plotting surface.",
"Display headlines use a condensed uppercase grotesk with generous tracking while long-form annotation uses a readable serif, creating a deliberate tension between newsroom authority and speculative instrumentation.",
"Every major module is framed by asymmetrical rule systems: one heavy vertical accent rail, multiple fine horizontal dividers, and corner metadata labels that simulate archival dossier indexing.",
"Data points, badges, and callouts glow with restrained amber and electric cyan against matte charcoal surfaces, using luminous accents as navigational punctuation rather than immersive full-screen neon wash.",
"Charts, cards, and article excerpts sit on a strict editorial grid with visible column logic, but selected panels break the rectangle through clipped corners and circular telemetry overlays to signal retro-futurist machinery."
],
"visualProfile": {
"family": "editorial",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": false,
"stickerBadges": true,
"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": "Retro-Futurist Systems Journalism 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 luminous cyan and amber as precise navigational accents against matte dark surfaces.",
"Keep editorial reading zones intact with serif body copy and generous line height.",
"Reveal the grid through rules, aligned edges, and consistent metadata placement.",
"Layer annotations and telemetry so worldbuilding enriches rather than interrupts comprehension."
],
"dont": [
"Do not flood full surfaces with neon gradients that reduce reading contrast.",
"Do not replace the serif reading voice with generic UI sans body copy everywhere.",
"Do not use soft cards, playful rounding, or consumer-dashboard emptiness.",
"Do not let decorative sci-fi chrome break the underlying editorial order."
]
}
}
related
More like this
Cinematic Data Editorialismshares mission-control · telemetry-panels · cockpit-hudLiterary Future Monographshares mission-control · telemetry-panels · cockpit-hudMission-Control Reviewshares mission-control · telemetry-panels · cockpit-hudNeon Rationalismshares mission-control · telemetry-panels · cockpit-hudSpeculative Publishing Interfacesshares mission-control · telemetry-panels · cockpit-hudOrbital Broadcast Controlshares mission-control