back to gallery
design language·kanso-context-weave

Kanso Context Weave

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
Kanso Context Weave is a contemporary Japanese SaaS language for teams reading, comparing, and connecting many pieces of context without visual noise. It treats the interface like a calm stack of annotated paper: low-chrome navigation, exact typography, restrained rules, warm amber and clay signals, and generous line-height that lets dense enterprise information remain humane.
values
reading-first hierarchyquiet operational confidencepaper-like material honestycomponent consistency across dense workflowsaccessible contrast with warm restraint
anti-values
×decorative dashboard spectacle×floating glass cards and heavy shadows×low-contrast gray text used as a style crutch×over-rounded generic SaaS controls
tokens
borders4 items
accent width
3px
character
Borders behave like printed rules: quiet separators first, decoration never.
default width
1px
style
solid hairlines with occasional dotted connector rules
colors12 items
accent
#C9823B
background
#F7F1E7
border
#D8CDBC
error
#B85B50
info
#5F7486
muted
#6F7470
primary
#3F463F
secondary
#8A6F55
success
#5E7D65
surface
#FFFDF8
text
#2F3332
warning
#C78A3D
motion3 items
duration
160ms
easing
cubic-bezier(0.2, 0, 0.1, 1)
philosophy
Small focus and hover state changes only: amber rule darkens, paper lifts by one pixel, no playful motion.
radii5 items
full
9999px
lg
10px
md
6px
none
0
sm
3px
shadows3 items
lg
0 18px 42px rgba(63, 70, 63, 0.10)
md
0 10px 24px rgba(63, 70, 63, 0.07)
sm
0 1px 0 rgba(63, 70, 63, 0.06)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
Layered radial paper speckles and a sparse 32px baseline grid at 4% opacity.
card style
Rectangular low-radius papers with 1px taupe borders, occasional amber left rule, and extremely soft contact shadow.
treatment
Warm ivory base with faint paper grain, flat white paper panels, and no glass or gradient cards.
typography8 items
base size
16px
body font
BIZ UDPGothic
google fonts url
https://fonts.googleapis.com/css2?family=BIZ+UDPGothic:wght@400;700&family=IBM+Plex+Mono:wght@400;500;600&display=swap
heading font
BIZ UDPGothic
letter spacing
-0.012em
line height
1.68
mono font
IBM Plex Mono
scale ratio
1.2
rules
composition
Compose screens as a low-chrome left rail, a measured reading column, and a comparison/context column. Align content to ruled sections rather than floating decorative modules.
density

Supports information-dense enterprise work through generous line-height, tight component chrome, and strong grouping by rule, not by large blank cards.

hierarchy
Lead with readable headings and prose summaries, then tabular metadata, then actions. Color is reserved for state and relationship, not for making every card compete.
signature patterns
Context-thread rails: a 1px vertical border with small amber nodes links notes, sources, owners, and decisions across stacked sections.Paper rule headers: section titles sit on a taupe bottom rule with mono metadata aligned right and a tiny clay square marker.Quiet comparison bands: side-by-side records use alternating ivory strips and tabular numerals instead of colorful chart decoration.Low-chrome navigation rail: active location is indicated by one vertical amber rule and bold ink text, never a filled rounded button.Semantic square chips: status badges use muted calm fills, square corners, and left inset dots to preserve legibility at dense sizes.
layout
breakpoints

mobile 375px, tablet 768px, desktop 1200px, wide 1440px

grid

Desktop uses a 72px navigation rail, 12-column content grid, and a 360px context aside; tablet collapses to rail plus stacked panels.

whitespace

Whitespace is measured and vertical: 24px between sections, 12px within dense rows, and ample line-height for long text.

guidance
do
  • Use real labels, summaries, owners, timestamps, and source relationships in product screens.
  • Prefer hairlines, rule headers, and connector rails over decorative cards.
  • Keep accent color limited to active navigation, key decisions, focus rings, and critical comparison markers.
  • Maintain WCAG-conscious contrast with ink text on ivory surfaces.
avoid
  • Do not use glassmorphism, neon gradients, or heavy drop shadows.
  • Do not replace reading hierarchy with icon-heavy navigation or generic metric tiles.
  • Do not make every badge saturated; semantic colors must remain calm and legible.
  • Do not center long enterprise text or use cramped line-height.
katagami spec
# Kanso Context Weave

## Philosophy

Kanso Context Weave is a contemporary Japanese SaaS language for teams reading, comparing, and connecting many pieces of context without visual noise. It treats the interface like a calm stack of annotated paper: low-chrome navigation, exact typography, restrained rules, warm amber and clay signals, and generous line-height that lets dense enterprise information remain humane.

### Values

- reading-first hierarchy
- quiet operational confidence
- paper-like material honesty
- component consistency across dense workflows
- accessible contrast with warm restraint

### Anti-Values

- decorative dashboard spectacle
- floating glass cards and heavy shadows
- low-contrast gray text used as a style crutch
- over-rounded generic SaaS controls

### Visual Character

- Use an ivory page background with subtle repeating paper-fiber radial gradients and flat off-white panels instead of glossy cards.
- Build hierarchy with 1px ink-gray and warm-taupe ruled lines, including vertical connector rails between related context blocks.
- Set BIZ UDPGothic at generous 1.68 body line-height with compact negative heading tracking and tabular numeric details.
- Apply small amber/clay left-edge markers and square status chips as the only saturated accents in otherwise neutral surfaces.
- Keep navigation as a narrow low-chrome rail with text labels, hairline dividers, and no filled active pill except a thin amber rule.

## Tokens

### Borders

- **Accent Width**: 3px
- **Character**: Borders behave like printed rules: quiet separators first, decoration never.
- **Default Width**: 1px
- **Style**: solid hairlines with occasional dotted connector rules

### Colors

| Name | Value |
|------|-------|
| accent | `#C9823B` |
| background | `#F7F1E7` |
| border | `#D8CDBC` |
| error | `#B85B50` |
| info | `#5F7486` |
| muted | `#6F7470` |
| primary | `#3F463F` |
| secondary | `#8A6F55` |
| success | `#5E7D65` |
| surface | `#FFFDF8` |
| text | `#2F3332` |
| warning | `#C78A3D` |

### Motion

- **Duration**: 160ms
- **Easing**: cubic-bezier(0.2, 0, 0.1, 1)
- **Philosophy**: Small focus and hover state changes only: amber rule darkens, paper lifts by one pixel, no playful motion.

### Radii

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

### Shadows

- **Lg**: 0 18px 42px rgba(63, 70, 63, 0.10)
- **Md**: 0 10px 24px rgba(63, 70, 63, 0.07)
- **Sm**: 0 1px 0 rgba(63, 70, 63, 0.06)

### Spacing

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

### Surfaces

- **Bg Pattern**: Layered radial paper speckles and a sparse 32px baseline grid at 4% opacity.
- **Card Style**: Rectangular low-radius papers with 1px taupe borders, occasional amber left rule, and extremely soft contact shadow.
- **Treatment**: Warm ivory base with faint paper grain, flat white paper panels, and no glass or gradient cards.

### Typography

- **Base Size**: 16px
- **Body Font**: BIZ UDPGothic
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=BIZ+UDPGothic:wght@400;700&family=IBM+Plex+Mono:wght@400;500;600&display=swap
- **Heading Font**: BIZ UDPGothic
- **Letter Spacing**: -0.012em
- **Line Height**: 1.68
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.2

## Rules

### Composition

Compose screens as a low-chrome left rail, a measured reading column, and a comparison/context column. Align content to ruled sections rather than floating decorative modules.

### Density

Supports information-dense enterprise work through generous line-height, tight component chrome, and strong grouping by rule, not by large blank cards.

### Hierarchy

Lead with readable headings and prose summaries, then tabular metadata, then actions. Color is reserved for state and relationship, not for making every card compete.

### Signature Patterns

- Context-thread rails: a 1px vertical border with small amber nodes links notes, sources, owners, and decisions across stacked sections.
- Paper rule headers: section titles sit on a taupe bottom rule with mono metadata aligned right and a tiny clay square marker.
- Quiet comparison bands: side-by-side records use alternating ivory strips and tabular numerals instead of colorful chart decoration.
- Low-chrome navigation rail: active location is indicated by one vertical amber rule and bold ink text, never a filled rounded button.
- Semantic square chips: status badges use muted calm fills, square corners, and left inset dots to preserve legibility at dense sizes.

## Layout

### Breakpoints

mobile 375px, tablet 768px, desktop 1200px, wide 1440px

### Grid

Desktop uses a 72px navigation rail, 12-column content grid, and a 360px context aside; tablet collapses to rail plus stacked panels.

### Whitespace

Whitespace is measured and vertical: 24px between sections, 12px within dense rows, and ample line-height for long text.

## Guidance

### Do

- Use real labels, summaries, owners, timestamps, and source relationships in product screens.
- Prefer hairlines, rule headers, and connector rails over decorative cards.
- Keep accent color limited to active navigation, key decisions, focus rings, and critical comparison markers.
- Maintain WCAG-conscious contrast with ink text on ivory surfaces.

### Don't

- Do not use glassmorphism, neon gradients, or heavy drop shadows.
- Do not replace reading hierarchy with icon-heavy navigation or generic metric tiles.
- Do not make every badge saturated; semantic colors must remain calm and legible.
- Do not center long enterprise text or use cramped line-height.
DESIGN.md
---
version: "alpha"
name: "Kanso Context Weave"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#C9823B"
  background: "#F7F1E7"
  border: "#D8CDBC"
  error: "#B85B50"
  info: "#5F7486"
  muted: "#6F7470"
  primary: "#3F463F"
  secondary: "#8A6F55"
  success: "#5E7D65"
  surface: "#FFFDF8"
  text: "#2F3332"
  warning: "#C78A3D"
typography:
  headline-lg:
    fontFamily: "BIZ UDPGothic"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.012em"
  headline-md:
    fontFamily: "BIZ UDPGothic"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.012em"
  body-md:
    fontFamily: "BIZ UDPGothic"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.68
    letterSpacing: "-0.012em"
  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"
---

# Kanso Context Weave

## Overview

Kanso Context Weave is a contemporary Japanese SaaS language for teams reading, comparing, and connecting many pieces of context without visual noise. It treats the interface like a calm stack of annotated paper: low-chrome navigation, exact typography, restrained rules, warm amber and clay signals, and generous line-height that lets dense enterprise information remain humane.

### Values

- reading-first hierarchy
- quiet operational confidence
- paper-like material honesty
- component consistency across dense workflows
- accessible contrast with warm restraint

### Anti-Values

- decorative dashboard spectacle
- floating glass cards and heavy shadows
- low-contrast gray text used as a style crutch
- over-rounded generic SaaS controls

### Visual Character

- Use an ivory page background with subtle repeating paper-fiber radial gradients and flat off-white panels instead of glossy cards.
- Build hierarchy with 1px ink-gray and warm-taupe ruled lines, including vertical connector rails between related context blocks.
- Set BIZ UDPGothic at generous 1.68 body line-height with compact negative heading tracking and tabular numeric details.
- Apply small amber/clay left-edge markers and square status chips as the only saturated accents in otherwise neutral surfaces.
- Keep navigation as a narrow low-chrome rail with text labels, hairline dividers, and no filled active pill except a thin amber rule.

## 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 | `#C9823B` |
| background | `#F7F1E7` |
| border | `#D8CDBC` |
| error | `#B85B50` |
| info | `#5F7486` |
| muted | `#6F7470` |
| primary | `#3F463F` |
| secondary | `#8A6F55` |
| success | `#5E7D65` |
| surface | `#FFFDF8` |
| text | `#2F3332` |
| warning | `#C78A3D` |

## Typography

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

## Layout

### Spacing Tokens

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

### Breakpoints

mobile 375px, tablet 768px, desktop 1200px, wide 1440px

### Grid

Desktop uses a 72px navigation rail, 12-column content grid, and a 360px context aside; tablet collapses to rail plus stacked panels.

### Whitespace

Whitespace is measured and vertical: 24px between sections, 12px within dense rows, and ample line-height for long text.

## Elevation & Depth

### Shadows

- **Lg**: 0 18px 42px rgba(63, 70, 63, 0.10)
- **Md**: 0 10px 24px rgba(63, 70, 63, 0.07)
- **Sm**: 0 1px 0 rgba(63, 70, 63, 0.06)

## Shapes

### Rounded

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

### Surfaces

- **Bg Pattern**: Layered radial paper speckles and a sparse 32px baseline grid at 4% opacity.
- **Card Style**: Rectangular low-radius papers with 1px taupe borders, occasional amber left rule, and extremely soft contact shadow.
- **Treatment**: Warm ivory base with faint paper grain, flat white paper panels, and no glass or gradient cards.

### Borders

- **Accent Width**: 3px
- **Character**: Borders behave like printed rules: quiet separators first, decoration never.
- **Default Width**: 1px
- **Style**: solid hairlines with occasional dotted connector rules

## Components

### Composition

Compose screens as a low-chrome left rail, a measured reading column, and a comparison/context column. Align content to ruled sections rather than floating decorative modules.

### Density

Supports information-dense enterprise work through generous line-height, tight component chrome, and strong grouping by rule, not by large blank cards.

### Hierarchy

Lead with readable headings and prose summaries, then tabular metadata, then actions. Color is reserved for state and relationship, not for making every card compete.

### Signature Patterns

- Context-thread rails: a 1px vertical border with small amber nodes links notes, sources, owners, and decisions across stacked sections.
- Paper rule headers: section titles sit on a taupe bottom rule with mono metadata aligned right and a tiny clay square marker.
- Quiet comparison bands: side-by-side records use alternating ivory strips and tabular numerals instead of colorful chart decoration.
- Low-chrome navigation rail: active location is indicated by one vertical amber rule and bold ink text, never a filled rounded button.
- Semantic square chips: status badges use muted calm fills, square corners, and left inset dots to preserve legibility at dense sizes.

## 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-019ed833-73e8-7590-b3e9-00a62b01a683/DESIGN.with-shadcn.md`.

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

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

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

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

## Do's and Don'ts

- Do Use real labels, summaries, owners, timestamps, and source relationships in product screens.
- Do Prefer hairlines, rule headers, and connector rails over decorative cards.
- Do Keep accent color limited to active navigation, key decisions, focus rings, and critical comparison markers.
- Do Maintain WCAG-conscious contrast with ink text on ivory surfaces.
- Don't Do not use glassmorphism, neon gradients, or heavy drop shadows.
- Don't Do not replace reading hierarchy with icon-heavy navigation or generic metric tiles.
- Don't Do not make every badge saturated; semantic colors must remain calm and legible.
- Don't Do not center long enterprise text or use cramped line-height.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "kanso-context-weave",
  "type": "registry:theme",
  "title": "Kanso Context Weave shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F1E7",
      "foreground": "#2F3332",
      "card": "#FFFDF8",
      "card-foreground": "#2F3332",
      "popover": "#FFFDF8",
      "popover-foreground": "#2F3332",
      "primary": "#3F463F",
      "primary-foreground": "#ffffff",
      "secondary": "#8A6F55",
      "secondary-foreground": "#ffffff",
      "muted": "#6F7470",
      "muted-foreground": "#2F3332",
      "accent": "#C9823B",
      "accent-foreground": "#ffffff",
      "destructive": "#B85B50",
      "border": "#D8CDBC",
      "input": "#D8CDBC",
      "ring": "#C9823B",
      "chart-1": "#3F463F",
      "chart-2": "#8A6F55",
      "chart-3": "#C9823B",
      "chart-4": "#5E7D65",
      "chart-5": "#C78A3D",
      "sidebar": "#FFFDF8",
      "sidebar-foreground": "#2F3332",
      "sidebar-primary": "#3F463F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5F7486",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8CDBC",
      "sidebar-ring": "#C9823B",
      "radius": "6px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#3F463F",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#C9823B",
      "accent-foreground": "#ffffff",
      "destructive": "#B85B50",
      "border": "#303642",
      "input": "#303642",
      "ring": "#C9823B",
      "chart-1": "#3F463F",
      "chart-2": "#8A6F55",
      "chart-3": "#C9823B",
      "chart-4": "#5E7D65",
      "chart-5": "#C78A3D",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#3F463F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#C9823B",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#C9823B",
      "radius": "6px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019ed833-73e8-7590-b3e9-00a62b01a683",
    "slug": "kanso-context-weave",
    "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

Kanso Context Weave

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-lgBIZ UDPGothic · 28px · 700

The quick brown fox jumps

headline-mdBIZ UDPGothic · 23px · 600

The quick brown fox jumps

body-mdBIZ UDPGothic · 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: #F7F1E7;
  --foreground: #2F3332;
  --card: #FFFDF8;
  --card-foreground: #2F3332;
  --popover: #FFFDF8;
  --popover-foreground: #2F3332;
  --primary: #3F463F;
  --primary-foreground: #ffffff;
  --secondary: #8A6F55;
  --secondary-foreground: #ffffff;
  --muted: #6F7470;
  --muted-foreground: #2F3332;
  --accent: #C9823B;
  --accent-foreground: #ffffff;
  --destructive: #B85B50;
  --border: #D8CDBC;
  --input: #D8CDBC;
  --ring: #C9823B;
  --chart-1: #3F463F;
  --chart-2: #8A6F55;
  --chart-3: #C9823B;
  --chart-4: #5E7D65;
  --chart-5: #C78A3D;
  --sidebar: #FFFDF8;
  --sidebar-foreground: #2F3332;
  --sidebar-primary: #3F463F;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #5F7486;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D8CDBC;
  --sidebar-ring: #C9823B;
  --radius: 6px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #3F463F;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #C9823B;
  --accent-foreground: #ffffff;
  --destructive: #B85B50;
  --border: #303642;
  --input: #303642;
  --ring: #C9823B;
  --chart-1: #3F463F;
  --chart-2: #8A6F55;
  --chart-3: #C9823B;
  --chart-4: #5E7D65;
  --chart-5: #C78A3D;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #3F463F;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #C9823B;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #C9823B;
  --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 KansoContextWeaveShadcnKit() {
  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">Kanso Context Weave</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": "kanso-context-weave",
  "type": "registry:theme",
  "title": "Kanso Context Weave shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F1E7",
      "foreground": "#2F3332",
      "card": "#FFFDF8",
      "card-foreground": "#2F3332",
      "popover": "#FFFDF8",
      "popover-foreground": "#2F3332",
      "primary": "#3F463F",
      "primary-foreground": "#ffffff",
      "secondary": "#8A6F55",
      "secondary-foreground": "#ffffff",
      "muted": "#6F7470",
      "muted-foreground": "#2F3332",
      "accent": "#C9823B",
      "accent-foreground": "#ffffff",
      "destructive": "#B85B50",
      "border": "#D8CDBC",
      "input": "#D8CDBC",
      "ring": "#C9823B",
      "chart-1": "#3F463F",
      "chart-2": "#8A6F55",
      "chart-3": "#C9823B",
      "chart-4": "#5E7D65",
      "chart-5": "#C78A3D",
      "sidebar": "#FFFDF8",
      "sidebar-foreground": "#2F3332",
      "sidebar-primary": "#3F463F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5F7486",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8CDBC",
      "sidebar-ring": "#C9823B",
      "radius": "6px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#3F463F",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#C9823B",
      "accent-foreground": "#ffffff",
      "destructive": "#B85B50",
      "border": "#303642",
      "input": "#303642",
      "ring": "#C9823B",
      "chart-1": "#3F463F",
      "chart-2": "#8A6F55",
      "chart-3": "#C9823B",
      "chart-4": "#5E7D65",
      "chart-5": "#C78A3D",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#3F463F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#C9823B",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#C9823B",
      "radius": "6px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019ed833-73e8-7590-b3e9-00a62b01a683",
    "slug": "kanso-context-weave",
    "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
# Kanso Context Weave shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019ed833-73e8-7590-b3e9-00a62b01a683`
Slug: `kanso-context-weave`

## Intent

Kanso Context Weave is a contemporary Japanese SaaS language for teams reading, comparing, and connecting many pieces of context without visual noise. It treats the interface like a calm stack of annotated paper: low-chrome navigation, exact typography, restrained rules, warm amber and clay signals, and generous line-height that lets dense enterprise information remain humane.

## 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": "#C9823B",
  "background": "#F7F1E7",
  "border": "#D8CDBC",
  "error": "#B85B50",
  "info": "#5F7486",
  "muted": "#6F7470",
  "primary": "#3F463F",
  "secondary": "#8A6F55",
  "success": "#5E7D65",
  "surface": "#FFFDF8",
  "text": "#2F3332",
  "warning": "#C78A3D"
}

Typography:

{
  "base_size": "16px",
  "body_font": "BIZ UDPGothic",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=BIZ+UDPGothic:wght@400;700&family=IBM+Plex+Mono:wght@400;500;600&display=swap",
  "heading_font": "BIZ UDPGothic",
  "letter_spacing": "-0.012em",
  "line_height": 1.68,
  "mono_font": "IBM Plex Mono",
  "scale_ratio": 1.2
}

## Visual character to preserve

- Use an ivory page background with subtle repeating paper-fiber radial gradients and flat off-white panels instead of glossy cards.
- Build hierarchy with 1px ink-gray and warm-taupe ruled lines, including vertical connector rails between related context blocks.
- Set BIZ UDPGothic at generous 1.68 body line-height with compact negative heading tracking and tabular numeric details.
- Apply small amber/clay left-edge markers and square status chips as the only saturated accents in otherwise neutral surfaces.
- Keep navigation as a narrow low-chrome rail with text labels, hairline dividers, and no filled active pill except a thin amber rule.

## ShadSync visual profile

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

## Signature component recipes

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

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

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

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

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

## Preview shots

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

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/kanso-context-weave/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use real labels, summaries, owners, timestamps, and source relationships in product screens.; Prefer hairlines, rule headers, and connector rails over decorative cards.; Keep accent color limited to active navigation, key decisions, focus rings, and critical comparison markers.; Maintain WCAG-conscious contrast with ink text on ivory surfaces.
- Do not: Do not use glassmorphism, neon gradients, or heavy drop shadows.; Do not replace reading hierarchy with icon-heavy navigation or generic metric tiles.; Do not make every badge saturated; semantic colors must remain calm and legible.; Do not center long enterprise text or use cramped line-height.

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

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

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

## Layout notes

{
  "breakpoints": "mobile 375px, tablet 768px, desktop 1200px, wide 1440px",
  "grid": "Desktop uses a 72px navigation rail, 12-column content grid, and a 360px context aside; tablet collapses to rail plus stacked panels.",
  "whitespace": "Whitespace is measured and vertical: 24px between sections, 12px within dense rows, and ample line-height for long text."
}
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-019ed833-73e8-7590-b3e9-00a62b01a683",
    "name": "Kanso Context Weave",
    "slug": "kanso-context-weave"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "Use an ivory page background with subtle repeating paper-fiber radial gradients and flat off-white panels instead of glossy cards.",
    "Build hierarchy with 1px ink-gray and warm-taupe ruled lines, including vertical connector rails between related context blocks.",
    "Set BIZ UDPGothic at generous 1.68 body line-height with compact negative heading tracking and tabular numeric details.",
    "Apply small amber/clay left-edge markers and square status chips as the only saturated accents in otherwise neutral surfaces.",
    "Keep navigation as a narrow low-chrome rail with text labels, hairline dividers, and no filled active pill except a thin amber rule."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "pebble",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": true,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Kanso Context Weave launch room",
        "description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
        "primaryAction": "Apply theme",
        "secondaryAction": "Review states",
        "stats": [
          {
            "label": "components",
            "value": "16",
            "tone": "accent"
          },
          {
            "label": "states",
            "value": "ready"
          },
          {
            "label": "density",
            "value": "balanced",
            "tone": "warning"
          }
        ],
        "rows": [
          {
            "label": "Primary flow",
            "value": "mapped",
            "status": "active"
          },
          {
            "label": "Token coverage",
            "value": "semantic",
            "status": "synced"
          },
          {
            "label": "Responsive proof",
            "value": "queued",
            "status": "review"
          }
        ],
        "statuses": [
          "Active",
          "Synced",
          "Draft"
        ]
      }
    },
    {
      "id": "detail-editor",
      "title": "Detail editor",
      "viewport": "tablet",
      "primitives": [
        "button",
        "card",
        "input",
        "textarea",
        "select",
        "checkbox",
        "switch",
        "slider",
        "dialog",
        "sheet"
      ],
      "composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
      "mustShow": [
        "focus ring",
        "error or destructive state",
        "dialog or sheet treatment",
        "written guidance content"
      ],
      "avoid": [
        "unstyled browser controls",
        "floating cards inside cards",
        "missing labels"
      ],
      "scene": {
        "eyebrow": "editing flow",
        "headline": "Language recipe editor",
        "description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
        "primaryAction": "Save recipe",
        "secondaryAction": "Open sheet",
        "fields": [
          {
            "label": "Component family",
            "value": "Narrative cards"
          },
          {
            "label": "State treatment",
            "value": "Visible focus + validation"
          },
          {
            "label": "Motion",
            "value": "Small lift, no opacity-only fade"
          }
        ],
        "statuses": [
          "Focus",
          "Invalid",
          "Confirmed"
        ]
      }
    },
    {
      "id": "data-operations",
      "title": "Data operations",
      "viewport": "mobile",
      "primitives": [
        "button",
        "tabs",
        "badge",
        "dropdown-menu",
        "table",
        "tooltip",
        "separator"
      ],
      "composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
      "mustShow": [
        "responsive reflow",
        "dense row styling",
        "menu affordance",
        "status badge system"
      ],
      "avoid": [
        "desktop-only tables",
        "text overflow",
        "default shadcn spacing without Katagami character"
      ],
      "scene": {
        "eyebrow": "operations",
        "headline": "Compact review queue",
        "description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
        "primaryAction": "Resolve",
        "secondaryAction": "Filter",
        "rows": [
          {
            "label": "Button hierarchy",
            "value": "approved",
            "status": "ok"
          },
          {
            "label": "Table rhythm",
            "value": "needs pass",
            "status": "watch"
          },
          {
            "label": "Empty state",
            "value": "designed",
            "status": "done"
          }
        ],
        "statuses": [
          "Queued",
          "Blocked",
          "Done"
        ]
      }
    }
  ],
  "componentRecipes": [
    {
      "primitive": "button",
      "intent": "Prove action hierarchy, focus, disabled, and destructive states."
    },
    {
      "primitive": "card",
      "intent": "Carry the language surface, border, elevation, and density rules."
    },
    {
      "primitive": "input",
      "intent": "Show labels, focus rings, validation, and spacing rhythm."
    },
    {
      "primitive": "textarea",
      "intent": "Show longer guidance, validation copy, and writing density."
    },
    {
      "primitive": "select",
      "intent": "Show filtering, selection contrast, and menu trigger styling."
    },
    {
      "primitive": "dialog",
      "intent": "Show centered decision states and overlay treatment."
    },
    {
      "primitive": "sheet",
      "intent": "Show contextual side panels and responsive editing."
    },
    {
      "primitive": "tabs",
      "intent": "Show navigational structure and active/inactive contrast."
    },
    {
      "primitive": "badge",
      "intent": "Show compact status vocabulary and semantic colors."
    },
    {
      "primitive": "separator",
      "intent": "Show section rhythm without generic gray dividers."
    },
    {
      "primitive": "checkbox",
      "intent": "Show binary selection with visible focus and checked states."
    },
    {
      "primitive": "switch",
      "intent": "Show settings toggles and on/off contrast."
    },
    {
      "primitive": "slider",
      "intent": "Show numeric adjustment with track/thumb styling."
    },
    {
      "primitive": "tooltip",
      "intent": "Show concise explanation styling above compact controls."
    },
    {
      "primitive": "dropdown-menu",
      "intent": "Show action menus, destructive items, and grouped choices."
    },
    {
      "primitive": "table",
      "intent": "Show dense operational data, separators, row states, and responsive behavior."
    }
  ],
  "qualityRules": {
    "do": [
      "Use real labels, summaries, owners, timestamps, and source relationships in product screens.",
      "Prefer hairlines, rule headers, and connector rails over decorative cards.",
      "Keep accent color limited to active navigation, key decisions, focus rings, and critical comparison markers.",
      "Maintain WCAG-conscious contrast with ink text on ivory surfaces."
    ],
    "dont": [
      "Do not use glassmorphism, neon gradients, or heavy drop shadows.",
      "Do not replace reading hierarchy with icon-heavy navigation or generic metric tiles.",
      "Do not make every badge saturated; semantic colors must remain calm and legible.",
      "Do not center long enterprise text or use cramped line-height."
    ]
  }
}
related

More like this