back to gallery
design language·speculative-publishing-interfaces

Speculative Publishing Interfaces

A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.

Download DESIGN.md

Portable DESIGN.md source of truth for most agents and apps.

the spec

specification

philosophy
summary
A dark-mode design language that treats speculative interfaces as if they were prestige editorial artifacts: telemetry, annotations, and reports are arranged with Swiss grid discipline, literary pacing, and cinematic restraint rather than chaotic neon excess.
values
Rational composition before spectacleLong-form readability inside dense technical scenesSpeculative atmosphere carried by typography, labeling, and calibrated light
anti-values
×Arcade-style clutter without hierarchy×Generic SaaS cards with a sci-fi palette pasted on top
tokens
colors12 items
primary
#9FE9FF
secondary
#A6A0FF
accent
#FFB86C
background
#070B12
surface
#111824
text
#EAF2FF
muted
#93A0B8
border
#2A3A4E
error
#FF6E7A
success
#6EE7B7
warning
#FFC857
info
#68D5FF
typography8 items
heading font
Cormorant Garamond
body font
Space Grotesk
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=Cormorant+Garamond:wght@500;600;700&family=IBM+Plex+Mono:wght@400;500;600&family=Space+Grotesk:wght@400;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(159,233,255,0.04), 0 8px 24px rgba(0,0,0,0.18)
md
0 0 0 1px rgba(159,233,255,0.06), 0 18px 44px rgba(0,0,0,0.28)
lg
0 0 0 1px rgba(159,233,255,0.08), 0 30px 80px rgba(0,0,0,0.42)
surfaces3 items
treatment
gradient
card style
Panels use layered charcoal gradients with faint inner glows and translucent top highlights so each block feels like illuminated archival paper behind glass.
bg pattern
grid
borders4 items
default width
1px
accent width
2px
style
solid
character
Borders are quiet technical rules: cool, thin, and precise, with occasional brighter section spines that mimic editorial keylines and instrument traces.
motion3 items
duration
220ms
easing
cubic-bezier(0.22,1,0.36,1)
philosophy
deliberate
rules
composition
Compose every screen as a publication spread where one dominant narrative column is supported by narrow metadata rails, captions, and telemetry sidebars instead of isolated app cards.
hierarchy
Use oversized literary headlines, disciplined section labels, and compact mono data strings so readers can scan from story headline to evidence panels to fine-grain readings without losing place.
density
High information density is allowed, but spacing must separate narrative blocks from technical blocks and preserve calm through consistent baselines and repeated rule spacing.
signature patterns
Every major panel begins with a full-width metadata strap containing an uppercase monospace label, sequence number, and timestamp divided by thin luminous rules.Section bodies use asymmetric editorial columns where a wide reading area is paired with a narrow annotation or statistics rail separated by a persistent vertical keyline.Charts, cards, and image frames use inset top glows plus faint radial cyan illumination behind headings so the darkness feels backlit like a museum display rather than flat black UI.Primary actions and active states are indicated by double-line outlines or underlines, echoing publication keylines instead of conventional rounded app buttons.
layout
grid
A twelve-column desktop grid with outer gutters and recurring side rails; major compositions typically span 7/3/2 or 8/4 column groupings before collapsing to stacked sections.
breakpoints
Desktop 1440px uses 12 columns, tablet 768px reduces to 6 columns with stacked side rails, mobile 375px becomes a single reading column with full-width controls and horizontally scrollable data tables where needed.
whitespace
Whitespace works like editorial pacing: generous between major spreads, tighter inside telemetry groups, and always reinforced by keylines rather than empty emptiness.
guidance
do
  • Pair expressive serif headlines with neutral grotesk body text and mono labels.
  • Use marginal notes, captions, and metadata straps to make dense UI feel curated.
  • Keep accent light localized to headings, signals, and active controls so reading comfort stays high in dark mode.
avoid
  • Flood the interface with saturated neon on every element.
  • Break the grid with randomly sized floating cards.
  • Use generic dashboard widgets without narrative framing or annotation.
katagami spec
# Speculative Publishing Interfaces

## Philosophy

A dark-mode design language that treats speculative interfaces as if they were prestige editorial artifacts: telemetry, annotations, and reports are arranged with Swiss grid discipline, literary pacing, and cinematic restraint rather than chaotic neon excess.

### Values

- Rational composition before spectacle
- Long-form readability inside dense technical scenes
- Speculative atmosphere carried by typography, labeling, and calibrated light

### Anti-Values

- Arcade-style clutter without hierarchy
- Generic SaaS cards with a sci-fi palette pasted on top

### Visual Character

- A rigid multi-column publication grid with oversized outer margins, hairline dividers, and sharply aligned baselines organizes dashboards, reports, and side annotations into one continuous reading surface.
- Large condensed serif or display headlines sit against disciplined grotesk body text and monospaced telemetry, creating a literary front-page hierarchy where data feels edited rather than merely dumped.
- Dark charcoal surfaces are interrupted by cool cyan and amber signal accents, luminous rule lines, and radial glows that stay trapped inside panels so the interface feels atmospheric but never neon-chaotic.
- Every major module reads like a dossier spread: stamped metadata bars, marginal notes, numbered sections, and caption rails make operational UI feel like a curated science-fiction publication.

## Tokens

### Colors

| Name | Value |
|------|-------|
| primary | `#9FE9FF` |
| secondary | `#A6A0FF` |
| accent | `#FFB86C` |
| background | `#070B12` |
| surface | `#111824` |
| text | `#EAF2FF` |
| muted | `#93A0B8` |
| border | `#2A3A4E` |
| error | `#FF6E7A` |
| success | `#6EE7B7` |
| warning | `#FFC857` |
| info | `#68D5FF` |

### Typography

- **Heading Font**: Cormorant Garamond
- **Body Font**: Space Grotesk
- **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=Cormorant+Garamond:wght@500;600;700&family=IBM+Plex+Mono:wght@400;500;600&family=Space+Grotesk:wght@400;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(159,233,255,0.04), 0 8px 24px rgba(0,0,0,0.18)
- **Md**: 0 0 0 1px rgba(159,233,255,0.06), 0 18px 44px rgba(0,0,0,0.28)
- **Lg**: 0 0 0 1px rgba(159,233,255,0.08), 0 30px 80px rgba(0,0,0,0.42)

### Surfaces

- **Treatment**: gradient
- **Card Style**: Panels use layered charcoal gradients with faint inner glows and translucent top highlights so each block feels like illuminated archival paper behind glass.
- **Bg Pattern**: grid

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Borders are quiet technical rules: cool, thin, and precise, with occasional brighter section spines that mimic editorial keylines and instrument traces.

### Motion

- **Duration**: 220ms
- **Easing**: cubic-bezier(0.22,1,0.36,1)
- **Philosophy**: deliberate

## Rules

### Composition

Compose every screen as a publication spread where one dominant narrative column is supported by narrow metadata rails, captions, and telemetry sidebars instead of isolated app cards.

### Hierarchy

Use oversized literary headlines, disciplined section labels, and compact mono data strings so readers can scan from story headline to evidence panels to fine-grain readings without losing place.

### Density

High information density is allowed, but spacing must separate narrative blocks from technical blocks and preserve calm through consistent baselines and repeated rule spacing.

### Signature Patterns

- Every major panel begins with a full-width metadata strap containing an uppercase monospace label, sequence number, and timestamp divided by thin luminous rules.
- Section bodies use asymmetric editorial columns where a wide reading area is paired with a narrow annotation or statistics rail separated by a persistent vertical keyline.
- Charts, cards, and image frames use inset top glows plus faint radial cyan illumination behind headings so the darkness feels backlit like a museum display rather than flat black UI.
- Primary actions and active states are indicated by double-line outlines or underlines, echoing publication keylines instead of conventional rounded app buttons.

## Layout

### Grid

A twelve-column desktop grid with outer gutters and recurring side rails; major compositions typically span 7/3/2 or 8/4 column groupings before collapsing to stacked sections.

### Breakpoints

Desktop 1440px uses 12 columns, tablet 768px reduces to 6 columns with stacked side rails, mobile 375px becomes a single reading column with full-width controls and horizontally scrollable data tables where needed.

### Whitespace

Whitespace works like editorial pacing: generous between major spreads, tighter inside telemetry groups, and always reinforced by keylines rather than empty emptiness.

## Guidance

### Do

- Pair expressive serif headlines with neutral grotesk body text and mono labels.
- Use marginal notes, captions, and metadata straps to make dense UI feel curated.
- Keep accent light localized to headings, signals, and active controls so reading comfort stays high in dark mode.

### Don't

- Flood the interface with saturated neon on every element.
- Break the grid with randomly sized floating cards.
- Use generic dashboard widgets without narrative framing or annotation.
DESIGN.md
---
version: "alpha"
name: "Speculative Publishing Interfaces"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  primary: "#9FE9FF"
  secondary: "#A6A0FF"
  accent: "#FFB86C"
  background: "#070B12"
  surface: "#111824"
  text: "#EAF2FF"
  muted: "#93A0B8"
  border: "#2A3A4E"
  error: "#FF6E7A"
  success: "#6EE7B7"
  warning: "#FFC857"
  info: "#68D5FF"
typography:
  headline-lg:
    fontFamily: "Cormorant Garamond"
    fontSize: "1.953rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "0.01em"
  headline-md:
    fontFamily: "Cormorant Garamond"
    fontSize: "1.563rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "0.01em"
  body-md:
    fontFamily: "Space Grotesk"
    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"
---

# Speculative Publishing Interfaces

## Overview

A dark-mode design language that treats speculative interfaces as if they were prestige editorial artifacts: telemetry, annotations, and reports are arranged with Swiss grid discipline, literary pacing, and cinematic restraint rather than chaotic neon excess.

### Values

- Rational composition before spectacle
- Long-form readability inside dense technical scenes
- Speculative atmosphere carried by typography, labeling, and calibrated light

### Anti-Values

- Arcade-style clutter without hierarchy
- Generic SaaS cards with a sci-fi palette pasted on top

### Visual Character

- A rigid multi-column publication grid with oversized outer margins, hairline dividers, and sharply aligned baselines organizes dashboards, reports, and side annotations into one continuous reading surface.
- Large condensed serif or display headlines sit against disciplined grotesk body text and monospaced telemetry, creating a literary front-page hierarchy where data feels edited rather than merely dumped.
- Dark charcoal surfaces are interrupted by cool cyan and amber signal accents, luminous rule lines, and radial glows that stay trapped inside panels so the interface feels atmospheric but never neon-chaotic.
- Every major module reads like a dossier spread: stamped metadata bars, marginal notes, numbered sections, and caption rails make operational UI feel like a curated science-fiction publication.

## 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 | `#9FE9FF` |
| secondary | `#A6A0FF` |
| accent | `#FFB86C` |
| background | `#070B12` |
| surface | `#111824` |
| text | `#EAF2FF` |
| muted | `#93A0B8` |
| border | `#2A3A4E` |
| error | `#FF6E7A` |
| success | `#6EE7B7` |
| warning | `#FFC857` |
| info | `#68D5FF` |

## Typography

- **Headline-Lg**: Cormorant Garamond, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Cormorant Garamond, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Space Grotesk, 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 twelve-column desktop grid with outer gutters and recurring side rails; major compositions typically span 7/3/2 or 8/4 column groupings before collapsing to stacked sections.

### Breakpoints

Desktop 1440px uses 12 columns, tablet 768px reduces to 6 columns with stacked side rails, mobile 375px becomes a single reading column with full-width controls and horizontally scrollable data tables where needed.

### Whitespace

Whitespace works like editorial pacing: generous between major spreads, tighter inside telemetry groups, and always reinforced by keylines rather than empty emptiness.

## Elevation & Depth

### Shadows

- **Sm**: 0 0 0 1px rgba(159,233,255,0.04), 0 8px 24px rgba(0,0,0,0.18)
- **Md**: 0 0 0 1px rgba(159,233,255,0.06), 0 18px 44px rgba(0,0,0,0.28)
- **Lg**: 0 0 0 1px rgba(159,233,255,0.08), 0 30px 80px rgba(0,0,0,0.42)

## Shapes

### Rounded

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

### Surfaces

- **Treatment**: gradient
- **Card Style**: Panels use layered charcoal gradients with faint inner glows and translucent top highlights so each block feels like illuminated archival paper behind glass.
- **Bg Pattern**: grid

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Borders are quiet technical rules: cool, thin, and precise, with occasional brighter section spines that mimic editorial keylines and instrument traces.

## Components

### Composition

Compose every screen as a publication spread where one dominant narrative column is supported by narrow metadata rails, captions, and telemetry sidebars instead of isolated app cards.

### Hierarchy

Use oversized literary headlines, disciplined section labels, and compact mono data strings so readers can scan from story headline to evidence panels to fine-grain readings without losing place.

### Density

High information density is allowed, but spacing must separate narrative blocks from technical blocks and preserve calm through consistent baselines and repeated rule spacing.

### Signature Patterns

- Every major panel begins with a full-width metadata strap containing an uppercase monospace label, sequence number, and timestamp divided by thin luminous rules.
- Section bodies use asymmetric editorial columns where a wide reading area is paired with a narrow annotation or statistics rail separated by a persistent vertical keyline.
- Charts, cards, and image frames use inset top glows plus faint radial cyan illumination behind headings so the darkness feels backlit like a museum display rather than flat black UI.
- Primary actions and active states are indicated by double-line outlines or underlines, echoing publication keylines instead of conventional rounded app buttons.

## 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-019d9eb2-6ae5-7f41-8e95-82262faf9f0e/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 expressive serif headlines with neutral grotesk body text and mono labels.
- Do Use marginal notes, captions, and metadata straps to make dense UI feel curated.
- Do Keep accent light localized to headings, signals, and active controls so reading comfort stays high in dark mode.
- Don't Flood the interface with saturated neon on every element.
- Don't Break the grid with randomly sized floating cards.
- Don't Use generic dashboard widgets without narrative framing or annotation.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "speculative-publishing-interfaces",
  "type": "registry:theme",
  "title": "Speculative Publishing Interfaces shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#070B12",
      "foreground": "#EAF2FF",
      "card": "#111824",
      "card-foreground": "#EAF2FF",
      "popover": "#111824",
      "popover-foreground": "#EAF2FF",
      "primary": "#9FE9FF",
      "primary-foreground": "#111111",
      "secondary": "#A6A0FF",
      "secondary-foreground": "#ffffff",
      "muted": "#93A0B8",
      "muted-foreground": "#EAF2FF",
      "accent": "#FFB86C",
      "accent-foreground": "#111111",
      "destructive": "#FF6E7A",
      "border": "#2A3A4E",
      "input": "#2A3A4E",
      "ring": "#FFB86C",
      "chart-1": "#9FE9FF",
      "chart-2": "#A6A0FF",
      "chart-3": "#FFB86C",
      "chart-4": "#6EE7B7",
      "chart-5": "#FFC857",
      "sidebar": "#111824",
      "sidebar-foreground": "#EAF2FF",
      "sidebar-primary": "#9FE9FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#68D5FF",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#2A3A4E",
      "sidebar-ring": "#FFB86C",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#9FE9FF",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#FFB86C",
      "accent-foreground": "#111111",
      "destructive": "#FF6E7A",
      "border": "#303642",
      "input": "#303642",
      "ring": "#FFB86C",
      "chart-1": "#9FE9FF",
      "chart-2": "#A6A0FF",
      "chart-3": "#FFB86C",
      "chart-4": "#6EE7B7",
      "chart-5": "#FFC857",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#9FE9FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#FFB86C",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#FFB86C",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019d9eb2-6ae5-7f41-8e95-82262faf9f0e",
    "slug": "speculative-publishing-interfaces",
    "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 · speculative-publishing-interfaces
DESIGN.md

at a glance

Palette

Typography

headline-lgCormorant Garamond · 31px · 700

The quick brown fox jumps

headline-mdCormorant Garamond · 25px · 600

The quick brown fox jumps

body-mdSpace Grotesk · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

Components rendered with this language’s tokens — colors, type, and rounded corners as specified.

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl48px
  • 4xl64px

Shape

none0px
sm6px
md12px
lg20px
full9999px
shadcn/ui

implementation kit

needs agent-authored kitcompatibility fallback
shadcn compatibility only
The generated theme variables are available, but the polished shadcn component recipes and shots have not been authored by the Katagami agent yet.
fallbackprimitives render
Compatibility proof
Local shadcn-style primitives accept the generated theme variables.
primaryaccentsurfacemutedwarningerror
table rhythm
buttonok
cardok
inputok
recommendedcompatibility fallback

DESIGN.md with shadcn

Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.

advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #070B12;
  --foreground: #EAF2FF;
  --card: #111824;
  --card-foreground: #EAF2FF;
  --popover: #111824;
  --popover-foreground: #EAF2FF;
  --primary: #9FE9FF;
  --primary-foreground: #111111;
  --secondary: #A6A0FF;
  --secondary-foreground: #ffffff;
  --muted: #93A0B8;
  --muted-foreground: #EAF2FF;
  --accent: #FFB86C;
  --accent-foreground: #111111;
  --destructive: #FF6E7A;
  --border: #2A3A4E;
  --input: #2A3A4E;
  --ring: #FFB86C;
  --chart-1: #9FE9FF;
  --chart-2: #A6A0FF;
  --chart-3: #FFB86C;
  --chart-4: #6EE7B7;
  --chart-5: #FFC857;
  --sidebar: #111824;
  --sidebar-foreground: #EAF2FF;
  --sidebar-primary: #9FE9FF;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #68D5FF;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #2A3A4E;
  --sidebar-ring: #FFB86C;
  --radius: 12px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #9FE9FF;
  --primary-foreground: #111111;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #FFB86C;
  --accent-foreground: #111111;
  --destructive: #FF6E7A;
  --border: #303642;
  --input: #303642;
  --ring: #FFB86C;
  --chart-1: #9FE9FF;
  --chart-2: #A6A0FF;
  --chart-3: #FFB86C;
  --chart-4: #6EE7B7;
  --chart-5: #FFC857;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #9FE9FF;
  --sidebar-primary-foreground: #111111;
  --sidebar-accent: #FFB86C;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #FFB86C;
  --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 SpeculativePublishingInterfacesShadcnKit() {
  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">Speculative Publishing Interfaces</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": "speculative-publishing-interfaces",
  "type": "registry:theme",
  "title": "Speculative Publishing Interfaces shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#070B12",
      "foreground": "#EAF2FF",
      "card": "#111824",
      "card-foreground": "#EAF2FF",
      "popover": "#111824",
      "popover-foreground": "#EAF2FF",
      "primary": "#9FE9FF",
      "primary-foreground": "#111111",
      "secondary": "#A6A0FF",
      "secondary-foreground": "#ffffff",
      "muted": "#93A0B8",
      "muted-foreground": "#EAF2FF",
      "accent": "#FFB86C",
      "accent-foreground": "#111111",
      "destructive": "#FF6E7A",
      "border": "#2A3A4E",
      "input": "#2A3A4E",
      "ring": "#FFB86C",
      "chart-1": "#9FE9FF",
      "chart-2": "#A6A0FF",
      "chart-3": "#FFB86C",
      "chart-4": "#6EE7B7",
      "chart-5": "#FFC857",
      "sidebar": "#111824",
      "sidebar-foreground": "#EAF2FF",
      "sidebar-primary": "#9FE9FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#68D5FF",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#2A3A4E",
      "sidebar-ring": "#FFB86C",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#9FE9FF",
      "primary-foreground": "#111111",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#FFB86C",
      "accent-foreground": "#111111",
      "destructive": "#FF6E7A",
      "border": "#303642",
      "input": "#303642",
      "ring": "#FFB86C",
      "chart-1": "#9FE9FF",
      "chart-2": "#A6A0FF",
      "chart-3": "#FFB86C",
      "chart-4": "#6EE7B7",
      "chart-5": "#FFC857",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#9FE9FF",
      "sidebar-primary-foreground": "#111111",
      "sidebar-accent": "#FFB86C",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#FFB86C",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019d9eb2-6ae5-7f41-8e95-82262faf9f0e",
    "slug": "speculative-publishing-interfaces",
    "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
# Speculative Publishing Interfaces shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019d9eb2-6ae5-7f41-8e95-82262faf9f0e`
Slug: `speculative-publishing-interfaces`

## Intent

A dark-mode design language that treats speculative interfaces as if they were prestige editorial artifacts: telemetry, annotations, and reports are arranged with Swiss grid discipline, literary pacing, and cinematic restraint rather than chaotic neon excess.

## 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": "#9FE9FF",
  "secondary": "#A6A0FF",
  "accent": "#FFB86C",
  "background": "#070B12",
  "surface": "#111824",
  "text": "#EAF2FF",
  "muted": "#93A0B8",
  "border": "#2A3A4E",
  "error": "#FF6E7A",
  "success": "#6EE7B7",
  "warning": "#FFC857",
  "info": "#68D5FF"
}

Typography:

{
  "heading_font": "Cormorant Garamond",
  "body_font": "Space Grotesk",
  "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=Cormorant+Garamond:wght@500;600;700&family=IBM+Plex+Mono:wght@400;500;600&family=Space+Grotesk:wght@400;500;700&display=swap"
}

## Visual character to preserve

- A rigid multi-column publication grid with oversized outer margins, hairline dividers, and sharply aligned baselines organizes dashboards, reports, and side annotations into one continuous reading surface.
- Large condensed serif or display headlines sit against disciplined grotesk body text and monospaced telemetry, creating a literary front-page hierarchy where data feels edited rather than merely dumped.
- Dark charcoal surfaces are interrupted by cool cyan and amber signal accents, luminous rule lines, and radial glows that stay trapped inside panels so the interface feels atmospheric but never neon-chaotic.
- Every major module reads like a dossier spread: stamped metadata bars, marginal notes, numbered sections, and caption rails make operational UI feel like a curated science-fiction publication.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "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/speculative-publishing-interfaces/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 expressive serif headlines with neutral grotesk body text and mono labels.; Use marginal notes, captions, and metadata straps to make dense UI feel curated.; Keep accent light localized to headings, signals, and active controls so reading comfort stays high in dark mode.
- Do not: Flood the interface with saturated neon on every element.; Break the grid with randomly sized floating cards.; Use generic dashboard widgets without narrative framing or annotation.

## 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 SpeculativePublishingInterfacesShadcnKit() {
  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">Speculative Publishing Interfaces</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 twelve-column desktop grid with outer gutters and recurring side rails; major compositions typically span 7/3/2 or 8/4 column groupings before collapsing to stacked sections.",
  "breakpoints": "Desktop 1440px uses 12 columns, tablet 768px reduces to 6 columns with stacked side rails, mobile 375px becomes a single reading column with full-width controls and horizontally scrollable data tables where needed.",
  "whitespace": "Whitespace works like editorial pacing: generous between major spreads, tighter inside telemetry groups, and always reinforced by keylines rather than empty emptiness."
}
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-019d9eb2-6ae5-7f41-8e95-82262faf9f0e",
    "name": "Speculative Publishing Interfaces",
    "slug": "speculative-publishing-interfaces"
  },
  "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 rigid multi-column publication grid with oversized outer margins, hairline dividers, and sharply aligned baselines organizes dashboards, reports, and side annotations into one continuous reading surface.",
    "Large condensed serif or display headlines sit against disciplined grotesk body text and monospaced telemetry, creating a literary front-page hierarchy where data feels edited rather than merely dumped.",
    "Dark charcoal surfaces are interrupted by cool cyan and amber signal accents, luminous rule lines, and radial glows that stay trapped inside panels so the interface feels atmospheric but never neon-chaotic.",
    "Every major module reads like a dossier spread: stamped metadata bars, marginal notes, numbered sections, and caption rails make operational UI feel like a curated science-fiction publication."
  ],
  "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": "Speculative Publishing Interfaces 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 expressive serif headlines with neutral grotesk body text and mono labels.",
      "Use marginal notes, captions, and metadata straps to make dense UI feel curated.",
      "Keep accent light localized to headings, signals, and active controls so reading comfort stays high in dark mode."
    ],
    "dont": [
      "Flood the interface with saturated neon on every element.",
      "Break the grid with randomly sized floating cards.",
      "Use generic dashboard widgets without narrative framing or annotation."
    ]
  }
}
related

More like this