back to gallery
design language·loom-note-field-v2

Loom Note Field

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
Loom Note Field is a quiet text-first workspace language for research notes, evidence panels, and non-dashboard information surfaces. It treats data as annotated reading material rather than chart furniture, using paper-warm planes, woven hairlines, and tiny tonal marks to create orientation without visual noise.
values
reading rhythm before decorationlow-contrast structure for sustained attentionevidence proximity and provenance claritysmall semantic accents instead of saturated dashboards
anti-values
×hero metrics and KPI dashboard chrome×generic white SaaS cards with blue primary buttons×heavy shadows gradients and glass effects
tokens
borders4 items
accent width
2px
character
low-contrast taupe seams, never black outlines
default width
1px
style
solid hairline with optional double-rule offset
colors12 items
accent
#A98F52
background
#F6F1E7
border
#D8CDBB
error
#A35B4D
info
#5F7288
muted
#777269
primary
#546D5A
secondary
#8E6F5A
success
#5F7A5B
surface
#FBF8F0
text
#2F302B
warning
#B08A45
motion3 items
duration
140ms
easing
cubic-bezier(0.2, 0, 0.1, 1)
philosophy
brief opacity and color changes only; calm workspace interactions should not move the reading surface
radii5 items
full
9999px
lg
10px
md
6px
none
0
sm
3px
shadows3 items
lg
0 10px 24px rgba(47,48,43,0.07)
md
0 1px 0 rgba(47,48,43,0.06), inset 0 0 0 1px rgba(216,205,187,0.46)
sm
0 1px 0 rgba(47,48,43,0.05)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
two overlaid repeating-linear-gradients that imply woven paper threads
card style
flat panels with 1px taupe seams, 6px radius, and no floating dashboard shadow
treatment
matte paper planes with low contrast woven fiber gradients
typography8 items
base size
16px
body font
Literata
google fonts url
https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,500;9..144,650&family=Literata:opsz,wght@7..72,400;7..72,500;7..72,600&family=IBM+Plex+Mono:wght@400;500&display=swap
heading font
Fraunces
letter spacing
-0.01em
line height
1.58
mono font
IBM Plex Mono
scale ratio
1.2
rules
composition
Compose screens as a reading desk: a slim context rail, a central annotated document stream, and a right evidence shelf. Avoid dashboard grids; every panel should support reading, comparison, or provenance.
density

Moderately dense text with a 12px baseline rhythm, compact controls, and deliberate whitespace gutters between reading columns.

hierarchy
Hierarchy comes from type size, rule weight, indentation, and muted metadata labels. Use accent color only for state and evidence relationships, not for decorative section branding.
signature patterns
Woven-page background created with crossed repeating-linear-gradients and a transparent dot field on body and panel surfaces.Evidence chips use tiny left-edge tonal ticks and mono source codes, turning data references into inline reading artifacts rather than badges.Double-rule dividers appear through pseudo-elements offset four pixels below primary hairlines to create quiet manuscript section breaks.Micro ledgers visualize status with three pixel vertical tonal marks aligned to text baselines, replacing large charts with notational data marks.
layout
breakpoints

Mobile <= 680px stacks rail, document, and evidence shelf; tablet <= 980px collapses the rail into a horizontal context strip.

grid

Desktop uses a 220px context rail, flexible document column, and 330px evidence shelf with 24px gutters on an 8px spacing system.

whitespace

Whitespace is narrow inside text groups and wider between evidence zones, preserving reading continuity while separating provenance layers.

guidance
do
  • Use warm off-white and taupe paper surfaces for sustained reading.
  • Keep charts small, inline, and tonal; prefer marks and ledgers over dashboard widgets.
  • Pair dense body copy with clear metadata rhythm and hairline separators.
  • Make accessibility states visible through border weight, underline, and text labels as well as color.
avoid
  • Do not use saturated blue SaaS primaries or rainbow analytics palettes.
  • Do not turn the workspace into a KPI dashboard with oversized metric cards.
  • Do not add glassmorphism, heavy shadows, or generic rounded marketing cards.
  • Do not leave evidence or data marks as unlabeled decorative dots.
katagami spec
# Loom Note Field

## Philosophy

Loom Note Field is a quiet text-first workspace language for research notes, evidence panels, and non-dashboard information surfaces. It treats data as annotated reading material rather than chart furniture, using paper-warm planes, woven hairlines, and tiny tonal marks to create orientation without visual noise.

### Values

- reading rhythm before decoration
- low-contrast structure for sustained attention
- evidence proximity and provenance clarity
- small semantic accents instead of saturated dashboards

### Anti-Values

- hero metrics and KPI dashboard chrome
- generic white SaaS cards with blue primary buttons
- heavy shadows gradients and glass effects

### Visual Character

- Use a warm paper background with crossed repeating-linear-gradient fiber texture at two and seven pixel intervals, kept low contrast so the surface reads woven rather than patterned.
- Separate sections with one pixel hairline borders in muted taupe and occasional double-rule dividers using pseudo-elements offset by four pixels for editorial rhythm.
- Represent data as small tonal ticks, ledger dots, and inline evidence chips instead of large charts, with accent colors limited to sage, clay, gold, and ink-blue semantic roles.
- Build text columns on a twelve pixel baseline grid with compact fourteen pixel body copy, generous line-height, and narrow uppercase metadata labels letter-spaced at 0.12em.
- Use shallow square-rounded containers with six pixel radius, no broad shadows, and inset paper seams to keep panels calm, flat, and knowledge-work oriented.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: low-contrast taupe seams, never black outlines
- **Default Width**: 1px
- **Style**: solid hairline with optional double-rule offset

### Colors

| Name | Value |
|------|-------|
| accent | `#A98F52` |
| background | `#F6F1E7` |
| border | `#D8CDBB` |
| error | `#A35B4D` |
| info | `#5F7288` |
| muted | `#777269` |
| primary | `#546D5A` |
| secondary | `#8E6F5A` |
| success | `#5F7A5B` |
| surface | `#FBF8F0` |
| text | `#2F302B` |
| warning | `#B08A45` |

### Motion

- **Duration**: 140ms
- **Easing**: cubic-bezier(0.2, 0, 0.1, 1)
- **Philosophy**: brief opacity and color changes only; calm workspace interactions should not move the reading surface

### Radii

- **Full**: 9999px
- **Lg**: 10px
- **Md**: 6px
- **None**: 0
- **Sm**: 3px

### Shadows

- **Lg**: 0 10px 24px rgba(47,48,43,0.07)
- **Md**: 0 1px 0 rgba(47,48,43,0.06), inset 0 0 0 1px rgba(216,205,187,0.46)
- **Sm**: 0 1px 0 rgba(47,48,43,0.05)

### Spacing

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

### Surfaces

- **Bg Pattern**: two overlaid repeating-linear-gradients that imply woven paper threads
- **Card Style**: flat panels with 1px taupe seams, 6px radius, and no floating dashboard shadow
- **Treatment**: matte paper planes with low contrast woven fiber gradients

### Typography

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

## Rules

### Composition

Compose screens as a reading desk: a slim context rail, a central annotated document stream, and a right evidence shelf. Avoid dashboard grids; every panel should support reading, comparison, or provenance.

### Density

Moderately dense text with a 12px baseline rhythm, compact controls, and deliberate whitespace gutters between reading columns.

### Hierarchy

Hierarchy comes from type size, rule weight, indentation, and muted metadata labels. Use accent color only for state and evidence relationships, not for decorative section branding.

### Signature Patterns

- Woven-page background created with crossed repeating-linear-gradients and a transparent dot field on body and panel surfaces.
- Evidence chips use tiny left-edge tonal ticks and mono source codes, turning data references into inline reading artifacts rather than badges.
- Double-rule dividers appear through pseudo-elements offset four pixels below primary hairlines to create quiet manuscript section breaks.
- Micro ledgers visualize status with three pixel vertical tonal marks aligned to text baselines, replacing large charts with notational data marks.

## Layout

### Breakpoints

Mobile <= 680px stacks rail, document, and evidence shelf; tablet <= 980px collapses the rail into a horizontal context strip.

### Grid

Desktop uses a 220px context rail, flexible document column, and 330px evidence shelf with 24px gutters on an 8px spacing system.

### Whitespace

Whitespace is narrow inside text groups and wider between evidence zones, preserving reading continuity while separating provenance layers.

## Guidance

### Do

- Use warm off-white and taupe paper surfaces for sustained reading.
- Keep charts small, inline, and tonal; prefer marks and ledgers over dashboard widgets.
- Pair dense body copy with clear metadata rhythm and hairline separators.
- Make accessibility states visible through border weight, underline, and text labels as well as color.

### Don't

- Do not use saturated blue SaaS primaries or rainbow analytics palettes.
- Do not turn the workspace into a KPI dashboard with oversized metric cards.
- Do not add glassmorphism, heavy shadows, or generic rounded marketing cards.
- Do not leave evidence or data marks as unlabeled decorative dots.
DESIGN.md
---
version: "alpha"
name: "Loom Note Field"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#A98F52"
  background: "#F6F1E7"
  border: "#D8CDBB"
  error: "#A35B4D"
  info: "#5F7288"
  muted: "#777269"
  primary: "#546D5A"
  secondary: "#8E6F5A"
  success: "#5F7A5B"
  surface: "#FBF8F0"
  text: "#2F302B"
  warning: "#B08A45"
typography:
  headline-lg:
    fontFamily: "Fraunces"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.01em"
  headline-md:
    fontFamily: "Fraunces"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.01em"
  body-md:
    fontFamily: "Literata"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.58
    letterSpacing: "-0.01em"
  label-md:
    fontFamily: "IBM Plex 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"
---

# Loom Note Field

## Overview

Loom Note Field is a quiet text-first workspace language for research notes, evidence panels, and non-dashboard information surfaces. It treats data as annotated reading material rather than chart furniture, using paper-warm planes, woven hairlines, and tiny tonal marks to create orientation without visual noise.

### Values

- reading rhythm before decoration
- low-contrast structure for sustained attention
- evidence proximity and provenance clarity
- small semantic accents instead of saturated dashboards

### Anti-Values

- hero metrics and KPI dashboard chrome
- generic white SaaS cards with blue primary buttons
- heavy shadows gradients and glass effects

### Visual Character

- Use a warm paper background with crossed repeating-linear-gradient fiber texture at two and seven pixel intervals, kept low contrast so the surface reads woven rather than patterned.
- Separate sections with one pixel hairline borders in muted taupe and occasional double-rule dividers using pseudo-elements offset by four pixels for editorial rhythm.
- Represent data as small tonal ticks, ledger dots, and inline evidence chips instead of large charts, with accent colors limited to sage, clay, gold, and ink-blue semantic roles.
- Build text columns on a twelve pixel baseline grid with compact fourteen pixel body copy, generous line-height, and narrow uppercase metadata labels letter-spaced at 0.12em.
- Use shallow square-rounded containers with six pixel radius, no broad shadows, and inset paper seams to keep panels calm, flat, and knowledge-work oriented.

## 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 | `#A98F52` |
| background | `#F6F1E7` |
| border | `#D8CDBB` |
| error | `#A35B4D` |
| info | `#5F7288` |
| muted | `#777269` |
| primary | `#546D5A` |
| secondary | `#8E6F5A` |
| success | `#5F7A5B` |
| surface | `#FBF8F0` |
| text | `#2F302B` |
| warning | `#B08A45` |

## Typography

- **Headline-Lg**: Fraunces, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Fraunces, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: Literata, 16px, weight 400, line-height 1.58.
- **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

Mobile <= 680px stacks rail, document, and evidence shelf; tablet <= 980px collapses the rail into a horizontal context strip.

### Grid

Desktop uses a 220px context rail, flexible document column, and 330px evidence shelf with 24px gutters on an 8px spacing system.

### Whitespace

Whitespace is narrow inside text groups and wider between evidence zones, preserving reading continuity while separating provenance layers.

## Elevation & Depth

### Shadows

- **Lg**: 0 10px 24px rgba(47,48,43,0.07)
- **Md**: 0 1px 0 rgba(47,48,43,0.06), inset 0 0 0 1px rgba(216,205,187,0.46)
- **Sm**: 0 1px 0 rgba(47,48,43,0.05)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `10px`
- **Md**: `6px`
- **None**: `0px`
- **Sm**: `3px`

### Surfaces

- **Bg Pattern**: two overlaid repeating-linear-gradients that imply woven paper threads
- **Card Style**: flat panels with 1px taupe seams, 6px radius, and no floating dashboard shadow
- **Treatment**: matte paper planes with low contrast woven fiber gradients

### Borders

- **Accent Width**: 2px
- **Character**: low-contrast taupe seams, never black outlines
- **Default Width**: 1px
- **Style**: solid hairline with optional double-rule offset

## Components

### Composition

Compose screens as a reading desk: a slim context rail, a central annotated document stream, and a right evidence shelf. Avoid dashboard grids; every panel should support reading, comparison, or provenance.

### Density

Moderately dense text with a 12px baseline rhythm, compact controls, and deliberate whitespace gutters between reading columns.

### Hierarchy

Hierarchy comes from type size, rule weight, indentation, and muted metadata labels. Use accent color only for state and evidence relationships, not for decorative section branding.

### Signature Patterns

- Woven-page background created with crossed repeating-linear-gradients and a transparent dot field on body and panel surfaces.
- Evidence chips use tiny left-edge tonal ticks and mono source codes, turning data references into inline reading artifacts rather than badges.
- Double-rule dividers appear through pseudo-elements offset four pixels below primary hairlines to create quiet manuscript section breaks.
- Micro ledgers visualize status with three pixel vertical tonal marks aligned to text baselines, replacing large charts with notational data marks.

## 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-019edcad-70df-74f2-b3aa-03b4049c771b/DESIGN.with-shadcn.md`.

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

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

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

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

## Do's and Don'ts

- Do Use warm off-white and taupe paper surfaces for sustained reading.
- Do Keep charts small, inline, and tonal; prefer marks and ledgers over dashboard widgets.
- Do Pair dense body copy with clear metadata rhythm and hairline separators.
- Do Make accessibility states visible through border weight, underline, and text labels as well as color.
- Don't Do not use saturated blue SaaS primaries or rainbow analytics palettes.
- Don't Do not turn the workspace into a KPI dashboard with oversized metric cards.
- Don't Do not add glassmorphism, heavy shadows, or generic rounded marketing cards.
- Don't Do not leave evidence or data marks as unlabeled decorative dots.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "loom-note-field-v2",
  "type": "registry:theme",
  "title": "Loom Note Field shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F6F1E7",
      "foreground": "#2F302B",
      "card": "#FBF8F0",
      "card-foreground": "#2F302B",
      "popover": "#FBF8F0",
      "popover-foreground": "#2F302B",
      "primary": "#546D5A",
      "primary-foreground": "#ffffff",
      "secondary": "#8E6F5A",
      "secondary-foreground": "#ffffff",
      "muted": "#777269",
      "muted-foreground": "#2F302B",
      "accent": "#A98F52",
      "accent-foreground": "#ffffff",
      "destructive": "#A35B4D",
      "border": "#D8CDBB",
      "input": "#D8CDBB",
      "ring": "#A98F52",
      "chart-1": "#546D5A",
      "chart-2": "#8E6F5A",
      "chart-3": "#A98F52",
      "chart-4": "#5F7A5B",
      "chart-5": "#B08A45",
      "sidebar": "#FBF8F0",
      "sidebar-foreground": "#2F302B",
      "sidebar-primary": "#546D5A",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5F7288",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8CDBB",
      "sidebar-ring": "#A98F52",
      "radius": "6px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#546D5A",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#A98F52",
      "accent-foreground": "#ffffff",
      "destructive": "#A35B4D",
      "border": "#303642",
      "input": "#303642",
      "ring": "#A98F52",
      "chart-1": "#546D5A",
      "chart-2": "#8E6F5A",
      "chart-3": "#A98F52",
      "chart-4": "#5F7A5B",
      "chart-5": "#B08A45",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#546D5A",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#A98F52",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#A98F52",
      "radius": "6px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edcad-70df-74f2-b3aa-03b4049c771b",
    "slug": "loom-note-field-v2",
    "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

Design Language Preview

Loom Note Field

Color Palette

primary
secondary
accent
background
surface
text
muted
border
error
success
warning
info

Typography

h1

Heading One

h2

Heading Two

h3

Heading Three

h4

Heading Four

body

Body text demonstrates the reading experience. Good typography is invisible — it lets the content speak without drawing attention to the letterforms themselves.

caption

Caption text for supplementary information and metadata.

code
const theme = applyTokens(designLanguage);
render(<App theme={theme} />);

Buttons

Form Controls

Navigation

tabs
Overview content area with contextual information about the design language.
segmented control
dropdown menu

Feedback & Status

badges
NewDefaultActivePendingErrorOutline
alerts
Info: A new version is available.
Success: Changes saved successfully.
Warning: Storage is almost full.
Error: Failed to process request.
progress
66% complete
tooltip
avatar
AKJDML

Containers & Overlays

card

Card Title

Cards group related content and actions. This example shows a basic content card with a title and description.

accordion

Design tokens are the atomic values of a design system — colors, spacing, typography, and other values stored as key-value pairs.

dialog
separator

Data Display

table
NameStatusCategoryScore
Neo BrutalismPublishedMaximalist94
Aero GlassDraftSpatial87
Signal UIReviewEnterprise91
stat cards
Languages
42
+12%
Elements
3,150
+8%
Usage
18.4k
+23%
DESIGN.md

at a glance

Palette

Typography

headline-lgFraunces · 28px · 700

The quick brown fox jumps

headline-mdFraunces · 23px · 600

The quick brown fox jumps

body-mdLiterata · 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
lg10px
md6px
none0px
sm3px
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: #F6F1E7;
  --foreground: #2F302B;
  --card: #FBF8F0;
  --card-foreground: #2F302B;
  --popover: #FBF8F0;
  --popover-foreground: #2F302B;
  --primary: #546D5A;
  --primary-foreground: #ffffff;
  --secondary: #8E6F5A;
  --secondary-foreground: #ffffff;
  --muted: #777269;
  --muted-foreground: #2F302B;
  --accent: #A98F52;
  --accent-foreground: #ffffff;
  --destructive: #A35B4D;
  --border: #D8CDBB;
  --input: #D8CDBB;
  --ring: #A98F52;
  --chart-1: #546D5A;
  --chart-2: #8E6F5A;
  --chart-3: #A98F52;
  --chart-4: #5F7A5B;
  --chart-5: #B08A45;
  --sidebar: #FBF8F0;
  --sidebar-foreground: #2F302B;
  --sidebar-primary: #546D5A;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #5F7288;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D8CDBB;
  --sidebar-ring: #A98F52;
  --radius: 6px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #546D5A;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #A98F52;
  --accent-foreground: #ffffff;
  --destructive: #A35B4D;
  --border: #303642;
  --input: #303642;
  --ring: #A98F52;
  --chart-1: #546D5A;
  --chart-2: #8E6F5A;
  --chart-3: #A98F52;
  --chart-4: #5F7A5B;
  --chart-5: #B08A45;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #546D5A;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #A98F52;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #A98F52;
  --radius: 6px;
}
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 LoomNoteFieldShadcnKit() {
  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">Loom Note Field</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": "loom-note-field-v2",
  "type": "registry:theme",
  "title": "Loom Note Field shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F6F1E7",
      "foreground": "#2F302B",
      "card": "#FBF8F0",
      "card-foreground": "#2F302B",
      "popover": "#FBF8F0",
      "popover-foreground": "#2F302B",
      "primary": "#546D5A",
      "primary-foreground": "#ffffff",
      "secondary": "#8E6F5A",
      "secondary-foreground": "#ffffff",
      "muted": "#777269",
      "muted-foreground": "#2F302B",
      "accent": "#A98F52",
      "accent-foreground": "#ffffff",
      "destructive": "#A35B4D",
      "border": "#D8CDBB",
      "input": "#D8CDBB",
      "ring": "#A98F52",
      "chart-1": "#546D5A",
      "chart-2": "#8E6F5A",
      "chart-3": "#A98F52",
      "chart-4": "#5F7A5B",
      "chart-5": "#B08A45",
      "sidebar": "#FBF8F0",
      "sidebar-foreground": "#2F302B",
      "sidebar-primary": "#546D5A",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5F7288",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8CDBB",
      "sidebar-ring": "#A98F52",
      "radius": "6px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#546D5A",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#A98F52",
      "accent-foreground": "#ffffff",
      "destructive": "#A35B4D",
      "border": "#303642",
      "input": "#303642",
      "ring": "#A98F52",
      "chart-1": "#546D5A",
      "chart-2": "#8E6F5A",
      "chart-3": "#A98F52",
      "chart-4": "#5F7A5B",
      "chart-5": "#B08A45",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#546D5A",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#A98F52",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#A98F52",
      "radius": "6px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edcad-70df-74f2-b3aa-03b4049c771b",
    "slug": "loom-note-field-v2",
    "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
# Loom Note Field shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019edcad-70df-74f2-b3aa-03b4049c771b`
Slug: `loom-note-field-v2`

## Intent

Loom Note Field is a quiet text-first workspace language for research notes, evidence panels, and non-dashboard information surfaces. It treats data as annotated reading material rather than chart furniture, using paper-warm planes, woven hairlines, and tiny tonal marks to create orientation without visual noise.

## 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": "#A98F52",
  "background": "#F6F1E7",
  "border": "#D8CDBB",
  "error": "#A35B4D",
  "info": "#5F7288",
  "muted": "#777269",
  "primary": "#546D5A",
  "secondary": "#8E6F5A",
  "success": "#5F7A5B",
  "surface": "#FBF8F0",
  "text": "#2F302B",
  "warning": "#B08A45"
}

Typography:

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

## Visual character to preserve

- Use a warm paper background with crossed repeating-linear-gradient fiber texture at two and seven pixel intervals, kept low contrast so the surface reads woven rather than patterned.
- Separate sections with one pixel hairline borders in muted taupe and occasional double-rule dividers using pseudo-elements offset by four pixels for editorial rhythm.
- Represent data as small tonal ticks, ledger dots, and inline evidence chips instead of large charts, with accent colors limited to sage, clay, gold, and ink-blue semantic roles.
- Build text columns on a twelve pixel baseline grid with compact fourteen pixel body copy, generous line-height, and narrow uppercase metadata labels letter-spaced at 0.12em.
- Use shallow square-rounded containers with six pixel radius, no broad shadows, and inset paper seams to keep panels calm, flat, and knowledge-work oriented.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "stickerBadges": true,
  "motion": "still",
  "density": "dense",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.

### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.

### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.

### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.

### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.

## Preview shots

- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/loom-note-field-v2/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use warm off-white and taupe paper surfaces for sustained reading.; Keep charts small, inline, and tonal; prefer marks and ledgers over dashboard widgets.; Pair dense body copy with clear metadata rhythm and hairline separators.; Make accessibility states visible through border weight, underline, and text labels as well as color.
- Do not: Do not use saturated blue SaaS primaries or rainbow analytics palettes.; Do not turn the workspace into a KPI dashboard with oversized metric cards.; Do not add glassmorphism, heavy shadows, or generic rounded marketing cards.; Do not leave evidence or data marks as unlabeled decorative dots.

## 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 LoomNoteFieldShadcnKit() {
  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">Loom Note Field</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

      <Tabs defaultValue="components">
        <TabsList>
          <TabsTrigger value="components">Components</TabsTrigger>
          <TabsTrigger value="states">States</TabsTrigger>
          <TabsTrigger value="export">Export</TabsTrigger>
        </TabsList>
      </Tabs>

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
```

## Layout notes

{
  "breakpoints": "Mobile <= 680px stacks rail, document, and evidence shelf; tablet <= 980px collapses the rail into a horizontal context strip.",
  "grid": "Desktop uses a 220px context rail, flexible document column, and 330px evidence shelf with 24px gutters on an 8px spacing system.",
  "whitespace": "Whitespace is narrow inside text groups and wider between evidence zones, preserving reading continuity while separating provenance layers."
}
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-019edcad-70df-74f2-b3aa-03b4049c771b",
    "name": "Loom Note Field",
    "slug": "loom-note-field-v2"
  },
  "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 paper background with crossed repeating-linear-gradient fiber texture at two and seven pixel intervals, kept low contrast so the surface reads woven rather than patterned.",
    "Separate sections with one pixel hairline borders in muted taupe and occasional double-rule dividers using pseudo-elements offset by four pixels for editorial rhythm.",
    "Represent data as small tonal ticks, ledger dots, and inline evidence chips instead of large charts, with accent colors limited to sage, clay, gold, and ink-blue semantic roles.",
    "Build text columns on a twelve pixel baseline grid with compact fourteen pixel body copy, generous line-height, and narrow uppercase metadata labels letter-spaced at 0.12em.",
    "Use shallow square-rounded containers with six pixel radius, no broad shadows, and inset paper seams to keep panels calm, flat, and knowledge-work oriented."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": true,
    "stickerBadges": true,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Loom Note Field launch room",
        "description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
        "primaryAction": "Apply theme",
        "secondaryAction": "Review states",
        "stats": [
          {
            "label": "components",
            "value": "16",
            "tone": "accent"
          },
          {
            "label": "states",
            "value": "ready"
          },
          {
            "label": "density",
            "value": "balanced",
            "tone": "warning"
          }
        ],
        "rows": [
          {
            "label": "Primary flow",
            "value": "mapped",
            "status": "active"
          },
          {
            "label": "Token coverage",
            "value": "semantic",
            "status": "synced"
          },
          {
            "label": "Responsive proof",
            "value": "queued",
            "status": "review"
          }
        ],
        "statuses": [
          "Active",
          "Synced",
          "Draft"
        ]
      }
    },
    {
      "id": "detail-editor",
      "title": "Detail editor",
      "viewport": "tablet",
      "primitives": [
        "button",
        "card",
        "input",
        "textarea",
        "select",
        "checkbox",
        "switch",
        "slider",
        "dialog",
        "sheet"
      ],
      "composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
      "mustShow": [
        "focus ring",
        "error or destructive state",
        "dialog or sheet treatment",
        "written guidance content"
      ],
      "avoid": [
        "unstyled browser controls",
        "floating cards inside cards",
        "missing labels"
      ],
      "scene": {
        "eyebrow": "editing flow",
        "headline": "Language recipe editor",
        "description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
        "primaryAction": "Save recipe",
        "secondaryAction": "Open sheet",
        "fields": [
          {
            "label": "Component family",
            "value": "Narrative cards"
          },
          {
            "label": "State treatment",
            "value": "Visible focus + validation"
          },
          {
            "label": "Motion",
            "value": "Small lift, no opacity-only fade"
          }
        ],
        "statuses": [
          "Focus",
          "Invalid",
          "Confirmed"
        ]
      }
    },
    {
      "id": "data-operations",
      "title": "Data operations",
      "viewport": "mobile",
      "primitives": [
        "button",
        "tabs",
        "badge",
        "dropdown-menu",
        "table",
        "tooltip",
        "separator"
      ],
      "composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
      "mustShow": [
        "responsive reflow",
        "dense row styling",
        "menu affordance",
        "status badge system"
      ],
      "avoid": [
        "desktop-only tables",
        "text overflow",
        "default shadcn spacing without Katagami character"
      ],
      "scene": {
        "eyebrow": "operations",
        "headline": "Compact review queue",
        "description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
        "primaryAction": "Resolve",
        "secondaryAction": "Filter",
        "rows": [
          {
            "label": "Button hierarchy",
            "value": "approved",
            "status": "ok"
          },
          {
            "label": "Table rhythm",
            "value": "needs pass",
            "status": "watch"
          },
          {
            "label": "Empty state",
            "value": "designed",
            "status": "done"
          }
        ],
        "statuses": [
          "Queued",
          "Blocked",
          "Done"
        ]
      }
    }
  ],
  "componentRecipes": [
    {
      "primitive": "button",
      "intent": "Prove action hierarchy, focus, disabled, and destructive states."
    },
    {
      "primitive": "card",
      "intent": "Carry the language surface, border, elevation, and density rules."
    },
    {
      "primitive": "input",
      "intent": "Show labels, focus rings, validation, and spacing rhythm."
    },
    {
      "primitive": "textarea",
      "intent": "Show longer guidance, validation copy, and writing density."
    },
    {
      "primitive": "select",
      "intent": "Show filtering, selection contrast, and menu trigger styling."
    },
    {
      "primitive": "dialog",
      "intent": "Show centered decision states and overlay treatment."
    },
    {
      "primitive": "sheet",
      "intent": "Show contextual side panels and responsive editing."
    },
    {
      "primitive": "tabs",
      "intent": "Show navigational structure and active/inactive contrast."
    },
    {
      "primitive": "badge",
      "intent": "Show compact status vocabulary and semantic colors."
    },
    {
      "primitive": "separator",
      "intent": "Show section rhythm without generic gray dividers."
    },
    {
      "primitive": "checkbox",
      "intent": "Show binary selection with visible focus and checked states."
    },
    {
      "primitive": "switch",
      "intent": "Show settings toggles and on/off contrast."
    },
    {
      "primitive": "slider",
      "intent": "Show numeric adjustment with track/thumb styling."
    },
    {
      "primitive": "tooltip",
      "intent": "Show concise explanation styling above compact controls."
    },
    {
      "primitive": "dropdown-menu",
      "intent": "Show action menus, destructive items, and grouped choices."
    },
    {
      "primitive": "table",
      "intent": "Show dense operational data, separators, row states, and responsive behavior."
    }
  ],
  "qualityRules": {
    "do": [
      "Use warm off-white and taupe paper surfaces for sustained reading.",
      "Keep charts small, inline, and tonal; prefer marks and ledgers over dashboard widgets.",
      "Pair dense body copy with clear metadata rhythm and hairline separators.",
      "Make accessibility states visible through border weight, underline, and text labels as well as color."
    ],
    "dont": [
      "Do not use saturated blue SaaS primaries or rainbow analytics palettes.",
      "Do not turn the workspace into a KPI dashboard with oversized metric cards.",
      "Do not add glassmorphism, heavy shadows, or generic rounded marketing cards.",
      "Do not leave evidence or data marks as unlabeled decorative dots."
    ]
  }
}