back to gallery
design language·literary-longform-interface

Literary Longform Interface

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 digital editorial language for immersive longform reading that borrows from literary magazines and newspaper feature layouts: restrained chrome, generous margins, serif-forward typography, and clear reading aids that support attention without feeling like product UI.
values
reading comfort over interface noveltyeditorial hierarchy that guides scanning into deep readingquiet utility tools that sit beside the story instead of competing with itscholarly credibility through precise rhythm, notes, and citations
anti-values
×app-like card grids that break narrative flow×bright promotional UI competing with the article body×compressed spacing that makes long passages feel claustrophobic×generic SaaS controls detached from editorial tone
tokens
colors12 items
primary
#1f2933
secondary
#6b5c53
accent
#8b2332
background
#f4efe8
surface
#fbf8f3
text
#1c1917
muted
#6a625b
border
#c9bfb2
error
#b42318
success
#2f6b45
warning
#9a6700
info
#355c7d
typography8 items
heading font
Newsreader
body font
Source Serif 4
mono font
IBM Plex Mono
base size
18px
scale ratio
1.2
line height
1.72
letter spacing
0.01em
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Newsreader:opsz,wght@6..72,400;6..72,600;6..72,700&family=Source+Serif+4:opsz,wght@8..60,400;8..60,500;8..60,600&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 1px 0 rgba(28,25,23,0.04)
md
0 12px 30px rgba(54,42,34,0.08)
lg
0 24px 60px rgba(54,42,34,0.12)
surfaces3 items
treatment
paper
card style
warm off-white panels with faint inset tinting and occasional drop caps or folio rules
bg pattern
lines
borders4 items
default width
1px
accent width
2px
style
solid
character
hairline editorial rules with occasional double-rule dividers for section transitions
motion3 items
duration
180ms
easing
cubic-bezier(0.2,0.8,0.2,1)
philosophy
deliberate
rules
composition
Organize the interface as a reading room: masthead and issue metadata above, a dominant article well in the middle, and secondary context such as notes, reading stats, and related pieces pushed to peripheral rails so the story remains visually sovereign.
hierarchy
The article title and deck establish entry, mono folio labels cue metadata, body paragraphs carry the primary rhythm, and notes or utility panels are deliberately quieter through reduced scale, muted color, and thinner rules.
density

Body content is spacious and breathable, while utility regions can be moderately dense as long as they remain visually lighter than the prose column.

signature patterns
Every major region uses top-and-bottom editorial rules, often doubled with a 3px gap, to create the feeling of magazine folios rather than rounded product cards.Meta labels, timestamps, and tool headings are rendered as uppercase mono captions with increased letter-spacing, contrasting sharply against large old-style serif display text.Pull quotes and side annotations deliberately break the main text measure using negative or offset alignment, with thin border-left or border-right rules to mimic margin commentary.The opening paragraph begins with an oversized drop cap and the reading column maintains a strict max-width around 38 to 42 characters for dense longform legibility.
layout
grid
Use a three-zone editorial grid: left rail for issue context and navigation, centered article column for continuous reading, and right rail for notes, stats, and saved highlights. On smaller viewports collapse rails beneath the article while preserving rule-based sectioning.
breakpoints
Desktop around 1440px shows full three-column reading room; tablet around 768px compresses to article plus stacked utility modules; mobile around 375px becomes a single reading column with sticky top controls and full-width panels.
whitespace

Keep oversized top margins, generous paragraph spacing, and broad outer gutters so the article feels calm and premium instead of crowded.

guidance
do
  • Use serif typography for all longform reading surfaces and reserve mono labeling for metadata and controls.
  • Express structure with rules, spacing, and measure before resorting to filled boxes or heavy shadows.
  • Let annotations, notes, and reading tools feel adjacent to the story, never louder than the prose itself.
avoid
  • Do not turn the page into a generic component gallery or analytics dashboard.
  • Do not use saturated accent colors as large backgrounds behind continuous reading text.
  • Do not widen body copy so far that the reading measure loses literary intimacy.
katagami spec
# Literary Longform Interface

## Philosophy

A digital editorial language for immersive longform reading that borrows from literary magazines and newspaper feature layouts: restrained chrome, generous margins, serif-forward typography, and clear reading aids that support attention without feeling like product UI.

### Values

- reading comfort over interface novelty
- editorial hierarchy that guides scanning into deep reading
- quiet utility tools that sit beside the story instead of competing with it
- scholarly credibility through precise rhythm, notes, and citations

### Anti-Values

- app-like card grids that break narrative flow
- bright promotional UI competing with the article body
- compressed spacing that makes long passages feel claustrophobic
- generic SaaS controls detached from editorial tone

### Visual Character

- A narrow central reading column set inside very wide outer gutters, with a visible but low-contrast vertical rule separating narrative text from annotation and metadata rails.
- Large high-contrast serif headlines paired with compact uppercase mono labels and bylines, using measured tracking and smallcaps-like treatment to echo literary journal decks and folios.
- Paragraphs use generous line-height, pronounced first-paragraph lead-in styling, and pull quotes that bleed beyond the text measure with thin hairline borders rather than heavy cards.
- Section breaks, note markers, and utility panels rely on fine editorial rules, muted paper-toned surfaces, and subtle tint blocks so the interface feels typeset instead of componentized.

## Tokens

### Colors

| Name | Value |
|------|-------|
| primary | `#1f2933` |
| secondary | `#6b5c53` |
| accent | `#8b2332` |
| background | `#f4efe8` |
| surface | `#fbf8f3` |
| text | `#1c1917` |
| muted | `#6a625b` |
| border | `#c9bfb2` |
| error | `#b42318` |
| success | `#2f6b45` |
| warning | `#9a6700` |
| info | `#355c7d` |

### Typography

- **Heading Font**: Newsreader
- **Body Font**: Source Serif 4
- **Mono Font**: IBM Plex Mono
- **Base Size**: 18px
- **Scale Ratio**: 1.2
- **Line Height**: 1.72
- **Letter Spacing**: 0.01em
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Newsreader:opsz,wght@6..72,400;6..72,600;6..72,700&family=Source+Serif+4:opsz,wght@8..60,400;8..60,500;8..60,600&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 1px 0 rgba(28,25,23,0.04)
- **Md**: 0 12px 30px rgba(54,42,34,0.08)
- **Lg**: 0 24px 60px rgba(54,42,34,0.12)

### Surfaces

- **Treatment**: paper
- **Card Style**: warm off-white panels with faint inset tinting and occasional drop caps or folio rules
- **Bg Pattern**: lines

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: hairline editorial rules with occasional double-rule dividers for section transitions

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.2,0.8,0.2,1)
- **Philosophy**: deliberate

## Rules

### Composition

Organize the interface as a reading room: masthead and issue metadata above, a dominant article well in the middle, and secondary context such as notes, reading stats, and related pieces pushed to peripheral rails so the story remains visually sovereign.

### Hierarchy

The article title and deck establish entry, mono folio labels cue metadata, body paragraphs carry the primary rhythm, and notes or utility panels are deliberately quieter through reduced scale, muted color, and thinner rules.

### Density

Body content is spacious and breathable, while utility regions can be moderately dense as long as they remain visually lighter than the prose column.

### Signature Patterns

- Every major region uses top-and-bottom editorial rules, often doubled with a 3px gap, to create the feeling of magazine folios rather than rounded product cards.
- Meta labels, timestamps, and tool headings are rendered as uppercase mono captions with increased letter-spacing, contrasting sharply against large old-style serif display text.
- Pull quotes and side annotations deliberately break the main text measure using negative or offset alignment, with thin border-left or border-right rules to mimic margin commentary.
- The opening paragraph begins with an oversized drop cap and the reading column maintains a strict max-width around 38 to 42 characters for dense longform legibility.

## Layout

### Grid

Use a three-zone editorial grid: left rail for issue context and navigation, centered article column for continuous reading, and right rail for notes, stats, and saved highlights. On smaller viewports collapse rails beneath the article while preserving rule-based sectioning.

### Breakpoints

Desktop around 1440px shows full three-column reading room; tablet around 768px compresses to article plus stacked utility modules; mobile around 375px becomes a single reading column with sticky top controls and full-width panels.

### Whitespace

Keep oversized top margins, generous paragraph spacing, and broad outer gutters so the article feels calm and premium instead of crowded.

## Guidance

### Do

- Use serif typography for all longform reading surfaces and reserve mono labeling for metadata and controls.
- Express structure with rules, spacing, and measure before resorting to filled boxes or heavy shadows.
- Let annotations, notes, and reading tools feel adjacent to the story, never louder than the prose itself.

### Don't

- Do not turn the page into a generic component gallery or analytics dashboard.
- Do not use saturated accent colors as large backgrounds behind continuous reading text.
- Do not widen body copy so far that the reading measure loses literary intimacy.
DESIGN.md
---
version: "alpha"
name: "Literary Longform Interface"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  primary: "#1f2933"
  secondary: "#6b5c53"
  accent: "#8b2332"
  background: "#f4efe8"
  surface: "#fbf8f3"
  text: "#1c1917"
  muted: "#6a625b"
  border: "#c9bfb2"
  error: "#b42318"
  success: "#2f6b45"
  warning: "#9a6700"
  info: "#355c7d"
typography:
  headline-lg:
    fontFamily: "Newsreader"
    fontSize: "1.944rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "0.01em"
  headline-md:
    fontFamily: "Newsreader"
    fontSize: "1.62rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "0.01em"
  body-md:
    fontFamily: "Source Serif 4"
    fontSize: "18px"
    fontWeight: 400
    lineHeight: 1.72
    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: "#ffffff"
    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"
---

# Literary Longform Interface

## Overview

A digital editorial language for immersive longform reading that borrows from literary magazines and newspaper feature layouts: restrained chrome, generous margins, serif-forward typography, and clear reading aids that support attention without feeling like product UI.

### Values

- reading comfort over interface novelty
- editorial hierarchy that guides scanning into deep reading
- quiet utility tools that sit beside the story instead of competing with it
- scholarly credibility through precise rhythm, notes, and citations

### Anti-Values

- app-like card grids that break narrative flow
- bright promotional UI competing with the article body
- compressed spacing that makes long passages feel claustrophobic
- generic SaaS controls detached from editorial tone

### Visual Character

- A narrow central reading column set inside very wide outer gutters, with a visible but low-contrast vertical rule separating narrative text from annotation and metadata rails.
- Large high-contrast serif headlines paired with compact uppercase mono labels and bylines, using measured tracking and smallcaps-like treatment to echo literary journal decks and folios.
- Paragraphs use generous line-height, pronounced first-paragraph lead-in styling, and pull quotes that bleed beyond the text measure with thin hairline borders rather than heavy cards.
- Section breaks, note markers, and utility panels rely on fine editorial rules, muted paper-toned surfaces, and subtle tint blocks so the interface feels typeset instead of componentized.

## 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 | `#1f2933` |
| secondary | `#6b5c53` |
| accent | `#8b2332` |
| background | `#f4efe8` |
| surface | `#fbf8f3` |
| text | `#1c1917` |
| muted | `#6a625b` |
| border | `#c9bfb2` |
| error | `#b42318` |
| success | `#2f6b45` |
| warning | `#9a6700` |
| info | `#355c7d` |

## Typography

- **Headline-Lg**: Newsreader, 1.944rem, weight 700, line-height 1.1.
- **Headline-Md**: Newsreader, 1.62rem, weight 600, line-height 1.15.
- **Body-Md**: Source Serif 4, 18px, weight 400, line-height 1.72.
- **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

Use a three-zone editorial grid: left rail for issue context and navigation, centered article column for continuous reading, and right rail for notes, stats, and saved highlights. On smaller viewports collapse rails beneath the article while preserving rule-based sectioning.

### Breakpoints

Desktop around 1440px shows full three-column reading room; tablet around 768px compresses to article plus stacked utility modules; mobile around 375px becomes a single reading column with sticky top controls and full-width panels.

### Whitespace

Keep oversized top margins, generous paragraph spacing, and broad outer gutters so the article feels calm and premium instead of crowded.

## Elevation & Depth

### Shadows

- **Sm**: 0 1px 0 rgba(28,25,23,0.04)
- **Md**: 0 12px 30px rgba(54,42,34,0.08)
- **Lg**: 0 24px 60px rgba(54,42,34,0.12)

## Shapes

### Rounded

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

### Surfaces

- **Treatment**: paper
- **Card Style**: warm off-white panels with faint inset tinting and occasional drop caps or folio rules
- **Bg Pattern**: lines

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: hairline editorial rules with occasional double-rule dividers for section transitions

## Components

### Composition

Organize the interface as a reading room: masthead and issue metadata above, a dominant article well in the middle, and secondary context such as notes, reading stats, and related pieces pushed to peripheral rails so the story remains visually sovereign.

### Hierarchy

The article title and deck establish entry, mono folio labels cue metadata, body paragraphs carry the primary rhythm, and notes or utility panels are deliberately quieter through reduced scale, muted color, and thinner rules.

### Density

Body content is spacious and breathable, while utility regions can be moderately dense as long as they remain visually lighter than the prose column.

### Signature Patterns

- Every major region uses top-and-bottom editorial rules, often doubled with a 3px gap, to create the feeling of magazine folios rather than rounded product cards.
- Meta labels, timestamps, and tool headings are rendered as uppercase mono captions with increased letter-spacing, contrasting sharply against large old-style serif display text.
- Pull quotes and side annotations deliberately break the main text measure using negative or offset alignment, with thin border-left or border-right rules to mimic margin commentary.
- The opening paragraph begins with an oversized drop cap and the reading column maintains a strict max-width around 38 to 42 characters for dense longform legibility.

## 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-019d9bb8-39bc-7cc3-96d2-c55e0aa1e520/DESIGN.with-shadcn.md`.

The shadcn page also exposes optional machine-readable files for automation, but the human-facing handoff is DESIGN.md with shadcn.

Install recommended primitives with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

Use these primitives in shadcn apps:
- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Implementation rule for agents: import shadcn primitives from `@/components/ui/*`, apply the generated CSS variables first, then compose the language-specific recipes from the companion MD. Katagami remains the source of truth; shadcn names are the implementation surface.

## Do's and Don'ts

- Do Use serif typography for all longform reading surfaces and reserve mono labeling for metadata and controls.
- Do Express structure with rules, spacing, and measure before resorting to filled boxes or heavy shadows.
- Do Let annotations, notes, and reading tools feel adjacent to the story, never louder than the prose itself.
- Don't Do not turn the page into a generic component gallery or analytics dashboard.
- Don't Do not use saturated accent colors as large backgrounds behind continuous reading text.
- Don't Do not widen body copy so far that the reading measure loses literary intimacy.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "literary-longform-interface",
  "type": "registry:theme",
  "title": "Literary Longform Interface shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#f4efe8",
      "foreground": "#1c1917",
      "card": "#fbf8f3",
      "card-foreground": "#1c1917",
      "popover": "#fbf8f3",
      "popover-foreground": "#1c1917",
      "primary": "#1f2933",
      "primary-foreground": "#ffffff",
      "secondary": "#6b5c53",
      "secondary-foreground": "#ffffff",
      "muted": "#6a625b",
      "muted-foreground": "#1c1917",
      "accent": "#8b2332",
      "accent-foreground": "#ffffff",
      "destructive": "#b42318",
      "border": "#c9bfb2",
      "input": "#c9bfb2",
      "ring": "#8b2332",
      "chart-1": "#1f2933",
      "chart-2": "#6b5c53",
      "chart-3": "#8b2332",
      "chart-4": "#2f6b45",
      "chart-5": "#9a6700",
      "sidebar": "#fbf8f3",
      "sidebar-foreground": "#1c1917",
      "sidebar-primary": "#1f2933",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#355c7d",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#c9bfb2",
      "sidebar-ring": "#8b2332",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1f2933",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#8b2332",
      "accent-foreground": "#ffffff",
      "destructive": "#b42318",
      "border": "#303642",
      "input": "#303642",
      "ring": "#8b2332",
      "chart-1": "#1f2933",
      "chart-2": "#6b5c53",
      "chart-3": "#8b2332",
      "chart-4": "#2f6b45",
      "chart-5": "#9a6700",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1f2933",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#8b2332",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#8b2332",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019d9bb8-39bc-7cc3-96d2-c55e0aa1e520",
    "slug": "literary-longform-interface",
    "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 · literary-longform-interface
DESIGN.md

at a glance

Palette

Typography

headline-lgNewsreader · 31px · 700

The quick brown fox jumps

headline-mdNewsreader · 26px · 600

The quick brown fox jumps

body-mdSource Serif 4 · 18px · 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: #f4efe8;
  --foreground: #1c1917;
  --card: #fbf8f3;
  --card-foreground: #1c1917;
  --popover: #fbf8f3;
  --popover-foreground: #1c1917;
  --primary: #1f2933;
  --primary-foreground: #ffffff;
  --secondary: #6b5c53;
  --secondary-foreground: #ffffff;
  --muted: #6a625b;
  --muted-foreground: #1c1917;
  --accent: #8b2332;
  --accent-foreground: #ffffff;
  --destructive: #b42318;
  --border: #c9bfb2;
  --input: #c9bfb2;
  --ring: #8b2332;
  --chart-1: #1f2933;
  --chart-2: #6b5c53;
  --chart-3: #8b2332;
  --chart-4: #2f6b45;
  --chart-5: #9a6700;
  --sidebar: #fbf8f3;
  --sidebar-foreground: #1c1917;
  --sidebar-primary: #1f2933;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #355c7d;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #c9bfb2;
  --sidebar-ring: #8b2332;
  --radius: 12px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #1f2933;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #8b2332;
  --accent-foreground: #ffffff;
  --destructive: #b42318;
  --border: #303642;
  --input: #303642;
  --ring: #8b2332;
  --chart-1: #1f2933;
  --chart-2: #6b5c53;
  --chart-3: #8b2332;
  --chart-4: #2f6b45;
  --chart-5: #9a6700;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #1f2933;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #8b2332;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #8b2332;
  --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 LiteraryLongformInterfaceShadcnKit() {
  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">Literary Longform Interface</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": "literary-longform-interface",
  "type": "registry:theme",
  "title": "Literary Longform Interface shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#f4efe8",
      "foreground": "#1c1917",
      "card": "#fbf8f3",
      "card-foreground": "#1c1917",
      "popover": "#fbf8f3",
      "popover-foreground": "#1c1917",
      "primary": "#1f2933",
      "primary-foreground": "#ffffff",
      "secondary": "#6b5c53",
      "secondary-foreground": "#ffffff",
      "muted": "#6a625b",
      "muted-foreground": "#1c1917",
      "accent": "#8b2332",
      "accent-foreground": "#ffffff",
      "destructive": "#b42318",
      "border": "#c9bfb2",
      "input": "#c9bfb2",
      "ring": "#8b2332",
      "chart-1": "#1f2933",
      "chart-2": "#6b5c53",
      "chart-3": "#8b2332",
      "chart-4": "#2f6b45",
      "chart-5": "#9a6700",
      "sidebar": "#fbf8f3",
      "sidebar-foreground": "#1c1917",
      "sidebar-primary": "#1f2933",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#355c7d",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#c9bfb2",
      "sidebar-ring": "#8b2332",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1f2933",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#8b2332",
      "accent-foreground": "#ffffff",
      "destructive": "#b42318",
      "border": "#303642",
      "input": "#303642",
      "ring": "#8b2332",
      "chart-1": "#1f2933",
      "chart-2": "#6b5c53",
      "chart-3": "#8b2332",
      "chart-4": "#2f6b45",
      "chart-5": "#9a6700",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1f2933",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#8b2332",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#8b2332",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019d9bb8-39bc-7cc3-96d2-c55e0aa1e520",
    "slug": "literary-longform-interface",
    "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
# Literary Longform Interface shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019d9bb8-39bc-7cc3-96d2-c55e0aa1e520`
Slug: `literary-longform-interface`

## Intent

A digital editorial language for immersive longform reading that borrows from literary magazines and newspaper feature layouts: restrained chrome, generous margins, serif-forward typography, and clear reading aids that support attention without feeling like product UI.

## 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": "#1f2933",
  "secondary": "#6b5c53",
  "accent": "#8b2332",
  "background": "#f4efe8",
  "surface": "#fbf8f3",
  "text": "#1c1917",
  "muted": "#6a625b",
  "border": "#c9bfb2",
  "error": "#b42318",
  "success": "#2f6b45",
  "warning": "#9a6700",
  "info": "#355c7d"
}

Typography:

{
  "heading_font": "Newsreader",
  "body_font": "Source Serif 4",
  "mono_font": "IBM Plex Mono",
  "base_size": "18px",
  "scale_ratio": 1.2,
  "line_height": 1.72,
  "letter_spacing": "0.01em",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Newsreader:opsz,wght@6..72,400;6..72,600;6..72,700&family=Source+Serif+4:opsz,wght@8..60,400;8..60,500;8..60,600&display=swap"
}

## Visual character to preserve

- A narrow central reading column set inside very wide outer gutters, with a visible but low-contrast vertical rule separating narrative text from annotation and metadata rails.
- Large high-contrast serif headlines paired with compact uppercase mono labels and bylines, using measured tracking and smallcaps-like treatment to echo literary journal decks and folios.
- Paragraphs use generous line-height, pronounced first-paragraph lead-in styling, and pull quotes that bleed beyond the text measure with thin hairline borders rather than heavy cards.
- Section breaks, note markers, and utility panels rely on fine editorial rules, muted paper-toned surfaces, and subtle tint blocks so the interface feels typeset instead of componentized.

## 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/literary-longform-interface/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use serif typography for all longform reading surfaces and reserve mono labeling for metadata and controls.; Express structure with rules, spacing, and measure before resorting to filled boxes or heavy shadows.; Let annotations, notes, and reading tools feel adjacent to the story, never louder than the prose itself.
- Do not: Do not turn the page into a generic component gallery or analytics dashboard.; Do not use saturated accent colors as large backgrounds behind continuous reading text.; Do not widen body copy so far that the reading measure loses literary intimacy.

## 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 LiteraryLongformInterfaceShadcnKit() {
  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">Literary Longform Interface</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": "Use a three-zone editorial grid: left rail for issue context and navigation, centered article column for continuous reading, and right rail for notes, stats, and saved highlights. On smaller viewports collapse rails beneath the article while preserving rule-based sectioning.",
  "breakpoints": "Desktop around 1440px shows full three-column reading room; tablet around 768px compresses to article plus stacked utility modules; mobile around 375px becomes a single reading column with sticky top controls and full-width panels.",
  "whitespace": "Keep oversized top margins, generous paragraph spacing, and broad outer gutters so the article feels calm and premium instead of crowded."
}
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-019d9bb8-39bc-7cc3-96d2-c55e0aa1e520",
    "name": "Literary Longform Interface",
    "slug": "literary-longform-interface"
  },
  "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 narrow central reading column set inside very wide outer gutters, with a visible but low-contrast vertical rule separating narrative text from annotation and metadata rails.",
    "Large high-contrast serif headlines paired with compact uppercase mono labels and bylines, using measured tracking and smallcaps-like treatment to echo literary journal decks and folios.",
    "Paragraphs use generous line-height, pronounced first-paragraph lead-in styling, and pull quotes that bleed beyond the text measure with thin hairline borders rather than heavy cards.",
    "Section breaks, note markers, and utility panels rely on fine editorial rules, muted paper-toned surfaces, and subtle tint blocks so the interface feels typeset instead of componentized."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": true,
    "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": "Literary Longform Interface launch room",
        "description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
        "primaryAction": "Apply theme",
        "secondaryAction": "Review states",
        "stats": [
          {
            "label": "components",
            "value": "16",
            "tone": "accent"
          },
          {
            "label": "states",
            "value": "ready"
          },
          {
            "label": "density",
            "value": "balanced",
            "tone": "warning"
          }
        ],
        "rows": [
          {
            "label": "Primary flow",
            "value": "mapped",
            "status": "active"
          },
          {
            "label": "Token coverage",
            "value": "semantic",
            "status": "synced"
          },
          {
            "label": "Responsive proof",
            "value": "queued",
            "status": "review"
          }
        ],
        "statuses": [
          "Active",
          "Synced",
          "Draft"
        ]
      }
    },
    {
      "id": "detail-editor",
      "title": "Detail editor",
      "viewport": "tablet",
      "primitives": [
        "button",
        "card",
        "input",
        "textarea",
        "select",
        "checkbox",
        "switch",
        "slider",
        "dialog",
        "sheet"
      ],
      "composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
      "mustShow": [
        "focus ring",
        "error or destructive state",
        "dialog or sheet treatment",
        "written guidance content"
      ],
      "avoid": [
        "unstyled browser controls",
        "floating cards inside cards",
        "missing labels"
      ],
      "scene": {
        "eyebrow": "editing flow",
        "headline": "Language recipe editor",
        "description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
        "primaryAction": "Save recipe",
        "secondaryAction": "Open sheet",
        "fields": [
          {
            "label": "Component family",
            "value": "Narrative cards"
          },
          {
            "label": "State treatment",
            "value": "Visible focus + validation"
          },
          {
            "label": "Motion",
            "value": "Small lift, no opacity-only fade"
          }
        ],
        "statuses": [
          "Focus",
          "Invalid",
          "Confirmed"
        ]
      }
    },
    {
      "id": "data-operations",
      "title": "Data operations",
      "viewport": "mobile",
      "primitives": [
        "button",
        "tabs",
        "badge",
        "dropdown-menu",
        "table",
        "tooltip",
        "separator"
      ],
      "composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
      "mustShow": [
        "responsive reflow",
        "dense row styling",
        "menu affordance",
        "status badge system"
      ],
      "avoid": [
        "desktop-only tables",
        "text overflow",
        "default shadcn spacing without Katagami character"
      ],
      "scene": {
        "eyebrow": "operations",
        "headline": "Compact review queue",
        "description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
        "primaryAction": "Resolve",
        "secondaryAction": "Filter",
        "rows": [
          {
            "label": "Button hierarchy",
            "value": "approved",
            "status": "ok"
          },
          {
            "label": "Table rhythm",
            "value": "needs pass",
            "status": "watch"
          },
          {
            "label": "Empty state",
            "value": "designed",
            "status": "done"
          }
        ],
        "statuses": [
          "Queued",
          "Blocked",
          "Done"
        ]
      }
    }
  ],
  "componentRecipes": [
    {
      "primitive": "button",
      "intent": "Prove action hierarchy, focus, disabled, and destructive states."
    },
    {
      "primitive": "card",
      "intent": "Carry the language surface, border, elevation, and density rules."
    },
    {
      "primitive": "input",
      "intent": "Show labels, focus rings, validation, and spacing rhythm."
    },
    {
      "primitive": "textarea",
      "intent": "Show longer guidance, validation copy, and writing density."
    },
    {
      "primitive": "select",
      "intent": "Show filtering, selection contrast, and menu trigger styling."
    },
    {
      "primitive": "dialog",
      "intent": "Show centered decision states and overlay treatment."
    },
    {
      "primitive": "sheet",
      "intent": "Show contextual side panels and responsive editing."
    },
    {
      "primitive": "tabs",
      "intent": "Show navigational structure and active/inactive contrast."
    },
    {
      "primitive": "badge",
      "intent": "Show compact status vocabulary and semantic colors."
    },
    {
      "primitive": "separator",
      "intent": "Show section rhythm without generic gray dividers."
    },
    {
      "primitive": "checkbox",
      "intent": "Show binary selection with visible focus and checked states."
    },
    {
      "primitive": "switch",
      "intent": "Show settings toggles and on/off contrast."
    },
    {
      "primitive": "slider",
      "intent": "Show numeric adjustment with track/thumb styling."
    },
    {
      "primitive": "tooltip",
      "intent": "Show concise explanation styling above compact controls."
    },
    {
      "primitive": "dropdown-menu",
      "intent": "Show action menus, destructive items, and grouped choices."
    },
    {
      "primitive": "table",
      "intent": "Show dense operational data, separators, row states, and responsive behavior."
    }
  ],
  "qualityRules": {
    "do": [
      "Use serif typography for all longform reading surfaces and reserve mono labeling for metadata and controls.",
      "Express structure with rules, spacing, and measure before resorting to filled boxes or heavy shadows.",
      "Let annotations, notes, and reading tools feel adjacent to the story, never louder than the prose itself."
    ],
    "dont": [
      "Do not turn the page into a generic component gallery or analytics dashboard.",
      "Do not use saturated accent colors as large backgrounds behind continuous reading text.",
      "Do not widen body copy so far that the reading measure loses literary intimacy."
    ]
  }
}
related

More like this