back to gallery
design language·ledgerline-paper-shell

Ledgerline Paper Shell

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
Ledgerline Paper Shell is a restrained application language for editorial operations products that need the calm of a printed production ledger and the speed of modern SaaS. It uses warm paper, exacting dark typography, quiet rules, modular panels, and a single fresh chartreuse accent to make selected navigation, live work, and critical metrics unmistakable without turning the interface into a colorful dashboard.
values
Paper-like neutrality as the default surface so content and state carry the product instead of decoration.Typographic authority through condensed editorial headings, readable sans body copy, and ledger-like mono metadata.One bright accent used only for selection, live indicators, active controls, and the primary performance number.System rigor with semantic tokens, predictable focus states, high contrast, and reusable panel anatomy.Editorial asymmetry: one oversized working panel and smaller supporting modules rather than equal dashboard cards.Quiet craft details such as hairline dividers, folio labels, corner tabs, and measured spacing changes.
anti-values
×Synthetic SaaS gradients, rainbow charts, or multiple brand accents competing for attention.×Three equal cards in a row, generic analytics tiles, and decorative illustrations that do not support workflow.×Low-contrast gray text, vague borders, or states indicated by color alone.×Over-rounded bubbly components; the language should feel precise, not toy-like.
tokens
borders4 items
accent width
4px
character
Near-invisible dark hairlines for structure; chartreuse accent bars only for active or live states.
default width
1px
style
solid
colors12 items
accent
#B7DC35
background
#F6F1E8
border
#181612
error
#B44B3F
info
#3F6593
muted
#746C60
primary
#191715
secondary
#5F584E
success
#567A35
surface
#FFFCF4
text
#191715
warning
#A36D1D
motion3 items
duration
180ms
easing
cubic-bezier(.2,.7,.2,1)
philosophy
Small translate and border-color changes confirm interaction; avoid bouncy motion and continuous animation except subtle live pulse.
radii5 items
full
9999px
lg
24px
md
24px
none
0
sm
16px
shadows3 items
lg
0 30px 80px rgba(47,39,27,0.12)
md
0 12px 28px rgba(47,39,27,0.08)
sm
0 1px 0 rgba(25,23,21,0.05)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64, 96
surfaces3 items
bg pattern
A barely visible repeating-linear-gradient at 90deg simulates paper grain while preserving text contrast.
card style
Ledger panels are #FFFCF4 with rgba(24,22,18,.08) borders, 24px radius, folio labels, and a fine inset rule.
treatment
Warm paper grounds with subtle linear paper fibers and no decorative gradients beyond low-opacity texture.
typography9 items
base size
16px
body font
Source Sans 3
display letter spacing
-0.04em
google fonts url
https://fonts.googleapis.com/css2?family=Azeret+Mono:wght@500;650&family=Fraunces:opsz,wght,SOFT,WONK@9..144,650..800,20,0&family=Source+Sans+3:wght@400;520;650;750&display=swap
heading font
Fraunces
letter spacing
-0.02em
line height
1.55
mono font
Azeret Mono
scale ratio
1.25
rules
composition
Use a true app shell: narrow left rail, top context strip, dominant editorial work panel, and a smaller right column. Avoid centering everything; align panels to a ledger grid and let one primary module break scale. Major regions are separated by hairline rules rather than saturated backgrounds.
density
Medium-high density is acceptable because editorial operations screens carry many moving parts, but related metadata must cluster at 4-12px while unrelated panel groups separate at 48-96px.
hierarchy
Display hierarchy comes from Fraunces headlines at tight line-height and -0.04em tracking, then Source Sans 3 for controls and prose, then Azeret Mono for time, IDs, and state metadata. The chartreuse accent is the final hierarchy layer and appears only once or twice per viewport.
signature patterns
Active navigation rows render a 4px chartreuse vertical tab that protrudes from a quiet paper row while the rest of the item remains neutral and typographic.Every major card has a folio label in mono type and an inset top rule, making panels feel like pages in an editorial production ledger.Production lists are built as ruled ledger rows with alternating warm paper tints, right-aligned mono timestamps, and semantic chips that include text plus shape.A clipped-corner note treatment uses a small folded paper pseudo-element on urgent modules instead of icons or decorative illustrations.Live indicators combine a small chartreuse dot, bold text, and a thin accent border so state is never communicated through hue alone.
layout
breakpoints

Mobile below 720px collapses the rail into a horizontal strip and stacks panels; tablet uses a two-column grid with the priority queue full width.

density

Compact editorial operations density with 16px body text, 24px card padding, 4-12px metadata clusters, and generous 64-96px gaps around primary groups.

grid

Desktop uses 88px rail plus 12-column content grid with 24px gutters and max-width 1440px; the hero work panel spans 7 columns while the right stack spans 4.

responsive

At narrow widths, keep the chartreuse active tab as a top border, preserve touch targets above 44px, and collapse nonessential metadata into concise rows.

whitespace

Whitespace is uneven by design: dense rows inside panels, 32px between sibling modules, and 64px around the primary workspace to avoid uniform SaaS spacing.

guidance
do
  • Start with warm paper neutrals and dark typography; add accent only after hierarchy works without it.
  • Use the chartreuse accent for selected navigation, live state, focus rings, and one key metric per screen.
  • Keep borders as rgba hairlines and use spacing or type weight before adding shadows.
  • Make at least one panel visually dominant through scale, not through color.
  • Include mono folio labels, timestamps, or IDs wherever a panel represents operational status.
  • Pair every semantic color with text, icon shape, or border weight for accessibility.
  • Use -0.02em tracking globally and -0.04em on display headings.
avoid
  • Do not add multicolor charts, decorative gradients, or rainbow status systems.
  • Do not make three equal cards in a row; vary scale and density.
  • Do not fill selected navigation with a bright rectangle; use the narrow tab signature.
  • Do not use low contrast muted text for essential labels or values.
  • Do not round components with arbitrary radii outside the 0/16/24/9999 scale.
  • Do not let paper texture interfere with legibility or focus visibility.
  • Do not communicate live, error, or success state by color alone.
katagami spec
# Ledgerline Paper Shell

## Philosophy

Ledgerline Paper Shell is a restrained application language for editorial operations products that need the calm of a printed production ledger and the speed of modern SaaS. It uses warm paper, exacting dark typography, quiet rules, modular panels, and a single fresh chartreuse accent to make selected navigation, live work, and critical metrics unmistakable without turning the interface into a colorful dashboard.

### Values

- Paper-like neutrality as the default surface so content and state carry the product instead of decoration.
- Typographic authority through condensed editorial headings, readable sans body copy, and ledger-like mono metadata.
- One bright accent used only for selection, live indicators, active controls, and the primary performance number.
- System rigor with semantic tokens, predictable focus states, high contrast, and reusable panel anatomy.
- Editorial asymmetry: one oversized working panel and smaller supporting modules rather than equal dashboard cards.
- Quiet craft details such as hairline dividers, folio labels, corner tabs, and measured spacing changes.

### Anti-Values

- Synthetic SaaS gradients, rainbow charts, or multiple brand accents competing for attention.
- Three equal cards in a row, generic analytics tiles, and decorative illustrations that do not support workflow.
- Low-contrast gray text, vague borders, or states indicated by color alone.
- Over-rounded bubbly components; the language should feel precise, not toy-like.

### Visual Character

- A fixed paper app shell uses an off-white body, a slightly warmer left rail, and crisp dark type with rgba(24,22,18,.08) hairline dividers between major regions.
- Panels use modular ledger cards with 24px radius, 1px near-invisible borders, a small uppercase folio label, and an inset top rule instead of heavy shadows.
- The selected navigation item and live metrics are marked by a narrow chartreuse vertical tab plus bold dark text, never by filled colorful pills across the whole row.
- Dense production rows use alternating paper tints, mono time stamps, small status chips, and vertical separator rules to create dashboard structure without charts dominating.
- One large asymmetric editorial workspace occupies roughly half the desktop grid while compact right-side modules stack as quiet reference panels.

## Tokens

### Borders

- **Accent Width**: 4px
- **Character**: Near-invisible dark hairlines for structure; chartreuse accent bars only for active or live states.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#B7DC35` |
| background | `#F6F1E8` |
| border | `#181612` |
| error | `#B44B3F` |
| info | `#3F6593` |
| muted | `#746C60` |
| primary | `#191715` |
| secondary | `#5F584E` |
| success | `#567A35` |
| surface | `#FFFCF4` |
| text | `#191715` |
| warning | `#A36D1D` |

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(.2,.7,.2,1)
- **Philosophy**: Small translate and border-color changes confirm interaction; avoid bouncy motion and continuous animation except subtle live pulse.

### Radii

- **Full**: 9999px
- **Lg**: 24px
- **Md**: 24px
- **None**: 0
- **Sm**: 16px

### Shadows

- **Lg**: 0 30px 80px rgba(47,39,27,0.12)
- **Md**: 0 12px 28px rgba(47,39,27,0.08)
- **Sm**: 0 1px 0 rgba(25,23,21,0.05)

### Spacing

- **Base**: 8px
- **Scale**: [4,8,12,16,24,32,48,64,96]

### Surfaces

- **Bg Pattern**: A barely visible repeating-linear-gradient at 90deg simulates paper grain while preserving text contrast.
- **Card Style**: Ledger panels are #FFFCF4 with rgba(24,22,18,.08) borders, 24px radius, folio labels, and a fine inset rule.
- **Treatment**: Warm paper grounds with subtle linear paper fibers and no decorative gradients beyond low-opacity texture.

### Typography

- **Base Size**: 16px
- **Body Font**: Source Sans 3
- **Display Letter Spacing**: -0.04em
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Azeret+Mono:wght@500;650&family=Fraunces:opsz,wght,SOFT,WONK@9..144,650..800,20,0&family=Source+Sans+3:wght@400;520;650;750&display=swap
- **Heading Font**: Fraunces
- **Letter Spacing**: -0.02em
- **Line Height**: 1.55
- **Mono Font**: Azeret Mono
- **Scale Ratio**: 1.25

## Rules

### Composition

Use a true app shell: narrow left rail, top context strip, dominant editorial work panel, and a smaller right column. Avoid centering everything; align panels to a ledger grid and let one primary module break scale. Major regions are separated by hairline rules rather than saturated backgrounds.

### Density

Medium-high density is acceptable because editorial operations screens carry many moving parts, but related metadata must cluster at 4-12px while unrelated panel groups separate at 48-96px.

### Hierarchy

Display hierarchy comes from Fraunces headlines at tight line-height and -0.04em tracking, then Source Sans 3 for controls and prose, then Azeret Mono for time, IDs, and state metadata. The chartreuse accent is the final hierarchy layer and appears only once or twice per viewport.

### Signature Patterns

- Active navigation rows render a 4px chartreuse vertical tab that protrudes from a quiet paper row while the rest of the item remains neutral and typographic.
- Every major card has a folio label in mono type and an inset top rule, making panels feel like pages in an editorial production ledger.
- Production lists are built as ruled ledger rows with alternating warm paper tints, right-aligned mono timestamps, and semantic chips that include text plus shape.
- A clipped-corner note treatment uses a small folded paper pseudo-element on urgent modules instead of icons or decorative illustrations.
- Live indicators combine a small chartreuse dot, bold text, and a thin accent border so state is never communicated through hue alone.

## Layout

### Breakpoints

Mobile below 720px collapses the rail into a horizontal strip and stacks panels; tablet uses a two-column grid with the priority queue full width.

### Density

Compact editorial operations density with 16px body text, 24px card padding, 4-12px metadata clusters, and generous 64-96px gaps around primary groups.

### Grid

Desktop uses 88px rail plus 12-column content grid with 24px gutters and max-width 1440px; the hero work panel spans 7 columns while the right stack spans 4.

### Responsive

At narrow widths, keep the chartreuse active tab as a top border, preserve touch targets above 44px, and collapse nonessential metadata into concise rows.

### Whitespace

Whitespace is uneven by design: dense rows inside panels, 32px between sibling modules, and 64px around the primary workspace to avoid uniform SaaS spacing.

## Guidance

### Do

- Start with warm paper neutrals and dark typography; add accent only after hierarchy works without it.
- Use the chartreuse accent for selected navigation, live state, focus rings, and one key metric per screen.
- Keep borders as rgba hairlines and use spacing or type weight before adding shadows.
- Make at least one panel visually dominant through scale, not through color.
- Include mono folio labels, timestamps, or IDs wherever a panel represents operational status.
- Pair every semantic color with text, icon shape, or border weight for accessibility.
- Use -0.02em tracking globally and -0.04em on display headings.

### Don't

- Do not add multicolor charts, decorative gradients, or rainbow status systems.
- Do not make three equal cards in a row; vary scale and density.
- Do not fill selected navigation with a bright rectangle; use the narrow tab signature.
- Do not use low contrast muted text for essential labels or values.
- Do not round components with arbitrary radii outside the 0/16/24/9999 scale.
- Do not let paper texture interfere with legibility or focus visibility.
- Do not communicate live, error, or success state by color alone.

### Accessibility

Body text and controls meet WCAG AA on paper surfaces; focus states use 2px dark or chartreuse outlines with offset, status chips include words, and touch controls remain at least 44px tall on mobile.

### Usage Context

Best for editorial production software, content operations, newsroom planning, publishing calendars, lightweight enterprise systems, and refined consumer SaaS tools that need polish without visual noise.
DESIGN.md
---
version: "alpha"
name: "Ledgerline Paper Shell"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#B7DC35"
  background: "#F6F1E8"
  border: "#181612"
  error: "#B44B3F"
  info: "#3F6593"
  muted: "#746C60"
  primary: "#191715"
  secondary: "#5F584E"
  success: "#567A35"
  surface: "#FFFCF4"
  text: "#191715"
  warning: "#A36D1D"
typography:
  headline-lg:
    fontFamily: "Fraunces"
    fontSize: "1.953rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Fraunces"
    fontSize: "1.563rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "Source Sans 3"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.55
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "Azeret Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "24px"
  md: "24px"
  none: "0px"
  sm: "16px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
  step-8: "96px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  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"
---

# Ledgerline Paper Shell

## Overview

Ledgerline Paper Shell is a restrained application language for editorial operations products that need the calm of a printed production ledger and the speed of modern SaaS. It uses warm paper, exacting dark typography, quiet rules, modular panels, and a single fresh chartreuse accent to make selected navigation, live work, and critical metrics unmistakable without turning the interface into a colorful dashboard.

### Values

- Paper-like neutrality as the default surface so content and state carry the product instead of decoration.
- Typographic authority through condensed editorial headings, readable sans body copy, and ledger-like mono metadata.
- One bright accent used only for selection, live indicators, active controls, and the primary performance number.
- System rigor with semantic tokens, predictable focus states, high contrast, and reusable panel anatomy.
- Editorial asymmetry: one oversized working panel and smaller supporting modules rather than equal dashboard cards.
- Quiet craft details such as hairline dividers, folio labels, corner tabs, and measured spacing changes.

### Anti-Values

- Synthetic SaaS gradients, rainbow charts, or multiple brand accents competing for attention.
- Three equal cards in a row, generic analytics tiles, and decorative illustrations that do not support workflow.
- Low-contrast gray text, vague borders, or states indicated by color alone.
- Over-rounded bubbly components; the language should feel precise, not toy-like.

### Visual Character

- A fixed paper app shell uses an off-white body, a slightly warmer left rail, and crisp dark type with rgba(24,22,18,.08) hairline dividers between major regions.
- Panels use modular ledger cards with 24px radius, 1px near-invisible borders, a small uppercase folio label, and an inset top rule instead of heavy shadows.
- The selected navigation item and live metrics are marked by a narrow chartreuse vertical tab plus bold dark text, never by filled colorful pills across the whole row.
- Dense production rows use alternating paper tints, mono time stamps, small status chips, and vertical separator rules to create dashboard structure without charts dominating.
- One large asymmetric editorial workspace occupies roughly half the desktop grid while compact right-side modules stack as quiet reference panels.

## Colors

Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.

| Token | Value |
|-------|-------|
| accent | `#B7DC35` |
| background | `#F6F1E8` |
| border | `#181612` |
| error | `#B44B3F` |
| info | `#3F6593` |
| muted | `#746C60` |
| primary | `#191715` |
| secondary | `#5F584E` |
| success | `#567A35` |
| surface | `#FFFCF4` |
| text | `#191715` |
| warning | `#A36D1D` |

## Typography

- **Headline-Lg**: Fraunces, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Fraunces, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Source Sans 3, 16px, weight 400, line-height 1.55.
- **Label-Md**: Azeret 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`
- **Step-8**: `96px`

### Breakpoints

Mobile below 720px collapses the rail into a horizontal strip and stacks panels; tablet uses a two-column grid with the priority queue full width.

### Density

Compact editorial operations density with 16px body text, 24px card padding, 4-12px metadata clusters, and generous 64-96px gaps around primary groups.

### Grid

Desktop uses 88px rail plus 12-column content grid with 24px gutters and max-width 1440px; the hero work panel spans 7 columns while the right stack spans 4.

### Responsive

At narrow widths, keep the chartreuse active tab as a top border, preserve touch targets above 44px, and collapse nonessential metadata into concise rows.

### Whitespace

Whitespace is uneven by design: dense rows inside panels, 32px between sibling modules, and 64px around the primary workspace to avoid uniform SaaS spacing.

## Elevation & Depth

### Shadows

- **Lg**: 0 30px 80px rgba(47,39,27,0.12)
- **Md**: 0 12px 28px rgba(47,39,27,0.08)
- **Sm**: 0 1px 0 rgba(25,23,21,0.05)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `24px`
- **Md**: `24px`
- **None**: `0px`
- **Sm**: `16px`

### Surfaces

- **Bg Pattern**: A barely visible repeating-linear-gradient at 90deg simulates paper grain while preserving text contrast.
- **Card Style**: Ledger panels are #FFFCF4 with rgba(24,22,18,.08) borders, 24px radius, folio labels, and a fine inset rule.
- **Treatment**: Warm paper grounds with subtle linear paper fibers and no decorative gradients beyond low-opacity texture.

### Borders

- **Accent Width**: 4px
- **Character**: Near-invisible dark hairlines for structure; chartreuse accent bars only for active or live states.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use a true app shell: narrow left rail, top context strip, dominant editorial work panel, and a smaller right column. Avoid centering everything; align panels to a ledger grid and let one primary module break scale. Major regions are separated by hairline rules rather than saturated backgrounds.

### Density

Medium-high density is acceptable because editorial operations screens carry many moving parts, but related metadata must cluster at 4-12px while unrelated panel groups separate at 48-96px.

### Hierarchy

Display hierarchy comes from Fraunces headlines at tight line-height and -0.04em tracking, then Source Sans 3 for controls and prose, then Azeret Mono for time, IDs, and state metadata. The chartreuse accent is the final hierarchy layer and appears only once or twice per viewport.

### Signature Patterns

- Active navigation rows render a 4px chartreuse vertical tab that protrudes from a quiet paper row while the rest of the item remains neutral and typographic.
- Every major card has a folio label in mono type and an inset top rule, making panels feel like pages in an editorial production ledger.
- Production lists are built as ruled ledger rows with alternating warm paper tints, right-aligned mono timestamps, and semantic chips that include text plus shape.
- A clipped-corner note treatment uses a small folded paper pseudo-element on urgent modules instead of icons or decorative illustrations.
- Live indicators combine a small chartreuse dot, bold text, and a thin accent border so state is never communicated through hue alone.

## 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/ledgerline-paper-shell/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 Start with warm paper neutrals and dark typography; add accent only after hierarchy works without it.
- Do Use the chartreuse accent for selected navigation, live state, focus rings, and one key metric per screen.
- Do Keep borders as rgba hairlines and use spacing or type weight before adding shadows.
- Do Make at least one panel visually dominant through scale, not through color.
- Do Include mono folio labels, timestamps, or IDs wherever a panel represents operational status.
- Do Pair every semantic color with text, icon shape, or border weight for accessibility.
- Do Use -0.02em tracking globally and -0.04em on display headings.
- Don't Do not add multicolor charts, decorative gradients, or rainbow status systems.
- Don't Do not make three equal cards in a row; vary scale and density.
- Don't Do not fill selected navigation with a bright rectangle; use the narrow tab signature.
- Don't Do not use low contrast muted text for essential labels or values.
- Don't Do not round components with arbitrary radii outside the 0/16/24/9999 scale.
- Don't Do not let paper texture interfere with legibility or focus visibility.
- Don't Do not communicate live, error, or success state by color alone.

### Accessibility

Body text and controls meet WCAG AA on paper surfaces; focus states use 2px dark or chartreuse outlines with offset, status chips include words, and touch controls remain at least 44px tall on mobile.

### Usage Context

Best for editorial production software, content operations, newsroom planning, publishing calendars, lightweight enterprise systems, and refined consumer SaaS tools that need polish without visual noise.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "ledgerline-paper-shell",
  "type": "registry:theme",
  "title": "Ledgerline Paper Shell shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F6F1E8",
      "foreground": "#191715",
      "card": "#FFFCF4",
      "card-foreground": "#191715",
      "popover": "#FFFCF4",
      "popover-foreground": "#191715",
      "primary": "#191715",
      "primary-foreground": "#ffffff",
      "secondary": "#5F584E",
      "secondary-foreground": "#ffffff",
      "muted": "#746C60",
      "muted-foreground": "#191715",
      "accent": "#B7DC35",
      "accent-foreground": "#111111",
      "destructive": "#B44B3F",
      "border": "#181612",
      "input": "#181612",
      "ring": "#B7DC35",
      "chart-1": "#191715",
      "chart-2": "#5F584E",
      "chart-3": "#B7DC35",
      "chart-4": "#567A35",
      "chart-5": "#A36D1D",
      "sidebar": "#FFFCF4",
      "sidebar-foreground": "#191715",
      "sidebar-primary": "#191715",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#3F6593",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#181612",
      "sidebar-ring": "#B7DC35",
      "radius": "24px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#191715",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#B7DC35",
      "accent-foreground": "#111111",
      "destructive": "#B44B3F",
      "border": "#303642",
      "input": "#303642",
      "ring": "#B7DC35",
      "chart-1": "#191715",
      "chart-2": "#5F584E",
      "chart-3": "#B7DC35",
      "chart-4": "#567A35",
      "chart-5": "#A36D1D",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#191715",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#B7DC35",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#B7DC35",
      "radius": "24px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "ledgerline-paper-shell",
    "slug": "ledgerline-paper-shell",
    "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": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "display_letter_spacing",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · ledgerline-paper-shell
DESIGN.md

at a glance

Palette

Typography

headline-lgFraunces · 31px · 700

The quick brown fox jumps

headline-mdFraunces · 25px · 600

The quick brown fox jumps

body-mdSource Sans 3 · 16px · 400

The quick brown fox jumps

label-mdAzeret 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
  • step-896px

Shape

full9999px
lg24px
md24px
none0px
sm16px
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: #F6F1E8;
  --foreground: #191715;
  --card: #FFFCF4;
  --card-foreground: #191715;
  --popover: #FFFCF4;
  --popover-foreground: #191715;
  --primary: #191715;
  --primary-foreground: #ffffff;
  --secondary: #5F584E;
  --secondary-foreground: #ffffff;
  --muted: #746C60;
  --muted-foreground: #191715;
  --accent: #B7DC35;
  --accent-foreground: #111111;
  --destructive: #B44B3F;
  --border: #181612;
  --input: #181612;
  --ring: #B7DC35;
  --chart-1: #191715;
  --chart-2: #5F584E;
  --chart-3: #B7DC35;
  --chart-4: #567A35;
  --chart-5: #A36D1D;
  --sidebar: #FFFCF4;
  --sidebar-foreground: #191715;
  --sidebar-primary: #191715;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #3F6593;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #181612;
  --sidebar-ring: #B7DC35;
  --radius: 24px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #191715;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #B7DC35;
  --accent-foreground: #111111;
  --destructive: #B44B3F;
  --border: #303642;
  --input: #303642;
  --ring: #B7DC35;
  --chart-1: #191715;
  --chart-2: #5F584E;
  --chart-3: #B7DC35;
  --chart-4: #567A35;
  --chart-5: #A36D1D;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #191715;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #B7DC35;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #B7DC35;
  --radius: 24px;
}
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 LedgerlinePaperShellShadcnKit() {
  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">Ledgerline Paper Shell</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": "ledgerline-paper-shell",
  "type": "registry:theme",
  "title": "Ledgerline Paper Shell shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F6F1E8",
      "foreground": "#191715",
      "card": "#FFFCF4",
      "card-foreground": "#191715",
      "popover": "#FFFCF4",
      "popover-foreground": "#191715",
      "primary": "#191715",
      "primary-foreground": "#ffffff",
      "secondary": "#5F584E",
      "secondary-foreground": "#ffffff",
      "muted": "#746C60",
      "muted-foreground": "#191715",
      "accent": "#B7DC35",
      "accent-foreground": "#111111",
      "destructive": "#B44B3F",
      "border": "#181612",
      "input": "#181612",
      "ring": "#B7DC35",
      "chart-1": "#191715",
      "chart-2": "#5F584E",
      "chart-3": "#B7DC35",
      "chart-4": "#567A35",
      "chart-5": "#A36D1D",
      "sidebar": "#FFFCF4",
      "sidebar-foreground": "#191715",
      "sidebar-primary": "#191715",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#3F6593",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#181612",
      "sidebar-ring": "#B7DC35",
      "radius": "24px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#191715",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#B7DC35",
      "accent-foreground": "#111111",
      "destructive": "#B44B3F",
      "border": "#303642",
      "input": "#303642",
      "ring": "#B7DC35",
      "chart-1": "#191715",
      "chart-2": "#5F584E",
      "chart-3": "#B7DC35",
      "chart-4": "#567A35",
      "chart-5": "#A36D1D",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#191715",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#B7DC35",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#B7DC35",
      "radius": "24px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "ledgerline-paper-shell",
    "slug": "ledgerline-paper-shell",
    "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": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "display_letter_spacing",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
component recipescompatibility fallback
# Ledgerline Paper Shell shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `ledgerline-paper-shell`
Slug: `ledgerline-paper-shell`

## Intent

Ledgerline Paper Shell is a restrained application language for editorial operations products that need the calm of a printed production ledger and the speed of modern SaaS. It uses warm paper, exacting dark typography, quiet rules, modular panels, and a single fresh chartreuse accent to make selected navigation, live work, and critical metrics unmistakable without turning the interface into a colorful dashboard.

## 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:

{
  "accent": "#B7DC35",
  "background": "#F6F1E8",
  "border": "#181612",
  "error": "#B44B3F",
  "info": "#3F6593",
  "muted": "#746C60",
  "primary": "#191715",
  "secondary": "#5F584E",
  "success": "#567A35",
  "surface": "#FFFCF4",
  "text": "#191715",
  "warning": "#A36D1D"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Source Sans 3",
  "display_letter_spacing": "-0.04em",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Azeret+Mono:wght@500;650&family=Fraunces:opsz,wght,SOFT,WONK@9..144,650..800,20,0&family=Source+Sans+3:wght@400;520;650;750&display=swap",
  "heading_font": "Fraunces",
  "letter_spacing": "-0.02em",
  "line_height": 1.55,
  "mono_font": "Azeret Mono",
  "scale_ratio": 1.25
}

## Visual character to preserve

- A fixed paper app shell uses an off-white body, a slightly warmer left rail, and crisp dark type with rgba(24,22,18,.08) hairline dividers between major regions.
- Panels use modular ledger cards with 24px radius, 1px near-invisible borders, a small uppercase folio label, and an inset top rule instead of heavy shadows.
- The selected navigation item and live metrics are marked by a narrow chartreuse vertical tab plus bold dark text, never by filled colorful pills across the whole row.
- Dense production rows use alternating paper tints, mono time stamps, small status chips, and vertical separator rules to create dashboard structure without charts dominating.
- One large asymmetric editorial workspace occupies roughly half the desktop grid while compact right-side modules stack as quiet reference panels.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "pebble",
  "border": "solid",
  "underlay": false,
  "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/ledgerline-paper-shell/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: Start with warm paper neutrals and dark typography; add accent only after hierarchy works without it.; Use the chartreuse accent for selected navigation, live state, focus rings, and one key metric per screen.; Keep borders as rgba hairlines and use spacing or type weight before adding shadows.; Make at least one panel visually dominant through scale, not through color.; Include mono folio labels, timestamps, or IDs wherever a panel represents operational status.; Pair every semantic color with text, icon shape, or border weight for accessibility.; Use -0.02em tracking globally and -0.04em on display headings.
- Do not: Do not add multicolor charts, decorative gradients, or rainbow status systems.; Do not make three equal cards in a row; vary scale and density.; Do not fill selected navigation with a bright rectangle; use the narrow tab signature.; Do not use low contrast muted text for essential labels or values.; Do not round components with arbitrary radii outside the 0/16/24/9999 scale.; Do not let paper texture interfere with legibility or focus visibility.; Do not communicate live, error, or success state by color alone.

## 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 LedgerlinePaperShellShadcnKit() {
  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">Ledgerline Paper Shell</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

{
  "breakpoints": "Mobile below 720px collapses the rail into a horizontal strip and stacks panels; tablet uses a two-column grid with the priority queue full width.",
  "density": "Compact editorial operations density with 16px body text, 24px card padding, 4-12px metadata clusters, and generous 64-96px gaps around primary groups.",
  "grid": "Desktop uses 88px rail plus 12-column content grid with 24px gutters and max-width 1440px; the hero work panel spans 7 columns while the right stack spans 4.",
  "responsive": "At narrow widths, keep the chartreuse active tab as a top border, preserve touch targets above 44px, and collapse nonessential metadata into concise rows.",
  "whitespace": "Whitespace is uneven by design: dense rows inside panels, 32px between sibling modules, and 64px around the primary workspace to avoid uniform SaaS spacing."
}
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": "ledgerline-paper-shell",
    "name": "Ledgerline Paper Shell",
    "slug": "ledgerline-paper-shell"
  },
  "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 fixed paper app shell uses an off-white body, a slightly warmer left rail, and crisp dark type with rgba(24,22,18,.08) hairline dividers between major regions.",
    "Panels use modular ledger cards with 24px radius, 1px near-invisible borders, a small uppercase folio label, and an inset top rule instead of heavy shadows.",
    "The selected navigation item and live metrics are marked by a narrow chartreuse vertical tab plus bold dark text, never by filled colorful pills across the whole row.",
    "Dense production rows use alternating paper tints, mono time stamps, small status chips, and vertical separator rules to create dashboard structure without charts dominating.",
    "One large asymmetric editorial workspace occupies roughly half the desktop grid while compact right-side modules stack as quiet reference panels."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "pebble",
    "border": "solid",
    "underlay": false,
    "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": "Ledgerline Paper Shell 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": [
      "Start with warm paper neutrals and dark typography; add accent only after hierarchy works without it.",
      "Use the chartreuse accent for selected navigation, live state, focus rings, and one key metric per screen.",
      "Keep borders as rgba hairlines and use spacing or type weight before adding shadows.",
      "Make at least one panel visually dominant through scale, not through color.",
      "Include mono folio labels, timestamps, or IDs wherever a panel represents operational status.",
      "Pair every semantic color with text, icon shape, or border weight for accessibility.",
      "Use -0.02em tracking globally and -0.04em on display headings."
    ],
    "dont": [
      "Do not add multicolor charts, decorative gradients, or rainbow status systems.",
      "Do not make three equal cards in a row; vary scale and density.",
      "Do not fill selected navigation with a bright rectangle; use the narrow tab signature.",
      "Do not use low contrast muted text for essential labels or values.",
      "Do not round components with arbitrary radii outside the 0/16/24/9999 scale.",
      "Do not let paper texture interfere with legibility or focus visibility.",
      "Do not communicate live, error, or success state by color alone."
    ]
  }
}
related

More like this