back to gallery
design language·reference-loom-shell

Reference Loom Shell

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
Reference Loom Shell is a calm, text-first command surface for AYA: a knowledge workspace where documents, threads, citations, and lightweight data modules are woven together without becoming a dashboard. It treats context as quiet strands that connect reading, command, and provenance across a generous editorial workspace.
values
Long-form readability before chromeCommand actions embedded in language, not oversized controlsContext shown as provenance strands and margins rather than dashboard panelsCompact modules that support the text flow instead of competing with itCalm contrast, precise spacing, and restraint under high information load
anti-values
×Metric-wall dashboards with equal-weight cards×Generic SaaS gradients, glass, and floating shadows×Dense sidebars that steal attention from the document×Arbitrary rounded-card softness without a single geometry
tokens
borders4 items
accent width
2px
character
Hairline borders in warm gray, with accent borders used only for selected anchors and active command rails.
default width
1px
style
solid
colors12 items
accent
#A36A3D
background
#F7F4EE
border
#D8D0C3
error
#A0443E
info
#496C8C
muted
#79746B
primary
#1E3A36
secondary
#6F665A
success
#3F765C
surface
#FFFCF6
text
#1F2320
warning
#B37A2B
motion3 items
duration
180ms
easing
cubic-bezier(0.2, 0.8, 0.2, 1)
philosophy
Motion is a quiet thread pull: command rails slide 6px, anchors underline from left to right, and context cards reveal by tracing their border path.
radii5 items
full
9999px
lg
18px
md
10px
none
0
sm
4px
shadows3 items
lg
0 24px 70px rgba(31,35,32,0.10)
md
0 12px 30px rgba(31,35,32,0.07)
sm
0 1px 0 rgba(31,35,32,0.04)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
Subtle horizontal paper ruling and occasional 1px woven connector lines at low opacity.
card style
Hairline bordered cards with clipped command tabs, small mono labels, and source-index notches.
treatment
Warm ivory paper panels over a chalk-shell background, with almost no elevation and visible reading gutters.
typography8 items
base size
16px
body font
Source Serif 4
google fonts url
https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,500;9..144,650&family=IBM+Plex+Mono:wght@400;500;600&family=Source+Serif+4:opsz,wght@8..60,400;8..60,500;8..60,600&display=swap
heading font
Fraunces
letter spacing
-0.015em
line height
1.62
mono font
IBM Plex Mono
scale ratio
1.2
rules
composition
Use one dominant reading artifact as the center of gravity, supported by a narrow command rail and a contextual margin. Compact data modules must attach to passages, commands, or timeline knots instead of forming a freestanding dashboard grid.
density
Medium-high textual density is acceptable when line length stays controlled, margins remain generous, and secondary modules use 12-14px mono labels with clear source relationships.
hierarchy
Hierarchy comes from typographic voice and spatial attachment: Fraunces for chapter-level intent, Source Serif 4 for readable prose, IBM Plex Mono for commands, references, timestamps, and state labels.
signature patterns
Reference strand connectors originate from inline text anchors and terminate at margin cards, changing from muted gray to accent umber only when selected or cited.Command tabs clip into card corners with mono bracket verbs such as [link], [summarize], and [trace], creating actions that read like language annotations.Timeline knots sit on a single quiet vertical rule and expand into short editorial notes, avoiding equal-height dashboard event cards.Context cards include source-index notches and baseline-aligned tabs so references appear stitched to the document rather than stacked as widgets.
layout
breakpoints
Desktop >=1100px keeps rail/document/context triad; tablet 700-1099px folds the context margin below the document as referenced strips; mobile <700px turns command rail into a top command bar and stacks strands as inline source drawers.
grid
Desktop uses a 72px fixed command rail, 1fr document canvas, and 320px context margin inside a max 1440px shell; document text maxes at 72 characters while modules hang from the right gutter.
whitespace
Whitespace is editorial: broad outer gutters, 24px between reading blocks, 12px inside cards, and deliberate quiet around active anchors so dense references remain calm.
guidance
do
  • Keep the document or thread as the dominant object; every module should answer what passage, source, or command it supports.
  • Use mono command verbs sparingly and place them near text baselines, tabs, and card corners.
  • Draw reference relationships with hairline strands, source notches, and selected anchor underlines rather than color blocks.
  • Maintain 16px body text, high contrast, and line lengths suitable for sustained reading.
avoid
  • Do not create a metrics dashboard, KPI grid, or wall of equal cards.
  • Do not use glassmorphism, neon gradients, heavy drop shadows, or arbitrary bright semantic colors.
  • Do not let context strands become decorative spaghetti; each line must connect a visible anchor to a useful reference.
  • Do not mix many radius sizes or pill shapes; preserve the 4px/10px/18px geometry.
katagami spec
# Reference Loom Shell

## Philosophy

Reference Loom Shell is a calm, text-first command surface for AYA: a knowledge workspace where documents, threads, citations, and lightweight data modules are woven together without becoming a dashboard. It treats context as quiet strands that connect reading, command, and provenance across a generous editorial workspace.

### Values

- Long-form readability before chrome
- Command actions embedded in language, not oversized controls
- Context shown as provenance strands and margins rather than dashboard panels
- Compact modules that support the text flow instead of competing with it
- Calm contrast, precise spacing, and restraint under high information load

### Anti-Values

- Metric-wall dashboards with equal-weight cards
- Generic SaaS gradients, glass, and floating shadows
- Dense sidebars that steal attention from the document
- Arbitrary rounded-card softness without a single geometry

### Visual Character

- A two-column editorial shell uses a 72px command rail, a minmax document column, and a 320px context margin so the reading surface remains dominant at desktop sizes.
- Reference strands are rendered as thin SVG or border-left paths in muted ink that connect highlighted text anchors to source cards, timeline events, and thread replies.
- Cards use nearly flat ivory surfaces with 1px hairline borders, 10px radius, and clipped corner command tabs instead of heavy shadows or colored fills.
- Tabs and command links are language-led: small mono verbs, bracket markers, underline rails, and active states that slide along the text baseline rather than large pills.
- Timelines use compact timestamp knots on a single vertical rule with alternating note widths, preserving narrative order without resembling analytics widgets.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Hairline borders in warm gray, with accent borders used only for selected anchors and active command rails.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#A36A3D` |
| background | `#F7F4EE` |
| border | `#D8D0C3` |
| error | `#A0443E` |
| info | `#496C8C` |
| muted | `#79746B` |
| primary | `#1E3A36` |
| secondary | `#6F665A` |
| success | `#3F765C` |
| surface | `#FFFCF6` |
| text | `#1F2320` |
| warning | `#B37A2B` |

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1)
- **Philosophy**: Motion is a quiet thread pull: command rails slide 6px, anchors underline from left to right, and context cards reveal by tracing their border path.

### Radii

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

### Shadows

- **Lg**: 0 24px 70px rgba(31,35,32,0.10)
- **Md**: 0 12px 30px rgba(31,35,32,0.07)
- **Sm**: 0 1px 0 rgba(31,35,32,0.04)

### Spacing

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

### Surfaces

- **Bg Pattern**: Subtle horizontal paper ruling and occasional 1px woven connector lines at low opacity.
- **Card Style**: Hairline bordered cards with clipped command tabs, small mono labels, and source-index notches.
- **Treatment**: Warm ivory paper panels over a chalk-shell background, with almost no elevation and visible reading gutters.

### Typography

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

## Rules

### Composition

Use one dominant reading artifact as the center of gravity, supported by a narrow command rail and a contextual margin. Compact data modules must attach to passages, commands, or timeline knots instead of forming a freestanding dashboard grid.

### Density

Medium-high textual density is acceptable when line length stays controlled, margins remain generous, and secondary modules use 12-14px mono labels with clear source relationships.

### Hierarchy

Hierarchy comes from typographic voice and spatial attachment: Fraunces for chapter-level intent, Source Serif 4 for readable prose, IBM Plex Mono for commands, references, timestamps, and state labels.

### Signature Patterns

- Reference strand connectors originate from inline text anchors and terminate at margin cards, changing from muted gray to accent umber only when selected or cited.
- Command tabs clip into card corners with mono bracket verbs such as [link], [summarize], and [trace], creating actions that read like language annotations.
- Timeline knots sit on a single quiet vertical rule and expand into short editorial notes, avoiding equal-height dashboard event cards.
- Context cards include source-index notches and baseline-aligned tabs so references appear stitched to the document rather than stacked as widgets.

## Layout

### Breakpoints

Desktop >=1100px keeps rail/document/context triad; tablet 700-1099px folds the context margin below the document as referenced strips; mobile <700px turns command rail into a top command bar and stacks strands as inline source drawers.

### Grid

Desktop uses a 72px fixed command rail, 1fr document canvas, and 320px context margin inside a max 1440px shell; document text maxes at 72 characters while modules hang from the right gutter.

### Whitespace

Whitespace is editorial: broad outer gutters, 24px between reading blocks, 12px inside cards, and deliberate quiet around active anchors so dense references remain calm.

## Guidance

### Do

- Keep the document or thread as the dominant object; every module should answer what passage, source, or command it supports.
- Use mono command verbs sparingly and place them near text baselines, tabs, and card corners.
- Draw reference relationships with hairline strands, source notches, and selected anchor underlines rather than color blocks.
- Maintain 16px body text, high contrast, and line lengths suitable for sustained reading.

### Don't

- Do not create a metrics dashboard, KPI grid, or wall of equal cards.
- Do not use glassmorphism, neon gradients, heavy drop shadows, or arbitrary bright semantic colors.
- Do not let context strands become decorative spaghetti; each line must connect a visible anchor to a useful reference.
- Do not mix many radius sizes or pill shapes; preserve the 4px/10px/18px geometry.

### Accessibility

Use strong text contrast on ivory backgrounds, never rely on strand color alone, keep focus rings visible with 2px accent outlines, and provide text labels for all command links and reference states.

### Usage Context

Best for text-heavy AI workspaces, research notebooks, legal or policy analysis tools, knowledge bases, and editorial planning systems where provenance and command operations must stay close to prose.
DESIGN.md
---
version: "alpha"
name: "Reference Loom Shell"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#A36A3D"
  background: "#F7F4EE"
  border: "#D8D0C3"
  error: "#A0443E"
  info: "#496C8C"
  muted: "#79746B"
  primary: "#1E3A36"
  secondary: "#6F665A"
  success: "#3F765C"
  surface: "#FFFCF6"
  text: "#1F2320"
  warning: "#B37A2B"
typography:
  headline-lg:
    fontFamily: "Fraunces"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.015em"
  headline-md:
    fontFamily: "Fraunces"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.015em"
  body-md:
    fontFamily: "Source Serif 4"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.62
    letterSpacing: "-0.015em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "18px"
  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"
---

# Reference Loom Shell

## Overview

Reference Loom Shell is a calm, text-first command surface for AYA: a knowledge workspace where documents, threads, citations, and lightweight data modules are woven together without becoming a dashboard. It treats context as quiet strands that connect reading, command, and provenance across a generous editorial workspace.

### Values

- Long-form readability before chrome
- Command actions embedded in language, not oversized controls
- Context shown as provenance strands and margins rather than dashboard panels
- Compact modules that support the text flow instead of competing with it
- Calm contrast, precise spacing, and restraint under high information load

### Anti-Values

- Metric-wall dashboards with equal-weight cards
- Generic SaaS gradients, glass, and floating shadows
- Dense sidebars that steal attention from the document
- Arbitrary rounded-card softness without a single geometry

### Visual Character

- A two-column editorial shell uses a 72px command rail, a minmax document column, and a 320px context margin so the reading surface remains dominant at desktop sizes.
- Reference strands are rendered as thin SVG or border-left paths in muted ink that connect highlighted text anchors to source cards, timeline events, and thread replies.
- Cards use nearly flat ivory surfaces with 1px hairline borders, 10px radius, and clipped corner command tabs instead of heavy shadows or colored fills.
- Tabs and command links are language-led: small mono verbs, bracket markers, underline rails, and active states that slide along the text baseline rather than large pills.
- Timelines use compact timestamp knots on a single vertical rule with alternating note widths, preserving narrative order without resembling analytics widgets.

## 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 | `#A36A3D` |
| background | `#F7F4EE` |
| border | `#D8D0C3` |
| error | `#A0443E` |
| info | `#496C8C` |
| muted | `#79746B` |
| primary | `#1E3A36` |
| secondary | `#6F665A` |
| success | `#3F765C` |
| surface | `#FFFCF6` |
| text | `#1F2320` |
| warning | `#B37A2B` |

## Typography

- **Headline-Lg**: Fraunces, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Fraunces, 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

Desktop >=1100px keeps rail/document/context triad; tablet 700-1099px folds the context margin below the document as referenced strips; mobile <700px turns command rail into a top command bar and stacks strands as inline source drawers.

### Grid

Desktop uses a 72px fixed command rail, 1fr document canvas, and 320px context margin inside a max 1440px shell; document text maxes at 72 characters while modules hang from the right gutter.

### Whitespace

Whitespace is editorial: broad outer gutters, 24px between reading blocks, 12px inside cards, and deliberate quiet around active anchors so dense references remain calm.

## Elevation & Depth

### Shadows

- **Lg**: 0 24px 70px rgba(31,35,32,0.10)
- **Md**: 0 12px 30px rgba(31,35,32,0.07)
- **Sm**: 0 1px 0 rgba(31,35,32,0.04)

## Shapes

### Rounded

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

### Surfaces

- **Bg Pattern**: Subtle horizontal paper ruling and occasional 1px woven connector lines at low opacity.
- **Card Style**: Hairline bordered cards with clipped command tabs, small mono labels, and source-index notches.
- **Treatment**: Warm ivory paper panels over a chalk-shell background, with almost no elevation and visible reading gutters.

### Borders

- **Accent Width**: 2px
- **Character**: Hairline borders in warm gray, with accent borders used only for selected anchors and active command rails.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use one dominant reading artifact as the center of gravity, supported by a narrow command rail and a contextual margin. Compact data modules must attach to passages, commands, or timeline knots instead of forming a freestanding dashboard grid.

### Density

Medium-high textual density is acceptable when line length stays controlled, margins remain generous, and secondary modules use 12-14px mono labels with clear source relationships.

### Hierarchy

Hierarchy comes from typographic voice and spatial attachment: Fraunces for chapter-level intent, Source Serif 4 for readable prose, IBM Plex Mono for commands, references, timestamps, and state labels.

### Signature Patterns

- Reference strand connectors originate from inline text anchors and terminate at margin cards, changing from muted gray to accent umber only when selected or cited.
- Command tabs clip into card corners with mono bracket verbs such as [link], [summarize], and [trace], creating actions that read like language annotations.
- Timeline knots sit on a single quiet vertical rule and expand into short editorial notes, avoiding equal-height dashboard event cards.
- Context cards include source-index notches and baseline-aligned tabs so references appear stitched to the document rather than stacked as widgets.

## 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-b3d3-7751-aa55-5e34b1110417/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 Keep the document or thread as the dominant object; every module should answer what passage, source, or command it supports.
- Do Use mono command verbs sparingly and place them near text baselines, tabs, and card corners.
- Do Draw reference relationships with hairline strands, source notches, and selected anchor underlines rather than color blocks.
- Do Maintain 16px body text, high contrast, and line lengths suitable for sustained reading.
- Don't Do not create a metrics dashboard, KPI grid, or wall of equal cards.
- Don't Do not use glassmorphism, neon gradients, heavy drop shadows, or arbitrary bright semantic colors.
- Don't Do not let context strands become decorative spaghetti; each line must connect a visible anchor to a useful reference.
- Don't Do not mix many radius sizes or pill shapes; preserve the 4px/10px/18px geometry.

### Accessibility

Use strong text contrast on ivory backgrounds, never rely on strand color alone, keep focus rings visible with 2px accent outlines, and provide text labels for all command links and reference states.

### Usage Context

Best for text-heavy AI workspaces, research notebooks, legal or policy analysis tools, knowledge bases, and editorial planning systems where provenance and command operations must stay close to prose.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "reference-loom-shell",
  "type": "registry:theme",
  "title": "Reference Loom Shell shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F4EE",
      "foreground": "#1F2320",
      "card": "#FFFCF6",
      "card-foreground": "#1F2320",
      "popover": "#FFFCF6",
      "popover-foreground": "#1F2320",
      "primary": "#1E3A36",
      "primary-foreground": "#ffffff",
      "secondary": "#6F665A",
      "secondary-foreground": "#ffffff",
      "muted": "#79746B",
      "muted-foreground": "#1F2320",
      "accent": "#A36A3D",
      "accent-foreground": "#ffffff",
      "destructive": "#A0443E",
      "border": "#D8D0C3",
      "input": "#D8D0C3",
      "ring": "#A36A3D",
      "chart-1": "#1E3A36",
      "chart-2": "#6F665A",
      "chart-3": "#A36A3D",
      "chart-4": "#3F765C",
      "chart-5": "#B37A2B",
      "sidebar": "#FFFCF6",
      "sidebar-foreground": "#1F2320",
      "sidebar-primary": "#1E3A36",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#496C8C",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8D0C3",
      "sidebar-ring": "#A36A3D",
      "radius": "10px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1E3A36",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#A36A3D",
      "accent-foreground": "#ffffff",
      "destructive": "#A0443E",
      "border": "#303642",
      "input": "#303642",
      "ring": "#A36A3D",
      "chart-1": "#1E3A36",
      "chart-2": "#6F665A",
      "chart-3": "#A36A3D",
      "chart-4": "#3F765C",
      "chart-5": "#B37A2B",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1E3A36",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#A36A3D",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#A36A3D",
      "radius": "10px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edab3-b3d3-7751-aa55-5e34b1110417",
    "slug": "reference-loom-shell",
    "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

Reference Loom Shell

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

The quick brown fox jumps

headline-mdFraunces · 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
lg18px
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: #1F2320;
  --card: #FFFCF6;
  --card-foreground: #1F2320;
  --popover: #FFFCF6;
  --popover-foreground: #1F2320;
  --primary: #1E3A36;
  --primary-foreground: #ffffff;
  --secondary: #6F665A;
  --secondary-foreground: #ffffff;
  --muted: #79746B;
  --muted-foreground: #1F2320;
  --accent: #A36A3D;
  --accent-foreground: #ffffff;
  --destructive: #A0443E;
  --border: #D8D0C3;
  --input: #D8D0C3;
  --ring: #A36A3D;
  --chart-1: #1E3A36;
  --chart-2: #6F665A;
  --chart-3: #A36A3D;
  --chart-4: #3F765C;
  --chart-5: #B37A2B;
  --sidebar: #FFFCF6;
  --sidebar-foreground: #1F2320;
  --sidebar-primary: #1E3A36;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #496C8C;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #D8D0C3;
  --sidebar-ring: #A36A3D;
  --radius: 10px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #1E3A36;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #A36A3D;
  --accent-foreground: #ffffff;
  --destructive: #A0443E;
  --border: #303642;
  --input: #303642;
  --ring: #A36A3D;
  --chart-1: #1E3A36;
  --chart-2: #6F665A;
  --chart-3: #A36A3D;
  --chart-4: #3F765C;
  --chart-5: #B37A2B;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #1E3A36;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #A36A3D;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #A36A3D;
  --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 ReferenceLoomShellShadcnKit() {
  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">Reference Loom Shell</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": "reference-loom-shell",
  "type": "registry:theme",
  "title": "Reference Loom Shell shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F7F4EE",
      "foreground": "#1F2320",
      "card": "#FFFCF6",
      "card-foreground": "#1F2320",
      "popover": "#FFFCF6",
      "popover-foreground": "#1F2320",
      "primary": "#1E3A36",
      "primary-foreground": "#ffffff",
      "secondary": "#6F665A",
      "secondary-foreground": "#ffffff",
      "muted": "#79746B",
      "muted-foreground": "#1F2320",
      "accent": "#A36A3D",
      "accent-foreground": "#ffffff",
      "destructive": "#A0443E",
      "border": "#D8D0C3",
      "input": "#D8D0C3",
      "ring": "#A36A3D",
      "chart-1": "#1E3A36",
      "chart-2": "#6F665A",
      "chart-3": "#A36A3D",
      "chart-4": "#3F765C",
      "chart-5": "#B37A2B",
      "sidebar": "#FFFCF6",
      "sidebar-foreground": "#1F2320",
      "sidebar-primary": "#1E3A36",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#496C8C",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#D8D0C3",
      "sidebar-ring": "#A36A3D",
      "radius": "10px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1E3A36",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#A36A3D",
      "accent-foreground": "#ffffff",
      "destructive": "#A0443E",
      "border": "#303642",
      "input": "#303642",
      "ring": "#A36A3D",
      "chart-1": "#1E3A36",
      "chart-2": "#6F665A",
      "chart-3": "#A36A3D",
      "chart-4": "#3F765C",
      "chart-5": "#B37A2B",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1E3A36",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#A36A3D",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#A36A3D",
      "radius": "10px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edab3-b3d3-7751-aa55-5e34b1110417",
    "slug": "reference-loom-shell",
    "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
# Reference Loom Shell shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019edab3-b3d3-7751-aa55-5e34b1110417`
Slug: `reference-loom-shell`

## Intent

Reference Loom Shell is a calm, text-first command surface for AYA: a knowledge workspace where documents, threads, citations, and lightweight data modules are woven together without becoming a dashboard. It treats context as quiet strands that connect reading, command, and provenance across a generous editorial workspace.

## 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": "#A36A3D",
  "background": "#F7F4EE",
  "border": "#D8D0C3",
  "error": "#A0443E",
  "info": "#496C8C",
  "muted": "#79746B",
  "primary": "#1E3A36",
  "secondary": "#6F665A",
  "success": "#3F765C",
  "surface": "#FFFCF6",
  "text": "#1F2320",
  "warning": "#B37A2B"
}

Typography:

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

## Visual character to preserve

- A two-column editorial shell uses a 72px command rail, a minmax document column, and a 320px context margin so the reading surface remains dominant at desktop sizes.
- Reference strands are rendered as thin SVG or border-left paths in muted ink that connect highlighted text anchors to source cards, timeline events, and thread replies.
- Cards use nearly flat ivory surfaces with 1px hairline borders, 10px radius, and clipped corner command tabs instead of heavy shadows or colored fills.
- Tabs and command links are language-led: small mono verbs, bracket markers, underline rails, and active states that slide along the text baseline rather than large pills.
- Timelines use compact timestamp knots on a single vertical rule with alternating note widths, preserving narrative order without resembling analytics widgets.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "pebble",
  "border": "dashed",
  "underlay": false,
  "grain": true,
  "stickerBadges": true,
  "motion": "still",
  "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/reference-loom-shell/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: Keep the document or thread as the dominant object; every module should answer what passage, source, or command it supports.; Use mono command verbs sparingly and place them near text baselines, tabs, and card corners.; Draw reference relationships with hairline strands, source notches, and selected anchor underlines rather than color blocks.; Maintain 16px body text, high contrast, and line lengths suitable for sustained reading.
- Do not: Do not create a metrics dashboard, KPI grid, or wall of equal cards.; Do not use glassmorphism, neon gradients, heavy drop shadows, or arbitrary bright semantic colors.; Do not let context strands become decorative spaghetti; each line must connect a visible anchor to a useful reference.; Do not mix many radius sizes or pill shapes; preserve the 4px/10px/18px geometry.

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

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

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

## Layout notes

{
  "breakpoints": "Desktop >=1100px keeps rail/document/context triad; tablet 700-1099px folds the context margin below the document as referenced strips; mobile <700px turns command rail into a top command bar and stacks strands as inline source drawers.",
  "grid": "Desktop uses a 72px fixed command rail, 1fr document canvas, and 320px context margin inside a max 1440px shell; document text maxes at 72 characters while modules hang from the right gutter.",
  "whitespace": "Whitespace is editorial: broad outer gutters, 24px between reading blocks, 12px inside cards, and deliberate quiet around active anchors so dense references remain 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-b3d3-7751-aa55-5e34b1110417",
    "name": "Reference Loom Shell",
    "slug": "reference-loom-shell"
  },
  "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 two-column editorial shell uses a 72px command rail, a minmax document column, and a 320px context margin so the reading surface remains dominant at desktop sizes.",
    "Reference strands are rendered as thin SVG or border-left paths in muted ink that connect highlighted text anchors to source cards, timeline events, and thread replies.",
    "Cards use nearly flat ivory surfaces with 1px hairline borders, 10px radius, and clipped corner command tabs instead of heavy shadows or colored fills.",
    "Tabs and command links are language-led: small mono verbs, bracket markers, underline rails, and active states that slide along the text baseline rather than large pills.",
    "Timelines use compact timestamp knots on a single vertical rule with alternating note widths, preserving narrative order without resembling analytics widgets."
  ],
  "visualProfile": {
    "family": "editorial",
    "material": "flat",
    "contour": "pebble",
    "border": "dashed",
    "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": "Reference Loom Shell 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": [
      "Keep the document or thread as the dominant object; every module should answer what passage, source, or command it supports.",
      "Use mono command verbs sparingly and place them near text baselines, tabs, and card corners.",
      "Draw reference relationships with hairline strands, source notches, and selected anchor underlines rather than color blocks.",
      "Maintain 16px body text, high contrast, and line lengths suitable for sustained reading."
    ],
    "dont": [
      "Do not create a metrics dashboard, KPI grid, or wall of equal cards.",
      "Do not use glassmorphism, neon gradients, heavy drop shadows, or arbitrary bright semantic colors.",
      "Do not let context strands become decorative spaghetti; each line must connect a visible anchor to a useful reference.",
      "Do not mix many radius sizes or pill shapes; preserve the 4px/10px/18px geometry."
    ]
  }
}
related

More like this