back to gallery
design language·margin-signal-sheets

Margin Signal Sheets

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

Download DESIGN.md

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

the spec

specification

philosophy
summary
A text-first language for AYA where analytic evidence lives beside work instead of replacing it: metrics become margin notes, quiet ribbons, inline deltas, and small proof marks on warm white documents.
values
Document primacy over dashboard spectaclePeripheral awareness through tiny durable signalsEvidence integrated at the point of reading and editingCalm operational confidence without saturated status theater
anti-values
×Chart walls, widget grids, and dashboard chrome that compete with the document×Semantic color confetti, oversized KPIs, and alarm-like notification styling×Generic white SaaS cards with arbitrary soft radii
tokens
borders4 items
accent width
2px
character
Pale blue-gray hairlines and bracket borders used as reading aids, not decoration.
default width
1px
style
solid
colors12 items
accent
#A9B8C2
background
#F8F5EE
border
#D9E0E3
error
#A65D55
info
#8196A5
muted
#7A817F
primary
#2F3A42
secondary
#6F7D85
success
#7E9279
surface
#FFFDF8
text
#24292D
warning
#B5A06E
motion3 items
duration
140ms
easing
cubic-bezier(0.2, 0, 0.1, 1)
philosophy
Only reveal peripheral details on intent; signals fade in softly and never pulse or bounce.
radii5 items
full
9999px
lg
6px
md
4px
none
0
sm
2px
shadows3 items
lg
0 18px 48px rgba(47,58,66,0.08)
md
0 8px 24px rgba(47,58,66,0.06)
sm
0 1px 0 rgba(47,58,66,0.04)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
Subtle repeating horizontal document rule every 32px in rgba(217,224,227,0.35).
card style
Square-shouldered paper panels with 1px hairlines, 4px radius maximum, baseline-aligned labels, and no floating dashboard cards.
treatment
Warm white document sheets with matte ink, faint ruled divisions, and inset marginal evidence bands.
typography8 items
base size
16px
body font
IBM Plex Sans
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&family=IBM+Plex+Sans:wght@400;450;500;600&family=Literata:opsz,wght@7..72,500;7..72,650&display=swap
heading font
Literata
letter spacing
-0.015em
line height
1.55
mono font
IBM Plex Mono
scale ratio
1.2
rules
composition
Start with a document or workflow artifact occupying most of the screen, then attach a slim analytic rail, context summary, and bottom proof strip as supporting evidence.
density

High information density is allowed through alignment, hairlines, and terse labels, while generous page margins prevent the surface from becoming a dashboard.

hierarchy

Long-form text and task language own the darkest ink; numeric signals are smaller, monospaced, and positioned beside the sentence or row they explain.

signature patterns
Margin signal rail: a 72-120px side column with vertical ticks, tiny counts, and bracket notes aligned to paragraphs or workflow rows.Baseline sparklines: inline SVG lines sized like words and placed inside sentences, table cells, or compact badges rather than full chart frames.Quiet status ribbon: a single 24-32px tall strip across a document section using low-contrast segments, dot labels, and monospaced timestamps.Evidence footnotes: small bordered callouts that cite source counts, drift, or confidence below the content they qualify instead of presenting a KPI card.
layout
breakpoints

desktop 1200px, tablet 768px, mobile 375px with rail-to-ribbon reflow

grid
A document-first grid: 260px context pane, flexible reading sheet, and 96px margin signal rail on desktop; rail collapses into inline ribbons below tablet width.
whitespace

Whitespace behaves like page margin: wide outer gutters, tight internal line spacing, and 16-24px between evidence groups.

guidance
do
  • Anchor every metric to a sentence, row, paragraph, or task it explains.
  • Use hairline separators, monospaced numbers, and margin brackets to create quiet hierarchy.
  • Prefer small temporal traces, confidence notes, and source counts over large charts.
  • Let progressive disclosure expand evidence only when the user asks for it.
avoid
  • Do not build a grid of KPI cards, donut charts, or dashboard widgets.
  • Do not use saturated traffic-light colors or pulsing alert animation for routine states.
  • Do not mix arbitrary rounded cards; keep the committed paper geometry.
  • Do not let decorative sparklines appear without adjacent explanatory text.
katagami spec
# Margin Signal Sheets

## Philosophy

A text-first language for AYA where analytic evidence lives beside work instead of replacing it: metrics become margin notes, quiet ribbons, inline deltas, and small proof marks on warm white documents.

### Values

- Document primacy over dashboard spectacle
- Peripheral awareness through tiny durable signals
- Evidence integrated at the point of reading and editing
- Calm operational confidence without saturated status theater

### Anti-Values

- Chart walls, widget grids, and dashboard chrome that compete with the document
- Semantic color confetti, oversized KPIs, and alarm-like notification styling
- Generic white SaaS cards with arbitrary soft radii

### Visual Character

- Use a warm-white page canvas with nested paper panels separated by 1px pale blue-gray hairlines and almost no shadow, making boundaries feel printed rather than boxed.
- Attach micro-analytics to the right margin as narrow ruled columns, vertical status ticks, and bracketed notes instead of standalone cards or dashboard tiles.
- Render data as word-sized graphics: 28-80px inline sparklines, tiny dot trails, tabular deltas, and badge-width counts aligned to text baselines.
- Use graphite text hierarchy with Literata document headings, IBM Plex Sans operational labels, and IBM Plex Mono numeric evidence blocks for high-resolution reading.
- Restrict status to low-contrast blue-gray, wheat, and sage marks with textureless flat fills, reserving red only for thin error underlines or one-pixel flags.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Pale blue-gray hairlines and bracket borders used as reading aids, not decoration.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#A9B8C2` |
| background | `#F8F5EE` |
| border | `#D9E0E3` |
| error | `#A65D55` |
| info | `#8196A5` |
| muted | `#7A817F` |
| primary | `#2F3A42` |
| secondary | `#6F7D85` |
| success | `#7E9279` |
| surface | `#FFFDF8` |
| text | `#24292D` |
| warning | `#B5A06E` |

### Motion

- **Duration**: 140ms
- **Easing**: cubic-bezier(0.2, 0, 0.1, 1)
- **Philosophy**: Only reveal peripheral details on intent; signals fade in softly and never pulse or bounce.

### Radii

- **Full**: 9999px
- **Lg**: 6px
- **Md**: 4px
- **None**: 0
- **Sm**: 2px

### Shadows

- **Lg**: 0 18px 48px rgba(47,58,66,0.08)
- **Md**: 0 8px 24px rgba(47,58,66,0.06)
- **Sm**: 0 1px 0 rgba(47,58,66,0.04)

### Spacing

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

### Surfaces

- **Bg Pattern**: Subtle repeating horizontal document rule every 32px in rgba(217,224,227,0.35).
- **Card Style**: Square-shouldered paper panels with 1px hairlines, 4px radius maximum, baseline-aligned labels, and no floating dashboard cards.
- **Treatment**: Warm white document sheets with matte ink, faint ruled divisions, and inset marginal evidence bands.

### Typography

- **Base Size**: 16px
- **Body Font**: IBM Plex Sans
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&family=IBM+Plex+Sans:wght@400;450;500;600&family=Literata:opsz,wght@7..72,500;7..72,650&display=swap
- **Heading Font**: Literata
- **Letter Spacing**: -0.015em
- **Line Height**: 1.55
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.2

## Rules

### Composition

Start with a document or workflow artifact occupying most of the screen, then attach a slim analytic rail, context summary, and bottom proof strip as supporting evidence.

### Density

High information density is allowed through alignment, hairlines, and terse labels, while generous page margins prevent the surface from becoming a dashboard.

### Hierarchy

Long-form text and task language own the darkest ink; numeric signals are smaller, monospaced, and positioned beside the sentence or row they explain.

### Signature Patterns

- Margin signal rail: a 72-120px side column with vertical ticks, tiny counts, and bracket notes aligned to paragraphs or workflow rows.
- Baseline sparklines: inline SVG lines sized like words and placed inside sentences, table cells, or compact badges rather than full chart frames.
- Quiet status ribbon: a single 24-32px tall strip across a document section using low-contrast segments, dot labels, and monospaced timestamps.
- Evidence footnotes: small bordered callouts that cite source counts, drift, or confidence below the content they qualify instead of presenting a KPI card.

## Layout

### Breakpoints

desktop 1200px, tablet 768px, mobile 375px with rail-to-ribbon reflow

### Grid

A document-first grid: 260px context pane, flexible reading sheet, and 96px margin signal rail on desktop; rail collapses into inline ribbons below tablet width.

### Whitespace

Whitespace behaves like page margin: wide outer gutters, tight internal line spacing, and 16-24px between evidence groups.

## Guidance

### Do

- Anchor every metric to a sentence, row, paragraph, or task it explains.
- Use hairline separators, monospaced numbers, and margin brackets to create quiet hierarchy.
- Prefer small temporal traces, confidence notes, and source counts over large charts.
- Let progressive disclosure expand evidence only when the user asks for it.

### Don't

- Do not build a grid of KPI cards, donut charts, or dashboard widgets.
- Do not use saturated traffic-light colors or pulsing alert animation for routine states.
- Do not mix arbitrary rounded cards; keep the committed paper geometry.
- Do not let decorative sparklines appear without adjacent explanatory text.

### Accessibility

Maintain AA contrast for graphite text, never use color alone for status, provide visible 1px graphite focus outlines with offset, and keep microcopy readable at 12px or larger.

### Usage Context

Best for AI workspaces, research review tools, operational documents, lightweight monitoring inside editors, and enterprise workflows where evidence should support writing rather than become a dashboard.
DESIGN.md
---
version: "alpha"
name: "Margin Signal Sheets"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#A9B8C2"
  background: "#F8F5EE"
  border: "#D9E0E3"
  error: "#A65D55"
  info: "#8196A5"
  muted: "#7A817F"
  primary: "#2F3A42"
  secondary: "#6F7D85"
  success: "#7E9279"
  surface: "#FFFDF8"
  text: "#24292D"
  warning: "#B5A06E"
typography:
  headline-lg:
    fontFamily: "Literata"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.015em"
  headline-md:
    fontFamily: "Literata"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.015em"
  body-md:
    fontFamily: "IBM Plex Sans"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.55
    letterSpacing: "-0.015em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "6px"
  md: "4px"
  none: "0px"
  sm: "2px"
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 Sheets

## Overview

A text-first language for AYA where analytic evidence lives beside work instead of replacing it: metrics become margin notes, quiet ribbons, inline deltas, and small proof marks on warm white documents.

### Values

- Document primacy over dashboard spectacle
- Peripheral awareness through tiny durable signals
- Evidence integrated at the point of reading and editing
- Calm operational confidence without saturated status theater

### Anti-Values

- Chart walls, widget grids, and dashboard chrome that compete with the document
- Semantic color confetti, oversized KPIs, and alarm-like notification styling
- Generic white SaaS cards with arbitrary soft radii

### Visual Character

- Use a warm-white page canvas with nested paper panels separated by 1px pale blue-gray hairlines and almost no shadow, making boundaries feel printed rather than boxed.
- Attach micro-analytics to the right margin as narrow ruled columns, vertical status ticks, and bracketed notes instead of standalone cards or dashboard tiles.
- Render data as word-sized graphics: 28-80px inline sparklines, tiny dot trails, tabular deltas, and badge-width counts aligned to text baselines.
- Use graphite text hierarchy with Literata document headings, IBM Plex Sans operational labels, and IBM Plex Mono numeric evidence blocks for high-resolution reading.
- Restrict status to low-contrast blue-gray, wheat, and sage marks with textureless flat fills, reserving red only for thin error underlines or one-pixel flags.

## 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 | `#A9B8C2` |
| background | `#F8F5EE` |
| border | `#D9E0E3` |
| error | `#A65D55` |
| info | `#8196A5` |
| muted | `#7A817F` |
| primary | `#2F3A42` |
| secondary | `#6F7D85` |
| success | `#7E9279` |
| surface | `#FFFDF8` |
| text | `#24292D` |
| warning | `#B5A06E` |

## Typography

- **Headline-Lg**: Literata, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Literata, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans, 16px, weight 400, line-height 1.55.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`

### Breakpoints

desktop 1200px, tablet 768px, mobile 375px with rail-to-ribbon reflow

### Grid

A document-first grid: 260px context pane, flexible reading sheet, and 96px margin signal rail on desktop; rail collapses into inline ribbons below tablet width.

### Whitespace

Whitespace behaves like page margin: wide outer gutters, tight internal line spacing, and 16-24px between evidence groups.

## Elevation & Depth

### Shadows

- **Lg**: 0 18px 48px rgba(47,58,66,0.08)
- **Md**: 0 8px 24px rgba(47,58,66,0.06)
- **Sm**: 0 1px 0 rgba(47,58,66,0.04)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `6px`
- **Md**: `4px`
- **None**: `0px`
- **Sm**: `2px`

### Surfaces

- **Bg Pattern**: Subtle repeating horizontal document rule every 32px in rgba(217,224,227,0.35).
- **Card Style**: Square-shouldered paper panels with 1px hairlines, 4px radius maximum, baseline-aligned labels, and no floating dashboard cards.
- **Treatment**: Warm white document sheets with matte ink, faint ruled divisions, and inset marginal evidence bands.

### Borders

- **Accent Width**: 2px
- **Character**: Pale blue-gray hairlines and bracket borders used as reading aids, not decoration.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Start with a document or workflow artifact occupying most of the screen, then attach a slim analytic rail, context summary, and bottom proof strip as supporting evidence.

### Density

High information density is allowed through alignment, hairlines, and terse labels, while generous page margins prevent the surface from becoming a dashboard.

### Hierarchy

Long-form text and task language own the darkest ink; numeric signals are smaller, monospaced, and positioned beside the sentence or row they explain.

### Signature Patterns

- Margin signal rail: a 72-120px side column with vertical ticks, tiny counts, and bracket notes aligned to paragraphs or workflow rows.
- Baseline sparklines: inline SVG lines sized like words and placed inside sentences, table cells, or compact badges rather than full chart frames.
- Quiet status ribbon: a single 24-32px tall strip across a document section using low-contrast segments, dot labels, and monospaced timestamps.
- Evidence footnotes: small bordered callouts that cite source counts, drift, or confidence below the content they qualify instead of presenting a KPI card.

## 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-019edc14-a554-7a50-830e-a83f121157f8/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 Anchor every metric to a sentence, row, paragraph, or task it explains.
- Do Use hairline separators, monospaced numbers, and margin brackets to create quiet hierarchy.
- Do Prefer small temporal traces, confidence notes, and source counts over large charts.
- Do Let progressive disclosure expand evidence only when the user asks for it.
- Don't Do not build a grid of KPI cards, donut charts, or dashboard widgets.
- Don't Do not use saturated traffic-light colors or pulsing alert animation for routine states.
- Don't Do not mix arbitrary rounded cards; keep the committed paper geometry.
- Don't Do not let decorative sparklines appear without adjacent explanatory text.

### Accessibility

Maintain AA contrast for graphite text, never use color alone for status, provide visible 1px graphite focus outlines with offset, and keep microcopy readable at 12px or larger.

### Usage Context

Best for AI workspaces, research review tools, operational documents, lightweight monitoring inside editors, and enterprise workflows where evidence should support writing rather than become a dashboard.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "margin-signal-sheets",
  "type": "registry:theme",
  "title": "Margin Signal Sheets shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F8F5EE",
      "foreground": "#24292D",
      "card": "#FFFDF8",
      "card-foreground": "#24292D",
      "popover": "#FFFDF8",
      "popover-foreground": "#24292D",
      "primary": "#2F3A42",
      "primary-foreground": "#ffffff",
      "secondary": "#6F7D85",
      "secondary-foreground": "#ffffff",
      "muted": "#7A817F",
      "muted-foreground": "#24292D",
      "accent": "#A9B8C2",
      "accent-foreground": "#ffffff",
      "destructive": "#A65D55",
      "border": "#D9E0E3",
      "input": "#D9E0E3",
      "ring": "#A9B8C2",
      "chart-1": "#2F3A42",
      "chart-2": "#6F7D85",
      "chart-3": "#A9B8C2",
      "chart-4": "#7E9279",
      "chart-5": "#B5A06E",
      "sidebar": "#FFFDF8",
      "sidebar-foreground": "#24292D",
      "sidebar-primary": "#2F3A42",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#8196A5",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D9E0E3",
      "sidebar-ring": "#A9B8C2",
      "radius": "4px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2F3A42",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#A9B8C2",
      "accent-foreground": "#ffffff",
      "destructive": "#A65D55",
      "border": "#303642",
      "input": "#303642",
      "ring": "#A9B8C2",
      "chart-1": "#2F3A42",
      "chart-2": "#6F7D85",
      "chart-3": "#A9B8C2",
      "chart-4": "#7E9279",
      "chart-5": "#B5A06E",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2F3A42",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#A9B8C2",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#A9B8C2",
      "radius": "4px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edc14-a554-7a50-830e-a83f121157f8",
    "slug": "margin-signal-sheets",
    "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"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · margin-signal-sheets
DESIGN.md

at a glance

Palette

Typography

headline-lgLiterata · 28px · 700

The quick brown fox jumps

headline-mdLiterata · 23px · 600

The quick brown fox jumps

body-mdIBM Plex Sans · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

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

Spacing

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

Shape

full9999px
lg6px
md4px
none0px
sm2px
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: #F8F5EE;
  --foreground: #24292D;
  --card: #FFFDF8;
  --card-foreground: #24292D;
  --popover: #FFFDF8;
  --popover-foreground: #24292D;
  --primary: #2F3A42;
  --primary-foreground: #ffffff;
  --secondary: #6F7D85;
  --secondary-foreground: #ffffff;
  --muted: #7A817F;
  --muted-foreground: #24292D;
  --accent: #A9B8C2;
  --accent-foreground: #ffffff;
  --destructive: #A65D55;
  --border: #D9E0E3;
  --input: #D9E0E3;
  --ring: #A9B8C2;
  --chart-1: #2F3A42;
  --chart-2: #6F7D85;
  --chart-3: #A9B8C2;
  --chart-4: #7E9279;
  --chart-5: #B5A06E;
  --sidebar: #FFFDF8;
  --sidebar-foreground: #24292D;
  --sidebar-primary: #2F3A42;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #8196A5;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D9E0E3;
  --sidebar-ring: #A9B8C2;
  --radius: 4px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #2F3A42;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #A9B8C2;
  --accent-foreground: #ffffff;
  --destructive: #A65D55;
  --border: #303642;
  --input: #303642;
  --ring: #A9B8C2;
  --chart-1: #2F3A42;
  --chart-2: #6F7D85;
  --chart-3: #A9B8C2;
  --chart-4: #7E9279;
  --chart-5: #B5A06E;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #2F3A42;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #A9B8C2;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #A9B8C2;
  --radius: 4px;
}
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 MarginSignalSheetsShadcnKit() {
  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 Sheets</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": "margin-signal-sheets",
  "type": "registry:theme",
  "title": "Margin Signal Sheets shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F8F5EE",
      "foreground": "#24292D",
      "card": "#FFFDF8",
      "card-foreground": "#24292D",
      "popover": "#FFFDF8",
      "popover-foreground": "#24292D",
      "primary": "#2F3A42",
      "primary-foreground": "#ffffff",
      "secondary": "#6F7D85",
      "secondary-foreground": "#ffffff",
      "muted": "#7A817F",
      "muted-foreground": "#24292D",
      "accent": "#A9B8C2",
      "accent-foreground": "#ffffff",
      "destructive": "#A65D55",
      "border": "#D9E0E3",
      "input": "#D9E0E3",
      "ring": "#A9B8C2",
      "chart-1": "#2F3A42",
      "chart-2": "#6F7D85",
      "chart-3": "#A9B8C2",
      "chart-4": "#7E9279",
      "chart-5": "#B5A06E",
      "sidebar": "#FFFDF8",
      "sidebar-foreground": "#24292D",
      "sidebar-primary": "#2F3A42",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#8196A5",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D9E0E3",
      "sidebar-ring": "#A9B8C2",
      "radius": "4px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2F3A42",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#A9B8C2",
      "accent-foreground": "#ffffff",
      "destructive": "#A65D55",
      "border": "#303642",
      "input": "#303642",
      "ring": "#A9B8C2",
      "chart-1": "#2F3A42",
      "chart-2": "#6F7D85",
      "chart-3": "#A9B8C2",
      "chart-4": "#7E9279",
      "chart-5": "#B5A06E",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2F3A42",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#A9B8C2",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#A9B8C2",
      "radius": "4px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edc14-a554-7a50-830e-a83f121157f8",
    "slug": "margin-signal-sheets",
    "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"
      ]
    }
  }
}
component recipescompatibility fallback
# Margin Signal Sheets shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019edc14-a554-7a50-830e-a83f121157f8`
Slug: `margin-signal-sheets`

## Intent

A text-first language for AYA where analytic evidence lives beside work instead of replacing it: metrics become margin notes, quiet ribbons, inline deltas, and small proof marks on warm white documents.

## 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": "#A9B8C2",
  "background": "#F8F5EE",
  "border": "#D9E0E3",
  "error": "#A65D55",
  "info": "#8196A5",
  "muted": "#7A817F",
  "primary": "#2F3A42",
  "secondary": "#6F7D85",
  "success": "#7E9279",
  "surface": "#FFFDF8",
  "text": "#24292D",
  "warning": "#B5A06E"
}

Typography:

{
  "base_size": "16px",
  "body_font": "IBM Plex Sans",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&family=IBM+Plex+Sans:wght@400;450;500;600&family=Literata:opsz,wght@7..72,500;7..72,650&display=swap",
  "heading_font": "Literata",
  "letter_spacing": "-0.015em",
  "line_height": 1.55,
  "mono_font": "IBM Plex Mono",
  "scale_ratio": 1.2
}

## Visual character to preserve

- Use a warm-white page canvas with nested paper panels separated by 1px pale blue-gray hairlines and almost no shadow, making boundaries feel printed rather than boxed.
- Attach micro-analytics to the right margin as narrow ruled columns, vertical status ticks, and bracketed notes instead of standalone cards or dashboard tiles.
- Render data as word-sized graphics: 28-80px inline sparklines, tiny dot trails, tabular deltas, and badge-width counts aligned to text baselines.
- Use graphite text hierarchy with Literata document headings, IBM Plex Sans operational labels, and IBM Plex Mono numeric evidence blocks for high-resolution reading.
- Restrict status to low-contrast blue-gray, wheat, and sage marks with textureless flat fills, reserving red only for thin error underlines or one-pixel flags.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "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/margin-signal-sheets/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: Anchor every metric to a sentence, row, paragraph, or task it explains.; Use hairline separators, monospaced numbers, and margin brackets to create quiet hierarchy.; Prefer small temporal traces, confidence notes, and source counts over large charts.; Let progressive disclosure expand evidence only when the user asks for it.
- Do not: Do not build a grid of KPI cards, donut charts, or dashboard widgets.; Do not use saturated traffic-light colors or pulsing alert animation for routine states.; Do not mix arbitrary rounded cards; keep the committed paper geometry.; Do not let decorative sparklines appear without adjacent explanatory text.

## 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 MarginSignalSheetsShadcnKit() {
  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 Sheets</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": "desktop 1200px, tablet 768px, mobile 375px with rail-to-ribbon reflow",
  "grid": "A document-first grid: 260px context pane, flexible reading sheet, and 96px margin signal rail on desktop; rail collapses into inline ribbons below tablet width.",
  "whitespace": "Whitespace behaves like page margin: wide outer gutters, tight internal line spacing, and 16-24px between evidence groups."
}
preview shotscompatibility fallback
{
  "artifact": "katagami:shadcn-preview-shots",
  "version": "preview-shots-v1",
  "generator": "katagami-ui-compatibility-projection",
  "generatedBy": "katagami-ui-projection",
  "requiresVisualProfile": true,
  "schema": "katagami:shadcn-preview-shots/renderable-v1",
  "renderable": true,
  "language": {
    "id": "en-019edc14-a554-7a50-830e-a83f121157f8",
    "name": "Margin Signal Sheets",
    "slug": "margin-signal-sheets"
  },
  "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": [
    "Use a warm-white page canvas with nested paper panels separated by 1px pale blue-gray hairlines and almost no shadow, making boundaries feel printed rather than boxed.",
    "Attach micro-analytics to the right margin as narrow ruled columns, vertical status ticks, and bracketed notes instead of standalone cards or dashboard tiles.",
    "Render data as word-sized graphics: 28-80px inline sparklines, tiny dot trails, tabular deltas, and badge-width counts aligned to text baselines.",
    "Use graphite text hierarchy with Literata document headings, IBM Plex Sans operational labels, and IBM Plex Mono numeric evidence blocks for high-resolution reading.",
    "Restrict status to low-contrast blue-gray, wheat, and sage marks with textureless flat fills, reserving red only for thin error underlines or one-pixel flags."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "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": "Margin Signal Sheets 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": [
      "Anchor every metric to a sentence, row, paragraph, or task it explains.",
      "Use hairline separators, monospaced numbers, and margin brackets to create quiet hierarchy.",
      "Prefer small temporal traces, confidence notes, and source counts over large charts.",
      "Let progressive disclosure expand evidence only when the user asks for it."
    ],
    "dont": [
      "Do not build a grid of KPI cards, donut charts, or dashboard widgets.",
      "Do not use saturated traffic-light colors or pulsing alert animation for routine states.",
      "Do not mix arbitrary rounded cards; keep the committed paper geometry.",
      "Do not let decorative sparklines appear without adjacent explanatory text."
    ]
  }
}
related

More like this