Margin Signal Ledger
A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.
Download DESIGN.md
Portable DESIGN.md source of truth for most agents and apps.
specification
philosophy
tokens
borders4 items
- accent width
- 2px
- character
- warm gray rules with occasional left ledger accent lines
- default width
- 1px
- style
- solid
colors12 items
motion3 items
- duration
- 160ms
- easing
- cubic-bezier(0.2, 0, 0.1, 1)
- philosophy
- only disclose and clarify; tiny fades and line draws, never bouncing dashboard animation
radii5 items
- full
- 9999px
- lg
- 10px
- md
- 6px
- none
- 0
- sm
- 3px
shadows3 items
- lg
- 0 24px 60px rgba(64,54,39,0.12)
- md
- 0 10px 30px rgba(64,54,39,0.08)
- sm
- 0 1px 0 rgba(37,35,30,0.05)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- subtle repeating linear paper fiber and page gutter guides
- card style
- thin ruled borders, square-ish corners, metadata bands, no glossy elevation
- treatment
- warm paper with low-contrast fiber grain and ivory panels
typography8 items
- base size
- 16px
- body font
- Source Serif 4
- google fonts url
- https://fonts.googleapis.com/css2?family=Commit+Mono:wght@400;500;600&family=Newsreader:opsz,wght@6..72,500;6..72,650&family=Source+Serif+4:opsz,wght@8..60,400;8..60,500;8..60,650&display=swap
- heading font
- Newsreader
- letter spacing
- -0.012em
- line height
- 1.55
- mono font
- Commit Mono
- scale ratio
- 1.22
rules
Compose screens like an annotated brief: a wide reading column, a narrow margin signal rail, and small operational inserts embedded near the text they explain.
Medium-dense but calm: many small signals may exist, yet each is attached to prose with enough line-height, gutters, and low-contrast grouping to avoid a dashboard feel.
Headlines use editorial serif weight, body prose carries the main hierarchy, and metrics stay subordinate through mono numerals, small caps labels, and muted ruled containers.
layout
>=1180px full annotated brief; 760-1179px two-column document plus stacked rail; <760px single reading column with margin cards inline.
Desktop uses a 12-column page grid with 7 columns for narrative content, 3 columns for margin signals, and 2 columns for navigation/support.
Whitespace behaves like page margins: generous outer gutters, tight internal ledger rows, and visible breathing room between unrelated signals.
guidance
- Place every metric next to the sentence, record, or task it qualifies.
- Use muted amber only for attention and tiny green or blue marks for healthy/known states.
- Favor small sparklines, summaries, and evidence notes over standalone charts.
- Keep typography readable with tabular numerals and high contrast text on paper surfaces.
- Do not create a dashboard top row of KPI cards or equal analytics tiles.
- Do not use saturated gradients, glowing status colors, or floating glass panels.
- Do not separate operational indicators from context or prose.
- Do not make charts visually louder than the document content.
katagami spec
# Margin Signal Ledger ## Philosophy Margin Signal Ledger is a document-adjacent operational language for AYA: analytics appear as quiet marginal evidence, inline confidence marks, and soft paper panels rather than dashboard widgets. It treats status as reading support for ongoing work, not a separate command center. ### Values - text-first operational awareness - ambient but legible status - paper material restraint - context before metric - progressive disclosure without dashboard chrome ### Anti-Values - chart walls and KPI grids - neon status theatrics - floating glass cards - decorative analytics without nearby prose ### Visual Character - CSS uses off-white page backgrounds with nested paper panels, 1px warm gray borders, and inset hairline separators instead of heavy shadows. - Metrics are rendered as inline ledger chips inside paragraphs and list rows, using tabular numerals, tiny labels, and restrained green blue amber dots. - Context summaries occupy margin-note columns with ruled headers, subtle paper grain, and compact sparklines drawn as SVG strokes beside prose. - Progressive detail appears through folded-corner panels, disclosure rows, and low-contrast metadata bands rather than modal dashboard blocks. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: warm gray rules with occasional left ledger accent lines - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#4D8A69` | | background | `#F5F1E8` | | border | `#D8D0C1` | | error | `#A65A4D` | | info | `#4F7893` | | muted | `#8B867A` | | primary | `#2F5E6E` | | secondary | `#7A766B` | | success | `#4D8A69` | | surface | `#FFFDF7` | | text | `#25231E` | | warning | `#B58A42` | ### Motion - **Duration**: 160ms - **Easing**: cubic-bezier(0.2, 0, 0.1, 1) - **Philosophy**: only disclose and clarify; tiny fades and line draws, never bouncing dashboard animation ### Radii - **Full**: 9999px - **Lg**: 10px - **Md**: 6px - **None**: 0 - **Sm**: 3px ### Shadows - **Lg**: 0 24px 60px rgba(64,54,39,0.12) - **Md**: 0 10px 30px rgba(64,54,39,0.08) - **Sm**: 0 1px 0 rgba(37,35,30,0.05) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: subtle repeating linear paper fiber and page gutter guides - **Card Style**: thin ruled borders, square-ish corners, metadata bands, no glossy elevation - **Treatment**: warm paper with low-contrast fiber grain and ivory panels ### Typography - **Base Size**: 16px - **Body Font**: Source Serif 4 - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Commit+Mono:wght@400;500;600&family=Newsreader:opsz,wght@6..72,500;6..72,650&family=Source+Serif+4:opsz,wght@8..60,400;8..60,500;8..60,650&display=swap - **Heading Font**: Newsreader - **Letter Spacing**: -0.012em - **Line Height**: 1.55 - **Mono Font**: Commit Mono - **Scale Ratio**: 1.22 ## Rules ### Composition Compose screens like an annotated brief: a wide reading column, a narrow margin signal rail, and small operational inserts embedded near the text they explain. ### Density Medium-dense but calm: many small signals may exist, yet each is attached to prose with enough line-height, gutters, and low-contrast grouping to avoid a dashboard feel. ### Hierarchy Headlines use editorial serif weight, body prose carries the main hierarchy, and metrics stay subordinate through mono numerals, small caps labels, and muted ruled containers. ### Signature Patterns - Inline metric lozenges sit on the text baseline with tabular numerals, a tiny status dot, and no chart frame around them. - Margin summary cards use ruled document headers, footnote numbering, and a narrow left accent rule keyed to status severity. - Sparklines are hairline SVG traces embedded in metadata bands, clipped to six to ten points with no axes or legends. - Folded-corner evidence panels reveal secondary operations through soft ivory backgrounds and diagonal corner marks made with CSS gradients. ## Layout ### Breakpoints >=1180px full annotated brief; 760-1179px two-column document plus stacked rail; <760px single reading column with margin cards inline. ### Grid Desktop uses a 12-column page grid with 7 columns for narrative content, 3 columns for margin signals, and 2 columns for navigation/support. ### Whitespace Whitespace behaves like page margins: generous outer gutters, tight internal ledger rows, and visible breathing room between unrelated signals. ## Guidance ### Do - Place every metric next to the sentence, record, or task it qualifies. - Use muted amber only for attention and tiny green or blue marks for healthy/known states. - Favor small sparklines, summaries, and evidence notes over standalone charts. - Keep typography readable with tabular numerals and high contrast text on paper surfaces. ### Don't - Do not create a dashboard top row of KPI cards or equal analytics tiles. - Do not use saturated gradients, glowing status colors, or floating glass panels. - Do not separate operational indicators from context or prose. - Do not make charts visually louder than the document content. ### Accessibility All body text maintains strong contrast, status never relies on color alone, sparklines are accompanied by text summaries, and focus states use visible ruled outlines. ### Usage Context Ideal for knowledge operations, AI review workflows, editorial pipelines, compliance work, research synthesis, and assistants that need to show status without becoming analytics software.
DESIGN.md
---
version: "alpha"
name: "Margin Signal Ledger"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#4D8A69"
background: "#F5F1E8"
border: "#D8D0C1"
error: "#A65A4D"
info: "#4F7893"
muted: "#8B867A"
primary: "#2F5E6E"
secondary: "#7A766B"
success: "#4D8A69"
surface: "#FFFDF7"
text: "#25231E"
warning: "#B58A42"
typography:
headline-lg:
fontFamily: "Newsreader"
fontSize: "1.816rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.012em"
headline-md:
fontFamily: "Newsreader"
fontSize: "1.488rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.012em"
body-md:
fontFamily: "Source Serif 4"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.55
letterSpacing: "-0.012em"
label-md:
fontFamily: "Commit Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "10px"
md: "6px"
none: "0px"
sm: "3px"
spacing:
base: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
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"
---
# Margin Signal Ledger
## Overview
Margin Signal Ledger is a document-adjacent operational language for AYA: analytics appear as quiet marginal evidence, inline confidence marks, and soft paper panels rather than dashboard widgets. It treats status as reading support for ongoing work, not a separate command center.
### Values
- text-first operational awareness
- ambient but legible status
- paper material restraint
- context before metric
- progressive disclosure without dashboard chrome
### Anti-Values
- chart walls and KPI grids
- neon status theatrics
- floating glass cards
- decorative analytics without nearby prose
### Visual Character
- CSS uses off-white page backgrounds with nested paper panels, 1px warm gray borders, and inset hairline separators instead of heavy shadows.
- Metrics are rendered as inline ledger chips inside paragraphs and list rows, using tabular numerals, tiny labels, and restrained green blue amber dots.
- Context summaries occupy margin-note columns with ruled headers, subtle paper grain, and compact sparklines drawn as SVG strokes beside prose.
- Progressive detail appears through folded-corner panels, disclosure rows, and low-contrast metadata bands rather than modal dashboard blocks.
## 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 | `#4D8A69` |
| background | `#F5F1E8` |
| border | `#D8D0C1` |
| error | `#A65A4D` |
| info | `#4F7893` |
| muted | `#8B867A` |
| primary | `#2F5E6E` |
| secondary | `#7A766B` |
| success | `#4D8A69` |
| surface | `#FFFDF7` |
| text | `#25231E` |
| warning | `#B58A42` |
## Typography
- **Headline-Lg**: Newsreader, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Newsreader, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Source Serif 4, 16px, weight 400, line-height 1.55.
- **Label-Md**: Commit 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`
### Breakpoints
>=1180px full annotated brief; 760-1179px two-column document plus stacked rail; <760px single reading column with margin cards inline.
### Grid
Desktop uses a 12-column page grid with 7 columns for narrative content, 3 columns for margin signals, and 2 columns for navigation/support.
### Whitespace
Whitespace behaves like page margins: generous outer gutters, tight internal ledger rows, and visible breathing room between unrelated signals.
## Elevation & Depth
### Shadows
- **Lg**: 0 24px 60px rgba(64,54,39,0.12)
- **Md**: 0 10px 30px rgba(64,54,39,0.08)
- **Sm**: 0 1px 0 rgba(37,35,30,0.05)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `10px`
- **Md**: `6px`
- **None**: `0px`
- **Sm**: `3px`
### Surfaces
- **Bg Pattern**: subtle repeating linear paper fiber and page gutter guides
- **Card Style**: thin ruled borders, square-ish corners, metadata bands, no glossy elevation
- **Treatment**: warm paper with low-contrast fiber grain and ivory panels
### Borders
- **Accent Width**: 2px
- **Character**: warm gray rules with occasional left ledger accent lines
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Compose screens like an annotated brief: a wide reading column, a narrow margin signal rail, and small operational inserts embedded near the text they explain.
### Density
Medium-dense but calm: many small signals may exist, yet each is attached to prose with enough line-height, gutters, and low-contrast grouping to avoid a dashboard feel.
### Hierarchy
Headlines use editorial serif weight, body prose carries the main hierarchy, and metrics stay subordinate through mono numerals, small caps labels, and muted ruled containers.
### Signature Patterns
- Inline metric lozenges sit on the text baseline with tabular numerals, a tiny status dot, and no chart frame around them.
- Margin summary cards use ruled document headers, footnote numbering, and a narrow left accent rule keyed to status severity.
- Sparklines are hairline SVG traces embedded in metadata bands, clipped to six to ten points with no axes or legends.
- Folded-corner evidence panels reveal secondary operations through soft ivory backgrounds and diagonal corner marks made with CSS gradients.
## 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-019edab3-6994-7783-98b1-ebafa6fcf0b2/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 Place every metric next to the sentence, record, or task it qualifies.
- Do Use muted amber only for attention and tiny green or blue marks for healthy/known states.
- Do Favor small sparklines, summaries, and evidence notes over standalone charts.
- Do Keep typography readable with tabular numerals and high contrast text on paper surfaces.
- Don't Do not create a dashboard top row of KPI cards or equal analytics tiles.
- Don't Do not use saturated gradients, glowing status colors, or floating glass panels.
- Don't Do not separate operational indicators from context or prose.
- Don't Do not make charts visually louder than the document content.
### Accessibility
All body text maintains strong contrast, status never relies on color alone, sparklines are accompanied by text summaries, and focus states use visible ruled outlines.
### Usage Context
Ideal for knowledge operations, AI review workflows, editorial pipelines, compliance work, research synthesis, and assistants that need to show status without becoming analytics software.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "margin-signal-ledger",
"type": "registry:theme",
"title": "Margin Signal Ledger shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F5F1E8",
"foreground": "#25231E",
"card": "#FFFDF7",
"card-foreground": "#25231E",
"popover": "#FFFDF7",
"popover-foreground": "#25231E",
"primary": "#2F5E6E",
"primary-foreground": "#ffffff",
"secondary": "#7A766B",
"secondary-foreground": "#ffffff",
"muted": "#8B867A",
"muted-foreground": "#25231E",
"accent": "#4D8A69",
"accent-foreground": "#ffffff",
"destructive": "#A65A4D",
"border": "#D8D0C1",
"input": "#D8D0C1",
"ring": "#4D8A69",
"chart-1": "#2F5E6E",
"chart-2": "#7A766B",
"chart-3": "#4D8A69",
"chart-4": "#4D8A69",
"chart-5": "#B58A42",
"sidebar": "#FFFDF7",
"sidebar-foreground": "#25231E",
"sidebar-primary": "#2F5E6E",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#4F7893",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#D8D0C1",
"sidebar-ring": "#4D8A69",
"radius": "6px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#2F5E6E",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#4D8A69",
"accent-foreground": "#ffffff",
"destructive": "#A65A4D",
"border": "#303642",
"input": "#303642",
"ring": "#4D8A69",
"chart-1": "#2F5E6E",
"chart-2": "#7A766B",
"chart-3": "#4D8A69",
"chart-4": "#4D8A69",
"chart-5": "#B58A42",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#2F5E6E",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#4D8A69",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#4D8A69",
"radius": "6px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019edab3-6994-7783-98b1-ebafa6fcf0b2",
"slug": "margin-signal-ledger",
"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",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
]
}
}
}
```embodiments
at a glance
Typography
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Components
Components rendered with this language’s tokens — colors, type, and rounded corners as specified.
Spacing
- base8px
- xs4px
- sm8px
- md12px
- lg16px
- xl24px
- 2xl32px
- 3xl48px
- 4xl64px
Shape
implementation kit
DESIGN.md with shadcn
Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.
advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #F5F1E8;
--foreground: #25231E;
--card: #FFFDF7;
--card-foreground: #25231E;
--popover: #FFFDF7;
--popover-foreground: #25231E;
--primary: #2F5E6E;
--primary-foreground: #ffffff;
--secondary: #7A766B;
--secondary-foreground: #ffffff;
--muted: #8B867A;
--muted-foreground: #25231E;
--accent: #4D8A69;
--accent-foreground: #ffffff;
--destructive: #A65A4D;
--border: #D8D0C1;
--input: #D8D0C1;
--ring: #4D8A69;
--chart-1: #2F5E6E;
--chart-2: #7A766B;
--chart-3: #4D8A69;
--chart-4: #4D8A69;
--chart-5: #B58A42;
--sidebar: #FFFDF7;
--sidebar-foreground: #25231E;
--sidebar-primary: #2F5E6E;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #4F7893;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #D8D0C1;
--sidebar-ring: #4D8A69;
--radius: 6px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #2F5E6E;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #4D8A69;
--accent-foreground: #ffffff;
--destructive: #A65A4D;
--border: #303642;
--input: #303642;
--ring: #4D8A69;
--chart-1: #2F5E6E;
--chart-2: #7A766B;
--chart-3: #4D8A69;
--chart-4: #4D8A69;
--chart-5: #B58A42;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #2F5E6E;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #4D8A69;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #4D8A69;
--radius: 6px;
}
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 MarginSignalLedgerShadcnKit() {
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">Margin Signal Ledger</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "margin-signal-ledger",
"type": "registry:theme",
"title": "Margin Signal Ledger shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F5F1E8",
"foreground": "#25231E",
"card": "#FFFDF7",
"card-foreground": "#25231E",
"popover": "#FFFDF7",
"popover-foreground": "#25231E",
"primary": "#2F5E6E",
"primary-foreground": "#ffffff",
"secondary": "#7A766B",
"secondary-foreground": "#ffffff",
"muted": "#8B867A",
"muted-foreground": "#25231E",
"accent": "#4D8A69",
"accent-foreground": "#ffffff",
"destructive": "#A65A4D",
"border": "#D8D0C1",
"input": "#D8D0C1",
"ring": "#4D8A69",
"chart-1": "#2F5E6E",
"chart-2": "#7A766B",
"chart-3": "#4D8A69",
"chart-4": "#4D8A69",
"chart-5": "#B58A42",
"sidebar": "#FFFDF7",
"sidebar-foreground": "#25231E",
"sidebar-primary": "#2F5E6E",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#4F7893",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#D8D0C1",
"sidebar-ring": "#4D8A69",
"radius": "6px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#2F5E6E",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#4D8A69",
"accent-foreground": "#ffffff",
"destructive": "#A65A4D",
"border": "#303642",
"input": "#303642",
"ring": "#4D8A69",
"chart-1": "#2F5E6E",
"chart-2": "#7A766B",
"chart-3": "#4D8A69",
"chart-4": "#4D8A69",
"chart-5": "#B58A42",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#2F5E6E",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#4D8A69",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#4D8A69",
"radius": "6px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019edab3-6994-7783-98b1-ebafa6fcf0b2",
"slug": "margin-signal-ledger",
"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",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
]
}
}
}
# Margin Signal Ledger shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019edab3-6994-7783-98b1-ebafa6fcf0b2`
Slug: `margin-signal-ledger`
## Intent
Margin Signal Ledger is a document-adjacent operational language for AYA: analytics appear as quiet marginal evidence, inline confidence marks, and soft paper panels rather than dashboard widgets. It treats status as reading support for ongoing work, not a separate command center.
## 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": "#4D8A69",
"background": "#F5F1E8",
"border": "#D8D0C1",
"error": "#A65A4D",
"info": "#4F7893",
"muted": "#8B867A",
"primary": "#2F5E6E",
"secondary": "#7A766B",
"success": "#4D8A69",
"surface": "#FFFDF7",
"text": "#25231E",
"warning": "#B58A42"
}
Typography:
{
"base_size": "16px",
"body_font": "Source Serif 4",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Commit+Mono:wght@400;500;600&family=Newsreader:opsz,wght@6..72,500;6..72,650&family=Source+Serif+4:opsz,wght@8..60,400;8..60,500;8..60,650&display=swap",
"heading_font": "Newsreader",
"letter_spacing": "-0.012em",
"line_height": 1.55,
"mono_font": "Commit Mono",
"scale_ratio": 1.22
}
## Visual character to preserve
- CSS uses off-white page backgrounds with nested paper panels, 1px warm gray borders, and inset hairline separators instead of heavy shadows.
- Metrics are rendered as inline ledger chips inside paragraphs and list rows, using tabular numerals, tiny labels, and restrained green blue amber dots.
- Context summaries occupy margin-note columns with ruled headers, subtle paper grain, and compact sparklines drawn as SVG strokes beside prose.
- Progressive detail appears through folded-corner panels, disclosure rows, and low-contrast metadata bands rather than modal dashboard blocks.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": true,
"stickerBadges": false,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
}
## Signature component recipes
### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.
### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.
### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.
### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.
### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.
## Preview shots
- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.
## Implementation contract
- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/margin-signal-ledger/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: Place every metric next to the sentence, record, or task it qualifies.; Use muted amber only for attention and tiny green or blue marks for healthy/known states.; Favor small sparklines, summaries, and evidence notes over standalone charts.; Keep typography readable with tabular numerals and high contrast text on paper surfaces.
- Do not: Do not create a dashboard top row of KPI cards or equal analytics tiles.; Do not use saturated gradients, glowing status colors, or floating glass panels.; Do not separate operational indicators from context or prose.; Do not make charts visually louder than the document content.
## 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 MarginSignalLedgerShadcnKit() {
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">Margin Signal Ledger</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": ">=1180px full annotated brief; 760-1179px two-column document plus stacked rail; <760px single reading column with margin cards inline.",
"grid": "Desktop uses a 12-column page grid with 7 columns for narrative content, 3 columns for margin signals, and 2 columns for navigation/support.",
"whitespace": "Whitespace behaves like page margins: generous outer gutters, tight internal ledger rows, and visible breathing room between unrelated signals."
}
{
"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-019edab3-6994-7783-98b1-ebafa6fcf0b2",
"name": "Margin Signal Ledger",
"slug": "margin-signal-ledger"
},
"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": [
"CSS uses off-white page backgrounds with nested paper panels, 1px warm gray borders, and inset hairline separators instead of heavy shadows.",
"Metrics are rendered as inline ledger chips inside paragraphs and list rows, using tabular numerals, tiny labels, and restrained green blue amber dots.",
"Context summaries occupy margin-note columns with ruled headers, subtle paper grain, and compact sparklines drawn as SVG strokes beside prose.",
"Progressive detail appears through folded-corner panels, disclosure rows, and low-contrast metadata bands rather than modal dashboard blocks."
],
"visualProfile": {
"family": "paper-collage",
"material": "paper",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": true,
"stickerBadges": false,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "Margin Signal Ledger 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": [
"Place every metric next to the sentence, record, or task it qualifies.",
"Use muted amber only for attention and tiny green or blue marks for healthy/known states.",
"Favor small sparklines, summaries, and evidence notes over standalone charts.",
"Keep typography readable with tabular numerals and high contrast text on paper surfaces."
],
"dont": [
"Do not create a dashboard top row of KPI cards or equal analytics tiles.",
"Do not use saturated gradients, glowing status colors, or floating glass panels.",
"Do not separate operational indicators from context or prose.",
"Do not make charts visually louder than the document content."
]
}
}