back to gallery
design language·katagami-con

Katagami Context Grid

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
A calm, text-first product language for AYA that translates katagami craft into modular apertures, repeated spacing rhythm, layered context, and quiet marginal signals rather than literal Japanese motifs.
tokens
borders3 items
focus
2px solid #485A8F with 2px offset
hairline
1px solid #DDE1E4
separator
1px hairline, preferably full-width within modules to maintain stencil rhythm
color16 items
canvas
#F8F8F5
copper soft
#F2E4DA
danger
#9A4B42
hairline
#DDE1E4
hairline strong
#C9CED3
indigo
#485A8F
indigo soft
#E7EAF4
panel
#F1F4F6
panel subtle
#F6F7F7
persimmon
#B45B32
success
#5F7B68
surface
#FFFFFF
text
#252525
text faint
#8A8E93
text muted
#63666A
warning
#A96B2B
radii3 items
chip
999px only for status/context chips; avoid bubbly decoration
control
8px
panel
10px
shadow2 items
default
none or 0 1px 2px rgba(37,37,37,.04); edges should come from hairlines, not elevation
floating
0 8px 24px rgba(37,37,37,.08) for menus/popovers only
spacing7 items
base unit
4px
context gap
12px between text and marginal signals
micro
4px
panel
24px
section
32px
standard
16px
tight
8px
typography5 items
body
15px/1.55, regular, charcoal
font stack
Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, sans-serif
label
11-12px uppercase or small caps only when it improves scanning; use sparingly
small
13px/1.45 for metadata, labels, and compact summaries
title
20-24px/1.2, medium, compact tracking
rules
0

Every screen must identify primary work, nearby context, and exception signals within the first visual pass.

1

Use at least one repeated spacing rhythm across navigation, summary rows, and panels so the workspace feels woven rather than assembled randomly.

2

Limit warm accent use to under five percent of the visible surface and tie it to meaning.

3

Prefer 1px borders and tinted planes to drop shadows for hierarchy.

4

Any Japanese craft reference must be explainable as structure, rhythm, material restraint, or negative space—not imagery.

layout
density
Calm density: text-first and information-rich, but every module has a clear aperture, readable line length, and enough margin to distinguish primary content from supporting context.
grid
Desktop uses a 12-column workspace with a persistent context rail and content apertures spanning 3/4/5/8 columns. Modules align to a 4px base and 16/24px panel rhythm.
layering
Use barely tinted blue-gray panels behind secondary context, white surfaces for active documents, and hairline separators to expose relationships without card-heavy clutter.
navigation
Navigation behaves as a context map: left rail for major areas, top breadcrumb for hierarchy, right or inline marginal lane for related sources, metrics, and exceptions.
responsive
On narrow screens, marginal signals become inline context strips after the relevant paragraph or row; preserve context order rather than collapsing everything into generic cards.
whitespace

Whitespace is functional negative space. Prefer measured gutters, clipped panel groups, and quiet margins over decorative patterns.

guidance
do
  • Build screens from stencil-like apertures: panels, rows, and context slots that feel cut precisely into a neutral canvas.
  • Use charcoal text on warm-neutral or blue-gray surfaces with strong readability and minimal chroma.
  • Expose relationships through context-map navigation, breadcrumb trails, source chips, marginal notes, and compact inline metrics.
  • Use persimmon or copper only as a tiny signal for exceptions, unresolved items, or important changes.
  • Favor hairline separators, subtle bands, and modular spacing over shadows or decorative dividers.
  • Let summaries sit near documents: inline counts, confidence, deltas, source provenance, and status should be legible at a glance.
  • Translate katagami into negative-space logic, rhythm, and repeatable cuts; keep the result modern and product-grade.
avoid
  • Do not use literal Japanese motifs such as waves, fans, sakura, torii gates, lanterns, koi, faux brush calligraphy, or ornamental textile patterns.
  • Do not make the interface beige heritage branding, museum craft collage, or tourist-Japan decoration.
  • Do not use heavy shadows, glassmorphism, gradient spectacle, neon indigo, or high-chroma dashboards.
  • Do not hide dense context in oversized cards; keep context compact, adjacent, and scannable.
  • Do not use persimmon as a broad brand color; reserve it for small exception marks and critical attention.
  • Do not make three equal marketing cards the default composition; vary aperture widths according to information relationships.
katagami spec
# Katagami Context Grid

## Philosophy

A calm, text-first product language for AYA that translates katagami craft into modular apertures, repeated spacing rhythm, layered context, and quiet marginal signals rather than literal Japanese motifs.

## Tokens

### Borders

- **Focus**: 2px solid #485A8F with 2px offset
- **Hairline**: 1px solid #DDE1E4
- **Separator**: 1px hairline, preferably full-width within modules to maintain stencil rhythm

### Color

- **Canvas**: #F8F8F5
- **Copper Soft**: #F2E4DA
- **Danger**: #9A4B42
- **Hairline**: #DDE1E4
- **Hairline Strong**: #C9CED3
- **Indigo**: #485A8F
- **Indigo Soft**: #E7EAF4
- **Panel**: #F1F4F6
- **Panel Subtle**: #F6F7F7
- **Persimmon**: #B45B32
- **Success**: #5F7B68
- **Surface**: #FFFFFF
- **Text**: #252525
- **Text Faint**: #8A8E93
- **Text Muted**: #63666A
- **Warning**: #A96B2B

### Radii

- **Chip**: 999px only for status/context chips; avoid bubbly decoration
- **Control**: 8px
- **Panel**: 10px

### Shadow

- **Default**: none or 0 1px 2px rgba(37,37,37,.04); edges should come from hairlines, not elevation
- **Floating**: 0 8px 24px rgba(37,37,37,.08) for menus/popovers only

### Spacing

- **Base Unit**: 4px
- **Context Gap**: 12px between text and marginal signals
- **Micro**: 4px
- **Panel**: 24px
- **Section**: 32px
- **Standard**: 16px
- **Tight**: 8px

### Typography

- **Body**: 15px/1.55, regular, charcoal
- **Font Stack**: Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, sans-serif
- **Label**: 11-12px uppercase or small caps only when it improves scanning; use sparingly
- **Small**: 13px/1.45 for metadata, labels, and compact summaries
- **Title**: 20-24px/1.2, medium, compact tracking

## Rules

### 0

Every screen must identify primary work, nearby context, and exception signals within the first visual pass.

### 1

Use at least one repeated spacing rhythm across navigation, summary rows, and panels so the workspace feels woven rather than assembled randomly.

### 2

Limit warm accent use to under five percent of the visible surface and tie it to meaning.

### 3

Prefer 1px borders and tinted planes to drop shadows for hierarchy.

### 4

Any Japanese craft reference must be explainable as structure, rhythm, material restraint, or negative space—not imagery.

## Layout

### Density

Calm density: text-first and information-rich, but every module has a clear aperture, readable line length, and enough margin to distinguish primary content from supporting context.

### Grid

Desktop uses a 12-column workspace with a persistent context rail and content apertures spanning 3/4/5/8 columns. Modules align to a 4px base and 16/24px panel rhythm.

### Layering

Use barely tinted blue-gray panels behind secondary context, white surfaces for active documents, and hairline separators to expose relationships without card-heavy clutter.

### Navigation

Navigation behaves as a context map: left rail for major areas, top breadcrumb for hierarchy, right or inline marginal lane for related sources, metrics, and exceptions.

### Responsive

On narrow screens, marginal signals become inline context strips after the relevant paragraph or row; preserve context order rather than collapsing everything into generic cards.

### Whitespace

Whitespace is functional negative space. Prefer measured gutters, clipped panel groups, and quiet margins over decorative patterns.

## Guidance

### Do

- Build screens from stencil-like apertures: panels, rows, and context slots that feel cut precisely into a neutral canvas.
- Use charcoal text on warm-neutral or blue-gray surfaces with strong readability and minimal chroma.
- Expose relationships through context-map navigation, breadcrumb trails, source chips, marginal notes, and compact inline metrics.
- Use persimmon or copper only as a tiny signal for exceptions, unresolved items, or important changes.
- Favor hairline separators, subtle bands, and modular spacing over shadows or decorative dividers.
- Let summaries sit near documents: inline counts, confidence, deltas, source provenance, and status should be legible at a glance.
- Translate katagami into negative-space logic, rhythm, and repeatable cuts; keep the result modern and product-grade.

### Don't

- Do not use literal Japanese motifs such as waves, fans, sakura, torii gates, lanterns, koi, faux brush calligraphy, or ornamental textile patterns.
- Do not make the interface beige heritage branding, museum craft collage, or tourist-Japan decoration.
- Do not use heavy shadows, glassmorphism, gradient spectacle, neon indigo, or high-chroma dashboards.
- Do not hide dense context in oversized cards; keep context compact, adjacent, and scannable.
- Do not use persimmon as a broad brand color; reserve it for small exception marks and critical attention.
- Do not make three equal marketing cards the default composition; vary aperture widths according to information relationships.

### Accessibility

Maintain WCAG AA contrast for all text and controls. Charcoal body text should remain the default. Indigo focus states must be visible without relying only on color. Persimmon warnings need text/icon labels. Compact metrics must remain at least 12-13px with adequate line-height.

### Usage Context

Best for AYA-style knowledge workspaces, research synthesis tools, document-adjacent analytics, calm dashboards, review queues, and interfaces that weave many related contexts without visual noise.
DESIGN.md
---
version: "alpha"
name: "Katagami Context Grid"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
typography:
  headline-lg:
    fontFamily: "Inter"
    fontSize: "1.953rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Inter"
    fontSize: "1.563rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "Inter"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "Inter"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  chip: "0px"
  control: "8px"
  panel: "10px"
spacing:
  base_unit: "4px"
  context_gap: "12px between text and marginal signals"
  micro: "4px"
  panel: "24px"
  section: "32px"
  standard: "16px"
  tight: "8px"
---

# Katagami Context Grid

## Overview

A calm, text-first product language for AYA that translates katagami craft into modular apertures, repeated spacing rhythm, layered context, and quiet marginal signals rather than literal Japanese motifs.

## Typography

- **Headline-Lg**: Inter, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Inter, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Inter, 16px, weight 400, line-height 1.5.
- **Label-Md**: Inter, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **Base Unit**: `4px`
- **Context Gap**: `12px between text and marginal signals`
- **Micro**: `4px`
- **Panel**: `24px`
- **Section**: `32px`
- **Standard**: `16px`
- **Tight**: `8px`

### Density

Calm density: text-first and information-rich, but every module has a clear aperture, readable line length, and enough margin to distinguish primary content from supporting context.

### Grid

Desktop uses a 12-column workspace with a persistent context rail and content apertures spanning 3/4/5/8 columns. Modules align to a 4px base and 16/24px panel rhythm.

### Layering

Use barely tinted blue-gray panels behind secondary context, white surfaces for active documents, and hairline separators to expose relationships without card-heavy clutter.

### Navigation

Navigation behaves as a context map: left rail for major areas, top breadcrumb for hierarchy, right or inline marginal lane for related sources, metrics, and exceptions.

### Responsive

On narrow screens, marginal signals become inline context strips after the relevant paragraph or row; preserve context order rather than collapsing everything into generic cards.

### Whitespace

Whitespace is functional negative space. Prefer measured gutters, clipped panel groups, and quiet margins over decorative patterns.

## Shapes

### Rounded

- **Chip**: `0px`
- **Control**: `8px`
- **Panel**: `10px`

### Borders

- **Focus**: 2px solid #485A8F with 2px offset
- **Hairline**: 1px solid #DDE1E4
- **Separator**: 1px hairline, preferably full-width within modules to maintain stencil rhythm

## Components

### 0

Every screen must identify primary work, nearby context, and exception signals within the first visual pass.

### 1

Use at least one repeated spacing rhythm across navigation, summary rows, and panels so the workspace feels woven rather than assembled randomly.

### 2

Limit warm accent use to under five percent of the visible surface and tie it to meaning.

### 3

Prefer 1px borders and tinted planes to drop shadows for hierarchy.

### 4

Any Japanese craft reference must be explainable as structure, rhythm, material restraint, or negative space—not imagery.

## 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/katagami-context-grid/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 Build screens from stencil-like apertures: panels, rows, and context slots that feel cut precisely into a neutral canvas.
- Do Use charcoal text on warm-neutral or blue-gray surfaces with strong readability and minimal chroma.
- Do Expose relationships through context-map navigation, breadcrumb trails, source chips, marginal notes, and compact inline metrics.
- Do Use persimmon or copper only as a tiny signal for exceptions, unresolved items, or important changes.
- Do Favor hairline separators, subtle bands, and modular spacing over shadows or decorative dividers.
- Do Let summaries sit near documents: inline counts, confidence, deltas, source provenance, and status should be legible at a glance.
- Do Translate katagami into negative-space logic, rhythm, and repeatable cuts; keep the result modern and product-grade.
- Don't Do not use literal Japanese motifs such as waves, fans, sakura, torii gates, lanterns, koi, faux brush calligraphy, or ornamental textile patterns.
- Don't Do not make the interface beige heritage branding, museum craft collage, or tourist-Japan decoration.
- Don't Do not use heavy shadows, glassmorphism, gradient spectacle, neon indigo, or high-chroma dashboards.
- Don't Do not hide dense context in oversized cards; keep context compact, adjacent, and scannable.
- Don't Do not use persimmon as a broad brand color; reserve it for small exception marks and critical attention.
- Don't Do not make three equal marketing cards the default composition; vary aperture widths according to information relationships.

### Accessibility

Maintain WCAG AA contrast for all text and controls. Charcoal body text should remain the default. Indigo focus states must be visible without relying only on color. Persimmon warnings need text/icon labels. Compact metrics must remain at least 12-13px with adequate line-height.

### Usage Context

Best for AYA-style knowledge workspaces, research synthesis tools, document-adjacent analytics, calm dashboards, review queues, and interfaces that weave many related contexts without visual noise.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "katagami-context-grid",
  "type": "registry:theme",
  "title": "Katagami Context Grid shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#ffffff",
      "foreground": "#111111",
      "card": "#ffffff",
      "card-foreground": "#111111",
      "popover": "#ffffff",
      "popover-foreground": "#111111",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#f4f4f5",
      "muted-foreground": "#111111",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#e4e4e7",
      "input": "#e4e4e7",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#ffffff",
      "sidebar-foreground": "#111111",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#e4e4e7",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#303642",
      "input": "#303642",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "katagami-context-grid",
    "slug": "katagami-context-grid",
    "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": [
        "focus",
        "hairline",
        "separator"
      ],
      "color": [
        "canvas",
        "copper_soft",
        "danger",
        "hairline",
        "hairline_strong",
        "indigo",
        "indigo_soft",
        "panel",
        "panel_subtle",
        "persimmon",
        "success",
        "surface",
        "text",
        "text_faint",
        "text_muted",
        "warning"
      ],
      "radii": [
        "chip",
        "control",
        "panel"
      ],
      "shadow": [
        "default",
        "floating"
      ],
      "spacing": [
        "base_unit",
        "context_gap",
        "micro",
        "panel",
        "section",
        "standard",
        "tight"
      ],
      "typography": [
        "body",
        "font_stack",
        "label",
        "small",
        "title"
      ]
    }
  }
}
```
in the wild

embodiments

Design Language Preview

Katagami Context Grid

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

Typography

headline-lgInter · 31px · 700

The quick brown fox jumps

headline-mdInter · 25px · 600

The quick brown fox jumps

body-mdInter · 16px · 400

The quick brown fox jumps

label-mdInter · 12px · 600

The quick brown fox jumps

Spacing

  • base_unit4px
  • context_gap12px between text and marginal signals
  • micro4px
  • panel24px
  • section32px
  • standard16px
  • tight8px

Shape

chip0px
control8px
panel10px
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: #ffffff;
  --foreground: #111111;
  --card: #ffffff;
  --card-foreground: #111111;
  --popover: #ffffff;
  --popover-foreground: #111111;
  --primary: #111111;
  --primary-foreground: #ffffff;
  --secondary: #f4f4f5;
  --secondary-foreground: #111111;
  --muted: #f4f4f5;
  --muted-foreground: #111111;
  --accent: #111111;
  --accent-foreground: #ffffff;
  --destructive: #dc2626;
  --border: #e4e4e7;
  --input: #e4e4e7;
  --ring: #111111;
  --chart-1: #111111;
  --chart-2: #f4f4f5;
  --chart-3: #111111;
  --chart-4: #16a34a;
  --chart-5: #d97706;
  --sidebar: #ffffff;
  --sidebar-foreground: #111111;
  --sidebar-primary: #111111;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #111111;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #e4e4e7;
  --sidebar-ring: #111111;
  --radius: 0.625rem;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #111111;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #111111;
  --accent-foreground: #ffffff;
  --destructive: #dc2626;
  --border: #303642;
  --input: #303642;
  --ring: #111111;
  --chart-1: #111111;
  --chart-2: #f4f4f5;
  --chart-3: #111111;
  --chart-4: #16a34a;
  --chart-5: #d97706;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #111111;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #111111;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #111111;
  --radius: 0.625rem;
}
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 KatagamiContextGridShadcnKit() {
  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">Katagami Context Grid</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": "katagami-context-grid",
  "type": "registry:theme",
  "title": "Katagami Context Grid shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#ffffff",
      "foreground": "#111111",
      "card": "#ffffff",
      "card-foreground": "#111111",
      "popover": "#ffffff",
      "popover-foreground": "#111111",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#f4f4f5",
      "muted-foreground": "#111111",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#e4e4e7",
      "input": "#e4e4e7",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#ffffff",
      "sidebar-foreground": "#111111",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#e4e4e7",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111111",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#111111",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#303642",
      "input": "#303642",
      "ring": "#111111",
      "chart-1": "#111111",
      "chart-2": "#f4f4f5",
      "chart-3": "#111111",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111111",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#111111",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#111111",
      "radius": "0.625rem"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "katagami-context-grid",
    "slug": "katagami-context-grid",
    "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": [
        "focus",
        "hairline",
        "separator"
      ],
      "color": [
        "canvas",
        "copper_soft",
        "danger",
        "hairline",
        "hairline_strong",
        "indigo",
        "indigo_soft",
        "panel",
        "panel_subtle",
        "persimmon",
        "success",
        "surface",
        "text",
        "text_faint",
        "text_muted",
        "warning"
      ],
      "radii": [
        "chip",
        "control",
        "panel"
      ],
      "shadow": [
        "default",
        "floating"
      ],
      "spacing": [
        "base_unit",
        "context_gap",
        "micro",
        "panel",
        "section",
        "standard",
        "tight"
      ],
      "typography": [
        "body",
        "font_stack",
        "label",
        "small",
        "title"
      ]
    }
  }
}
component recipescompatibility fallback
# Katagami Context Grid shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `katagami-context-grid`
Slug: `katagami-context-grid`

## Intent

A calm, text-first product language for AYA that translates katagami craft into modular apertures, repeated spacing rhythm, layered context, and quiet marginal signals rather than literal Japanese motifs.

## 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:

Defined by the Katagami source fields.

Typography:

{
  "body": "15px/1.55, regular, charcoal",
  "font_stack": "Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, sans-serif",
  "label": "11-12px uppercase or small caps only when it improves scanning; use sparingly",
  "small": "13px/1.45 for metadata, labels, and compact summaries",
  "title": "20-24px/1.2, medium, compact tracking"
}

## Visual character to preserve

- Make the source language's structural identity visible in every component state.

## ShadSync visual profile

{
  "family": "system",
  "material": "flat",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": false,
  "stickerBadges": false,
  "motion": "still",
  "density": "balanced",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

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

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

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

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

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

## Preview shots

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

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/katagami-context-grid/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: Build screens from stencil-like apertures: panels, rows, and context slots that feel cut precisely into a neutral canvas.; Use charcoal text on warm-neutral or blue-gray surfaces with strong readability and minimal chroma.; Expose relationships through context-map navigation, breadcrumb trails, source chips, marginal notes, and compact inline metrics.; Use persimmon or copper only as a tiny signal for exceptions, unresolved items, or important changes.; Favor hairline separators, subtle bands, and modular spacing over shadows or decorative dividers.; Let summaries sit near documents: inline counts, confidence, deltas, source provenance, and status should be legible at a glance.; Translate katagami into negative-space logic, rhythm, and repeatable cuts; keep the result modern and product-grade.
- Do not: Do not use literal Japanese motifs such as waves, fans, sakura, torii gates, lanterns, koi, faux brush calligraphy, or ornamental textile patterns.; Do not make the interface beige heritage branding, museum craft collage, or tourist-Japan decoration.; Do not use heavy shadows, glassmorphism, gradient spectacle, neon indigo, or high-chroma dashboards.; Do not hide dense context in oversized cards; keep context compact, adjacent, and scannable.; Do not use persimmon as a broad brand color; reserve it for small exception marks and critical attention.; Do not make three equal marketing cards the default composition; vary aperture widths according to information 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 KatagamiContextGridShadcnKit() {
  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">Katagami Context Grid</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

{
  "density": "Calm density: text-first and information-rich, but every module has a clear aperture, readable line length, and enough margin to distinguish primary content from supporting context.",
  "grid": "Desktop uses a 12-column workspace with a persistent context rail and content apertures spanning 3/4/5/8 columns. Modules align to a 4px base and 16/24px panel rhythm.",
  "layering": "Use barely tinted blue-gray panels behind secondary context, white surfaces for active documents, and hairline separators to expose relationships without card-heavy clutter.",
  "navigation": "Navigation behaves as a context map: left rail for major areas, top breadcrumb for hierarchy, right or inline marginal lane for related sources, metrics, and exceptions.",
  "responsive": "On narrow screens, marginal signals become inline context strips after the relevant paragraph or row; preserve context order rather than collapsing everything into generic cards.",
  "whitespace": "Whitespace is functional negative space. Prefer measured gutters, clipped panel groups, and quiet margins over decorative patterns."
}
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": "katagami-context-grid",
    "name": "Katagami Context Grid",
    "slug": "katagami-context-grid"
  },
  "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": [],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": false,
    "stickerBadges": false,
    "motion": "still",
    "density": "balanced",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Katagami Context Grid 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": [
      "Build screens from stencil-like apertures: panels, rows, and context slots that feel cut precisely into a neutral canvas.",
      "Use charcoal text on warm-neutral or blue-gray surfaces with strong readability and minimal chroma.",
      "Expose relationships through context-map navigation, breadcrumb trails, source chips, marginal notes, and compact inline metrics.",
      "Use persimmon or copper only as a tiny signal for exceptions, unresolved items, or important changes.",
      "Favor hairline separators, subtle bands, and modular spacing over shadows or decorative dividers.",
      "Let summaries sit near documents: inline counts, confidence, deltas, source provenance, and status should be legible at a glance.",
      "Translate katagami into negative-space logic, rhythm, and repeatable cuts; keep the result modern and product-grade."
    ],
    "dont": [
      "Do not use literal Japanese motifs such as waves, fans, sakura, torii gates, lanterns, koi, faux brush calligraphy, or ornamental textile patterns.",
      "Do not make the interface beige heritage branding, museum craft collage, or tourist-Japan decoration.",
      "Do not use heavy shadows, glassmorphism, gradient spectacle, neon indigo, or high-chroma dashboards.",
      "Do not hide dense context in oversized cards; keep context compact, adjacent, and scannable.",
      "Do not use persimmon as a broad brand color; reserve it for small exception marks and critical attention.",
      "Do not make three equal marketing cards the default composition; vary aperture widths according to information relationships."
    ]
  }
}