Captioned Clarity
A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.
Download DESIGN.md
Portable DESIGN.md source of truth for most agents and apps.
specification
philosophy
tokens
colors12 items
typography8 items
- heading font
- Chivo
- body font
- Noto Sans
- mono font
- Victor Mono
- base size
- 16px
- scale ratio
- 1.25
- line height
- 1.55
- letter spacing
- -0.02em
- google fonts url
- https://fonts.googleapis.com/css2?family=Chivo:wght@500;700;800;900&family=Noto+Sans:wght@400;500;700&family=Victor+Mono:wght@500;700&display=swap
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64, 96
radii5 items
- none
- 0
- sm
- 0
- md
- 16px
- lg
- 24px
- full
- 9999px
shadows3 items
- sm
- 4px 4px 0 #07111C
- md
- 8px 8px 0 #07111C
- lg
- 12px 12px 0 #07111C
surfaces3 items
- treatment
- Warm paper background with white editorial cards, hard ink outlines, and small blocks of blue or amber used only for meaning.
- card style
- Cards are bordered with 3px solid {colors.border}, radius {radii.md}, and offset slab shadows instead of soft elevation.
- bg pattern
- Subtle 24px measurement grid using low-opacity ink lines to imply diagram paper without reducing text contrast.
borders4 items
- default width
- 3px
- accent width
- 6px
- style
- solid
- character
- Ink-heavy editorial rules, caption dividers, and connector strokes that make structure visible.
motion3 items
- duration
- 160ms
- easing
- cubic-bezier(0.2, 0, 0, 1)
- philosophy
- Motion is functional and brief: controls shift by 2px, callouts highlight, and panels reveal in reading order without decorative drifting.
rules
Use a figure-first composition: each screen begins with a clear editorial claim, then pairs an annotated visual panel with explanation, evidence, and next action. Keep graphics in bounded cards, align connector labels to a visible grid, reserve accent color for current state or warning, and make reading order explicit from headline to figure number to caption to action.
Hierarchy is built with strong typographic contrast and labelled structure: Chivo headings at heavy weights, uppercase mono figure labels, medium body text, caption strips, numbered callouts, and status pills. Important messages must appear in text as well as imagery so the graphic never carries meaning alone.
Moderate density with spacious captions and compact diagrams; every viewport should show a complete claim, one major figure, and at least one practical action without crowding.
layout
Twelve-column desktop grid with 24px gutters and max-width 1180px; figure panels span seven columns while interpretation cards span five.
Desktop 1200px+, tablet 768-1199px with two-column cards, mobile below 640px stacking figure, caption, evidence, and actions in one column.
Use 24px internal card padding, 32px section gaps, and 64px page rhythm so high-contrast borders never feel cramped.
Information is chunked into one illustrated claim per panel; dense data is summarized in short rows with labels and never hidden in imagery.
On smaller screens, callout labels move below graphics, connector lines shorten, and action groups wrap into full-width buttons.
guidance
- Write the message in text first, then create a graphic that supports the same message.
- Use caption rails, figure numbers, and labels on every editorial graphic.
- Keep contrast high between text, fills, rules, and background; test accent text against the surface.
- Use blue, amber, green, and red semantically rather than decoratively.
- Prefer diagrams, sequences, comparisons, and annotated product states over symbolic scenes.
- Repeat the same border widths, callout dots, and label pills across product and marketing contexts.
- Provide alt text or adjacent explanatory copy for every informative image.
- Use the measurement grid only as a quiet structural cue, not as a busy texture.
- Do not use unlabeled abstract shapes as the only explanation of a concept.
- Do not rely on pale tints, low-contrast captions, or color alone to distinguish states.
- Do not introduce mascots, decorative characters, or whimsical scenes when a diagram would be clearer.
- Do not mix soft shadows, glass effects, or arbitrary radii with the ink-rule system.
- Do not overload one figure with more than four callouts or multiple competing messages.
- Do not place important copy inside image assets where it cannot reflow or be read by assistive technology.
- Do not use accent yellow behind small body text unless paired with ink text and sufficient padding.
katagami spec
# Captioned Clarity
## Philosophy
Captioned Clarity is an accessible editorial-graphics language for product and brand communication where every image behaves like evidence: labelled, high-contrast, and composed to explain one idea quickly. It borrows from public-service diagrams, newspaper explainers, and design-system illustration guidance, favoring purposeful imagery over mood decoration so readers can understand status, sequence, and consequence without decoding style tricks.
### Values
- Comprehension before charm: graphics must clarify a decision, state, or story point before they add personality.
- Purposeful restraint: every rule, fill, caption, and connector earns its place by improving scan speed or confidence.
- Accessible contrast: palettes, labels, and focus states are designed for legibility under low vision, glare, and fast product contexts.
- Systematic editorial rhythm: repeated caption rails, figure numbers, and measured grids make varied graphics feel like one publication.
- Plain-language trust: imagery avoids metaphor when direct annotation, comparison, or sequence would communicate more honestly.
- Reusable product storytelling: the same primitives work for onboarding, empty states, release notes, reports, and interface education.
### Anti-Values
- Decorative spot illustrations that consume space without explaining user benefit or product meaning.
- Low-contrast pastel palettes, mystery icons, unlabeled abstractions, or illustration-only messages.
- Over-rendered characters, gratuitous gradients, and visual jokes that age faster than the interface around them.
- Dense infographic clutter where every element competes instead of guiding the eye through a clear reading order.
### Visual Character
- High-contrast cream, ink, blue, and amber blocks with every illustrated panel framed by a 3px black rule and an attached caption strip.
- Editorial figure cards use a two-column explanation grid: left-side annotated graphic primitives, right-side plain-language interpretation and status evidence.
- Graphic objects are built from flat SVG-like CSS shapes, numbered callout dots, connector lines, and label pills rather than decorative characters.
- Section hierarchy relies on compressed uppercase eyebrow labels, large sturdy sans headings, and generous body line-height for comprehension-first scanning.
- Interactive controls and data rows use visible focus outlines, square edges with only 16px large radii, and no decorative shadows beyond offset ink slabs.
## Tokens
### Colors
| Name | Value |
|------|-------|
| primary | `#0B1B2B` |
| secondary | `#0057D9` |
| accent | `#FFB000` |
| background | `#F6F1E4` |
| surface | `#FFFDF6` |
| text | `#07111C` |
| muted | `#53606B` |
| border | `#07111C` |
| error | `#B42318` |
| success | `#127A3A` |
| warning | `#9A5B00` |
| info | `#0057D9` |
### Typography
- **Heading Font**: Chivo
- **Body Font**: Noto Sans
- **Mono Font**: Victor Mono
- **Base Size**: 16px
- **Scale Ratio**: 1.25
- **Line Height**: 1.55
- **Letter Spacing**: -0.02em
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Chivo:wght@500;700;800;900&family=Noto+Sans:wght@400;500;700&family=Victor+Mono:wght@500;700&display=swap
### Spacing
- **Base**: 8px
- **Scale**: [4,8,12,16,24,32,48,64,96]
### Radii
- **None**: 0
- **Sm**: 0
- **Md**: 16px
- **Lg**: 24px
- **Full**: 9999px
### Shadows
- **Sm**: 4px 4px 0 #07111C
- **Md**: 8px 8px 0 #07111C
- **Lg**: 12px 12px 0 #07111C
### Surfaces
- **Treatment**: Warm paper background with white editorial cards, hard ink outlines, and small blocks of blue or amber used only for meaning.
- **Card Style**: Cards are bordered with 3px solid {colors.border}, radius {radii.md}, and offset slab shadows instead of soft elevation.
- **Bg Pattern**: Subtle 24px measurement grid using low-opacity ink lines to imply diagram paper without reducing text contrast.
### Borders
- **Default Width**: 3px
- **Accent Width**: 6px
- **Style**: solid
- **Character**: Ink-heavy editorial rules, caption dividers, and connector strokes that make structure visible.
### Motion
- **Duration**: 160ms
- **Easing**: cubic-bezier(0.2, 0, 0, 1)
- **Philosophy**: Motion is functional and brief: controls shift by 2px, callouts highlight, and panels reveal in reading order without decorative drifting.
## Rules
### Composition
Use a figure-first composition: each screen begins with a clear editorial claim, then pairs an annotated visual panel with explanation, evidence, and next action. Keep graphics in bounded cards, align connector labels to a visible grid, reserve accent color for current state or warning, and make reading order explicit from headline to figure number to caption to action.
### Hierarchy
Hierarchy is built with strong typographic contrast and labelled structure: Chivo headings at heavy weights, uppercase mono figure labels, medium body text, caption strips, numbered callouts, and status pills. Important messages must appear in text as well as imagery so the graphic never carries meaning alone.
### Density
Moderate density with spacious captions and compact diagrams; every viewport should show a complete claim, one major figure, and at least one practical action without crowding.
### Signature Patterns
- Attached caption rails: each illustration card has a black top or bottom strip containing a figure number, source-like label, and one-sentence explanation.
- Numbered callout dots connected by orthogonal ink lines to plain-language labels, ensuring the visual can be read as a diagram rather than decoration.
- Offset slab shadows in pure ink under key panels and buttons, creating a print-cutout feel without soft blur or ornamental texture.
- Contrast-coded evidence blocks where blue means informational path, amber means attention, green means resolved, and red is reserved for actual failure.
- Background measurement grid and alignment ticks appear only behind figure areas, giving editorial precision while leaving reading surfaces quiet.
## Layout
### Grid
Twelve-column desktop grid with 24px gutters and max-width 1180px; figure panels span seven columns while interpretation cards span five.
### Breakpoints
Desktop 1200px+, tablet 768-1199px with two-column cards, mobile below 640px stacking figure, caption, evidence, and actions in one column.
### Whitespace
Use 24px internal card padding, 32px section gaps, and 64px page rhythm so high-contrast borders never feel cramped.
### Density
Information is chunked into one illustrated claim per panel; dense data is summarized in short rows with labels and never hidden in imagery.
### Responsive
On smaller screens, callout labels move below graphics, connector lines shorten, and action groups wrap into full-width buttons.
## Guidance
### Do
- Write the message in text first, then create a graphic that supports the same message.
- Use caption rails, figure numbers, and labels on every editorial graphic.
- Keep contrast high between text, fills, rules, and background; test accent text against the surface.
- Use blue, amber, green, and red semantically rather than decoratively.
- Prefer diagrams, sequences, comparisons, and annotated product states over symbolic scenes.
- Repeat the same border widths, callout dots, and label pills across product and marketing contexts.
- Provide alt text or adjacent explanatory copy for every informative image.
- Use the measurement grid only as a quiet structural cue, not as a busy texture.
### Don't
- Do not use unlabeled abstract shapes as the only explanation of a concept.
- Do not rely on pale tints, low-contrast captions, or color alone to distinguish states.
- Do not introduce mascots, decorative characters, or whimsical scenes when a diagram would be clearer.
- Do not mix soft shadows, glass effects, or arbitrary radii with the ink-rule system.
- Do not overload one figure with more than four callouts or multiple competing messages.
- Do not place important copy inside image assets where it cannot reflow or be read by assistive technology.
- Do not use accent yellow behind small body text unless paired with ink text and sufficient padding.
### Usage Context
Best for product education, release notes, help-center illustrations, onboarding, empty states, public-service dashboards, and editorial brand reports where trust and comprehension matter more than decoration.
### Accessibility
All meaningful graphics require text equivalents, visible labels, keyboard focus outlines, high contrast, and non-color indicators such as icons, rules, captions, and numbering.
DESIGN.md
---
version: "alpha"
name: "Captioned Clarity"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
primary: "#0B1B2B"
secondary: "#0057D9"
accent: "#FFB000"
background: "#F6F1E4"
surface: "#FFFDF6"
text: "#07111C"
muted: "#53606B"
border: "#07111C"
error: "#B42318"
success: "#127A3A"
warning: "#9A5B00"
info: "#0057D9"
typography:
headline-lg:
fontFamily: "Chivo"
fontSize: "1.953rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.02em"
headline-md:
fontFamily: "Chivo"
fontSize: "1.563rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.02em"
body-md:
fontFamily: "Noto Sans"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.55
letterSpacing: "-0.02em"
label-md:
fontFamily: "Victor Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
none: "0px"
sm: "0px"
md: "16px"
lg: "24px"
full: "9999px"
spacing:
base: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
step-8: "96px"
components:
color-reference-primary:
backgroundColor: "{colors.primary}"
color-reference-secondary:
backgroundColor: "{colors.secondary}"
color-reference-accent:
backgroundColor: "{colors.accent}"
color-reference-background:
backgroundColor: "{colors.background}"
color-reference-surface:
backgroundColor: "{colors.surface}"
color-reference-text:
backgroundColor: "{colors.text}"
color-reference-muted:
backgroundColor: "{colors.muted}"
color-reference-border:
backgroundColor: "{colors.border}"
color-reference-error:
backgroundColor: "{colors.error}"
color-reference-success:
backgroundColor: "{colors.success}"
color-reference-warning:
backgroundColor: "{colors.warning}"
color-reference-info:
backgroundColor: "{colors.info}"
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"
---
# Captioned Clarity
## Overview
Captioned Clarity is an accessible editorial-graphics language for product and brand communication where every image behaves like evidence: labelled, high-contrast, and composed to explain one idea quickly. It borrows from public-service diagrams, newspaper explainers, and design-system illustration guidance, favoring purposeful imagery over mood decoration so readers can understand status, sequence, and consequence without decoding style tricks.
### Values
- Comprehension before charm: graphics must clarify a decision, state, or story point before they add personality.
- Purposeful restraint: every rule, fill, caption, and connector earns its place by improving scan speed or confidence.
- Accessible contrast: palettes, labels, and focus states are designed for legibility under low vision, glare, and fast product contexts.
- Systematic editorial rhythm: repeated caption rails, figure numbers, and measured grids make varied graphics feel like one publication.
- Plain-language trust: imagery avoids metaphor when direct annotation, comparison, or sequence would communicate more honestly.
- Reusable product storytelling: the same primitives work for onboarding, empty states, release notes, reports, and interface education.
### Anti-Values
- Decorative spot illustrations that consume space without explaining user benefit or product meaning.
- Low-contrast pastel palettes, mystery icons, unlabeled abstractions, or illustration-only messages.
- Over-rendered characters, gratuitous gradients, and visual jokes that age faster than the interface around them.
- Dense infographic clutter where every element competes instead of guiding the eye through a clear reading order.
### Visual Character
- High-contrast cream, ink, blue, and amber blocks with every illustrated panel framed by a 3px black rule and an attached caption strip.
- Editorial figure cards use a two-column explanation grid: left-side annotated graphic primitives, right-side plain-language interpretation and status evidence.
- Graphic objects are built from flat SVG-like CSS shapes, numbered callout dots, connector lines, and label pills rather than decorative characters.
- Section hierarchy relies on compressed uppercase eyebrow labels, large sturdy sans headings, and generous body line-height for comprehension-first scanning.
- Interactive controls and data rows use visible focus outlines, square edges with only 16px large radii, and no decorative shadows beyond offset ink slabs.
## Colors
Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.
| Token | Value |
|-------|-------|
| primary | `#0B1B2B` |
| secondary | `#0057D9` |
| accent | `#FFB000` |
| background | `#F6F1E4` |
| surface | `#FFFDF6` |
| text | `#07111C` |
| muted | `#53606B` |
| border | `#07111C` |
| error | `#B42318` |
| success | `#127A3A` |
| warning | `#9A5B00` |
| info | `#0057D9` |
## Typography
- **Headline-Lg**: Chivo, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Chivo, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Noto Sans, 16px, weight 400, line-height 1.55.
- **Label-Md**: Victor Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
- **Step-8**: `96px`
### Grid
Twelve-column desktop grid with 24px gutters and max-width 1180px; figure panels span seven columns while interpretation cards span five.
### Breakpoints
Desktop 1200px+, tablet 768-1199px with two-column cards, mobile below 640px stacking figure, caption, evidence, and actions in one column.
### Whitespace
Use 24px internal card padding, 32px section gaps, and 64px page rhythm so high-contrast borders never feel cramped.
### Density
Information is chunked into one illustrated claim per panel; dense data is summarized in short rows with labels and never hidden in imagery.
### Responsive
On smaller screens, callout labels move below graphics, connector lines shorten, and action groups wrap into full-width buttons.
## Elevation & Depth
### Shadows
- **Sm**: 4px 4px 0 #07111C
- **Md**: 8px 8px 0 #07111C
- **Lg**: 12px 12px 0 #07111C
## Shapes
### Rounded
- **None**: `0px`
- **Sm**: `0px`
- **Md**: `16px`
- **Lg**: `24px`
- **Full**: `9999px`
### Surfaces
- **Treatment**: Warm paper background with white editorial cards, hard ink outlines, and small blocks of blue or amber used only for meaning.
- **Card Style**: Cards are bordered with 3px solid {colors.border}, radius {radii.md}, and offset slab shadows instead of soft elevation.
- **Bg Pattern**: Subtle 24px measurement grid using low-opacity ink lines to imply diagram paper without reducing text contrast.
### Borders
- **Default Width**: 3px
- **Accent Width**: 6px
- **Style**: solid
- **Character**: Ink-heavy editorial rules, caption dividers, and connector strokes that make structure visible.
## Components
### Composition
Use a figure-first composition: each screen begins with a clear editorial claim, then pairs an annotated visual panel with explanation, evidence, and next action. Keep graphics in bounded cards, align connector labels to a visible grid, reserve accent color for current state or warning, and make reading order explicit from headline to figure number to caption to action.
### Hierarchy
Hierarchy is built with strong typographic contrast and labelled structure: Chivo headings at heavy weights, uppercase mono figure labels, medium body text, caption strips, numbered callouts, and status pills. Important messages must appear in text as well as imagery so the graphic never carries meaning alone.
### Density
Moderate density with spacious captions and compact diagrams; every viewport should show a complete claim, one major figure, and at least one practical action without crowding.
### Signature Patterns
- Attached caption rails: each illustration card has a black top or bottom strip containing a figure number, source-like label, and one-sentence explanation.
- Numbered callout dots connected by orthogonal ink lines to plain-language labels, ensuring the visual can be read as a diagram rather than decoration.
- Offset slab shadows in pure ink under key panels and buttons, creating a print-cutout feel without soft blur or ornamental texture.
- Contrast-coded evidence blocks where blue means informational path, amber means attention, green means resolved, and red is reserved for actual failure.
- Background measurement grid and alignment ticks appear only behind figure areas, giving editorial precision while leaving reading surfaces quiet.
## 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-019dddaf-11d9-76b2-9ba0-99c9e75929e9/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 Write the message in text first, then create a graphic that supports the same message.
- Do Use caption rails, figure numbers, and labels on every editorial graphic.
- Do Keep contrast high between text, fills, rules, and background; test accent text against the surface.
- Do Use blue, amber, green, and red semantically rather than decoratively.
- Do Prefer diagrams, sequences, comparisons, and annotated product states over symbolic scenes.
- Do Repeat the same border widths, callout dots, and label pills across product and marketing contexts.
- Do Provide alt text or adjacent explanatory copy for every informative image.
- Do Use the measurement grid only as a quiet structural cue, not as a busy texture.
- Don't Do not use unlabeled abstract shapes as the only explanation of a concept.
- Don't Do not rely on pale tints, low-contrast captions, or color alone to distinguish states.
- Don't Do not introduce mascots, decorative characters, or whimsical scenes when a diagram would be clearer.
- Don't Do not mix soft shadows, glass effects, or arbitrary radii with the ink-rule system.
- Don't Do not overload one figure with more than four callouts or multiple competing messages.
- Don't Do not place important copy inside image assets where it cannot reflow or be read by assistive technology.
- Don't Do not use accent yellow behind small body text unless paired with ink text and sufficient padding.
### Usage Context
Best for product education, release notes, help-center illustrations, onboarding, empty states, public-service dashboards, and editorial brand reports where trust and comprehension matter more than decoration.
### Accessibility
All meaningful graphics require text equivalents, visible labels, keyboard focus outlines, high contrast, and non-color indicators such as icons, rules, captions, and numbering.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "captioned-clarity",
"type": "registry:theme",
"title": "Captioned Clarity shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F6F1E4",
"foreground": "#07111C",
"card": "#FFFDF6",
"card-foreground": "#07111C",
"popover": "#FFFDF6",
"popover-foreground": "#07111C",
"primary": "#0B1B2B",
"primary-foreground": "#ffffff",
"secondary": "#0057D9",
"secondary-foreground": "#ffffff",
"muted": "#53606B",
"muted-foreground": "#07111C",
"accent": "#FFB000",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#07111C",
"input": "#07111C",
"ring": "#FFB000",
"chart-1": "#0B1B2B",
"chart-2": "#0057D9",
"chart-3": "#FFB000",
"chart-4": "#127A3A",
"chart-5": "#9A5B00",
"sidebar": "#FFFDF6",
"sidebar-foreground": "#07111C",
"sidebar-primary": "#0B1B2B",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#0057D9",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#07111C",
"sidebar-ring": "#FFB000",
"radius": "16px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#0B1B2B",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#FFB000",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#303642",
"input": "#303642",
"ring": "#FFB000",
"chart-1": "#0B1B2B",
"chart-2": "#0057D9",
"chart-3": "#FFB000",
"chart-4": "#127A3A",
"chart-5": "#9A5B00",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#0B1B2B",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#FFB000",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#FFB000",
"radius": "16px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019dddaf-11d9-76b2-9ba0-99c9e75929e9",
"slug": "captioned-clarity",
"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": {
"colors": [
"accent",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
],
"spacing": [
"base",
"scale"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"motion": [
"duration",
"easing",
"philosophy"
]
}
}
}
```embodiments
at a glance
Typography
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Components
Components rendered with this language’s tokens — colors, type, and rounded corners as specified.
Spacing
- base8px
- xs4px
- sm8px
- md12px
- lg16px
- xl24px
- 2xl32px
- 3xl48px
- 4xl64px
- step-896px
Shape
implementation kit
DESIGN.md with shadcn
Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.
advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #F6F1E4;
--foreground: #07111C;
--card: #FFFDF6;
--card-foreground: #07111C;
--popover: #FFFDF6;
--popover-foreground: #07111C;
--primary: #0B1B2B;
--primary-foreground: #ffffff;
--secondary: #0057D9;
--secondary-foreground: #ffffff;
--muted: #53606B;
--muted-foreground: #07111C;
--accent: #FFB000;
--accent-foreground: #ffffff;
--destructive: #B42318;
--border: #07111C;
--input: #07111C;
--ring: #FFB000;
--chart-1: #0B1B2B;
--chart-2: #0057D9;
--chart-3: #FFB000;
--chart-4: #127A3A;
--chart-5: #9A5B00;
--sidebar: #FFFDF6;
--sidebar-foreground: #07111C;
--sidebar-primary: #0B1B2B;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #0057D9;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #07111C;
--sidebar-ring: #FFB000;
--radius: 16px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #0B1B2B;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #FFB000;
--accent-foreground: #ffffff;
--destructive: #B42318;
--border: #303642;
--input: #303642;
--ring: #FFB000;
--chart-1: #0B1B2B;
--chart-2: #0057D9;
--chart-3: #FFB000;
--chart-4: #127A3A;
--chart-5: #9A5B00;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #0B1B2B;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #FFB000;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #FFB000;
--radius: 16px;
}
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 CaptionedClarityShadcnKit() {
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">Captioned Clarity</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "captioned-clarity",
"type": "registry:theme",
"title": "Captioned Clarity shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F6F1E4",
"foreground": "#07111C",
"card": "#FFFDF6",
"card-foreground": "#07111C",
"popover": "#FFFDF6",
"popover-foreground": "#07111C",
"primary": "#0B1B2B",
"primary-foreground": "#ffffff",
"secondary": "#0057D9",
"secondary-foreground": "#ffffff",
"muted": "#53606B",
"muted-foreground": "#07111C",
"accent": "#FFB000",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#07111C",
"input": "#07111C",
"ring": "#FFB000",
"chart-1": "#0B1B2B",
"chart-2": "#0057D9",
"chart-3": "#FFB000",
"chart-4": "#127A3A",
"chart-5": "#9A5B00",
"sidebar": "#FFFDF6",
"sidebar-foreground": "#07111C",
"sidebar-primary": "#0B1B2B",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#0057D9",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#07111C",
"sidebar-ring": "#FFB000",
"radius": "16px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#0B1B2B",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#FFB000",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#303642",
"input": "#303642",
"ring": "#FFB000",
"chart-1": "#0B1B2B",
"chart-2": "#0057D9",
"chart-3": "#FFB000",
"chart-4": "#127A3A",
"chart-5": "#9A5B00",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#0B1B2B",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#FFB000",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#FFB000",
"radius": "16px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019dddaf-11d9-76b2-9ba0-99c9e75929e9",
"slug": "captioned-clarity",
"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": {
"colors": [
"accent",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
],
"spacing": [
"base",
"scale"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"motion": [
"duration",
"easing",
"philosophy"
]
}
}
}
# Captioned Clarity shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019dddaf-11d9-76b2-9ba0-99c9e75929e9`
Slug: `captioned-clarity`
## Intent
Captioned Clarity is an accessible editorial-graphics language for product and brand communication where every image behaves like evidence: labelled, high-contrast, and composed to explain one idea quickly. It borrows from public-service diagrams, newspaper explainers, and design-system illustration guidance, favoring purposeful imagery over mood decoration so readers can understand status, sequence, and consequence without decoding style tricks.
## 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:
{
"primary": "#0B1B2B",
"secondary": "#0057D9",
"accent": "#FFB000",
"background": "#F6F1E4",
"surface": "#FFFDF6",
"text": "#07111C",
"muted": "#53606B",
"border": "#07111C",
"error": "#B42318",
"success": "#127A3A",
"warning": "#9A5B00",
"info": "#0057D9"
}
Typography:
{
"heading_font": "Chivo",
"body_font": "Noto Sans",
"mono_font": "Victor Mono",
"base_size": "16px",
"scale_ratio": 1.25,
"line_height": 1.55,
"letter_spacing": "-0.02em",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Chivo:wght@500;700;800;900&family=Noto+Sans:wght@400;500;700&family=Victor+Mono:wght@500;700&display=swap"
}
## Visual character to preserve
- High-contrast cream, ink, blue, and amber blocks with every illustrated panel framed by a 3px black rule and an attached caption strip.
- Editorial figure cards use a two-column explanation grid: left-side annotated graphic primitives, right-side plain-language interpretation and status evidence.
- Graphic objects are built from flat SVG-like CSS shapes, numbered callout dots, connector lines, and label pills rather than decorative characters.
- Section hierarchy relies on compressed uppercase eyebrow labels, large sturdy sans headings, and generous body line-height for comprehension-first scanning.
- Interactive controls and data rows use visible focus outlines, square edges with only 16px large radii, and no decorative shadows beyond offset ink slabs.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": false,
"motion": "still",
"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/captioned-clarity/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: Write the message in text first, then create a graphic that supports the same message.; Use caption rails, figure numbers, and labels on every editorial graphic.; Keep contrast high between text, fills, rules, and background; test accent text against the surface.; Use blue, amber, green, and red semantically rather than decoratively.; Prefer diagrams, sequences, comparisons, and annotated product states over symbolic scenes.; Repeat the same border widths, callout dots, and label pills across product and marketing contexts.; Provide alt text or adjacent explanatory copy for every informative image.; Use the measurement grid only as a quiet structural cue, not as a busy texture.
- Do not: Do not use unlabeled abstract shapes as the only explanation of a concept.; Do not rely on pale tints, low-contrast captions, or color alone to distinguish states.; Do not introduce mascots, decorative characters, or whimsical scenes when a diagram would be clearer.; Do not mix soft shadows, glass effects, or arbitrary radii with the ink-rule system.; Do not overload one figure with more than four callouts or multiple competing messages.; Do not place important copy inside image assets where it cannot reflow or be read by assistive technology.; Do not use accent yellow behind small body text unless paired with ink text and sufficient padding.
## 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 CaptionedClarityShadcnKit() {
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">Captioned Clarity</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
{
"grid": "Twelve-column desktop grid with 24px gutters and max-width 1180px; figure panels span seven columns while interpretation cards span five.",
"breakpoints": "Desktop 1200px+, tablet 768-1199px with two-column cards, mobile below 640px stacking figure, caption, evidence, and actions in one column.",
"whitespace": "Use 24px internal card padding, 32px section gaps, and 64px page rhythm so high-contrast borders never feel cramped.",
"density": "Information is chunked into one illustrated claim per panel; dense data is summarized in short rows with labels and never hidden in imagery.",
"responsive": "On smaller screens, callout labels move below graphics, connector lines shorten, and action groups wrap into full-width buttons."
}
{
"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-019dddaf-11d9-76b2-9ba0-99c9e75929e9",
"name": "Captioned Clarity",
"slug": "captioned-clarity"
},
"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": [
"High-contrast cream, ink, blue, and amber blocks with every illustrated panel framed by a 3px black rule and an attached caption strip.",
"Editorial figure cards use a two-column explanation grid: left-side annotated graphic primitives, right-side plain-language interpretation and status evidence.",
"Graphic objects are built from flat SVG-like CSS shapes, numbered callout dots, connector lines, and label pills rather than decorative characters.",
"Section hierarchy relies on compressed uppercase eyebrow labels, large sturdy sans headings, and generous body line-height for comprehension-first scanning.",
"Interactive controls and data rows use visible focus outlines, square edges with only 16px large radii, and no decorative shadows beyond offset ink slabs."
],
"visualProfile": {
"family": "editorial",
"material": "flat",
"contour": "pebble",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": false,
"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": "Captioned Clarity 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": [
"Write the message in text first, then create a graphic that supports the same message.",
"Use caption rails, figure numbers, and labels on every editorial graphic.",
"Keep contrast high between text, fills, rules, and background; test accent text against the surface.",
"Use blue, amber, green, and red semantically rather than decoratively.",
"Prefer diagrams, sequences, comparisons, and annotated product states over symbolic scenes.",
"Repeat the same border widths, callout dots, and label pills across product and marketing contexts.",
"Provide alt text or adjacent explanatory copy for every informative image.",
"Use the measurement grid only as a quiet structural cue, not as a busy texture."
],
"dont": [
"Do not use unlabeled abstract shapes as the only explanation of a concept.",
"Do not rely on pale tints, low-contrast captions, or color alone to distinguish states.",
"Do not introduce mascots, decorative characters, or whimsical scenes when a diagram would be clearer.",
"Do not mix soft shadows, glass effects, or arbitrary radii with the ink-rule system.",
"Do not overload one figure with more than four callouts or multiple competing messages.",
"Do not place important copy inside image assets where it cannot reflow or be read by assistive technology.",
"Do not use accent yellow behind small body text unless paired with ink text and sufficient padding."
]
}
}