Threaded Ma Product System
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.
specification
philosophy
tokens
borders4 items
- accent width
- 1px
- character
- Hairline separators and thread rules; borders are quiet registration marks, not card decoration.
- default width
- 1px
- style
- solid
colors15 items
motion3 items
- duration
- 140ms
- easing
- cubic-bezier(0.2, 0, 0, 1)
- philosophy
- Motion is a quiet reveal: context lines illuminate, selected source layers softly tint, and metrics unfold inline without bounce or spectacle.
radii5 items
- full
- 9999px
- lg
- 10px
- md
- 6px
- none
- 0
- sm
- 3px
shadows3 items
- lg
- 0 18px 44px rgba(36,33,29,0.08)
- md
- 0 8px 24px rgba(36,33,29,0.06)
- sm
- 0 1px 2px rgba(36,33,29,0.04)
spacing2 items
- base
- 4px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64, 80, 96
surfaces3 items
- bg pattern
- No decorative motif; only functional thread rules, registration ticks, or faint column guides where they clarify relationships.
- card style
- Low-chrome document panels with fine borders, generous interior padding, and optional clipped reveal notches.
- treatment
- Matte near-white and mist-gray layers with faint paper-like warmth; use translucency only to show context depth.
typography9 items
- base size
- 16px
- body font
- Inter
- display letter spacing
- -0.025em
- google fonts url
- https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&family=Inter:wght@400;500;600;700&display=swap
- heading font
- Inter
- letter spacing
- -0.01em
- line height
- 1.58
- measure
- 64-76 characters for prose
- mono font
- IBM Plex Mono
rules
Use a document workspace, not a dashboard. The central reading surface owns the page; a narrow thread rail shows origin, reuse, and dependencies; marginal chips, inline metrics, and small decision markers annotate the document. Compose with asymmetry and functional negative space so dense context clusters are separated by calm pauses.
Medium information density with disciplined breathing room. Prose lines stay within 64-76 characters, evidence clusters may tighten to 4-12px gaps, and major context transitions require 32-64px pauses. Large areas remain uncolored.
Hierarchy comes from text scale, line length, source position, thread continuity, and proximity. Color is never the first hierarchy tool; indigo indicates action, focus, or active relationship, while persimmon indicates unresolved work only.
layout
mobile <= 640px stacks thread rail into a top breadcrumb trail; tablet 641px-1024px uses reading surface plus collapsible context drawer; desktop >= 1025px exposes rail and marginal annotations.
Text-first density with calm pauses: compact tables and chips are allowed, but long-form reading modules keep generous line height and controlled measure.
Desktop uses a 12-column max-width 1280px workspace: 1-2 columns for thread rail, 7-8 for primary reading/composition, and 2-3 for compact context notes when needed. Align to 4px baseline and 8/16px component rhythm.
Preserve source order and comprehension on small screens: relationship lines become ordered breadcrumbs, side notes become inline disclosure blocks, and metrics remain adjacent to the referenced text.
Negative space is an active buffer around decisions and between source layers; use 32-96px pauses to separate evidence, synthesis, and action.
guidance
- Start every screen from the primary reading task, then add rails, chips, and annotations only where they clarify context.
- Use indigo for primary actions, active thread links, selected context, focus outlines, and relationship emphasis.
- Represent provenance through breadcrumbs and dependency trails that can be followed forwards and backwards.
- Use mist-gray surfaces, hairlines, and marginal metadata to separate layers without building heavy cards.
- Let empty states be short, textual, and calm, with one clear next action or suggested source to add.
- Do not use literal Japanese motifs, tourist cliches, faux brush typography, decorative textile patterns, or ornamental stencil cutouts.
- Do not lead with dashboard cards, KPI grids, large charts, or colorful analytics panels.
- Do not flood surfaces with indigo, persimmon, or semantic colors; accents must remain small and intentional.
- Do not let relationship lines cross through prose or compete with reading; route them through margins and rails.
- Do not hide provenance behind generic icons; source, reuse, and decision dependency should be textual and traceable.
katagami spec
# Threaded Ma Product System ## Philosophy Threaded Ma Product System is a calm, text-first workspace language for weaving many sources into one coherent decision surface. It turns Japanese-inspired restraint into product structure: generous negative space protects comprehension, fine connective threads reveal relationships, and katagami-like masking/layering controls how context is disclosed without becoming ornament. ### Values - Protect reading and judgment before adding interface chrome; every visual choice should improve comprehension, source trust, or decision flow. - Use ma as workflow breathing room: purposeful gaps separate evidence, interpretation, and action so users can think between dense context clusters. - Make threads the relationship grammar: fine lines, trails, breadcrumbs, and chips show where context came from, where it is reused, and what depends on it. - Translate katagami as masking, reveal, registration, and layered translucency rather than literal stencil pattern decoration. - Keep signals marginal and quiet: metrics, statuses, and unresolved markers live in margins, rails, headers, or inline annotations rather than dashboard panels. - Let color stay scarce and meaningful: indigo for action/focus/context links, persimmon only for unresolved micro-markers, and low-saturation semantics for state. ### Anti-Values - literal Japanese motifs such as waves, temples, fans, koi, cherry blossom, faux brush lettering, or tourist-poster references - dashboard-first layouts with large KPI tiles, colorful chart panels, or analytics widgets competing with source text - decorative weaving or stencil patterns that do not carry navigational, masking, or relationship meaning - large colored areas, saturated semantic panels, gradients, glow, glassmorphism, or ornamental texture that reduces reading comfort - low-contrast gray text, cramped prose, ambiguous source trails, or relationship lines that become visual noise ### Visual Character - Near-white washi-like canvas with mist-gray layered surfaces, charcoal/sumi text, and extremely fine gray separators. - Thread rails, source trails, and dependency lines are structural navigation devices, using 1px rules, dotted continuation marks, and small junction nodes. - Context chips use compact labels, tiny relationship verbs, and subtle indigo outlines or tints when selected. - Katagami abstraction appears as clipped masks, soft registration gutters, reveal windows, and translucent overlays that align evidence layers. - Metrics appear as inline numbers, compact deltas, footnote grains, or tiny sparklines attached to documents rather than standalone dashboards. - Persimmon appears only as pinhead markers for unresolved questions, conflicts, or required attention. ## Tokens ### Borders - **Accent Width**: 1px - **Character**: Hairline separators and thread rules; borders are quiet registration marks, not card decoration. - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#2F4F8F` | | accent_soft | `#E8ECF6` | | background | `#F8F7F2` | | border | `#DCD8CF` | | error | `#9F5148` | | info | `#536F8A` | | muted | `#8A867E` | | primary | `#2A2520` | | secondary | `#5F5B54` | | success | `#60766A` | | surface | `#FFFFFF` | | surface_mist | `#F1F2EF` | | text | `#24211D` | | unresolved | `#C7652C` | | warning | `#9A7A3D` | ### Motion - **Duration**: 140ms - **Easing**: cubic-bezier(0.2, 0, 0, 1) - **Philosophy**: Motion is a quiet reveal: context lines illuminate, selected source layers softly tint, and metrics unfold inline without bounce or spectacle. ### Radii - **Full**: 9999px - **Lg**: 10px - **Md**: 6px - **None**: 0 - **Sm**: 3px ### Shadows - **Lg**: 0 18px 44px rgba(36,33,29,0.08) - **Md**: 0 8px 24px rgba(36,33,29,0.06) - **Sm**: 0 1px 2px rgba(36,33,29,0.04) ### Spacing - **Base**: 4px - **Scale**: [4,8,12,16,24,32,48,64,80,96] ### Surfaces - **Bg Pattern**: No decorative motif; only functional thread rules, registration ticks, or faint column guides where they clarify relationships. - **Card Style**: Low-chrome document panels with fine borders, generous interior padding, and optional clipped reveal notches. - **Treatment**: Matte near-white and mist-gray layers with faint paper-like warmth; use translucency only to show context depth. ### Typography - **Base Size**: 16px - **Body Font**: Inter - **Display Letter Spacing**: -0.025em - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&family=Inter:wght@400;500;600;700&display=swap - **Heading Font**: Inter - **Letter Spacing**: -0.01em - **Line Height**: 1.58 - **Measure**: 64-76 characters for prose - **Mono Font**: IBM Plex Mono ## Rules ### Composition Use a document workspace, not a dashboard. The central reading surface owns the page; a narrow thread rail shows origin, reuse, and dependencies; marginal chips, inline metrics, and small decision markers annotate the document. Compose with asymmetry and functional negative space so dense context clusters are separated by calm pauses. ### Density Medium information density with disciplined breathing room. Prose lines stay within 64-76 characters, evidence clusters may tighten to 4-12px gaps, and major context transitions require 32-64px pauses. Large areas remain uncolored. ### Hierarchy Hierarchy comes from text scale, line length, source position, thread continuity, and proximity. Color is never the first hierarchy tool; indigo indicates action, focus, or active relationship, while persimmon indicates unresolved work only. ### Signature Patterns - Thread rail: a slim vertical or horizontal rail with source breadcrumbs, relationship verbs, dependency counts, and fine connecting rules that illuminate on hover/focus. - Context chips: compact pills containing source name, relationship type, and confidence/status grain; selected chips softly tint the linked document region. - Katagami reveal windows: clipped, aligned overlays that expose supporting evidence or alternate readings without covering the primary text. - Inline metrics: numbers, deltas, and tiny sparklines embedded in sentences, table margins, or footnotes rather than presented as dashboard cards. - Unresolved markers: tiny persimmon dots, ticks, or bracket marks placed at the exact line or chip requiring decision; never large warning banners unless blocking. ## Layout ### Breakpoints mobile <= 640px stacks thread rail into a top breadcrumb trail; tablet 641px-1024px uses reading surface plus collapsible context drawer; desktop >= 1025px exposes rail and marginal annotations. ### Density Text-first density with calm pauses: compact tables and chips are allowed, but long-form reading modules keep generous line height and controlled measure. ### Grid Desktop uses a 12-column max-width 1280px workspace: 1-2 columns for thread rail, 7-8 for primary reading/composition, and 2-3 for compact context notes when needed. Align to 4px baseline and 8/16px component rhythm. ### Responsive Preserve source order and comprehension on small screens: relationship lines become ordered breadcrumbs, side notes become inline disclosure blocks, and metrics remain adjacent to the referenced text. ### Whitespace Negative space is an active buffer around decisions and between source layers; use 32-96px pauses to separate evidence, synthesis, and action. ## Guidance ### Do - Start every screen from the primary reading task, then add rails, chips, and annotations only where they clarify context. - Use indigo for primary actions, active thread links, selected context, focus outlines, and relationship emphasis. - Represent provenance through breadcrumbs and dependency trails that can be followed forwards and backwards. - Use mist-gray surfaces, hairlines, and marginal metadata to separate layers without building heavy cards. - Let empty states be short, textual, and calm, with one clear next action or suggested source to add. ### Don't - Do not use literal Japanese motifs, tourist cliches, faux brush typography, decorative textile patterns, or ornamental stencil cutouts. - Do not lead with dashboard cards, KPI grids, large charts, or colorful analytics panels. - Do not flood surfaces with indigo, persimmon, or semantic colors; accents must remain small and intentional. - Do not let relationship lines cross through prose or compete with reading; route them through margins and rails. - Do not hide provenance behind generic icons; source, reuse, and decision dependency should be textual and traceable. ### Accessibility Maintain WCAG AA contrast for all text. Do not rely on line color alone for relationship meaning; pair threads with labels, chips, or ARIA descriptions. Keep focus rings visible in indigo and ensure selected background tints remain subtle but perceivable. Body copy should remain at 16px or larger with comfortable line height. ### Usage Context Best for research workspaces, AI synthesis tools, legal/strategy review, knowledge management, editorial planning, and any product where many sources must be woven into a trustworthy decision trail.
DESIGN.md
---
version: "alpha"
name: "Threaded Ma Product System"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#2F4F8F"
accent_soft: "#E8ECF6"
background: "#F8F7F2"
border: "#DCD8CF"
error: "#9F5148"
info: "#536F8A"
muted: "#8A867E"
primary: "#2A2520"
secondary: "#5F5B54"
success: "#60766A"
surface: "#FFFFFF"
surface_mist: "#F1F2EF"
text: "#24211D"
unresolved: "#C7652C"
warning: "#9A7A3D"
typography:
headline-lg:
fontFamily: "Inter"
fontSize: "1.953rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.01em"
headline-md:
fontFamily: "Inter"
fontSize: "1.563rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.01em"
body-md:
fontFamily: "Inter"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.58
letterSpacing: "-0.01em"
label-md:
fontFamily: "IBM Plex Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "10px"
md: "6px"
none: "0px"
sm: "3px"
spacing:
base: "4px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
step-8: "80px"
step-9: "96px"
components:
color-reference-accent:
backgroundColor: "{colors.accent}"
color-reference-accent_soft:
backgroundColor: "{colors.accent_soft}"
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-surface_mist:
backgroundColor: "{colors.surface_mist}"
color-reference-text:
backgroundColor: "{colors.text}"
color-reference-unresolved:
backgroundColor: "{colors.unresolved}"
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"
---
# Threaded Ma Product System
## Overview
Threaded Ma Product System is a calm, text-first workspace language for weaving many sources into one coherent decision surface. It turns Japanese-inspired restraint into product structure: generous negative space protects comprehension, fine connective threads reveal relationships, and katagami-like masking/layering controls how context is disclosed without becoming ornament.
### Values
- Protect reading and judgment before adding interface chrome; every visual choice should improve comprehension, source trust, or decision flow.
- Use ma as workflow breathing room: purposeful gaps separate evidence, interpretation, and action so users can think between dense context clusters.
- Make threads the relationship grammar: fine lines, trails, breadcrumbs, and chips show where context came from, where it is reused, and what depends on it.
- Translate katagami as masking, reveal, registration, and layered translucency rather than literal stencil pattern decoration.
- Keep signals marginal and quiet: metrics, statuses, and unresolved markers live in margins, rails, headers, or inline annotations rather than dashboard panels.
- Let color stay scarce and meaningful: indigo for action/focus/context links, persimmon only for unresolved micro-markers, and low-saturation semantics for state.
### Anti-Values
- literal Japanese motifs such as waves, temples, fans, koi, cherry blossom, faux brush lettering, or tourist-poster references
- dashboard-first layouts with large KPI tiles, colorful chart panels, or analytics widgets competing with source text
- decorative weaving or stencil patterns that do not carry navigational, masking, or relationship meaning
- large colored areas, saturated semantic panels, gradients, glow, glassmorphism, or ornamental texture that reduces reading comfort
- low-contrast gray text, cramped prose, ambiguous source trails, or relationship lines that become visual noise
### Visual Character
- Near-white washi-like canvas with mist-gray layered surfaces, charcoal/sumi text, and extremely fine gray separators.
- Thread rails, source trails, and dependency lines are structural navigation devices, using 1px rules, dotted continuation marks, and small junction nodes.
- Context chips use compact labels, tiny relationship verbs, and subtle indigo outlines or tints when selected.
- Katagami abstraction appears as clipped masks, soft registration gutters, reveal windows, and translucent overlays that align evidence layers.
- Metrics appear as inline numbers, compact deltas, footnote grains, or tiny sparklines attached to documents rather than standalone dashboards.
- Persimmon appears only as pinhead markers for unresolved questions, conflicts, or required attention.
## 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 | `#2F4F8F` |
| accent_soft | `#E8ECF6` |
| background | `#F8F7F2` |
| border | `#DCD8CF` |
| error | `#9F5148` |
| info | `#536F8A` |
| muted | `#8A867E` |
| primary | `#2A2520` |
| secondary | `#5F5B54` |
| success | `#60766A` |
| surface | `#FFFFFF` |
| surface_mist | `#F1F2EF` |
| text | `#24211D` |
| unresolved | `#C7652C` |
| warning | `#9A7A3D` |
## 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.58.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `4px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
- **Step-8**: `80px`
- **Step-9**: `96px`
### Breakpoints
mobile <= 640px stacks thread rail into a top breadcrumb trail; tablet 641px-1024px uses reading surface plus collapsible context drawer; desktop >= 1025px exposes rail and marginal annotations.
### Density
Text-first density with calm pauses: compact tables and chips are allowed, but long-form reading modules keep generous line height and controlled measure.
### Grid
Desktop uses a 12-column max-width 1280px workspace: 1-2 columns for thread rail, 7-8 for primary reading/composition, and 2-3 for compact context notes when needed. Align to 4px baseline and 8/16px component rhythm.
### Responsive
Preserve source order and comprehension on small screens: relationship lines become ordered breadcrumbs, side notes become inline disclosure blocks, and metrics remain adjacent to the referenced text.
### Whitespace
Negative space is an active buffer around decisions and between source layers; use 32-96px pauses to separate evidence, synthesis, and action.
## Elevation & Depth
### Shadows
- **Lg**: 0 18px 44px rgba(36,33,29,0.08)
- **Md**: 0 8px 24px rgba(36,33,29,0.06)
- **Sm**: 0 1px 2px rgba(36,33,29,0.04)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `10px`
- **Md**: `6px`
- **None**: `0px`
- **Sm**: `3px`
### Surfaces
- **Bg Pattern**: No decorative motif; only functional thread rules, registration ticks, or faint column guides where they clarify relationships.
- **Card Style**: Low-chrome document panels with fine borders, generous interior padding, and optional clipped reveal notches.
- **Treatment**: Matte near-white and mist-gray layers with faint paper-like warmth; use translucency only to show context depth.
### Borders
- **Accent Width**: 1px
- **Character**: Hairline separators and thread rules; borders are quiet registration marks, not card decoration.
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Use a document workspace, not a dashboard. The central reading surface owns the page; a narrow thread rail shows origin, reuse, and dependencies; marginal chips, inline metrics, and small decision markers annotate the document. Compose with asymmetry and functional negative space so dense context clusters are separated by calm pauses.
### Density
Medium information density with disciplined breathing room. Prose lines stay within 64-76 characters, evidence clusters may tighten to 4-12px gaps, and major context transitions require 32-64px pauses. Large areas remain uncolored.
### Hierarchy
Hierarchy comes from text scale, line length, source position, thread continuity, and proximity. Color is never the first hierarchy tool; indigo indicates action, focus, or active relationship, while persimmon indicates unresolved work only.
### Signature Patterns
- Thread rail: a slim vertical or horizontal rail with source breadcrumbs, relationship verbs, dependency counts, and fine connecting rules that illuminate on hover/focus.
- Context chips: compact pills containing source name, relationship type, and confidence/status grain; selected chips softly tint the linked document region.
- Katagami reveal windows: clipped, aligned overlays that expose supporting evidence or alternate readings without covering the primary text.
- Inline metrics: numbers, deltas, and tiny sparklines embedded in sentences, table margins, or footnotes rather than presented as dashboard cards.
- Unresolved markers: tiny persimmon dots, ticks, or bracket marks placed at the exact line or chip requiring decision; never large warning banners unless blocking.
## 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/threaded-ma-product-system/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 Start every screen from the primary reading task, then add rails, chips, and annotations only where they clarify context.
- Do Use indigo for primary actions, active thread links, selected context, focus outlines, and relationship emphasis.
- Do Represent provenance through breadcrumbs and dependency trails that can be followed forwards and backwards.
- Do Use mist-gray surfaces, hairlines, and marginal metadata to separate layers without building heavy cards.
- Do Let empty states be short, textual, and calm, with one clear next action or suggested source to add.
- Don't Do not use literal Japanese motifs, tourist cliches, faux brush typography, decorative textile patterns, or ornamental stencil cutouts.
- Don't Do not lead with dashboard cards, KPI grids, large charts, or colorful analytics panels.
- Don't Do not flood surfaces with indigo, persimmon, or semantic colors; accents must remain small and intentional.
- Don't Do not let relationship lines cross through prose or compete with reading; route them through margins and rails.
- Don't Do not hide provenance behind generic icons; source, reuse, and decision dependency should be textual and traceable.
### Accessibility
Maintain WCAG AA contrast for all text. Do not rely on line color alone for relationship meaning; pair threads with labels, chips, or ARIA descriptions. Keep focus rings visible in indigo and ensure selected background tints remain subtle but perceivable. Body copy should remain at 16px or larger with comfortable line height.
### Usage Context
Best for research workspaces, AI synthesis tools, legal/strategy review, knowledge management, editorial planning, and any product where many sources must be woven into a trustworthy decision trail.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "threaded-ma-product-system",
"type": "registry:theme",
"title": "Threaded Ma Product System shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F8F7F2",
"foreground": "#24211D",
"card": "#FFFFFF",
"card-foreground": "#24211D",
"popover": "#FFFFFF",
"popover-foreground": "#24211D",
"primary": "#2A2520",
"primary-foreground": "#ffffff",
"secondary": "#5F5B54",
"secondary-foreground": "#ffffff",
"muted": "#8A867E",
"muted-foreground": "#24211D",
"accent": "#2F4F8F",
"accent-foreground": "#ffffff",
"destructive": "#9F5148",
"border": "#DCD8CF",
"input": "#DCD8CF",
"ring": "#2F4F8F",
"chart-1": "#2A2520",
"chart-2": "#5F5B54",
"chart-3": "#2F4F8F",
"chart-4": "#60766A",
"chart-5": "#9A7A3D",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#24211D",
"sidebar-primary": "#2A2520",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#536F8A",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#DCD8CF",
"sidebar-ring": "#2F4F8F",
"radius": "6px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#2A2520",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#2F4F8F",
"accent-foreground": "#ffffff",
"destructive": "#9F5148",
"border": "#303642",
"input": "#303642",
"ring": "#2F4F8F",
"chart-1": "#2A2520",
"chart-2": "#5F5B54",
"chart-3": "#2F4F8F",
"chart-4": "#60766A",
"chart-5": "#9A7A3D",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#2A2520",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#2F4F8F",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#2F4F8F",
"radius": "6px"
}
},
"meta": {
"source": "katagami",
"languageId": "threaded-ma-product-system",
"slug": "threaded-ma-product-system",
"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",
"accent_soft",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"surface_mist",
"text",
"unresolved",
"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",
"display_letter_spacing",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"measure",
"mono_font"
]
}
}
}
```embodiments
at a glance
Typography
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Components
Components rendered with this language’s tokens — colors, type, and rounded corners as specified.
Spacing
- base4px
- xs4px
- sm8px
- md12px
- lg16px
- xl24px
- 2xl32px
- 3xl48px
- 4xl64px
- step-880px
- step-996px
Shape
implementation kit
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
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #F8F7F2;
--foreground: #24211D;
--card: #FFFFFF;
--card-foreground: #24211D;
--popover: #FFFFFF;
--popover-foreground: #24211D;
--primary: #2A2520;
--primary-foreground: #ffffff;
--secondary: #5F5B54;
--secondary-foreground: #ffffff;
--muted: #8A867E;
--muted-foreground: #24211D;
--accent: #2F4F8F;
--accent-foreground: #ffffff;
--destructive: #9F5148;
--border: #DCD8CF;
--input: #DCD8CF;
--ring: #2F4F8F;
--chart-1: #2A2520;
--chart-2: #5F5B54;
--chart-3: #2F4F8F;
--chart-4: #60766A;
--chart-5: #9A7A3D;
--sidebar: #FFFFFF;
--sidebar-foreground: #24211D;
--sidebar-primary: #2A2520;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #536F8A;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #DCD8CF;
--sidebar-ring: #2F4F8F;
--radius: 6px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #2A2520;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #2F4F8F;
--accent-foreground: #ffffff;
--destructive: #9F5148;
--border: #303642;
--input: #303642;
--ring: #2F4F8F;
--chart-1: #2A2520;
--chart-2: #5F5B54;
--chart-3: #2F4F8F;
--chart-4: #60766A;
--chart-5: #9A7A3D;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #2A2520;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #2F4F8F;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #2F4F8F;
--radius: 6px;
}
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 ThreadedMaProductSystemShadcnKit() {
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">Threaded Ma Product System</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>
);
}
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "threaded-ma-product-system",
"type": "registry:theme",
"title": "Threaded Ma Product System shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F8F7F2",
"foreground": "#24211D",
"card": "#FFFFFF",
"card-foreground": "#24211D",
"popover": "#FFFFFF",
"popover-foreground": "#24211D",
"primary": "#2A2520",
"primary-foreground": "#ffffff",
"secondary": "#5F5B54",
"secondary-foreground": "#ffffff",
"muted": "#8A867E",
"muted-foreground": "#24211D",
"accent": "#2F4F8F",
"accent-foreground": "#ffffff",
"destructive": "#9F5148",
"border": "#DCD8CF",
"input": "#DCD8CF",
"ring": "#2F4F8F",
"chart-1": "#2A2520",
"chart-2": "#5F5B54",
"chart-3": "#2F4F8F",
"chart-4": "#60766A",
"chart-5": "#9A7A3D",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#24211D",
"sidebar-primary": "#2A2520",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#536F8A",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#DCD8CF",
"sidebar-ring": "#2F4F8F",
"radius": "6px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#2A2520",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#2F4F8F",
"accent-foreground": "#ffffff",
"destructive": "#9F5148",
"border": "#303642",
"input": "#303642",
"ring": "#2F4F8F",
"chart-1": "#2A2520",
"chart-2": "#5F5B54",
"chart-3": "#2F4F8F",
"chart-4": "#60766A",
"chart-5": "#9A7A3D",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#2A2520",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#2F4F8F",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#2F4F8F",
"radius": "6px"
}
},
"meta": {
"source": "katagami",
"languageId": "threaded-ma-product-system",
"slug": "threaded-ma-product-system",
"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",
"accent_soft",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"surface_mist",
"text",
"unresolved",
"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",
"display_letter_spacing",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"measure",
"mono_font"
]
}
}
}
# Threaded Ma Product System shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `threaded-ma-product-system`
Slug: `threaded-ma-product-system`
## Intent
Threaded Ma Product System is a calm, text-first workspace language for weaving many sources into one coherent decision surface. It turns Japanese-inspired restraint into product structure: generous negative space protects comprehension, fine connective threads reveal relationships, and katagami-like masking/layering controls how context is disclosed without becoming ornament.
## 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": "#2F4F8F",
"accent_soft": "#E8ECF6",
"background": "#F8F7F2",
"border": "#DCD8CF",
"error": "#9F5148",
"info": "#536F8A",
"muted": "#8A867E",
"primary": "#2A2520",
"secondary": "#5F5B54",
"success": "#60766A",
"surface": "#FFFFFF",
"surface_mist": "#F1F2EF",
"text": "#24211D",
"unresolved": "#C7652C",
"warning": "#9A7A3D"
}
Typography:
{
"base_size": "16px",
"body_font": "Inter",
"display_letter_spacing": "-0.025em",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&family=Inter:wght@400;500;600;700&display=swap",
"heading_font": "Inter",
"letter_spacing": "-0.01em",
"line_height": 1.58,
"measure": "64-76 characters for prose",
"mono_font": "IBM Plex Mono"
}
## Visual character to preserve
- Near-white washi-like canvas with mist-gray layered surfaces, charcoal/sumi text, and extremely fine gray separators.
- Thread rails, source trails, and dependency lines are structural navigation devices, using 1px rules, dotted continuation marks, and small junction nodes.
- Context chips use compact labels, tiny relationship verbs, and subtle indigo outlines or tints when selected.
- Katagami abstraction appears as clipped masks, soft registration gutters, reveal windows, and translucent overlays that align evidence layers.
- Metrics appear as inline numbers, compact deltas, footnote grains, or tiny sparklines attached to documents rather than standalone dashboards.
- Persimmon appears only as pinhead markers for unresolved questions, conflicts, or required attention.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": false,
"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/threaded-ma-product-system/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: Start every screen from the primary reading task, then add rails, chips, and annotations only where they clarify context.; Use indigo for primary actions, active thread links, selected context, focus outlines, and relationship emphasis.; Represent provenance through breadcrumbs and dependency trails that can be followed forwards and backwards.; Use mist-gray surfaces, hairlines, and marginal metadata to separate layers without building heavy cards.; Let empty states be short, textual, and calm, with one clear next action or suggested source to add.
- Do not: Do not use literal Japanese motifs, tourist cliches, faux brush typography, decorative textile patterns, or ornamental stencil cutouts.; Do not lead with dashboard cards, KPI grids, large charts, or colorful analytics panels.; Do not flood surfaces with indigo, persimmon, or semantic colors; accents must remain small and intentional.; Do not let relationship lines cross through prose or compete with reading; route them through margins and rails.; Do not hide provenance behind generic icons; source, reuse, and decision dependency should be textual and traceable.
## 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 ThreadedMaProductSystemShadcnKit() {
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">Threaded Ma Product System</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
```
## Layout notes
{
"breakpoints": "mobile <= 640px stacks thread rail into a top breadcrumb trail; tablet 641px-1024px uses reading surface plus collapsible context drawer; desktop >= 1025px exposes rail and marginal annotations.",
"density": "Text-first density with calm pauses: compact tables and chips are allowed, but long-form reading modules keep generous line height and controlled measure.",
"grid": "Desktop uses a 12-column max-width 1280px workspace: 1-2 columns for thread rail, 7-8 for primary reading/composition, and 2-3 for compact context notes when needed. Align to 4px baseline and 8/16px component rhythm.",
"responsive": "Preserve source order and comprehension on small screens: relationship lines become ordered breadcrumbs, side notes become inline disclosure blocks, and metrics remain adjacent to the referenced text.",
"whitespace": "Negative space is an active buffer around decisions and between source layers; use 32-96px pauses to separate evidence, synthesis, and action."
}
{
"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": "threaded-ma-product-system",
"name": "Threaded Ma Product System",
"slug": "threaded-ma-product-system"
},
"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": [
"Near-white washi-like canvas with mist-gray layered surfaces, charcoal/sumi text, and extremely fine gray separators.",
"Thread rails, source trails, and dependency lines are structural navigation devices, using 1px rules, dotted continuation marks, and small junction nodes.",
"Context chips use compact labels, tiny relationship verbs, and subtle indigo outlines or tints when selected.",
"Katagami abstraction appears as clipped masks, soft registration gutters, reveal windows, and translucent overlays that align evidence layers.",
"Metrics appear as inline numbers, compact deltas, footnote grains, or tiny sparklines attached to documents rather than standalone dashboards.",
"Persimmon appears only as pinhead markers for unresolved questions, conflicts, or required attention."
],
"visualProfile": {
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": false,
"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": "Threaded Ma Product System 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": [
"Start every screen from the primary reading task, then add rails, chips, and annotations only where they clarify context.",
"Use indigo for primary actions, active thread links, selected context, focus outlines, and relationship emphasis.",
"Represent provenance through breadcrumbs and dependency trails that can be followed forwards and backwards.",
"Use mist-gray surfaces, hairlines, and marginal metadata to separate layers without building heavy cards.",
"Let empty states be short, textual, and calm, with one clear next action or suggested source to add."
],
"dont": [
"Do not use literal Japanese motifs, tourist cliches, faux brush typography, decorative textile patterns, or ornamental stencil cutouts.",
"Do not lead with dashboard cards, KPI grids, large charts, or colorful analytics panels.",
"Do not flood surfaces with indigo, persimmon, or semantic colors; accents must remain small and intentional.",
"Do not let relationship lines cross through prose or compete with reading; route them through margins and rails.",
"Do not hide provenance behind generic icons; source, reuse, and decision dependency should be textual and traceable."
]
}
}