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 a dark editorial spread: an open masthead (never boxed), a dominant lead column, supporting telemetry modules, and horizontally banded sections sharing baselines. Every panel is registered with a corner crosshair and a coordinate string.
Oversized uppercase grotesk titles for narrative framing, compact uppercase mono labels for metadata and coordinate strings, and neon accents only where the eye must jump or a state must change.
High information density is welcome, but every dense area is offset by deliberate gutters, hairline separators, and stable type scales so scanning stays calm.
The reticle: each module carries a cyan corner crosshair (two edges at one corner), a mono coordinate string, magenta registration ticks, and exactly one lime measurement caliper bracketing the figure worth acting on.
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; minmax(0,1fr) columns and min-width:0 children prevent blowout.
Strong perimeter margins, even internal padding, narrow inter-module gutters, and padding above every title so the page reads publication-designed rather than app-template.
Dense but banded — modules separated by hairlines and gutters, never crowded against their containers.
Single column under 768px with non-essential nav links and table columns hidden; only the landing hero spans 100vw; contained content caps and centres on ultra-wide.
reticle
Solid, lit, dimensional subjects on a deep blue-black control-room void, with thin neon signal-lines laid over as a calibrated annotation system: cyan contour traces, magenta registration crosshairs, one lime measurement bracket, and mono telemetry labels.
Hero is full-bleed with the subject filling the frame; neon stays a thin annotation layer over solid form, never a flood. Generated with nano-banana-pro (gemini).
# Phosphor ## Philosophy Phosphor is a speculative interface language with Swiss bones: rigid editorial grids and evidence-forward hierarchy on a deep blue-black control-room field, where neon behaves as an annotation layer rather than a flood. Each module is registered with a corner crosshair, captioned with a mono coordinate string, and dimensioned with a single lime caliper, so dense telemetry stays calm and scannable. Cyan contours walk the eye, magenta ticks lock the grid, and one lime bracket marks the figure worth acting on. ### Values - discipline before spectacle — the grid sets authority before any colour appears - neon as a thin annotation layer over solid dark form, never a flood - dense information made scannable through editorial hierarchy and mono notation - register every panel like an instrument readout ### Anti-Values - glowing wireframe surfaces and full neon floods that erase contrast - chaotic cyberpunk clutter or glitch noise used as decoration - light or pale grounds that break the dark-mode field - single decorative accent edges and boxed-in pill navigation ### Visual Character - A deep blue-black control-room void with a faint 1px cyan coordinate grid, organized by strict Swiss columns and generous perimeter margins so every module reads as typeset. - Each panel carries a cyan corner crosshair (two edges meeting at one corner only) and a tiny uppercase mono coordinate string in its top-right, doing the work of chrome. - One lime measurement caliper per module brackets the single acting figure; magenta registration ticks mark joints and edges. - Large uppercase Space Grotesk headlines pair with IBM Plex Mono telemetry labels and a luminous oscilloscope trace, with glow kept to thin edge highlights. ## Tokens ### Colors | Name | Value | |------|-------| | bg | `#071018` | | surface | `#0D1721` | | surface_2 | `#122231` | | text | `#E8F4FF` | | muted | `#8EA3B5` | | border | `#29465C` | | accent | `#78F0FF` | | accent_2 | `#FF5FD2` | | accent_3 | `#B6FF46` | | on_accent | `#071018` | | success | `#6FF7B3` | | warning | `#FFC857` | | error | `#FF6B7A` | | info | `#72B7FF` | ### Typography - **Base Size**: 17px - **Body Font**: IBM Plex Sans - **Heading Font**: Space Grotesk - **Mono Font**: IBM Plex Mono - **Heading Weight**: 700 - **Heading Transform**: uppercase - **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;700&display=swap ### Radii - **None**: 0 - **Md**: 16px - **Lg**: 24px - **Full**: 9999px ### Shadows - **Ring**: 0 0 0 1px rgba(120,240,255,0.12) - **Primary Glow**: 0 0 0 1px rgba(182,255,70,0.3), 0 0 28px rgba(182,255,70,0.14) - **Lift**: 0 12px 32px rgba(0,0,0,0.35) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Treatment**: gradient - **Card Style**: Dark instrument panels with a subtle linear gradient (#0D1721 to #122231), a 1px housing border, a cyan corner crosshair at top-left + bottom-right, and a mono coordinate string. - **Bg Pattern**: faint 1px cyan coordinate grid on a deep blue-black void ### Borders - **Default Width**: 1px - **Accent Width**: 2px - **Style**: solid - **Character**: Hairline housing borders in #29465C; accents appear only as 2px corner crosshair segments and registration ticks, never a full glowing edge. ### Motion - **Duration**: 180ms - **Easing**: cubic-bezier(0.22,1,0.36,1) - **Philosophy**: snappy and purposeful; settled state renders with no JS, reveal layered on top, respects prefers-reduced-motion ## Rules ### Composition Compose screens like a dark editorial spread: an open masthead (never boxed), a dominant lead column, supporting telemetry modules, and horizontally banded sections sharing baselines. Every panel is registered with a corner crosshair and a coordinate string. ### Hierarchy Oversized uppercase grotesk titles for narrative framing, compact uppercase mono labels for metadata and coordinate strings, and neon accents only where the eye must jump or a state must change. ### Density High information density is welcome, but every dense area is offset by deliberate gutters, hairline separators, and stable type scales so scanning stays calm. ### Signature The reticle: each module carries a cyan corner crosshair (two edges at one corner), a mono coordinate string, magenta registration ticks, and exactly one lime measurement caliper bracketing the figure worth acting on. ## 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; minmax(0,1fr) columns and min-width:0 children prevent blowout. ### Whitespace Strong perimeter margins, even internal padding, narrow inter-module gutters, and padding above every title so the page reads publication-designed rather than app-template. ### Density Dense but banded — modules separated by hairlines and gutters, never crowded against their containers. ### Responsive Single column under 768px with non-essential nav links and table columns hidden; only the landing hero spans 100vw; contained content caps and centres on ultra-wide. ### Breakpoints - **Mobile**: 390 - **Tablet**: 768 - **Desktop**: 1100 - **Ultrawide**: 1480 ## Guidance ### Do - Let the grid and mono coordinate strings carry the speculative mood; reserve neon for crosshairs, contours, underlines, chips, and the single primary button. - Register every panel with the corner crosshair and a coordinate string, and bracket one figure per module with the lime caliper. - Keep glow to thin edge highlights so contrast and Swiss-precise calm survive. ### Don't - Do not flood a surface in neon or turn a card into a glowing wireframe. - Do not give a card a single decorative accent edge, nest cards, or box the nav into a pill bar. - Do not break alignment to look futuristic, and never use a light or pale ground. ### Accessibility Text on the void clears WCAG AA at body size (text ~14.8:1, cyan ~9.4:1, muted ~6.2:1). Lime is reserved for the single acting figure; semantic colours are carried by a tick plus text colour, never a saturated background. Motion respects prefers-reduced-motion and the settled state renders with no JavaScript. ## Imagery Direction ### Pairs With reticle ### Summary Solid, lit, dimensional subjects on a deep blue-black control-room void, with thin neon signal-lines laid over as a calibrated annotation system: cyan contour traces, magenta registration crosshairs, one lime measurement bracket, and mono telemetry labels. ### Subjects - instruments and apparatus - vehicles and machinery - architecture and interiors - civic infrastructure - single hero objects ### Usage Hero is full-bleed with the subject filling the frame; neon stays a thin annotation layer over solid form, never a flood. Generated with nano-banana-pro (gemini).
---
version: "alpha"
name: "Phosphor"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
bg: "#071018"
surface: "#0D1721"
surface_2: "#122231"
text: "#E8F4FF"
muted: "#8EA3B5"
border: "#29465C"
accent: "#78F0FF"
accent_2: "#FF5FD2"
accent_3: "#B6FF46"
on_accent: "#071018"
success: "#6FF7B3"
warning: "#FFC857"
error: "#FF6B7A"
info: "#72B7FF"
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"
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-text:
backgroundColor: "{colors.text}"
color-reference-muted:
backgroundColor: "{colors.muted}"
color-reference-border:
backgroundColor: "{colors.border}"
color-reference-accent:
backgroundColor: "{colors.accent}"
color-reference-accent_2:
backgroundColor: "{colors.accent_2}"
color-reference-accent_3:
backgroundColor: "{colors.accent_3}"
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"
---
# Phosphor
## Overview
Phosphor is a speculative interface language with Swiss bones: rigid editorial grids and evidence-forward hierarchy on a deep blue-black control-room field, where neon behaves as an annotation layer rather than a flood. Each module is registered with a corner crosshair, captioned with a mono coordinate string, and dimensioned with a single lime caliper, so dense telemetry stays calm and scannable. Cyan contours walk the eye, magenta ticks lock the grid, and one lime bracket marks the figure worth acting on.
### Values
- discipline before spectacle — the grid sets authority before any colour appears
- neon as a thin annotation layer over solid dark form, never a flood
- dense information made scannable through editorial hierarchy and mono notation
- register every panel like an instrument readout
### Anti-Values
- glowing wireframe surfaces and full neon floods that erase contrast
- chaotic cyberpunk clutter or glitch noise used as decoration
- light or pale grounds that break the dark-mode field
- single decorative accent edges and boxed-in pill navigation
### Visual Character
- A deep blue-black control-room void with a faint 1px cyan coordinate grid, organized by strict Swiss columns and generous perimeter margins so every module reads as typeset.
- Each panel carries a cyan corner crosshair (two edges meeting at one corner only) and a tiny uppercase mono coordinate string in its top-right, doing the work of chrome.
- One lime measurement caliper per module brackets the single acting figure; magenta registration ticks mark joints and edges.
- Large uppercase Space Grotesk headlines pair with IBM Plex Mono telemetry labels and a luminous oscilloscope trace, with glow kept to thin edge highlights.
## 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 | `#071018` |
| surface | `#0D1721` |
| surface_2 | `#122231` |
| text | `#E8F4FF` |
| muted | `#8EA3B5` |
| border | `#29465C` |
| accent | `#78F0FF` |
| accent_2 | `#FF5FD2` |
| accent_3 | `#B6FF46` |
| on_accent | `#071018` |
| success | `#6FF7B3` |
| warning | `#FFC857` |
| error | `#FF6B7A` |
| info | `#72B7FF` |
## 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 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; minmax(0,1fr) columns and min-width:0 children prevent blowout.
### Whitespace
Strong perimeter margins, even internal padding, narrow inter-module gutters, and padding above every title so the page reads publication-designed rather than app-template.
### Density
Dense but banded — modules separated by hairlines and gutters, never crowded against their containers.
### Responsive
Single column under 768px with non-essential nav links and table columns hidden; only the landing hero spans 100vw; contained content caps and centres on ultra-wide.
### Breakpoints
- **Mobile**: 390
- **Tablet**: 768
- **Desktop**: 1100
- **Ultrawide**: 1480
## Elevation & Depth
### Shadows
- **Ring**: 0 0 0 1px rgba(120,240,255,0.12)
- **Primary Glow**: 0 0 0 1px rgba(182,255,70,0.3), 0 0 28px rgba(182,255,70,0.14)
- **Lift**: 0 12px 32px rgba(0,0,0,0.35)
## Shapes
### Rounded
- **None**: `0px`
- **Md**: `16px`
- **Lg**: `24px`
- **Full**: `9999px`
### Surfaces
- **Treatment**: gradient
- **Card Style**: Dark instrument panels with a subtle linear gradient (#0D1721 to #122231), a 1px housing border, a cyan corner crosshair at top-left + bottom-right, and a mono coordinate string.
- **Bg Pattern**: faint 1px cyan coordinate grid on a deep blue-black void
### Borders
- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Hairline housing borders in #29465C; accents appear only as 2px corner crosshair segments and registration ticks, never a full glowing edge.
## Components
### Composition
Compose screens like a dark editorial spread: an open masthead (never boxed), a dominant lead column, supporting telemetry modules, and horizontally banded sections sharing baselines. Every panel is registered with a corner crosshair and a coordinate string.
### Hierarchy
Oversized uppercase grotesk titles for narrative framing, compact uppercase mono labels for metadata and coordinate strings, and neon accents only where the eye must jump or a state must change.
### Density
High information density is welcome, but every dense area is offset by deliberate gutters, hairline separators, and stable type scales so scanning stays calm.
### Signature
The reticle: each module carries a cyan corner crosshair (two edges at one corner), a mono coordinate string, magenta registration ticks, and exactly one lime measurement caliper bracketing the figure worth acting on.
## 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-019ef9b0-219f-7af0-be35-c6e1632d42f5/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 Let the grid and mono coordinate strings carry the speculative mood; reserve neon for crosshairs, contours, underlines, chips, and the single primary button.
- Do Register every panel with the corner crosshair and a coordinate string, and bracket one figure per module with the lime caliper.
- Do Keep glow to thin edge highlights so contrast and Swiss-precise calm survive.
- Don't Do not flood a surface in neon or turn a card into a glowing wireframe.
- Don't Do not give a card a single decorative accent edge, nest cards, or box the nav into a pill bar.
- Don't Do not break alignment to look futuristic, and never use a light or pale ground.
### Accessibility
Text on the void clears WCAG AA at body size (text ~14.8:1, cyan ~9.4:1, muted ~6.2:1). Lime is reserved for the single acting figure; semantic colours are carried by a tick plus text colour, never a saturated background. Motion respects prefers-reduced-motion and the settled state renders with no JavaScript.
## Imagery Direction
### Pairs With
reticle
### Summary
Solid, lit, dimensional subjects on a deep blue-black control-room void, with thin neon signal-lines laid over as a calibrated annotation system: cyan contour traces, magenta registration crosshairs, one lime measurement bracket, and mono telemetry labels.
### Subjects
- instruments and apparatus
- vehicles and machinery
- architecture and interiors
- civic infrastructure
- single hero objects
### Usage
Hero is full-bleed with the subject filling the frame; neon stays a thin annotation layer over solid form, never a flood. Generated with nano-banana-pro (gemini).
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "phosphor",
"type": "registry:theme",
"title": "Phosphor shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#071018",
"foreground": "#E8F4FF",
"card": "#0D1721",
"card-foreground": "#E8F4FF",
"popover": "#0D1721",
"popover-foreground": "#E8F4FF",
"primary": "#E8F4FF",
"primary-foreground": "#111111",
"secondary": "#f4f4f5",
"secondary-foreground": "#111111",
"muted": "#8EA3B5",
"muted-foreground": "#E8F4FF",
"accent": "#78F0FF",
"accent-foreground": "#111111",
"destructive": "#FF6B7A",
"border": "#29465C",
"input": "#29465C",
"ring": "#78F0FF",
"chart-1": "#E8F4FF",
"chart-2": "#f4f4f5",
"chart-3": "#78F0FF",
"chart-4": "#6FF7B3",
"chart-5": "#FFC857",
"sidebar": "#0D1721",
"sidebar-foreground": "#E8F4FF",
"sidebar-primary": "#E8F4FF",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#72B7FF",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#29465C",
"sidebar-ring": "#78F0FF",
"radius": "16px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#E8F4FF",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#78F0FF",
"accent-foreground": "#111111",
"destructive": "#FF6B7A",
"border": "#303642",
"input": "#303642",
"ring": "#78F0FF",
"chart-1": "#E8F4FF",
"chart-2": "#f4f4f5",
"chart-3": "#78F0FF",
"chart-4": "#6FF7B3",
"chart-5": "#FFC857",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#E8F4FF",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#78F0FF",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#78F0FF",
"radius": "16px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019ef9b0-219f-7af0-be35-c6e1632d42f5",
"slug": "phosphor",
"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",
"accent_3",
"bg",
"border",
"error",
"info",
"muted",
"on_accent",
"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"
],
"shadows": [
"lift",
"primary_glow",
"ring"
],
"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 Phosphorand 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: #071018;
--foreground: #E8F4FF;
--card: #0D1721;
--card-foreground: #E8F4FF;
--popover: #0D1721;
--popover-foreground: #E8F4FF;
--primary: #E8F4FF;
--primary-foreground: #111111;
--secondary: #f4f4f5;
--secondary-foreground: #111111;
--muted: #8EA3B5;
--muted-foreground: #E8F4FF;
--accent: #78F0FF;
--accent-foreground: #111111;
--destructive: #FF6B7A;
--border: #29465C;
--input: #29465C;
--ring: #78F0FF;
--chart-1: #E8F4FF;
--chart-2: #f4f4f5;
--chart-3: #78F0FF;
--chart-4: #6FF7B3;
--chart-5: #FFC857;
--sidebar: #0D1721;
--sidebar-foreground: #E8F4FF;
--sidebar-primary: #E8F4FF;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #72B7FF;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #29465C;
--sidebar-ring: #78F0FF;
--radius: 16px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #E8F4FF;
--primary-foreground: #111111;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #78F0FF;
--accent-foreground: #111111;
--destructive: #FF6B7A;
--border: #303642;
--input: #303642;
--ring: #78F0FF;
--chart-1: #E8F4FF;
--chart-2: #f4f4f5;
--chart-3: #78F0FF;
--chart-4: #6FF7B3;
--chart-5: #FFC857;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #E8F4FF;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #78F0FF;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #78F0FF;
--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 PhosphorShadcnKit() {
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">Phosphor</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": "phosphor",
"type": "registry:theme",
"title": "Phosphor",
"description": "Signal-trace systems — Swiss editorial discipline on a deep blue-black control-room field, with cyan contour, magenta registration, and one lime caliper as the only accents.",
"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"
},
"light": {
"background": "#071018",
"foreground": "#E8F4FF",
"card": "#0D1721",
"card-foreground": "#E8F4FF",
"popover": "#0D1721",
"popover-foreground": "#E8F4FF",
"primary": "#B6FF46",
"primary-foreground": "#071018",
"secondary": "#122231",
"secondary-foreground": "#E8F4FF",
"muted": "#122231",
"muted-foreground": "#8EA3B5",
"accent": "#78F0FF",
"accent-foreground": "#071018",
"destructive": "#FF6B7A",
"destructive-foreground": "#071018",
"border": "#29465C",
"input": "#29465C",
"ring": "#78F0FF",
"chart-1": "#78F0FF",
"chart-2": "#FF5FD2",
"chart-3": "#B6FF46",
"chart-4": "#72B7FF",
"chart-5": "#FFC857",
"radius": "0rem"
},
"dark": {
"background": "#071018",
"foreground": "#E8F4FF",
"card": "#0D1721",
"card-foreground": "#E8F4FF",
"popover": "#0D1721",
"popover-foreground": "#E8F4FF",
"primary": "#B6FF46",
"primary-foreground": "#071018",
"secondary": "#122231",
"secondary-foreground": "#E8F4FF",
"muted": "#122231",
"muted-foreground": "#8EA3B5",
"accent": "#78F0FF",
"accent-foreground": "#071018",
"destructive": "#FF6B7A",
"destructive-foreground": "#071018",
"border": "#29465C",
"input": "#29465C",
"ring": "#78F0FF",
"chart-1": "#78F0FF",
"chart-2": "#FF5FD2",
"chart-3": "#B6FF46",
"chart-4": "#72B7FF",
"chart-5": "#FFC857",
"radius": "0rem"
}
}
}
# Phosphor shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019ef9b0-219f-7af0-be35-c6e1632d42f5`
Slug: `phosphor`
## Intent
Phosphor is a speculative interface language with Swiss bones: rigid editorial grids and evidence-forward hierarchy on a deep blue-black control-room field, where neon behaves as an annotation layer rather than a flood. Each module is registered with a corner crosshair, captioned with a mono coordinate string, and dimensioned with a single lime caliper, so dense telemetry stays calm and scannable. Cyan contours walk the eye, magenta ticks lock the grid, and one lime bracket marks the figure worth acting on.
## 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": "#071018",
"surface": "#0D1721",
"surface_2": "#122231",
"text": "#E8F4FF",
"muted": "#8EA3B5",
"border": "#29465C",
"accent": "#78F0FF",
"accent_2": "#FF5FD2",
"accent_3": "#B6FF46",
"on_accent": "#071018",
"success": "#6FF7B3",
"warning": "#FFC857",
"error": "#FF6B7A",
"info": "#72B7FF"
}
Typography:
{
"base_size": "17px",
"body_font": "IBM Plex Sans",
"heading_font": "Space Grotesk",
"mono_font": "IBM Plex Mono",
"heading_weight": "700",
"heading_transform": "uppercase",
"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;700&display=swap"
}
## Visual character to preserve
- A deep blue-black control-room void with a faint 1px cyan coordinate grid, organized by strict Swiss columns and generous perimeter margins so every module reads as typeset.
- Each panel carries a cyan corner crosshair (two edges meeting at one corner only) and a tiny uppercase mono coordinate string in its top-right, doing the work of chrome.
- One lime measurement caliper per module brackets the single acting figure; magenta registration ticks mark joints and edges.
- Large uppercase Space Grotesk headlines pair with IBM Plex Mono telemetry labels and a luminous oscilloscope trace, with glow kept to thin edge highlights.
## ShadSync visual profile
{
"family": "system",
"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/phosphor/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: Let the grid and mono coordinate strings carry the speculative mood; reserve neon for crosshairs, contours, underlines, chips, and the single primary button.; Register every panel with the corner crosshair and a coordinate string, and bracket one figure per module with the lime caliper.; Keep glow to thin edge highlights so contrast and Swiss-precise calm survive.
- Do not: Do not flood a surface in neon or turn a card into a glowing wireframe.; Do not give a card a single decorative accent edge, nest cards, or box the nav into a pill bar.; Do not break alignment to look futuristic, and never use a light or pale ground.
## 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 PhosphorShadcnKit() {
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">Phosphor</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; minmax(0,1fr) columns and min-width:0 children prevent blowout.",
"whitespace": "Strong perimeter margins, even internal padding, narrow inter-module gutters, and padding above every title so the page reads publication-designed rather than app-template.",
"density": "Dense but banded — modules separated by hairlines and gutters, never crowded against their containers.",
"responsive": "Single column under 768px with non-essential nav links and table columns hidden; only the landing hero spans 100vw; contained content caps and centres on ultra-wide.",
"breakpoints": {
"mobile": "390",
"tablet": "768",
"desktop": "1100",
"ultrawide": "1480"
}
}
{
"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-019ef9b0-219f-7af0-be35-c6e1632d42f5",
"name": "Phosphor",
"slug": "phosphor"
},
"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 deep blue-black control-room void with a faint 1px cyan coordinate grid, organized by strict Swiss columns and generous perimeter margins so every module reads as typeset.",
"Each panel carries a cyan corner crosshair (two edges meeting at one corner only) and a tiny uppercase mono coordinate string in its top-right, doing the work of chrome.",
"One lime measurement caliper per module brackets the single acting figure; magenta registration ticks mark joints and edges.",
"Large uppercase Space Grotesk headlines pair with IBM Plex Mono telemetry labels and a luminous oscilloscope trace, with glow kept to thin edge highlights."
],
"visualProfile": {
"family": "system",
"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": "Phosphor 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": [
"Let the grid and mono coordinate strings carry the speculative mood; reserve neon for crosshairs, contours, underlines, chips, and the single primary button.",
"Register every panel with the corner crosshair and a coordinate string, and bracket one figure per module with the lime caliper.",
"Keep glow to thin edge highlights so contrast and Swiss-precise calm survive."
],
"dont": [
"Do not flood a surface in neon or turn a card into a glowing wireframe.",
"Do not give a card a single decorative accent edge, nest cards, or box the nav into a pill bar.",
"Do not break alignment to look futuristic, and never use a light or pale ground."
]
}
}