back to gallery
design language·context-loom-command-surface

Context Loom Command Surface

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
Context Loom Command Surface gives a text-heavy knowledge workspace the calm of an annotated reading room: command phrases, threaded references, soft document cards, and fine connective strands organize dense context without turning the product into a metrics dashboard.
values
Language is the primary interface; commands, tabs, filters, and navigation should read as clear editorial phrases rather than icon-heavy controls.Context should feel woven beside the main text through slim reference strands, marginal notes, and timestamped thread rails instead of competing panels.Compact data modules are allowed only when they support reading, synthesis, or source confidence; they stay quiet and typographic.The screen should preserve long-form readability with generous measure, visible hierarchy, and calm surfaces that tolerate many notes.
anti-values
×No dashboard wall of charts, KPI tiles, saturated status colors, or business-intelligence chrome.×No glassmorphism, floating neon command palettes, generic AI gradient blobs, or icon-only navigation.×No dense table-first layout that makes the workspace feel like an admin console rather than a thinking surface.
tokens
borders4 items
accent width
2px
character
Hairline editorial rules, quote brackets, and dotted strands rather than heavy containers.
default width
1px
style
solid with dotted connector variants
colors12 items
accent
#8C6F3E
background
#F7F4EE
border
#D8D1C4
error
#A34D3F
info
#557186
muted
#7E7A70
primary
#2F3A35
secondary
#6D675D
success
#4F7A61
surface
#FFFEFA
text
#242824
warning
#A97832
motion3 items
duration
140ms
easing
cubic-bezier(0.2, 0, 0.1, 1)
philosophy
Motion is almost invisible: command links tint, strand knots firm up, and cards lift by one pixel only on intentional focus.
radii5 items
full
9999px
lg
16px
md
10px
none
0
sm
4px
shadows3 items
lg
0 24px 60px rgba(47,58,53,0.10)
md
0 10px 26px rgba(47,58,53,0.07)
sm
0 1px 0 rgba(47,58,53,0.06)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
A barely visible vertical strand grid: linear gradients at 1px width every 32px in warm beige.
card style
Ivory cards with 1px warm-gray borders, small radius, restrained shadow, and occasional folded-corner label strips.
treatment
Warm matte paper over shell background with very subtle ruled-line gradients for reading alignment.
typography8 items
base size
16px
body font
Source Serif 4
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Literata:wght@500;600;700&family=Source+Serif+4:opsz,wght@8..60,400;8..60,500;8..60,600&display=swap
heading font
Literata
letter spacing
-0.012em
line height
1.62
mono font
IBM Plex Mono
scale ratio
1.2
rules
composition
Compose as a reading surface with three purposeful zones: a slim command vocabulary rail, a dominant text and synthesis column, and a narrow reference/thread rail stitched to the text by strands.
density

Medium text density with high line-height; dense references are stacked as excerpts and knots, while data modules stay compact and secondary.

hierarchy
Use serif headings and body copy for authority, mono labels for provenance and command hints, and hairline rules to create sections before adding new cards or color.
signature patterns
Reference strands are 1px or dotted pseudo-element lines that connect citation knots, paragraph anchors, and right-rail excerpts across the surface.Language-led command links use verb-first text, bracketed mono shortcuts, and an active underline instead of icon buttons or heavy filled controls.Editorial folio cards combine a small mono eyebrow, serif title, quiet excerpt, and bottom provenance line with tabular numerals.Thread timelines use numbered knots, alternating excerpt indentation, and soft amber markers for unresolved context rather than colored alert badges.Tabs behave like chapter markers: low rectangular pills on a ruled baseline with the active tab expressed by text weight, underline, and a tiny strand notch.
layout
breakpoints
mobile <= 640px stacks command rail as top phrase bar and references as inline accordions; tablet 641px-1024px uses 8 columns with collapsible right rail; desktop >= 1025px uses full 12-column loom.
density

Prioritize reading measure around 68-76 characters; compact modules may sit in sidebars but never outnumber editorial text blocks.

grid
Desktop uses a 12-column shell: 2 columns command rail, 7 columns reading workspace, 3 columns context rail; all zones align to an 8px baseline and 32px strand grid.
responsive

References collapse after their paragraph anchors on small screens so strands become vertical rather than cross-page.

whitespace

Keep 40-72px outer breathing room on desktop, 24px between rails, and 16-24px internal card rhythm so heavy text remains calm.

guidance
do
  • Write controls as clear command phrases such as “Weave sources”, “Trace contradiction”, and “Pin excerpt”.
  • Keep long-form text in comfortable serif measure with line-height above 1.55 and visible paragraph anchors.
  • Use dotted strands, numbered knots, tabs, and marginal folios to show context relationships.
  • Reserve accent color for provenance, active commands, and unresolved threads rather than decoration.
  • Use compact data modules only as supporting evidence panels with tabular numerals and quiet labels.
avoid
  • Do not turn the scene into analytics, CRM, admin, or KPI dashboards.
  • Do not rely on floating glass palettes, AI gradient blobs, or icon-only controls.
  • Do not compress threads into tiny unreadable chips; excerpts must remain scannable.
  • Do not use more than two accent colors in one viewport.
  • Do not let borders become boxy clutter; strands and rules should clarify relationships.
katagami spec
# Context Loom Command Surface

## Philosophy

Context Loom Command Surface gives a text-heavy knowledge workspace the calm of an annotated reading room: command phrases, threaded references, soft document cards, and fine connective strands organize dense context without turning the product into a metrics dashboard.

### Values

- Language is the primary interface; commands, tabs, filters, and navigation should read as clear editorial phrases rather than icon-heavy controls.
- Context should feel woven beside the main text through slim reference strands, marginal notes, and timestamped thread rails instead of competing panels.
- Compact data modules are allowed only when they support reading, synthesis, or source confidence; they stay quiet and typographic.
- The screen should preserve long-form readability with generous measure, visible hierarchy, and calm surfaces that tolerate many notes.

### Anti-Values

- No dashboard wall of charts, KPI tiles, saturated status colors, or business-intelligence chrome.
- No glassmorphism, floating neon command palettes, generic AI gradient blobs, or icon-only navigation.
- No dense table-first layout that makes the workspace feel like an admin console rather than a thinking surface.

### Visual Character

- A centered reading column uses max-width text measure with a left command rail and a right reference rail connected by one-pixel beige strand lines.
- Cards use near-flat ivory surfaces, 1px warm-gray borders, square-to-soft 10px corners, and only tiny contact shadows for document layering.
- Tabs and command links are language-led pills with underlined active verbs, bracketed keyboard hints, and no filled primary button slabs.
- Threads appear as vertical timeline rails with small numbered knots, excerpt cards, and dotted connector pseudo-elements that visually weave citations back to paragraphs.
- Compact modules are inset as quiet marginal folios with tabular numerals, hairline separators, and muted amber or blue emphasis only for provenance states.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Hairline editorial rules, quote brackets, and dotted strands rather than heavy containers.
- **Default Width**: 1px
- **Style**: solid with dotted connector variants

### Colors

| Name | Value |
|------|-------|
| accent | `#8C6F3E` |
| background | `#F7F4EE` |
| border | `#D8D1C4` |
| error | `#A34D3F` |
| info | `#557186` |
| muted | `#7E7A70` |
| primary | `#2F3A35` |
| secondary | `#6D675D` |
| success | `#4F7A61` |
| surface | `#FFFEFA` |
| text | `#242824` |
| warning | `#A97832` |

### Motion

- **Duration**: 140ms
- **Easing**: cubic-bezier(0.2, 0, 0.1, 1)
- **Philosophy**: Motion is almost invisible: command links tint, strand knots firm up, and cards lift by one pixel only on intentional focus.

### Radii

- **Full**: 9999px
- **Lg**: 16px
- **Md**: 10px
- **None**: 0
- **Sm**: 4px

### Shadows

- **Lg**: 0 24px 60px rgba(47,58,53,0.10)
- **Md**: 0 10px 26px rgba(47,58,53,0.07)
- **Sm**: 0 1px 0 rgba(47,58,53,0.06)

### Spacing

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

### Surfaces

- **Bg Pattern**: A barely visible vertical strand grid: linear gradients at 1px width every 32px in warm beige.
- **Card Style**: Ivory cards with 1px warm-gray borders, small radius, restrained shadow, and occasional folded-corner label strips.
- **Treatment**: Warm matte paper over shell background with very subtle ruled-line gradients for reading alignment.

### Typography

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

## Rules

### Composition

Compose as a reading surface with three purposeful zones: a slim command vocabulary rail, a dominant text and synthesis column, and a narrow reference/thread rail stitched to the text by strands.

### Density

Medium text density with high line-height; dense references are stacked as excerpts and knots, while data modules stay compact and secondary.

### Hierarchy

Use serif headings and body copy for authority, mono labels for provenance and command hints, and hairline rules to create sections before adding new cards or color.

### Signature Patterns

- Reference strands are 1px or dotted pseudo-element lines that connect citation knots, paragraph anchors, and right-rail excerpts across the surface.
- Language-led command links use verb-first text, bracketed mono shortcuts, and an active underline instead of icon buttons or heavy filled controls.
- Editorial folio cards combine a small mono eyebrow, serif title, quiet excerpt, and bottom provenance line with tabular numerals.
- Thread timelines use numbered knots, alternating excerpt indentation, and soft amber markers for unresolved context rather than colored alert badges.
- Tabs behave like chapter markers: low rectangular pills on a ruled baseline with the active tab expressed by text weight, underline, and a tiny strand notch.

## Layout

### Breakpoints

mobile <= 640px stacks command rail as top phrase bar and references as inline accordions; tablet 641px-1024px uses 8 columns with collapsible right rail; desktop >= 1025px uses full 12-column loom.

### Density

Prioritize reading measure around 68-76 characters; compact modules may sit in sidebars but never outnumber editorial text blocks.

### Grid

Desktop uses a 12-column shell: 2 columns command rail, 7 columns reading workspace, 3 columns context rail; all zones align to an 8px baseline and 32px strand grid.

### Responsive

References collapse after their paragraph anchors on small screens so strands become vertical rather than cross-page.

### Whitespace

Keep 40-72px outer breathing room on desktop, 24px between rails, and 16-24px internal card rhythm so heavy text remains calm.

## Guidance

### Do

- Write controls as clear command phrases such as “Weave sources”, “Trace contradiction”, and “Pin excerpt”.
- Keep long-form text in comfortable serif measure with line-height above 1.55 and visible paragraph anchors.
- Use dotted strands, numbered knots, tabs, and marginal folios to show context relationships.
- Reserve accent color for provenance, active commands, and unresolved threads rather than decoration.
- Use compact data modules only as supporting evidence panels with tabular numerals and quiet labels.

### Don't

- Do not turn the scene into analytics, CRM, admin, or KPI dashboards.
- Do not rely on floating glass palettes, AI gradient blobs, or icon-only controls.
- Do not compress threads into tiny unreadable chips; excerpts must remain scannable.
- Do not use more than two accent colors in one viewport.
- Do not let borders become boxy clutter; strands and rules should clarify relationships.

### Accessibility

Maintain WCAG AA contrast, visible focus outlines using accent hairlines, readable 16px body type, keyboard hints that supplement labels, and non-color cues for statuses.

### Usage Context

Ideal for research assistants, knowledge bases, legal or policy synthesis, editorial planning, source review, and AI copilots where trust depends on readable context.
DESIGN.md
---
version: "alpha"
name: "Context Loom Command Surface"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#8C6F3E"
  background: "#F7F4EE"
  border: "#D8D1C4"
  error: "#A34D3F"
  info: "#557186"
  muted: "#7E7A70"
  primary: "#2F3A35"
  secondary: "#6D675D"
  success: "#4F7A61"
  surface: "#FFFEFA"
  text: "#242824"
  warning: "#A97832"
typography:
  headline-lg:
    fontFamily: "Literata"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.012em"
  headline-md:
    fontFamily: "Literata"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.012em"
  body-md:
    fontFamily: "Source Serif 4"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.62
    letterSpacing: "-0.012em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "16px"
  md: "10px"
  none: "0px"
  sm: "4px"
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"
---

# Context Loom Command Surface

## Overview

Context Loom Command Surface gives a text-heavy knowledge workspace the calm of an annotated reading room: command phrases, threaded references, soft document cards, and fine connective strands organize dense context without turning the product into a metrics dashboard.

### Values

- Language is the primary interface; commands, tabs, filters, and navigation should read as clear editorial phrases rather than icon-heavy controls.
- Context should feel woven beside the main text through slim reference strands, marginal notes, and timestamped thread rails instead of competing panels.
- Compact data modules are allowed only when they support reading, synthesis, or source confidence; they stay quiet and typographic.
- The screen should preserve long-form readability with generous measure, visible hierarchy, and calm surfaces that tolerate many notes.

### Anti-Values

- No dashboard wall of charts, KPI tiles, saturated status colors, or business-intelligence chrome.
- No glassmorphism, floating neon command palettes, generic AI gradient blobs, or icon-only navigation.
- No dense table-first layout that makes the workspace feel like an admin console rather than a thinking surface.

### Visual Character

- A centered reading column uses max-width text measure with a left command rail and a right reference rail connected by one-pixel beige strand lines.
- Cards use near-flat ivory surfaces, 1px warm-gray borders, square-to-soft 10px corners, and only tiny contact shadows for document layering.
- Tabs and command links are language-led pills with underlined active verbs, bracketed keyboard hints, and no filled primary button slabs.
- Threads appear as vertical timeline rails with small numbered knots, excerpt cards, and dotted connector pseudo-elements that visually weave citations back to paragraphs.
- Compact modules are inset as quiet marginal folios with tabular numerals, hairline separators, and muted amber or blue emphasis only for provenance states.

## 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 | `#8C6F3E` |
| background | `#F7F4EE` |
| border | `#D8D1C4` |
| error | `#A34D3F` |
| info | `#557186` |
| muted | `#7E7A70` |
| primary | `#2F3A35` |
| secondary | `#6D675D` |
| success | `#4F7A61` |
| surface | `#FFFEFA` |
| text | `#242824` |
| warning | `#A97832` |

## Typography

- **Headline-Lg**: Literata, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Literata, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: Source Serif 4, 16px, weight 400, line-height 1.62.
- **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 stacks command rail as top phrase bar and references as inline accordions; tablet 641px-1024px uses 8 columns with collapsible right rail; desktop >= 1025px uses full 12-column loom.

### Density

Prioritize reading measure around 68-76 characters; compact modules may sit in sidebars but never outnumber editorial text blocks.

### Grid

Desktop uses a 12-column shell: 2 columns command rail, 7 columns reading workspace, 3 columns context rail; all zones align to an 8px baseline and 32px strand grid.

### Responsive

References collapse after their paragraph anchors on small screens so strands become vertical rather than cross-page.

### Whitespace

Keep 40-72px outer breathing room on desktop, 24px between rails, and 16-24px internal card rhythm so heavy text remains calm.

## Elevation & Depth

### Shadows

- **Lg**: 0 24px 60px rgba(47,58,53,0.10)
- **Md**: 0 10px 26px rgba(47,58,53,0.07)
- **Sm**: 0 1px 0 rgba(47,58,53,0.06)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `16px`
- **Md**: `10px`
- **None**: `0px`
- **Sm**: `4px`

### Surfaces

- **Bg Pattern**: A barely visible vertical strand grid: linear gradients at 1px width every 32px in warm beige.
- **Card Style**: Ivory cards with 1px warm-gray borders, small radius, restrained shadow, and occasional folded-corner label strips.
- **Treatment**: Warm matte paper over shell background with very subtle ruled-line gradients for reading alignment.

### Borders

- **Accent Width**: 2px
- **Character**: Hairline editorial rules, quote brackets, and dotted strands rather than heavy containers.
- **Default Width**: 1px
- **Style**: solid with dotted connector variants

## Components

### Composition

Compose as a reading surface with three purposeful zones: a slim command vocabulary rail, a dominant text and synthesis column, and a narrow reference/thread rail stitched to the text by strands.

### Density

Medium text density with high line-height; dense references are stacked as excerpts and knots, while data modules stay compact and secondary.

### Hierarchy

Use serif headings and body copy for authority, mono labels for provenance and command hints, and hairline rules to create sections before adding new cards or color.

### Signature Patterns

- Reference strands are 1px or dotted pseudo-element lines that connect citation knots, paragraph anchors, and right-rail excerpts across the surface.
- Language-led command links use verb-first text, bracketed mono shortcuts, and an active underline instead of icon buttons or heavy filled controls.
- Editorial folio cards combine a small mono eyebrow, serif title, quiet excerpt, and bottom provenance line with tabular numerals.
- Thread timelines use numbered knots, alternating excerpt indentation, and soft amber markers for unresolved context rather than colored alert badges.
- Tabs behave like chapter markers: low rectangular pills on a ruled baseline with the active tab expressed by text weight, underline, and a tiny strand notch.

## 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-019edab3-2dbd-79e0-9950-aaec5bb5fd2e/DESIGN.with-shadcn.md`.

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

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

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

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

## Do's and Don'ts

- Do Write controls as clear command phrases such as “Weave sources”, “Trace contradiction”, and “Pin excerpt”.
- Do Keep long-form text in comfortable serif measure with line-height above 1.55 and visible paragraph anchors.
- Do Use dotted strands, numbered knots, tabs, and marginal folios to show context relationships.
- Do Reserve accent color for provenance, active commands, and unresolved threads rather than decoration.
- Do Use compact data modules only as supporting evidence panels with tabular numerals and quiet labels.
- Don't Do not turn the scene into analytics, CRM, admin, or KPI dashboards.
- Don't Do not rely on floating glass palettes, AI gradient blobs, or icon-only controls.
- Don't Do not compress threads into tiny unreadable chips; excerpts must remain scannable.
- Don't Do not use more than two accent colors in one viewport.
- Don't Do not let borders become boxy clutter; strands and rules should clarify relationships.

### Accessibility

Maintain WCAG AA contrast, visible focus outlines using accent hairlines, readable 16px body type, keyboard hints that supplement labels, and non-color cues for statuses.

### Usage Context

Ideal for research assistants, knowledge bases, legal or policy synthesis, editorial planning, source review, and AI copilots where trust depends on readable context.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "context-loom-command-surface",
  "type": "registry:theme",
  "title": "Context Loom Command Surface shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F4EE",
      "foreground": "#242824",
      "card": "#FFFEFA",
      "card-foreground": "#242824",
      "popover": "#FFFEFA",
      "popover-foreground": "#242824",
      "primary": "#2F3A35",
      "primary-foreground": "#ffffff",
      "secondary": "#6D675D",
      "secondary-foreground": "#ffffff",
      "muted": "#7E7A70",
      "muted-foreground": "#242824",
      "accent": "#8C6F3E",
      "accent-foreground": "#ffffff",
      "destructive": "#A34D3F",
      "border": "#D8D1C4",
      "input": "#D8D1C4",
      "ring": "#8C6F3E",
      "chart-1": "#2F3A35",
      "chart-2": "#6D675D",
      "chart-3": "#8C6F3E",
      "chart-4": "#4F7A61",
      "chart-5": "#A97832",
      "sidebar": "#FFFEFA",
      "sidebar-foreground": "#242824",
      "sidebar-primary": "#2F3A35",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#557186",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8D1C4",
      "sidebar-ring": "#8C6F3E",
      "radius": "10px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2F3A35",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#8C6F3E",
      "accent-foreground": "#ffffff",
      "destructive": "#A34D3F",
      "border": "#303642",
      "input": "#303642",
      "ring": "#8C6F3E",
      "chart-1": "#2F3A35",
      "chart-2": "#6D675D",
      "chart-3": "#8C6F3E",
      "chart-4": "#4F7A61",
      "chart-5": "#A97832",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2F3A35",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#8C6F3E",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#8C6F3E",
      "radius": "10px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edab3-2dbd-79e0-9950-aaec5bb5fd2e",
    "slug": "context-loom-command-surface",
    "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

the full element showcase
embodiment · context-loom-command-surface
DESIGN.md

at a glance

Palette

Typography

headline-lgLiterata · 28px · 700

The quick brown fox jumps

headline-mdLiterata · 23px · 600

The quick brown fox jumps

body-mdSource Serif 4 · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

Components rendered with this language’s tokens — colors, type, and rounded corners as specified.

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl48px
  • 4xl64px

Shape

full9999px
lg16px
md10px
none0px
sm4px
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: #F7F4EE;
  --foreground: #242824;
  --card: #FFFEFA;
  --card-foreground: #242824;
  --popover: #FFFEFA;
  --popover-foreground: #242824;
  --primary: #2F3A35;
  --primary-foreground: #ffffff;
  --secondary: #6D675D;
  --secondary-foreground: #ffffff;
  --muted: #7E7A70;
  --muted-foreground: #242824;
  --accent: #8C6F3E;
  --accent-foreground: #ffffff;
  --destructive: #A34D3F;
  --border: #D8D1C4;
  --input: #D8D1C4;
  --ring: #8C6F3E;
  --chart-1: #2F3A35;
  --chart-2: #6D675D;
  --chart-3: #8C6F3E;
  --chart-4: #4F7A61;
  --chart-5: #A97832;
  --sidebar: #FFFEFA;
  --sidebar-foreground: #242824;
  --sidebar-primary: #2F3A35;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #557186;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D8D1C4;
  --sidebar-ring: #8C6F3E;
  --radius: 10px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #2F3A35;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #8C6F3E;
  --accent-foreground: #ffffff;
  --destructive: #A34D3F;
  --border: #303642;
  --input: #303642;
  --ring: #8C6F3E;
  --chart-1: #2F3A35;
  --chart-2: #6D675D;
  --chart-3: #8C6F3E;
  --chart-4: #4F7A61;
  --chart-5: #A97832;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #2F3A35;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #8C6F3E;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #8C6F3E;
  --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 ContextLoomCommandSurfaceShadcnKit() {
  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">Context Loom Command Surface</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": "context-loom-command-surface",
  "type": "registry:theme",
  "title": "Context Loom Command Surface shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F4EE",
      "foreground": "#242824",
      "card": "#FFFEFA",
      "card-foreground": "#242824",
      "popover": "#FFFEFA",
      "popover-foreground": "#242824",
      "primary": "#2F3A35",
      "primary-foreground": "#ffffff",
      "secondary": "#6D675D",
      "secondary-foreground": "#ffffff",
      "muted": "#7E7A70",
      "muted-foreground": "#242824",
      "accent": "#8C6F3E",
      "accent-foreground": "#ffffff",
      "destructive": "#A34D3F",
      "border": "#D8D1C4",
      "input": "#D8D1C4",
      "ring": "#8C6F3E",
      "chart-1": "#2F3A35",
      "chart-2": "#6D675D",
      "chart-3": "#8C6F3E",
      "chart-4": "#4F7A61",
      "chart-5": "#A97832",
      "sidebar": "#FFFEFA",
      "sidebar-foreground": "#242824",
      "sidebar-primary": "#2F3A35",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#557186",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8D1C4",
      "sidebar-ring": "#8C6F3E",
      "radius": "10px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2F3A35",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#8C6F3E",
      "accent-foreground": "#ffffff",
      "destructive": "#A34D3F",
      "border": "#303642",
      "input": "#303642",
      "ring": "#8C6F3E",
      "chart-1": "#2F3A35",
      "chart-2": "#6D675D",
      "chart-3": "#8C6F3E",
      "chart-4": "#4F7A61",
      "chart-5": "#A97832",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2F3A35",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#8C6F3E",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#8C6F3E",
      "radius": "10px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edab3-2dbd-79e0-9950-aaec5bb5fd2e",
    "slug": "context-loom-command-surface",
    "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
# Context Loom Command Surface shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019edab3-2dbd-79e0-9950-aaec5bb5fd2e`
Slug: `context-loom-command-surface`

## Intent

Context Loom Command Surface gives a text-heavy knowledge workspace the calm of an annotated reading room: command phrases, threaded references, soft document cards, and fine connective strands organize dense context without turning the product into a metrics dashboard.

## Required primitives

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

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

## Token cues

Colors:

{
  "accent": "#8C6F3E",
  "background": "#F7F4EE",
  "border": "#D8D1C4",
  "error": "#A34D3F",
  "info": "#557186",
  "muted": "#7E7A70",
  "primary": "#2F3A35",
  "secondary": "#6D675D",
  "success": "#4F7A61",
  "surface": "#FFFEFA",
  "text": "#242824",
  "warning": "#A97832"
}

Typography:

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

## Visual character to preserve

- A centered reading column uses max-width text measure with a left command rail and a right reference rail connected by one-pixel beige strand lines.
- Cards use near-flat ivory surfaces, 1px warm-gray borders, square-to-soft 10px corners, and only tiny contact shadows for document layering.
- Tabs and command links are language-led pills with underlined active verbs, bracketed keyboard hints, and no filled primary button slabs.
- Threads appear as vertical timeline rails with small numbered knots, excerpt cards, and dotted connector pseudo-elements that visually weave citations back to paragraphs.
- Compact modules are inset as quiet marginal folios with tabular numerals, hairline separators, and muted amber or blue emphasis only for provenance states.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "pebble",
  "border": "solid",
  "underlay": false,
  "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/context-loom-command-surface/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Write controls as clear command phrases such as “Weave sources”, “Trace contradiction”, and “Pin excerpt”.; Keep long-form text in comfortable serif measure with line-height above 1.55 and visible paragraph anchors.; Use dotted strands, numbered knots, tabs, and marginal folios to show context relationships.; Reserve accent color for provenance, active commands, and unresolved threads rather than decoration.; Use compact data modules only as supporting evidence panels with tabular numerals and quiet labels.
- Do not: Do not turn the scene into analytics, CRM, admin, or KPI dashboards.; Do not rely on floating glass palettes, AI gradient blobs, or icon-only controls.; Do not compress threads into tiny unreadable chips; excerpts must remain scannable.; Do not use more than two accent colors in one viewport.; Do not let borders become boxy clutter; strands and rules should clarify relationships.

## 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 ContextLoomCommandSurfaceShadcnKit() {
  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">Context Loom Command Surface</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 stacks command rail as top phrase bar and references as inline accordions; tablet 641px-1024px uses 8 columns with collapsible right rail; desktop >= 1025px uses full 12-column loom.",
  "density": "Prioritize reading measure around 68-76 characters; compact modules may sit in sidebars but never outnumber editorial text blocks.",
  "grid": "Desktop uses a 12-column shell: 2 columns command rail, 7 columns reading workspace, 3 columns context rail; all zones align to an 8px baseline and 32px strand grid.",
  "responsive": "References collapse after their paragraph anchors on small screens so strands become vertical rather than cross-page.",
  "whitespace": "Keep 40-72px outer breathing room on desktop, 24px between rails, and 16-24px internal card rhythm so heavy text remains calm."
}
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-019edab3-2dbd-79e0-9950-aaec5bb5fd2e",
    "name": "Context Loom Command Surface",
    "slug": "context-loom-command-surface"
  },
  "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": [
    "A centered reading column uses max-width text measure with a left command rail and a right reference rail connected by one-pixel beige strand lines.",
    "Cards use near-flat ivory surfaces, 1px warm-gray borders, square-to-soft 10px corners, and only tiny contact shadows for document layering.",
    "Tabs and command links are language-led pills with underlined active verbs, bracketed keyboard hints, and no filled primary button slabs.",
    "Threads appear as vertical timeline rails with small numbered knots, excerpt cards, and dotted connector pseudo-elements that visually weave citations back to paragraphs.",
    "Compact modules are inset as quiet marginal folios with tabular numerals, hairline separators, and muted amber or blue emphasis only for provenance states."
  ],
  "visualProfile": {
    "family": "editorial",
    "material": "flat",
    "contour": "pebble",
    "border": "solid",
    "underlay": false,
    "grain": false,
    "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": "Context Loom Command Surface launch room",
        "description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
        "primaryAction": "Apply theme",
        "secondaryAction": "Review states",
        "stats": [
          {
            "label": "components",
            "value": "16",
            "tone": "accent"
          },
          {
            "label": "states",
            "value": "ready"
          },
          {
            "label": "density",
            "value": "balanced",
            "tone": "warning"
          }
        ],
        "rows": [
          {
            "label": "Primary flow",
            "value": "mapped",
            "status": "active"
          },
          {
            "label": "Token coverage",
            "value": "semantic",
            "status": "synced"
          },
          {
            "label": "Responsive proof",
            "value": "queued",
            "status": "review"
          }
        ],
        "statuses": [
          "Active",
          "Synced",
          "Draft"
        ]
      }
    },
    {
      "id": "detail-editor",
      "title": "Detail editor",
      "viewport": "tablet",
      "primitives": [
        "button",
        "card",
        "input",
        "textarea",
        "select",
        "checkbox",
        "switch",
        "slider",
        "dialog",
        "sheet"
      ],
      "composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
      "mustShow": [
        "focus ring",
        "error or destructive state",
        "dialog or sheet treatment",
        "written guidance content"
      ],
      "avoid": [
        "unstyled browser controls",
        "floating cards inside cards",
        "missing labels"
      ],
      "scene": {
        "eyebrow": "editing flow",
        "headline": "Language recipe editor",
        "description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
        "primaryAction": "Save recipe",
        "secondaryAction": "Open sheet",
        "fields": [
          {
            "label": "Component family",
            "value": "Narrative cards"
          },
          {
            "label": "State treatment",
            "value": "Visible focus + validation"
          },
          {
            "label": "Motion",
            "value": "Small lift, no opacity-only fade"
          }
        ],
        "statuses": [
          "Focus",
          "Invalid",
          "Confirmed"
        ]
      }
    },
    {
      "id": "data-operations",
      "title": "Data operations",
      "viewport": "mobile",
      "primitives": [
        "button",
        "tabs",
        "badge",
        "dropdown-menu",
        "table",
        "tooltip",
        "separator"
      ],
      "composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
      "mustShow": [
        "responsive reflow",
        "dense row styling",
        "menu affordance",
        "status badge system"
      ],
      "avoid": [
        "desktop-only tables",
        "text overflow",
        "default shadcn spacing without Katagami character"
      ],
      "scene": {
        "eyebrow": "operations",
        "headline": "Compact review queue",
        "description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
        "primaryAction": "Resolve",
        "secondaryAction": "Filter",
        "rows": [
          {
            "label": "Button hierarchy",
            "value": "approved",
            "status": "ok"
          },
          {
            "label": "Table rhythm",
            "value": "needs pass",
            "status": "watch"
          },
          {
            "label": "Empty state",
            "value": "designed",
            "status": "done"
          }
        ],
        "statuses": [
          "Queued",
          "Blocked",
          "Done"
        ]
      }
    }
  ],
  "componentRecipes": [
    {
      "primitive": "button",
      "intent": "Prove action hierarchy, focus, disabled, and destructive states."
    },
    {
      "primitive": "card",
      "intent": "Carry the language surface, border, elevation, and density rules."
    },
    {
      "primitive": "input",
      "intent": "Show labels, focus rings, validation, and spacing rhythm."
    },
    {
      "primitive": "textarea",
      "intent": "Show longer guidance, validation copy, and writing density."
    },
    {
      "primitive": "select",
      "intent": "Show filtering, selection contrast, and menu trigger styling."
    },
    {
      "primitive": "dialog",
      "intent": "Show centered decision states and overlay treatment."
    },
    {
      "primitive": "sheet",
      "intent": "Show contextual side panels and responsive editing."
    },
    {
      "primitive": "tabs",
      "intent": "Show navigational structure and active/inactive contrast."
    },
    {
      "primitive": "badge",
      "intent": "Show compact status vocabulary and semantic colors."
    },
    {
      "primitive": "separator",
      "intent": "Show section rhythm without generic gray dividers."
    },
    {
      "primitive": "checkbox",
      "intent": "Show binary selection with visible focus and checked states."
    },
    {
      "primitive": "switch",
      "intent": "Show settings toggles and on/off contrast."
    },
    {
      "primitive": "slider",
      "intent": "Show numeric adjustment with track/thumb styling."
    },
    {
      "primitive": "tooltip",
      "intent": "Show concise explanation styling above compact controls."
    },
    {
      "primitive": "dropdown-menu",
      "intent": "Show action menus, destructive items, and grouped choices."
    },
    {
      "primitive": "table",
      "intent": "Show dense operational data, separators, row states, and responsive behavior."
    }
  ],
  "qualityRules": {
    "do": [
      "Write controls as clear command phrases such as “Weave sources”, “Trace contradiction”, and “Pin excerpt”.",
      "Keep long-form text in comfortable serif measure with line-height above 1.55 and visible paragraph anchors.",
      "Use dotted strands, numbered knots, tabs, and marginal folios to show context relationships.",
      "Reserve accent color for provenance, active commands, and unresolved threads rather than decoration.",
      "Use compact data modules only as supporting evidence panels with tabular numerals and quiet labels."
    ],
    "dont": [
      "Do not turn the scene into analytics, CRM, admin, or KPI dashboards.",
      "Do not rely on floating glass palettes, AI gradient blobs, or icon-only controls.",
      "Do not compress threads into tiny unreadable chips; excerpts must remain scannable.",
      "Do not use more than two accent colors in one viewport.",
      "Do not let borders become boxy clutter; strands and rules should clarify relationships."
    ]
  }
}
related

More like this