back to gallery
design language·ma-context-panels

Ma Context Panels

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
Ma Context Panels makes enterprise intelligence feel composed rather than analytical-heavy: broad intervals of quiet space, soft low-chroma surfaces, and precise contextual panels let the user understand state, next action, and supporting evidence without visual noise.
values
quiet intelligence through absencecontent-first hierarchysemantic restraintstructured context over ornamental dashboardshigh readability at working density
anti-values
×No rainbow KPI walls, busy chart palettes, glassy gradients, or accent color used as decoration.×No generic white SaaS cards stacked in equal grids without contextual relationships.×No tiny gray text, invisible affordances, or whitespace that becomes emptiness instead of guidance.
tokens
borders4 items
accent width
2px
character
low-chroma divider lines, vertical anchors, and short accent rules used only for state or primary action
default width
1px
style
solid
colors12 items
accent
#596E8F
background
#F4F1EA
border
#D9D4C9
error
#A5524B
info
#596E8F
muted
#7A7C78
primary
#2F3742
secondary
#6F746F
success
#5E7865
surface
#FFFEFB
text
#20242A
warning
#9A7442
motion3 items
duration
160ms
easing
cubic-bezier(0.2, 0, 0.1, 1)
philosophy
quiet reveal and focus confirmation only; no decorative motion or bouncing analytics
radii5 items
full
9999px
lg
14px
md
10px
none
0
sm
6px
shadows3 items
lg
0 24px 60px rgba(47,55,66,0.08)
md
0 10px 28px rgba(47,55,66,0.06)
sm
0 1px 0 rgba(32,36,42,0.04)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
bare warm field with occasional hairline grid guides at very low opacity
card style
soft rectangular context panels using 10px or 14px radius, 1px beige-gray borders, and sparse header shelves
treatment
matte warm paper surfaces with almost-flat depth, separated by low-chroma dividers and generous gutters
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&family=Instrument+Sans:wght@500;600;700&display=swap
heading font
Instrument Sans
letter spacing
-0.012em
line height
1.58
mono font
IBM Plex Mono
scale ratio
1.2
rules
composition
Use a minimal app shell with an understated left rail, one command strip, and large structured context panels arranged on a 12-column grid with purposeful negative space between evidence groups.
density
Medium working density inside panels, low density between panels: preserve ma by keeping gutters and empty shelves visible even when rows contain operational data.
hierarchy
Lead with content labels, time, owner, and action readiness; create hierarchy through type size, weight, indentation, and divider length before using accent color.
signature patterns
Ma gutters: maintain 32px to 72px unoccupied intervals between major panels and use them as attention rests, not as places for decoration.Context shelves: each panel header has a quiet metadata shelf with owner, confidence, or freshness aligned to a single baseline above the main content.Accent-as-state rule: muted indigo appears only on active nav, primary action, focus outline, selected row, and one short status rule per active panel.Hairline anchors: related rows connect to their panel title through a vertical 1px divider and aligned left insets rather than colored badges.Quiet metrics: charts reduce to monochrome ticks, thin bars, and two-color semantic exceptions so the screen reads as context rather than analytics theater.
layout
breakpoints

mobile <= 640px, tablet 641px-1024px, desktop >= 1025px; rail collapses to a top strip and panels stack with preserved 24px ma gaps.

density

Panel interiors can hold tables and controls, but surrounding gutters stay open to keep the app calm and readable.

grid
Desktop uses a 12-column grid within a 1360px canvas; the rail spans 2 columns, main content spans 10, and context panels use 7/5 or 4/8 relationships rather than equal cards.
whitespace

Outer margins start at 32px and grow to 64px; interior panel padding uses 24px to 32px with deliberate blank shelves so absence actively guides attention.

guidance
do
  • Use broad negative space as a structural element separating command, evidence, and action zones.
  • Keep accent color sparse and semantic: active, focus, selected, primary, or state only.
  • Prefer low-chroma dividers, aligned metadata shelves, and quiet inline meters for dashboard information.
  • Write real product labels and content so panels feel like context for decisions, not component demos.
  • Maintain readable text contrast and visible focus rings on all controls.
avoid
  • Do not introduce colorful chart palettes, decorative gradients, glassmorphism, or floating neon effects.
  • Do not fill every gap with widgets; empty space is part of the hierarchy.
  • Do not use multiple arbitrary radii; keep panel geometry to the 10px/14px system and controls to 6px.
  • Do not make semantic colors carry identity when spacing, rules, and panel relationships should do the work.
  • Do not create identical card grids or KPI walls that feel analytical-heavy.
katagami spec
# Ma Context Panels

## Philosophy

Ma Context Panels makes enterprise intelligence feel composed rather than analytical-heavy: broad intervals of quiet space, soft low-chroma surfaces, and precise contextual panels let the user understand state, next action, and supporting evidence without visual noise.

### Values

- quiet intelligence through absence
- content-first hierarchy
- semantic restraint
- structured context over ornamental dashboards
- high readability at working density

### Anti-Values

- No rainbow KPI walls, busy chart palettes, glassy gradients, or accent color used as decoration.
- No generic white SaaS cards stacked in equal grids without contextual relationships.
- No tiny gray text, invisible affordances, or whitespace that becomes emptiness instead of guidance.

### Visual Character

- Use a warm off-white page with nested #F7F5F0 and #FFFFFF panels separated by 1px low-chroma gray-beige rules rather than shadow-heavy cards.
- Compose the app shell as a narrow text-led rail, a calm command band, and asymmetrical context panels with deliberate empty gutters of 32px to 72px.
- Reserve the muted indigo accent for active navigation, primary action, focus rings, and selected data state; all other emphasis uses weight, spacing, and rule length.
- Render dashboard data as quiet inline meters, small monochrome sparklines, and labeled evidence rows instead of colorful chart blocks.
- Create panel relationships with aligned header baselines, vertical hairline anchors, and inset metadata shelves that make context feel spatially organized.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: low-chroma divider lines, vertical anchors, and short accent rules used only for state or primary action
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#596E8F` |
| background | `#F4F1EA` |
| border | `#D9D4C9` |
| error | `#A5524B` |
| info | `#596E8F` |
| muted | `#7A7C78` |
| primary | `#2F3742` |
| secondary | `#6F746F` |
| success | `#5E7865` |
| surface | `#FFFEFB` |
| text | `#20242A` |
| warning | `#9A7442` |

### Motion

- **Duration**: 160ms
- **Easing**: cubic-bezier(0.2, 0, 0.1, 1)
- **Philosophy**: quiet reveal and focus confirmation only; no decorative motion or bouncing analytics

### Radii

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

### Shadows

- **Lg**: 0 24px 60px rgba(47,55,66,0.08)
- **Md**: 0 10px 28px rgba(47,55,66,0.06)
- **Sm**: 0 1px 0 rgba(32,36,42,0.04)

### Spacing

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

### Surfaces

- **Bg Pattern**: bare warm field with occasional hairline grid guides at very low opacity
- **Card Style**: soft rectangular context panels using 10px or 14px radius, 1px beige-gray borders, and sparse header shelves
- **Treatment**: matte warm paper surfaces with almost-flat depth, separated by low-chroma dividers and generous gutters

### 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&family=Instrument+Sans:wght@500;600;700&display=swap
- **Heading Font**: Instrument Sans
- **Letter Spacing**: -0.012em
- **Line Height**: 1.58
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.2

## Rules

### Composition

Use a minimal app shell with an understated left rail, one command strip, and large structured context panels arranged on a 12-column grid with purposeful negative space between evidence groups.

### Density

Medium working density inside panels, low density between panels: preserve ma by keeping gutters and empty shelves visible even when rows contain operational data.

### Hierarchy

Lead with content labels, time, owner, and action readiness; create hierarchy through type size, weight, indentation, and divider length before using accent color.

### Signature Patterns

- Ma gutters: maintain 32px to 72px unoccupied intervals between major panels and use them as attention rests, not as places for decoration.
- Context shelves: each panel header has a quiet metadata shelf with owner, confidence, or freshness aligned to a single baseline above the main content.
- Accent-as-state rule: muted indigo appears only on active nav, primary action, focus outline, selected row, and one short status rule per active panel.
- Hairline anchors: related rows connect to their panel title through a vertical 1px divider and aligned left insets rather than colored badges.
- Quiet metrics: charts reduce to monochrome ticks, thin bars, and two-color semantic exceptions so the screen reads as context rather than analytics theater.

## Layout

### Breakpoints

mobile <= 640px, tablet 641px-1024px, desktop >= 1025px; rail collapses to a top strip and panels stack with preserved 24px ma gaps.

### Density

Panel interiors can hold tables and controls, but surrounding gutters stay open to keep the app calm and readable.

### Grid

Desktop uses a 12-column grid within a 1360px canvas; the rail spans 2 columns, main content spans 10, and context panels use 7/5 or 4/8 relationships rather than equal cards.

### Whitespace

Outer margins start at 32px and grow to 64px; interior panel padding uses 24px to 32px with deliberate blank shelves so absence actively guides attention.

## Guidance

### Do

- Use broad negative space as a structural element separating command, evidence, and action zones.
- Keep accent color sparse and semantic: active, focus, selected, primary, or state only.
- Prefer low-chroma dividers, aligned metadata shelves, and quiet inline meters for dashboard information.
- Write real product labels and content so panels feel like context for decisions, not component demos.
- Maintain readable text contrast and visible focus rings on all controls.

### Don't

- Do not introduce colorful chart palettes, decorative gradients, glassmorphism, or floating neon effects.
- Do not fill every gap with widgets; empty space is part of the hierarchy.
- Do not use multiple arbitrary radii; keep panel geometry to the 10px/14px system and controls to 6px.
- Do not make semantic colors carry identity when spacing, rules, and panel relationships should do the work.
- Do not create identical card grids or KPI walls that feel analytical-heavy.

### Accessibility

All text colors meet WCAG AA on the warm surfaces, focus uses a 2px indigo ring plus offset, semantic states include labels or icons, and body text remains at 15px-16px minimum.

### Usage Context

Best for AI workbenches, enterprise operations consoles, policy review tools, knowledge management systems, and calm executive dashboards where context and action readiness matter more than chart volume.
DESIGN.md
---
version: "alpha"
name: "Ma Context Panels"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#596E8F"
  background: "#F4F1EA"
  border: "#D9D4C9"
  error: "#A5524B"
  info: "#596E8F"
  muted: "#7A7C78"
  primary: "#2F3742"
  secondary: "#6F746F"
  success: "#5E7865"
  surface: "#FFFEFB"
  text: "#20242A"
  warning: "#9A7442"
typography:
  headline-lg:
    fontFamily: "Instrument Sans"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.012em"
  headline-md:
    fontFamily: "Instrument Sans"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.012em"
  body-md:
    fontFamily: "BIZ UDPGothic"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.58
    letterSpacing: "-0.012em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "14px"
  md: "10px"
  none: "0px"
  sm: "6px"
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"
---

# Ma Context Panels

## Overview

Ma Context Panels makes enterprise intelligence feel composed rather than analytical-heavy: broad intervals of quiet space, soft low-chroma surfaces, and precise contextual panels let the user understand state, next action, and supporting evidence without visual noise.

### Values

- quiet intelligence through absence
- content-first hierarchy
- semantic restraint
- structured context over ornamental dashboards
- high readability at working density

### Anti-Values

- No rainbow KPI walls, busy chart palettes, glassy gradients, or accent color used as decoration.
- No generic white SaaS cards stacked in equal grids without contextual relationships.
- No tiny gray text, invisible affordances, or whitespace that becomes emptiness instead of guidance.

### Visual Character

- Use a warm off-white page with nested #F7F5F0 and #FFFFFF panels separated by 1px low-chroma gray-beige rules rather than shadow-heavy cards.
- Compose the app shell as a narrow text-led rail, a calm command band, and asymmetrical context panels with deliberate empty gutters of 32px to 72px.
- Reserve the muted indigo accent for active navigation, primary action, focus rings, and selected data state; all other emphasis uses weight, spacing, and rule length.
- Render dashboard data as quiet inline meters, small monochrome sparklines, and labeled evidence rows instead of colorful chart blocks.
- Create panel relationships with aligned header baselines, vertical hairline anchors, and inset metadata shelves that make context feel spatially organized.

## 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 | `#596E8F` |
| background | `#F4F1EA` |
| border | `#D9D4C9` |
| error | `#A5524B` |
| info | `#596E8F` |
| muted | `#7A7C78` |
| primary | `#2F3742` |
| secondary | `#6F746F` |
| success | `#5E7865` |
| surface | `#FFFEFB` |
| text | `#20242A` |
| warning | `#9A7442` |

## Typography

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

## Layout

### Spacing Tokens

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

### Breakpoints

mobile <= 640px, tablet 641px-1024px, desktop >= 1025px; rail collapses to a top strip and panels stack with preserved 24px ma gaps.

### Density

Panel interiors can hold tables and controls, but surrounding gutters stay open to keep the app calm and readable.

### Grid

Desktop uses a 12-column grid within a 1360px canvas; the rail spans 2 columns, main content spans 10, and context panels use 7/5 or 4/8 relationships rather than equal cards.

### Whitespace

Outer margins start at 32px and grow to 64px; interior panel padding uses 24px to 32px with deliberate blank shelves so absence actively guides attention.

## Elevation & Depth

### Shadows

- **Lg**: 0 24px 60px rgba(47,55,66,0.08)
- **Md**: 0 10px 28px rgba(47,55,66,0.06)
- **Sm**: 0 1px 0 rgba(32,36,42,0.04)

## Shapes

### Rounded

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

### Surfaces

- **Bg Pattern**: bare warm field with occasional hairline grid guides at very low opacity
- **Card Style**: soft rectangular context panels using 10px or 14px radius, 1px beige-gray borders, and sparse header shelves
- **Treatment**: matte warm paper surfaces with almost-flat depth, separated by low-chroma dividers and generous gutters

### Borders

- **Accent Width**: 2px
- **Character**: low-chroma divider lines, vertical anchors, and short accent rules used only for state or primary action
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use a minimal app shell with an understated left rail, one command strip, and large structured context panels arranged on a 12-column grid with purposeful negative space between evidence groups.

### Density

Medium working density inside panels, low density between panels: preserve ma by keeping gutters and empty shelves visible even when rows contain operational data.

### Hierarchy

Lead with content labels, time, owner, and action readiness; create hierarchy through type size, weight, indentation, and divider length before using accent color.

### Signature Patterns

- Ma gutters: maintain 32px to 72px unoccupied intervals between major panels and use them as attention rests, not as places for decoration.
- Context shelves: each panel header has a quiet metadata shelf with owner, confidence, or freshness aligned to a single baseline above the main content.
- Accent-as-state rule: muted indigo appears only on active nav, primary action, focus outline, selected row, and one short status rule per active panel.
- Hairline anchors: related rows connect to their panel title through a vertical 1px divider and aligned left insets rather than colored badges.
- Quiet metrics: charts reduce to monochrome ticks, thin bars, and two-color semantic exceptions so the screen reads as context rather than analytics theater.

## 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-019ed742-9a0f-70f1-a756-f8af09bf114d/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 broad negative space as a structural element separating command, evidence, and action zones.
- Do Keep accent color sparse and semantic: active, focus, selected, primary, or state only.
- Do Prefer low-chroma dividers, aligned metadata shelves, and quiet inline meters for dashboard information.
- Do Write real product labels and content so panels feel like context for decisions, not component demos.
- Do Maintain readable text contrast and visible focus rings on all controls.
- Don't Do not introduce colorful chart palettes, decorative gradients, glassmorphism, or floating neon effects.
- Don't Do not fill every gap with widgets; empty space is part of the hierarchy.
- Don't Do not use multiple arbitrary radii; keep panel geometry to the 10px/14px system and controls to 6px.
- Don't Do not make semantic colors carry identity when spacing, rules, and panel relationships should do the work.
- Don't Do not create identical card grids or KPI walls that feel analytical-heavy.

### Accessibility

All text colors meet WCAG AA on the warm surfaces, focus uses a 2px indigo ring plus offset, semantic states include labels or icons, and body text remains at 15px-16px minimum.

### Usage Context

Best for AI workbenches, enterprise operations consoles, policy review tools, knowledge management systems, and calm executive dashboards where context and action readiness matter more than chart volume.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "ma-context-panels",
  "type": "registry:theme",
  "title": "Ma Context Panels shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F4F1EA",
      "foreground": "#20242A",
      "card": "#FFFEFB",
      "card-foreground": "#20242A",
      "popover": "#FFFEFB",
      "popover-foreground": "#20242A",
      "primary": "#2F3742",
      "primary-foreground": "#ffffff",
      "secondary": "#6F746F",
      "secondary-foreground": "#ffffff",
      "muted": "#7A7C78",
      "muted-foreground": "#20242A",
      "accent": "#596E8F",
      "accent-foreground": "#ffffff",
      "destructive": "#A5524B",
      "border": "#D9D4C9",
      "input": "#D9D4C9",
      "ring": "#596E8F",
      "chart-1": "#2F3742",
      "chart-2": "#6F746F",
      "chart-3": "#596E8F",
      "chart-4": "#5E7865",
      "chart-5": "#9A7442",
      "sidebar": "#FFFEFB",
      "sidebar-foreground": "#20242A",
      "sidebar-primary": "#2F3742",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#596E8F",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D9D4C9",
      "sidebar-ring": "#596E8F",
      "radius": "10px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2F3742",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#596E8F",
      "accent-foreground": "#ffffff",
      "destructive": "#A5524B",
      "border": "#303642",
      "input": "#303642",
      "ring": "#596E8F",
      "chart-1": "#2F3742",
      "chart-2": "#6F746F",
      "chart-3": "#596E8F",
      "chart-4": "#5E7865",
      "chart-5": "#9A7442",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2F3742",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#596E8F",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#596E8F",
      "radius": "10px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019ed742-9a0f-70f1-a756-f8af09bf114d",
    "slug": "ma-context-panels",
    "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

Ma Context Panels

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

The quick brown fox jumps

headline-mdInstrument Sans · 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
lg14px
md10px
none0px
sm6px
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: #F4F1EA;
  --foreground: #20242A;
  --card: #FFFEFB;
  --card-foreground: #20242A;
  --popover: #FFFEFB;
  --popover-foreground: #20242A;
  --primary: #2F3742;
  --primary-foreground: #ffffff;
  --secondary: #6F746F;
  --secondary-foreground: #ffffff;
  --muted: #7A7C78;
  --muted-foreground: #20242A;
  --accent: #596E8F;
  --accent-foreground: #ffffff;
  --destructive: #A5524B;
  --border: #D9D4C9;
  --input: #D9D4C9;
  --ring: #596E8F;
  --chart-1: #2F3742;
  --chart-2: #6F746F;
  --chart-3: #596E8F;
  --chart-4: #5E7865;
  --chart-5: #9A7442;
  --sidebar: #FFFEFB;
  --sidebar-foreground: #20242A;
  --sidebar-primary: #2F3742;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #596E8F;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D9D4C9;
  --sidebar-ring: #596E8F;
  --radius: 10px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #2F3742;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #596E8F;
  --accent-foreground: #ffffff;
  --destructive: #A5524B;
  --border: #303642;
  --input: #303642;
  --ring: #596E8F;
  --chart-1: #2F3742;
  --chart-2: #6F746F;
  --chart-3: #596E8F;
  --chart-4: #5E7865;
  --chart-5: #9A7442;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #2F3742;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #596E8F;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #596E8F;
  --radius: 10px;
}
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 MaContextPanelsShadcnKit() {
  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">Ma Context Panels</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": "ma-context-panels",
  "type": "registry:theme",
  "title": "Ma Context Panels shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F4F1EA",
      "foreground": "#20242A",
      "card": "#FFFEFB",
      "card-foreground": "#20242A",
      "popover": "#FFFEFB",
      "popover-foreground": "#20242A",
      "primary": "#2F3742",
      "primary-foreground": "#ffffff",
      "secondary": "#6F746F",
      "secondary-foreground": "#ffffff",
      "muted": "#7A7C78",
      "muted-foreground": "#20242A",
      "accent": "#596E8F",
      "accent-foreground": "#ffffff",
      "destructive": "#A5524B",
      "border": "#D9D4C9",
      "input": "#D9D4C9",
      "ring": "#596E8F",
      "chart-1": "#2F3742",
      "chart-2": "#6F746F",
      "chart-3": "#596E8F",
      "chart-4": "#5E7865",
      "chart-5": "#9A7442",
      "sidebar": "#FFFEFB",
      "sidebar-foreground": "#20242A",
      "sidebar-primary": "#2F3742",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#596E8F",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D9D4C9",
      "sidebar-ring": "#596E8F",
      "radius": "10px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2F3742",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#596E8F",
      "accent-foreground": "#ffffff",
      "destructive": "#A5524B",
      "border": "#303642",
      "input": "#303642",
      "ring": "#596E8F",
      "chart-1": "#2F3742",
      "chart-2": "#6F746F",
      "chart-3": "#596E8F",
      "chart-4": "#5E7865",
      "chart-5": "#9A7442",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2F3742",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#596E8F",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#596E8F",
      "radius": "10px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019ed742-9a0f-70f1-a756-f8af09bf114d",
    "slug": "ma-context-panels",
    "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
# Ma Context Panels shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019ed742-9a0f-70f1-a756-f8af09bf114d`
Slug: `ma-context-panels`

## Intent

Ma Context Panels makes enterprise intelligence feel composed rather than analytical-heavy: broad intervals of quiet space, soft low-chroma surfaces, and precise contextual panels let the user understand state, next action, and supporting evidence without visual noise.

## Required primitives

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

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

## Token cues

Colors:

{
  "accent": "#596E8F",
  "background": "#F4F1EA",
  "border": "#D9D4C9",
  "error": "#A5524B",
  "info": "#596E8F",
  "muted": "#7A7C78",
  "primary": "#2F3742",
  "secondary": "#6F746F",
  "success": "#5E7865",
  "surface": "#FFFEFB",
  "text": "#20242A",
  "warning": "#9A7442"
}

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&family=Instrument+Sans:wght@500;600;700&display=swap",
  "heading_font": "Instrument Sans",
  "letter_spacing": "-0.012em",
  "line_height": 1.58,
  "mono_font": "IBM Plex Mono",
  "scale_ratio": 1.2
}

## Visual character to preserve

- Use a warm off-white page with nested #F7F5F0 and #FFFFFF panels separated by 1px low-chroma gray-beige rules rather than shadow-heavy cards.
- Compose the app shell as a narrow text-led rail, a calm command band, and asymmetrical context panels with deliberate empty gutters of 32px to 72px.
- Reserve the muted indigo accent for active navigation, primary action, focus rings, and selected data state; all other emphasis uses weight, spacing, and rule length.
- Render dashboard data as quiet inline meters, small monochrome sparklines, and labeled evidence rows instead of colorful chart blocks.
- Create panel relationships with aligned header baselines, vertical hairline anchors, and inset metadata shelves that make context feel spatially organized.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": true,
  "stickerBadges": true,
  "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/ma-context-panels/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 broad negative space as a structural element separating command, evidence, and action zones.; Keep accent color sparse and semantic: active, focus, selected, primary, or state only.; Prefer low-chroma dividers, aligned metadata shelves, and quiet inline meters for dashboard information.; Write real product labels and content so panels feel like context for decisions, not component demos.; Maintain readable text contrast and visible focus rings on all controls.
- Do not: Do not introduce colorful chart palettes, decorative gradients, glassmorphism, or floating neon effects.; Do not fill every gap with widgets; empty space is part of the hierarchy.; Do not use multiple arbitrary radii; keep panel geometry to the 10px/14px system and controls to 6px.; Do not make semantic colors carry identity when spacing, rules, and panel relationships should do the work.; Do not create identical card grids or KPI walls that feel analytical-heavy.

## 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 MaContextPanelsShadcnKit() {
  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">Ma Context Panels</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 <= 640px, tablet 641px-1024px, desktop >= 1025px; rail collapses to a top strip and panels stack with preserved 24px ma gaps.",
  "density": "Panel interiors can hold tables and controls, but surrounding gutters stay open to keep the app calm and readable.",
  "grid": "Desktop uses a 12-column grid within a 1360px canvas; the rail spans 2 columns, main content spans 10, and context panels use 7/5 or 4/8 relationships rather than equal cards.",
  "whitespace": "Outer margins start at 32px and grow to 64px; interior panel padding uses 24px to 32px with deliberate blank shelves so absence actively guides attention."
}
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-019ed742-9a0f-70f1-a756-f8af09bf114d",
    "name": "Ma Context Panels",
    "slug": "ma-context-panels"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "Use a warm off-white page with nested #F7F5F0 and #FFFFFF panels separated by 1px low-chroma gray-beige rules rather than shadow-heavy cards.",
    "Compose the app shell as a narrow text-led rail, a calm command band, and asymmetrical context panels with deliberate empty gutters of 32px to 72px.",
    "Reserve the muted indigo accent for active navigation, primary action, focus rings, and selected data state; all other emphasis uses weight, spacing, and rule length.",
    "Render dashboard data as quiet inline meters, small monochrome sparklines, and labeled evidence rows instead of colorful chart blocks.",
    "Create panel relationships with aligned header baselines, vertical hairline anchors, and inset metadata shelves that make context feel spatially organized."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": false,
    "stickerBadges": true,
    "motion": "still",
    "density": "balanced",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Ma Context Panels 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 broad negative space as a structural element separating command, evidence, and action zones.",
      "Keep accent color sparse and semantic: active, focus, selected, primary, or state only.",
      "Prefer low-chroma dividers, aligned metadata shelves, and quiet inline meters for dashboard information.",
      "Write real product labels and content so panels feel like context for decisions, not component demos.",
      "Maintain readable text contrast and visible focus rings on all controls."
    ],
    "dont": [
      "Do not introduce colorful chart palettes, decorative gradients, glassmorphism, or floating neon effects.",
      "Do not fill every gap with widgets; empty space is part of the hierarchy.",
      "Do not use multiple arbitrary radii; keep panel geometry to the 10px/14px system and controls to 6px.",
      "Do not make semantic colors carry identity when spacing, rules, and panel relationships should do the work.",
      "Do not create identical card grids or KPI walls that feel analytical-heavy."
    ]
  }
}
related

More like this