back to gallery
design language·calm-operational-ribbons-aya

Calm Operational Ribbons

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
Calm Operational Ribbons is a text-first interface language for analytic signal that lives inside working documents, briefs, records, and operational queues without turning the page into a dashboard.
values
Evidence remains adjacent to the sentence, decision, or field it explains.Status is visible at the edge before it interrupts the center of attention.Metrics are treated as annotations, not as hero objects or decorative charts.Color communicates state sparingly through muted green, amber, and blue signals.
anti-values
×Dashboard walls of cards, KPI tiles, gauges, and saturated chart panels.×Floating notifications, loud gradients, and decorative analytics disconnected from workflow.×Dense grid chrome that makes every number compete for priority.
tokens
borders4 items
accent width
3px
character
quiet dividers and state ribbons; borders are semantic edges, not decoration
default width
1px
style
solid hairline
colors12 items
accent
#5E7D9A
background
#F6F3EC
border
#D8D1C3
error
#B45E52
info
#5D7E9D
muted
#7A8179
primary
#4E6B5D
secondary
#8A6E3D
success
#5E7C58
surface
#FFFDF8
text
#26312C
warning
#B8873F
motion3 items
duration
140ms
easing
cubic-bezier(0.2, 0, 0.1, 1)
philosophy
Only peripheral signals fade or nudge into place; primary document content stays still.
radii5 items
full
9999px
lg
10px
md
6px
none
0
sm
3px
shadows3 items
lg
0 18px 44px rgba(72,64,48,0.11)
md
0 10px 26px rgba(72,64,48,0.08)
sm
0 1px 0 rgba(38,49,44,0.05)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
subtle repeating horizontal paper rules every 32px plus a soft blue marginal wash
card style
flat document panels with 1px borders, inner hairline separators, and almost no lift
treatment
matte paper surfaces on a warm neutral canvas with faint ruled-line texture
typography8 items
base size
16px
body font
Source Serif 4
google fonts url
https://fonts.googleapis.com/css2?family=Alegreya+Sans:wght@500;700&family=IBM+Plex+Mono:wght@400;500&family=Source+Serif+4:opsz,wght@8..60,400;8..60,600&display=swap
heading font
Alegreya Sans
letter spacing
-0.01em
line height
1.56
mono font
IBM Plex Mono
scale ratio
1.2
rules
composition

Begin with a readable document spine, place analytic signals inline with text, then reserve a narrow right rail for context summaries and peripheral operations.

density

Moderately dense but calm: many small evidence marks are permitted when each has a semantic anchor and generous line-height.

hierarchy

Typographic hierarchy leads; signals earn attention through proximity, small caps labels, and ribbon color rather than scale or chart saturation.

signature patterns
Inline metric chips combine a monospace value, tiny SVG sparkline, and two-word natural-language state inside a 24px-high pill.Ribboned document blocks use a 3px left border plus a pale top rule to encode success, warning, info, or error without creating card stacks.Marginal indicators sit in a right-side evidence rail as dot-led micro-timelines aligned to the document sections they summarize.Operational tables use text-first rows with small badges and word-sized trend strokes instead of separate chart cells or KPI cards.
layout
breakpoints

Desktop 1200px+, tablet 720-1199px with stacked rail below the active section, mobile below 720px as a single document stream.

grid

Desktop uses a 12-column page with an 8-column document spine, 3-column evidence rail, and one column of breathing room.

whitespace

Whitespace is line-based and editorial: 24px section gaps, 12px inline signal gaps, and generous margins around the document canvas.

guidance
do
  • Attach metrics directly to text, rows, fields, or decisions they clarify.
  • Use muted green, amber, and blue only for semantic status ribbons, badges, and tiny trend strokes.
  • Prefer progressive disclosure, marginal summaries, and inline sparklines over separate dashboard regions.
  • Keep charts word-sized unless the user explicitly asks for deeper analysis.
avoid
  • Do not build KPI card grids, oversized chart panels, or dashboard headers.
  • Do not use saturated color fills, glossy shadows, or animated notification noise.
  • Do not detach analytic evidence from the workflow object it supports.
  • Do not let badges become decorative confetti; each one must encode a state or count.
katagami spec
# Calm Operational Ribbons

## Philosophy

Calm Operational Ribbons is a text-first interface language for analytic signal that lives inside working documents, briefs, records, and operational queues without turning the page into a dashboard.

### Values

- Evidence remains adjacent to the sentence, decision, or field it explains.
- Status is visible at the edge before it interrupts the center of attention.
- Metrics are treated as annotations, not as hero objects or decorative charts.
- Color communicates state sparingly through muted green, amber, and blue signals.

### Anti-Values

- Dashboard walls of cards, KPI tiles, gauges, and saturated chart panels.
- Floating notifications, loud gradients, and decorative analytics disconnected from workflow.
- Dense grid chrome that makes every number compete for priority.

### Visual Character

- Documents use a warm off-white canvas with narrow 1px hairline section rules and inset paper panels instead of elevated dashboard cards.
- Operational state appears as slim left-edge ribbons, top hairline bands, and small rounded badges attached to paragraphs, rows, and field labels.
- Sparklines are word-sized inline SVG strokes with no axes, occupying the cap-height rhythm beside text and tabular labels.
- Side context panels are structured like marginalia with vertical micro-timelines, tiny dot indicators, and muted blue dividers rather than chart containers.

## Tokens

### Borders

- **Accent Width**: 3px
- **Character**: quiet dividers and state ribbons; borders are semantic edges, not decoration
- **Default Width**: 1px
- **Style**: solid hairline

### Colors

| Name | Value |
|------|-------|
| accent | `#5E7D9A` |
| background | `#F6F3EC` |
| border | `#D8D1C3` |
| error | `#B45E52` |
| info | `#5D7E9D` |
| muted | `#7A8179` |
| primary | `#4E6B5D` |
| secondary | `#8A6E3D` |
| success | `#5E7C58` |
| surface | `#FFFDF8` |
| text | `#26312C` |
| warning | `#B8873F` |

### Motion

- **Duration**: 140ms
- **Easing**: cubic-bezier(0.2, 0, 0.1, 1)
- **Philosophy**: Only peripheral signals fade or nudge into place; primary document content stays still.

### Radii

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

### Shadows

- **Lg**: 0 18px 44px rgba(72,64,48,0.11)
- **Md**: 0 10px 26px rgba(72,64,48,0.08)
- **Sm**: 0 1px 0 rgba(38,49,44,0.05)

### Spacing

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

### Surfaces

- **Bg Pattern**: subtle repeating horizontal paper rules every 32px plus a soft blue marginal wash
- **Card Style**: flat document panels with 1px borders, inner hairline separators, and almost no lift
- **Treatment**: matte paper surfaces on a warm neutral canvas with faint ruled-line texture

### Typography

- **Base Size**: 16px
- **Body Font**: Source Serif 4
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Alegreya+Sans:wght@500;700&family=IBM+Plex+Mono:wght@400;500&family=Source+Serif+4:opsz,wght@8..60,400;8..60,600&display=swap
- **Heading Font**: Alegreya Sans
- **Letter Spacing**: -0.01em
- **Line Height**: 1.56
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.2

## Rules

### Composition

Begin with a readable document spine, place analytic signals inline with text, then reserve a narrow right rail for context summaries and peripheral operations.

### Density

Moderately dense but calm: many small evidence marks are permitted when each has a semantic anchor and generous line-height.

### Hierarchy

Typographic hierarchy leads; signals earn attention through proximity, small caps labels, and ribbon color rather than scale or chart saturation.

### Signature Patterns

- Inline metric chips combine a monospace value, tiny SVG sparkline, and two-word natural-language state inside a 24px-high pill.
- Ribboned document blocks use a 3px left border plus a pale top rule to encode success, warning, info, or error without creating card stacks.
- Marginal indicators sit in a right-side evidence rail as dot-led micro-timelines aligned to the document sections they summarize.
- Operational tables use text-first rows with small badges and word-sized trend strokes instead of separate chart cells or KPI cards.

## Layout

### Breakpoints

Desktop 1200px+, tablet 720-1199px with stacked rail below the active section, mobile below 720px as a single document stream.

### Grid

Desktop uses a 12-column page with an 8-column document spine, 3-column evidence rail, and one column of breathing room.

### Whitespace

Whitespace is line-based and editorial: 24px section gaps, 12px inline signal gaps, and generous margins around the document canvas.

## Guidance

### Do

- Attach metrics directly to text, rows, fields, or decisions they clarify.
- Use muted green, amber, and blue only for semantic status ribbons, badges, and tiny trend strokes.
- Prefer progressive disclosure, marginal summaries, and inline sparklines over separate dashboard regions.
- Keep charts word-sized unless the user explicitly asks for deeper analysis.

### Don't

- Do not build KPI card grids, oversized chart panels, or dashboard headers.
- Do not use saturated color fills, glossy shadows, or animated notification noise.
- Do not detach analytic evidence from the workflow object it supports.
- Do not let badges become decorative confetti; each one must encode a state or count.
DESIGN.md
---
version: "alpha"
name: "Calm Operational Ribbons"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#5E7D9A"
  background: "#F6F3EC"
  border: "#D8D1C3"
  error: "#B45E52"
  info: "#5D7E9D"
  muted: "#7A8179"
  primary: "#4E6B5D"
  secondary: "#8A6E3D"
  success: "#5E7C58"
  surface: "#FFFDF8"
  text: "#26312C"
  warning: "#B8873F"
typography:
  headline-lg:
    fontFamily: "Alegreya Sans"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.01em"
  headline-md:
    fontFamily: "Alegreya Sans"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.01em"
  body-md:
    fontFamily: "Source Serif 4"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.56
    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"
---

# Calm Operational Ribbons

## Overview

Calm Operational Ribbons is a text-first interface language for analytic signal that lives inside working documents, briefs, records, and operational queues without turning the page into a dashboard.

### Values

- Evidence remains adjacent to the sentence, decision, or field it explains.
- Status is visible at the edge before it interrupts the center of attention.
- Metrics are treated as annotations, not as hero objects or decorative charts.
- Color communicates state sparingly through muted green, amber, and blue signals.

### Anti-Values

- Dashboard walls of cards, KPI tiles, gauges, and saturated chart panels.
- Floating notifications, loud gradients, and decorative analytics disconnected from workflow.
- Dense grid chrome that makes every number compete for priority.

### Visual Character

- Documents use a warm off-white canvas with narrow 1px hairline section rules and inset paper panels instead of elevated dashboard cards.
- Operational state appears as slim left-edge ribbons, top hairline bands, and small rounded badges attached to paragraphs, rows, and field labels.
- Sparklines are word-sized inline SVG strokes with no axes, occupying the cap-height rhythm beside text and tabular labels.
- Side context panels are structured like marginalia with vertical micro-timelines, tiny dot indicators, and muted blue dividers rather than chart containers.

## 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 | `#5E7D9A` |
| background | `#F6F3EC` |
| border | `#D8D1C3` |
| error | `#B45E52` |
| info | `#5D7E9D` |
| muted | `#7A8179` |
| primary | `#4E6B5D` |
| secondary | `#8A6E3D` |
| success | `#5E7C58` |
| surface | `#FFFDF8` |
| text | `#26312C` |
| warning | `#B8873F` |

## Typography

- **Headline-Lg**: Alegreya Sans, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Alegreya Sans, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: Source Serif 4, 16px, weight 400, line-height 1.56.
- **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 720-1199px with stacked rail below the active section, mobile below 720px as a single document stream.

### Grid

Desktop uses a 12-column page with an 8-column document spine, 3-column evidence rail, and one column of breathing room.

### Whitespace

Whitespace is line-based and editorial: 24px section gaps, 12px inline signal gaps, and generous margins around the document canvas.

## Elevation & Depth

### Shadows

- **Lg**: 0 18px 44px rgba(72,64,48,0.11)
- **Md**: 0 10px 26px rgba(72,64,48,0.08)
- **Sm**: 0 1px 0 rgba(38,49,44,0.05)

## Shapes

### Rounded

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

### Surfaces

- **Bg Pattern**: subtle repeating horizontal paper rules every 32px plus a soft blue marginal wash
- **Card Style**: flat document panels with 1px borders, inner hairline separators, and almost no lift
- **Treatment**: matte paper surfaces on a warm neutral canvas with faint ruled-line texture

### Borders

- **Accent Width**: 3px
- **Character**: quiet dividers and state ribbons; borders are semantic edges, not decoration
- **Default Width**: 1px
- **Style**: solid hairline

## Components

### Composition

Begin with a readable document spine, place analytic signals inline with text, then reserve a narrow right rail for context summaries and peripheral operations.

### Density

Moderately dense but calm: many small evidence marks are permitted when each has a semantic anchor and generous line-height.

### Hierarchy

Typographic hierarchy leads; signals earn attention through proximity, small caps labels, and ribbon color rather than scale or chart saturation.

### Signature Patterns

- Inline metric chips combine a monospace value, tiny SVG sparkline, and two-word natural-language state inside a 24px-high pill.
- Ribboned document blocks use a 3px left border plus a pale top rule to encode success, warning, info, or error without creating card stacks.
- Marginal indicators sit in a right-side evidence rail as dot-led micro-timelines aligned to the document sections they summarize.
- Operational tables use text-first rows with small badges and word-sized trend strokes instead of separate chart cells or KPI cards.

## 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-019edc18-8258-7210-9cb2-06d1467410af/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 Attach metrics directly to text, rows, fields, or decisions they clarify.
- Do Use muted green, amber, and blue only for semantic status ribbons, badges, and tiny trend strokes.
- Do Prefer progressive disclosure, marginal summaries, and inline sparklines over separate dashboard regions.
- Do Keep charts word-sized unless the user explicitly asks for deeper analysis.
- Don't Do not build KPI card grids, oversized chart panels, or dashboard headers.
- Don't Do not use saturated color fills, glossy shadows, or animated notification noise.
- Don't Do not detach analytic evidence from the workflow object it supports.
- Don't Do not let badges become decorative confetti; each one must encode a state or count.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "calm-operational-ribbons-aya",
  "type": "registry:theme",
  "title": "Calm Operational Ribbons shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F6F3EC",
      "foreground": "#26312C",
      "card": "#FFFDF8",
      "card-foreground": "#26312C",
      "popover": "#FFFDF8",
      "popover-foreground": "#26312C",
      "primary": "#4E6B5D",
      "primary-foreground": "#ffffff",
      "secondary": "#8A6E3D",
      "secondary-foreground": "#ffffff",
      "muted": "#7A8179",
      "muted-foreground": "#26312C",
      "accent": "#5E7D9A",
      "accent-foreground": "#ffffff",
      "destructive": "#B45E52",
      "border": "#D8D1C3",
      "input": "#D8D1C3",
      "ring": "#5E7D9A",
      "chart-1": "#4E6B5D",
      "chart-2": "#8A6E3D",
      "chart-3": "#5E7D9A",
      "chart-4": "#5E7C58",
      "chart-5": "#B8873F",
      "sidebar": "#FFFDF8",
      "sidebar-foreground": "#26312C",
      "sidebar-primary": "#4E6B5D",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5D7E9D",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8D1C3",
      "sidebar-ring": "#5E7D9A",
      "radius": "6px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#4E6B5D",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#5E7D9A",
      "accent-foreground": "#ffffff",
      "destructive": "#B45E52",
      "border": "#303642",
      "input": "#303642",
      "ring": "#5E7D9A",
      "chart-1": "#4E6B5D",
      "chart-2": "#8A6E3D",
      "chart-3": "#5E7D9A",
      "chart-4": "#5E7C58",
      "chart-5": "#B8873F",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#4E6B5D",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5E7D9A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#5E7D9A",
      "radius": "6px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edc18-8258-7210-9cb2-06d1467410af",
    "slug": "calm-operational-ribbons-aya",
    "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

Calm Operational Ribbons

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-lgAlegreya Sans · 28px · 700

The quick brown fox jumps

headline-mdAlegreya Sans · 23px · 600

The quick brown fox jumps

body-mdSource Serif 4 · 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: #F6F3EC;
  --foreground: #26312C;
  --card: #FFFDF8;
  --card-foreground: #26312C;
  --popover: #FFFDF8;
  --popover-foreground: #26312C;
  --primary: #4E6B5D;
  --primary-foreground: #ffffff;
  --secondary: #8A6E3D;
  --secondary-foreground: #ffffff;
  --muted: #7A8179;
  --muted-foreground: #26312C;
  --accent: #5E7D9A;
  --accent-foreground: #ffffff;
  --destructive: #B45E52;
  --border: #D8D1C3;
  --input: #D8D1C3;
  --ring: #5E7D9A;
  --chart-1: #4E6B5D;
  --chart-2: #8A6E3D;
  --chart-3: #5E7D9A;
  --chart-4: #5E7C58;
  --chart-5: #B8873F;
  --sidebar: #FFFDF8;
  --sidebar-foreground: #26312C;
  --sidebar-primary: #4E6B5D;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #5D7E9D;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D8D1C3;
  --sidebar-ring: #5E7D9A;
  --radius: 6px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #4E6B5D;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #5E7D9A;
  --accent-foreground: #ffffff;
  --destructive: #B45E52;
  --border: #303642;
  --input: #303642;
  --ring: #5E7D9A;
  --chart-1: #4E6B5D;
  --chart-2: #8A6E3D;
  --chart-3: #5E7D9A;
  --chart-4: #5E7C58;
  --chart-5: #B8873F;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #4E6B5D;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #5E7D9A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #5E7D9A;
  --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 CalmOperationalRibbonsShadcnKit() {
  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">Calm Operational Ribbons</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": "calm-operational-ribbons-aya",
  "type": "registry:theme",
  "title": "Calm Operational Ribbons shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F6F3EC",
      "foreground": "#26312C",
      "card": "#FFFDF8",
      "card-foreground": "#26312C",
      "popover": "#FFFDF8",
      "popover-foreground": "#26312C",
      "primary": "#4E6B5D",
      "primary-foreground": "#ffffff",
      "secondary": "#8A6E3D",
      "secondary-foreground": "#ffffff",
      "muted": "#7A8179",
      "muted-foreground": "#26312C",
      "accent": "#5E7D9A",
      "accent-foreground": "#ffffff",
      "destructive": "#B45E52",
      "border": "#D8D1C3",
      "input": "#D8D1C3",
      "ring": "#5E7D9A",
      "chart-1": "#4E6B5D",
      "chart-2": "#8A6E3D",
      "chart-3": "#5E7D9A",
      "chart-4": "#5E7C58",
      "chart-5": "#B8873F",
      "sidebar": "#FFFDF8",
      "sidebar-foreground": "#26312C",
      "sidebar-primary": "#4E6B5D",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5D7E9D",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8D1C3",
      "sidebar-ring": "#5E7D9A",
      "radius": "6px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#4E6B5D",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#5E7D9A",
      "accent-foreground": "#ffffff",
      "destructive": "#B45E52",
      "border": "#303642",
      "input": "#303642",
      "ring": "#5E7D9A",
      "chart-1": "#4E6B5D",
      "chart-2": "#8A6E3D",
      "chart-3": "#5E7D9A",
      "chart-4": "#5E7C58",
      "chart-5": "#B8873F",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#4E6B5D",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5E7D9A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#5E7D9A",
      "radius": "6px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edc18-8258-7210-9cb2-06d1467410af",
    "slug": "calm-operational-ribbons-aya",
    "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
# Calm Operational Ribbons shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019edc18-8258-7210-9cb2-06d1467410af`
Slug: `calm-operational-ribbons-aya`

## Intent

Calm Operational Ribbons is a text-first interface language for analytic signal that lives inside working documents, briefs, records, and operational queues without turning the page into a dashboard.

## Required primitives

- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

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

## Token cues

Colors:

{
  "accent": "#5E7D9A",
  "background": "#F6F3EC",
  "border": "#D8D1C3",
  "error": "#B45E52",
  "info": "#5D7E9D",
  "muted": "#7A8179",
  "primary": "#4E6B5D",
  "secondary": "#8A6E3D",
  "success": "#5E7C58",
  "surface": "#FFFDF8",
  "text": "#26312C",
  "warning": "#B8873F"
}

Typography:

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

## Visual character to preserve

- Documents use a warm off-white canvas with narrow 1px hairline section rules and inset paper panels instead of elevated dashboard cards.
- Operational state appears as slim left-edge ribbons, top hairline bands, and small rounded badges attached to paragraphs, rows, and field labels.
- Sparklines are word-sized inline SVG strokes with no axes, occupying the cap-height rhythm beside text and tabular labels.
- Side context panels are structured like marginalia with vertical micro-timelines, tiny dot indicators, and muted blue dividers rather than chart containers.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "pebble",
  "border": "solid",
  "underlay": false,
  "grain": true,
  "stickerBadges": true,
  "motion": "lift",
  "density": "balanced",
  "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/calm-operational-ribbons-aya/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: Attach metrics directly to text, rows, fields, or decisions they clarify.; Use muted green, amber, and blue only for semantic status ribbons, badges, and tiny trend strokes.; Prefer progressive disclosure, marginal summaries, and inline sparklines over separate dashboard regions.; Keep charts word-sized unless the user explicitly asks for deeper analysis.
- Do not: Do not build KPI card grids, oversized chart panels, or dashboard headers.; Do not use saturated color fills, glossy shadows, or animated notification noise.; Do not detach analytic evidence from the workflow object it supports.; Do not let badges become decorative confetti; each one must encode a state or count.

## 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 CalmOperationalRibbonsShadcnKit() {
  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">Calm Operational Ribbons</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 720-1199px with stacked rail below the active section, mobile below 720px as a single document stream.",
  "grid": "Desktop uses a 12-column page with an 8-column document spine, 3-column evidence rail, and one column of breathing room.",
  "whitespace": "Whitespace is line-based and editorial: 24px section gaps, 12px inline signal gaps, and generous margins around the document canvas."
}
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-019edc18-8258-7210-9cb2-06d1467410af",
    "name": "Calm Operational Ribbons",
    "slug": "calm-operational-ribbons-aya"
  },
  "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": [
    "Documents use a warm off-white canvas with narrow 1px hairline section rules and inset paper panels instead of elevated dashboard cards.",
    "Operational state appears as slim left-edge ribbons, top hairline bands, and small rounded badges attached to paragraphs, rows, and field labels.",
    "Sparklines are word-sized inline SVG strokes with no axes, occupying the cap-height rhythm beside text and tabular labels.",
    "Side context panels are structured like marginalia with vertical micro-timelines, tiny dot indicators, and muted blue dividers rather than chart containers."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "pebble",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": true,
    "motion": "still",
    "density": "balanced",
    "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": "Calm Operational Ribbons 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": [
      "Attach metrics directly to text, rows, fields, or decisions they clarify.",
      "Use muted green, amber, and blue only for semantic status ribbons, badges, and tiny trend strokes.",
      "Prefer progressive disclosure, marginal summaries, and inline sparklines over separate dashboard regions.",
      "Keep charts word-sized unless the user explicitly asks for deeper analysis."
    ],
    "dont": [
      "Do not build KPI card grids, oversized chart panels, or dashboard headers.",
      "Do not use saturated color fills, glossy shadows, or animated notification noise.",
      "Do not detach analytic evidence from the workflow object it supports.",
      "Do not let badges become decorative confetti; each one must encode a state or count."
    ]
  }
}