Neon Rationalism
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.
specification
philosophy
tokens
colors12 items
typography8 items
- heading font
- Space Grotesk
- body font
- IBM Plex Sans
- mono font
- IBM Plex Mono
- base size
- 16px
- scale ratio
- 1.25
- line height
- 1.5
- letter spacing
- 0.01em
- google fonts url
- https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600;700&family=Space+Grotesk:wght@500;700&display=swap
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
radii5 items
- none
- 0
- sm
- 6px
- md
- 12px
- lg
- 20px
- full
- 9999px
shadows3 items
- sm
- 0 0 0 1px rgba(120,240,255,0.12)
- md
- 0 12px 32px rgba(0,0,0,0.35)
- lg
- 0 24px 72px rgba(4,10,18,0.72)
surfaces3 items
- treatment
- gradient
- card style
- Layered dark panels with subtle linear gradients, inner shadow channels, and restrained radial glow blooms at signal intersections.
- bg pattern
- grid
borders4 items
- default width
- 1px
- accent width
- 2px
- style
- solid
- character
- Borders are technical and exact: hairline outer frames, brighter inset channels, and occasional neon edge segments that imply instrument calibration.
motion3 items
- duration
- 180ms
- easing
- cubic-bezier(0.22,1,0.36,1)
- philosophy
- snappy
rules
Compose screens like a dark editorial spread: a dominant lead story column, supporting telemetry modules, and clearly banded horizontal sections with shared baselines.
Use oversized headings for narrative framing, compact uppercase mono labels for metadata, and bright neon accents only where the eye must jump or a state must change.
High information density is welcome, but every dense area must be offset by deliberate gutters, separators, and stable type scales so scanning remains calm.
layout
A 12-column desktop grid with asymmetric spans for narrative and data modules, collapsing to 8 columns on tablet and a single stacked flow on mobile.
Desktop 1440 and above, tablet around 768, mobile around 375 with stacked panels and full-width controls.
Use strong perimeter margins, even internal padding, and narrow inter-module gutters so the page feels publication-designed rather than app-template generic.
guidance
- Pair rational grid structure with a very limited neon accent system.
- Let mono metadata and rule lines carry the sci-fi mood more than decorative illustration.
- Keep long-form annotations and operational data in the same typographic family so the screen feels editorially unified.
- Do not turn every border and surface into a bright glow box.
- Do not break alignment just to appear futuristic.
- Do not rely on generic glassmorphism or blurred blobs that erase the publication character.
katagami spec
# Neon Rationalism ## Philosophy Neon Rationalism fuses Swiss editorial discipline with speculative interface atmospheres: rigid publication grids, evidence-forward hierarchy, and calm information architecture electrified by thin neon signal lines, telemetry notation, and dark-mode control-room contrast. It avoids chaotic cyberpunk clutter by letting fluorescent accents behave like annotation systems inside a sober, legible publishing frame. ### Values - discipline before spectacle - dense information made scannable through editorial hierarchy - dark interfaces with measured, purposeful signal color - science-fiction atmosphere grounded in real typographic order ### Anti-Values - glitch noise as decoration without meaning - random asymmetry that breaks reading flow - over-saturated neon floods that reduce contrast ### Visual Character - Deep charcoal and blue-black fields are organized by strict Swiss-style columns, with generous outer margins and visible alignment that makes every module feel typeset rather than improvised. - Thin electric cyan and magenta rule lines act as annotation infrastructure around cards, charts, and controls, replacing bulky chrome with precision strokes and measured luminous edges. - Large uppercase grotesk headlines pair with compact mono telemetry labels and restrained serif-free body copy, creating a publication-like hierarchy between editorial narrative and machine data. - Panels use clipped corners, inset border channels, and radial glow hotspots that feel like retro-futurist instrument housings while preserving a rational rectangular grid. ## Tokens ### Colors | Name | Value | |------|-------| | primary | `#78F0FF` | | secondary | `#FF5FD2` | | accent | `#B6FF46` | | background | `#071018` | | surface | `#0D1721` | | text | `#E8F4FF` | | muted | `#8EA3B5` | | border | `#29465C` | | error | `#FF6B7A` | | success | `#6FF7B3` | | warning | `#FFC857` | | info | `#72B7FF` | ### Typography - **Heading Font**: Space Grotesk - **Body Font**: IBM Plex Sans - **Mono Font**: IBM Plex Mono - **Base Size**: 16px - **Scale Ratio**: 1.25 - **Line Height**: 1.5 - **Letter Spacing**: 0.01em - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600;700&family=Space+Grotesk:wght@500;700&display=swap ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Radii - **None**: 0 - **Sm**: 6px - **Md**: 12px - **Lg**: 20px - **Full**: 9999px ### Shadows - **Sm**: 0 0 0 1px rgba(120,240,255,0.12) - **Md**: 0 12px 32px rgba(0,0,0,0.35) - **Lg**: 0 24px 72px rgba(4,10,18,0.72) ### Surfaces - **Treatment**: gradient - **Card Style**: Layered dark panels with subtle linear gradients, inner shadow channels, and restrained radial glow blooms at signal intersections. - **Bg Pattern**: grid ### Borders - **Default Width**: 1px - **Accent Width**: 2px - **Style**: solid - **Character**: Borders are technical and exact: hairline outer frames, brighter inset channels, and occasional neon edge segments that imply instrument calibration. ### Motion - **Duration**: 180ms - **Easing**: cubic-bezier(0.22,1,0.36,1) - **Philosophy**: snappy ## Rules ### Composition Compose screens like a dark editorial spread: a dominant lead story column, supporting telemetry modules, and clearly banded horizontal sections with shared baselines. ### Hierarchy Use oversized headings for narrative framing, compact uppercase mono labels for metadata, and bright neon accents only where the eye must jump or a state must change. ### Density High information density is welcome, but every dense area must be offset by deliberate gutters, separators, and stable type scales so scanning remains calm. ### Signature Patterns - Every major panel uses a double-frame treatment: a muted outer border plus an offset inner rule or corner segment in cyan, creating a calibrated instrument-housing effect. - Section headers combine oversized grotesk titles with small mono coordinate strings and horizontal rule lines that extend into the grid like editorial folios or telemetry baselines. - Cards and dialogs use selective clipped corners or notch details on one or two edges, giving retro-futurist character without abandoning the core rectangular layout. - Status chips, toggles, and chart legends use neon as a thin signal layer on dark surfaces, with glow kept to edge highlights and text underlines rather than full fills. ## Layout ### Grid A 12-column desktop grid with asymmetric spans for narrative and data modules, collapsing to 8 columns on tablet and a single stacked flow on mobile. ### Breakpoints Desktop 1440 and above, tablet around 768, mobile around 375 with stacked panels and full-width controls. ### Whitespace Use strong perimeter margins, even internal padding, and narrow inter-module gutters so the page feels publication-designed rather than app-template generic. ## Guidance ### Do - Pair rational grid structure with a very limited neon accent system. - Let mono metadata and rule lines carry the sci-fi mood more than decorative illustration. - Keep long-form annotations and operational data in the same typographic family so the screen feels editorially unified. ### Don't - Do not turn every border and surface into a bright glow box. - Do not break alignment just to appear futuristic. - Do not rely on generic glassmorphism or blurred blobs that erase the publication character.
DESIGN.md
---
version: "alpha"
name: "Neon Rationalism"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
primary: "#78F0FF"
secondary: "#FF5FD2"
accent: "#B6FF46"
background: "#071018"
surface: "#0D1721"
text: "#E8F4FF"
muted: "#8EA3B5"
border: "#29465C"
error: "#FF6B7A"
success: "#6FF7B3"
warning: "#FFC857"
info: "#72B7FF"
typography:
headline-lg:
fontFamily: "Space Grotesk"
fontSize: "1.953rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "0.01em"
headline-md:
fontFamily: "Space Grotesk"
fontSize: "1.563rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "0.01em"
body-md:
fontFamily: "IBM Plex Sans"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.5
letterSpacing: "0.01em"
label-md:
fontFamily: "IBM Plex Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
none: "0px"
sm: "6px"
md: "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"
---
# Neon Rationalism
## Overview
Neon Rationalism fuses Swiss editorial discipline with speculative interface atmospheres: rigid publication grids, evidence-forward hierarchy, and calm information architecture electrified by thin neon signal lines, telemetry notation, and dark-mode control-room contrast. It avoids chaotic cyberpunk clutter by letting fluorescent accents behave like annotation systems inside a sober, legible publishing frame.
### Values
- discipline before spectacle
- dense information made scannable through editorial hierarchy
- dark interfaces with measured, purposeful signal color
- science-fiction atmosphere grounded in real typographic order
### Anti-Values
- glitch noise as decoration without meaning
- random asymmetry that breaks reading flow
- over-saturated neon floods that reduce contrast
### Visual Character
- Deep charcoal and blue-black fields are organized by strict Swiss-style columns, with generous outer margins and visible alignment that makes every module feel typeset rather than improvised.
- Thin electric cyan and magenta rule lines act as annotation infrastructure around cards, charts, and controls, replacing bulky chrome with precision strokes and measured luminous edges.
- Large uppercase grotesk headlines pair with compact mono telemetry labels and restrained serif-free body copy, creating a publication-like hierarchy between editorial narrative and machine data.
- Panels use clipped corners, inset border channels, and radial glow hotspots that feel like retro-futurist instrument housings while preserving a rational rectangular grid.
## 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 | `#78F0FF` |
| secondary | `#FF5FD2` |
| accent | `#B6FF46` |
| background | `#071018` |
| surface | `#0D1721` |
| text | `#E8F4FF` |
| muted | `#8EA3B5` |
| border | `#29465C` |
| error | `#FF6B7A` |
| success | `#6FF7B3` |
| warning | `#FFC857` |
| info | `#72B7FF` |
## Typography
- **Headline-Lg**: Space Grotesk, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Space Grotesk, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans, 16px, weight 400, line-height 1.5.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
### Grid
A 12-column desktop grid with asymmetric spans for narrative and data modules, collapsing to 8 columns on tablet and a single stacked flow on mobile.
### Breakpoints
Desktop 1440 and above, tablet around 768, mobile around 375 with stacked panels and full-width controls.
### Whitespace
Use strong perimeter margins, even internal padding, and narrow inter-module gutters so the page feels publication-designed rather than app-template generic.
## Elevation & Depth
### Shadows
- **Sm**: 0 0 0 1px rgba(120,240,255,0.12)
- **Md**: 0 12px 32px rgba(0,0,0,0.35)
- **Lg**: 0 24px 72px rgba(4,10,18,0.72)
## Shapes
### Rounded
- **None**: `0px`
- **Sm**: `6px`
- **Md**: `12px`
- **Lg**: `20px`
- **Full**: `9999px`
### Surfaces
- **Treatment**: gradient
- **Card Style**: Layered dark panels with subtle linear gradients, inner shadow channels, and restrained radial glow blooms at signal intersections.
- **Bg Pattern**: grid
### Borders
- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Borders are technical and exact: hairline outer frames, brighter inset channels, and occasional neon edge segments that imply instrument calibration.
## Components
### Composition
Compose screens like a dark editorial spread: a dominant lead story column, supporting telemetry modules, and clearly banded horizontal sections with shared baselines.
### Hierarchy
Use oversized headings for narrative framing, compact uppercase mono labels for metadata, and bright neon accents only where the eye must jump or a state must change.
### Density
High information density is welcome, but every dense area must be offset by deliberate gutters, separators, and stable type scales so scanning remains calm.
### Signature Patterns
- Every major panel uses a double-frame treatment: a muted outer border plus an offset inner rule or corner segment in cyan, creating a calibrated instrument-housing effect.
- Section headers combine oversized grotesk titles with small mono coordinate strings and horizontal rule lines that extend into the grid like editorial folios or telemetry baselines.
- Cards and dialogs use selective clipped corners or notch details on one or two edges, giving retro-futurist character without abandoning the core rectangular layout.
- Status chips, toggles, and chart legends use neon as a thin signal layer on dark surfaces, with glow kept to edge highlights and text underlines rather than full fills.
## 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-019d9eb1-9b51-7773-b68c-9adf5f72c8d0/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 Pair rational grid structure with a very limited neon accent system.
- Do Let mono metadata and rule lines carry the sci-fi mood more than decorative illustration.
- Do Keep long-form annotations and operational data in the same typographic family so the screen feels editorially unified.
- Don't Do not turn every border and surface into a bright glow box.
- Don't Do not break alignment just to appear futuristic.
- Don't Do not rely on generic glassmorphism or blurred blobs that erase the publication character.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "neon-rationalism",
"type": "registry:theme",
"title": "Neon Rationalism shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#071018",
"foreground": "#E8F4FF",
"card": "#0D1721",
"card-foreground": "#E8F4FF",
"popover": "#0D1721",
"popover-foreground": "#E8F4FF",
"primary": "#78F0FF",
"primary-foreground": "#111111",
"secondary": "#FF5FD2",
"secondary-foreground": "#ffffff",
"muted": "#8EA3B5",
"muted-foreground": "#E8F4FF",
"accent": "#B6FF46",
"accent-foreground": "#111111",
"destructive": "#FF6B7A",
"border": "#29465C",
"input": "#29465C",
"ring": "#B6FF46",
"chart-1": "#78F0FF",
"chart-2": "#FF5FD2",
"chart-3": "#B6FF46",
"chart-4": "#6FF7B3",
"chart-5": "#FFC857",
"sidebar": "#0D1721",
"sidebar-foreground": "#E8F4FF",
"sidebar-primary": "#78F0FF",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#72B7FF",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#29465C",
"sidebar-ring": "#B6FF46",
"radius": "12px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#78F0FF",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#B6FF46",
"accent-foreground": "#111111",
"destructive": "#FF6B7A",
"border": "#303642",
"input": "#303642",
"ring": "#B6FF46",
"chart-1": "#78F0FF",
"chart-2": "#FF5FD2",
"chart-3": "#B6FF46",
"chart-4": "#6FF7B3",
"chart-5": "#FFC857",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#78F0FF",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#B6FF46",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#B6FF46",
"radius": "12px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019d9eb1-9b51-7773-b68c-9adf5f72c8d0",
"slug": "neon-rationalism",
"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"
]
}
}
}
```embodiments
at a glance
Typography
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Components
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
implementation kit
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
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #071018;
--foreground: #E8F4FF;
--card: #0D1721;
--card-foreground: #E8F4FF;
--popover: #0D1721;
--popover-foreground: #E8F4FF;
--primary: #78F0FF;
--primary-foreground: #111111;
--secondary: #FF5FD2;
--secondary-foreground: #ffffff;
--muted: #8EA3B5;
--muted-foreground: #E8F4FF;
--accent: #B6FF46;
--accent-foreground: #111111;
--destructive: #FF6B7A;
--border: #29465C;
--input: #29465C;
--ring: #B6FF46;
--chart-1: #78F0FF;
--chart-2: #FF5FD2;
--chart-3: #B6FF46;
--chart-4: #6FF7B3;
--chart-5: #FFC857;
--sidebar: #0D1721;
--sidebar-foreground: #E8F4FF;
--sidebar-primary: #78F0FF;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #72B7FF;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #29465C;
--sidebar-ring: #B6FF46;
--radius: 12px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #78F0FF;
--primary-foreground: #111111;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #B6FF46;
--accent-foreground: #111111;
--destructive: #FF6B7A;
--border: #303642;
--input: #303642;
--ring: #B6FF46;
--chart-1: #78F0FF;
--chart-2: #FF5FD2;
--chart-3: #B6FF46;
--chart-4: #6FF7B3;
--chart-5: #FFC857;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #78F0FF;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #B6FF46;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #B6FF46;
--radius: 12px;
}
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 NeonRationalismShadcnKit() {
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">Neon Rationalism</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": "neon-rationalism",
"type": "registry:theme",
"title": "Neon Rationalism shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#071018",
"foreground": "#E8F4FF",
"card": "#0D1721",
"card-foreground": "#E8F4FF",
"popover": "#0D1721",
"popover-foreground": "#E8F4FF",
"primary": "#78F0FF",
"primary-foreground": "#111111",
"secondary": "#FF5FD2",
"secondary-foreground": "#ffffff",
"muted": "#8EA3B5",
"muted-foreground": "#E8F4FF",
"accent": "#B6FF46",
"accent-foreground": "#111111",
"destructive": "#FF6B7A",
"border": "#29465C",
"input": "#29465C",
"ring": "#B6FF46",
"chart-1": "#78F0FF",
"chart-2": "#FF5FD2",
"chart-3": "#B6FF46",
"chart-4": "#6FF7B3",
"chart-5": "#FFC857",
"sidebar": "#0D1721",
"sidebar-foreground": "#E8F4FF",
"sidebar-primary": "#78F0FF",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#72B7FF",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#29465C",
"sidebar-ring": "#B6FF46",
"radius": "12px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#78F0FF",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#B6FF46",
"accent-foreground": "#111111",
"destructive": "#FF6B7A",
"border": "#303642",
"input": "#303642",
"ring": "#B6FF46",
"chart-1": "#78F0FF",
"chart-2": "#FF5FD2",
"chart-3": "#B6FF46",
"chart-4": "#6FF7B3",
"chart-5": "#FFC857",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#78F0FF",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#B6FF46",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#B6FF46",
"radius": "12px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019d9eb1-9b51-7773-b68c-9adf5f72c8d0",
"slug": "neon-rationalism",
"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"
]
}
}
}
# Neon Rationalism shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019d9eb1-9b51-7773-b68c-9adf5f72c8d0`
Slug: `neon-rationalism`
## Intent
Neon Rationalism fuses Swiss editorial discipline with speculative interface atmospheres: rigid publication grids, evidence-forward hierarchy, and calm information architecture electrified by thin neon signal lines, telemetry notation, and dark-mode control-room contrast. It avoids chaotic cyberpunk clutter by letting fluorescent accents behave like annotation systems inside a sober, legible publishing frame.
## 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": "#78F0FF",
"secondary": "#FF5FD2",
"accent": "#B6FF46",
"background": "#071018",
"surface": "#0D1721",
"text": "#E8F4FF",
"muted": "#8EA3B5",
"border": "#29465C",
"error": "#FF6B7A",
"success": "#6FF7B3",
"warning": "#FFC857",
"info": "#72B7FF"
}
Typography:
{
"heading_font": "Space Grotesk",
"body_font": "IBM Plex Sans",
"mono_font": "IBM Plex Mono",
"base_size": "16px",
"scale_ratio": 1.25,
"line_height": 1.5,
"letter_spacing": "0.01em",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600;700&family=Space+Grotesk:wght@500;700&display=swap"
}
## Visual character to preserve
- Deep charcoal and blue-black fields are organized by strict Swiss-style columns, with generous outer margins and visible alignment that makes every module feel typeset rather than improvised.
- Thin electric cyan and magenta rule lines act as annotation infrastructure around cards, charts, and controls, replacing bulky chrome with precision strokes and measured luminous edges.
- Large uppercase grotesk headlines pair with compact mono telemetry labels and restrained serif-free body copy, creating a publication-like hierarchy between editorial narrative and machine data.
- Panels use clipped corners, inset border channels, and radial glow hotspots that feel like retro-futurist instrument housings while preserving a rational rectangular grid.
## ShadSync visual profile
{
"family": "editorial",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": false,
"stickerBadges": false,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
}
## Signature component recipes
### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.
### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.
### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.
### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.
### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.
## Preview shots
- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.
## Implementation contract
- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/neon-rationalism/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: Pair rational grid structure with a very limited neon accent system.; Let mono metadata and rule lines carry the sci-fi mood more than decorative illustration.; Keep long-form annotations and operational data in the same typographic family so the screen feels editorially unified.
- Do not: Do not turn every border and surface into a bright glow box.; Do not break alignment just to appear futuristic.; Do not rely on generic glassmorphism or blurred blobs that erase the publication character.
## 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 NeonRationalismShadcnKit() {
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">Neon Rationalism</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 grid with asymmetric spans for narrative and data modules, collapsing to 8 columns on tablet and a single stacked flow on mobile.",
"breakpoints": "Desktop 1440 and above, tablet around 768, mobile around 375 with stacked panels and full-width controls.",
"whitespace": "Use strong perimeter margins, even internal padding, and narrow inter-module gutters so the page feels publication-designed rather than app-template generic."
}
{
"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-019d9eb1-9b51-7773-b68c-9adf5f72c8d0",
"name": "Neon Rationalism",
"slug": "neon-rationalism"
},
"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": [
"Deep charcoal and blue-black fields are organized by strict Swiss-style columns, with generous outer margins and visible alignment that makes every module feel typeset rather than improvised.",
"Thin electric cyan and magenta rule lines act as annotation infrastructure around cards, charts, and controls, replacing bulky chrome with precision strokes and measured luminous edges.",
"Large uppercase grotesk headlines pair with compact mono telemetry labels and restrained serif-free body copy, creating a publication-like hierarchy between editorial narrative and machine data.",
"Panels use clipped corners, inset border channels, and radial glow hotspots that feel like retro-futurist instrument housings while preserving a rational rectangular grid."
],
"visualProfile": {
"family": "editorial",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": false,
"stickerBadges": false,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "Neon Rationalism 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": [
"Pair rational grid structure with a very limited neon accent system.",
"Let mono metadata and rule lines carry the sci-fi mood more than decorative illustration.",
"Keep long-form annotations and operational data in the same typographic family so the screen feels editorially unified."
],
"dont": [
"Do not turn every border and surface into a bright glow box.",
"Do not break alignment just to appear futuristic.",
"Do not rely on generic glassmorphism or blurred blobs that erase the publication character."
]
}
}