AYA Threaded Manuscript
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
- 2px
- character
- quiet print-like rules that bind text, margin notes, and command affordances
- default width
- 1px
- style
- solid hairlines with occasional double-rule separators
colors12 items
motion3 items
- duration
- 140ms
- easing
- cubic-bezier(0.2, 0, 0.1, 1)
- philosophy
- only small underline, focus, and background tint transitions; never sliding dashboard panels
radii5 items
- full
- 9999px
- lg
- 10px
- md
- 6px
- none
- 0
- sm
- 3px
shadows3 items
- lg
- 0 24px 60px rgba(36,33,29,0.08)
- md
- 0 10px 24px rgba(36,33,29,0.06)
- sm
- 0 1px 0 rgba(36,33,29,0.05)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64, 96
surfaces3 items
- bg pattern
- subtle linear paper grain and faint vertical manuscript guides
- card style
- flat editorial plates with one-pixel borders, caption bars, and small square radii
- treatment
- warm neutral canvas with matte paper panels and no glass effects
typography8 items
- base size
- 16px
- body font
- Source Sans 3
- google fonts url
- https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&family=Literata:opsz,wght@7..72,500;7..72,650&family=Source+Sans+3:wght@400;500;600;700&display=swap
- heading font
- Literata
- letter spacing
- -0.005em
- line height
- 1.62
- mono font
- IBM Plex Mono
- scale ratio
- 1.22
rules
Build screens around a dominant reading surface, a persistent reference rail, and compact footnote plates; command surfaces sit inline with text rather than above it.
Text can be dense inside the reading column, but surrounding whitespace and rail grouping must keep the screen calm and scannable.
Use Literata for article titles and section heads, Source Sans 3 for interface text, IBM Plex Mono for IDs; hierarchy comes from measure, rule weight, spacing, and small caps labels.
layout
Desktop 1200+, tablet 768-1199 stacks rail below active text, mobile under 640 uses single column with collapsible reference groups.
Desktop uses a 12-column page with a 68ch manuscript column, 280px reference rail, and elastic outer margins.
Whitespace is generous around groups and narrow inside text: 32-48px section gaps, 16px paragraph rhythm, and 24px rail clusters.
guidance
- Lead with readable paragraphs, threads, citations, and inline commands before showing metrics.
- Keep accent color scarce and tied to provenance, selection, or primary command links.
- Use hairline rules and margin notes to reveal relationships between text and context.
- Make compact modules look like footnotes or editorial plates, not analytics dashboards.
- Do not turn AYA into a KPI dashboard or fill the canvas with equal metric cards.
- Do not use gradients, glassmorphism, heavy shadows, or arbitrary rounded pill surfaces.
- Do not color-code every status; use labels, rules, and text hierarchy first.
- Do not let reference links float without visible attachment to the reading context.
katagami spec
# AYA Threaded Manuscript ## Philosophy AYA Threaded Manuscript treats a knowledge workspace as a calm annotated reading room: long text is primary, references are woven in at the margin, and commands feel like editorial marks rather than dashboard controls. ### Values - long-form readability before widget density - context links that feel attached to sentences - quiet hierarchy from measure, rules, and margin rhythm - restrained accent color used only for action and provenance ### Anti-Values - dashboard-first metric walls - generic SaaS card grids - colorful status confetti - floating glass panels detached from text ### Visual Character - Use a two-column manuscript grid with a 68ch reading column and a narrow reference rail separated by a hairline vertical rule. - Render threads as indented editorial blocks with left-side stitch rules, small sequence numerals, and clipped quote headers. - Use flat warm paper surfaces, one-pixel stone borders, square-to-small radii, and no decorative drop shadows on primary text areas. - Apply a muted blue-violet accent only to command links, active tabs, reference pins, and focus outlines while most UI remains ink and paper. - Place compact data modules as footnote plates with tabular lining numerals and top caption rules instead of bright dashboard cards. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: quiet print-like rules that bind text, margin notes, and command affordances - **Default Width**: 1px - **Style**: solid hairlines with occasional double-rule separators ### Colors | Name | Value | |------|-------| | accent | `#5D6FAE` | | background | `#F7F3EA` | | border | `#D8D0C2` | | error | `#A44E3F` | | info | `#5D6FAE` | | muted | `#80776B` | | primary | `#24211D` | | secondary | `#6F685F` | | success | `#5D7D64` | | surface | `#FFFCF4` | | text | `#24211D` | | warning | `#A97835` | ### Motion - **Duration**: 140ms - **Easing**: cubic-bezier(0.2, 0, 0.1, 1) - **Philosophy**: only small underline, focus, and background tint transitions; never sliding dashboard panels ### Radii - **Full**: 9999px - **Lg**: 10px - **Md**: 6px - **None**: 0 - **Sm**: 3px ### Shadows - **Lg**: 0 24px 60px rgba(36,33,29,0.08) - **Md**: 0 10px 24px rgba(36,33,29,0.06) - **Sm**: 0 1px 0 rgba(36,33,29,0.05) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64,96] ### Surfaces - **Bg Pattern**: subtle linear paper grain and faint vertical manuscript guides - **Card Style**: flat editorial plates with one-pixel borders, caption bars, and small square radii - **Treatment**: warm neutral canvas with matte paper panels and no glass effects ### Typography - **Base Size**: 16px - **Body Font**: Source Sans 3 - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&family=Literata:opsz,wght@7..72,500;7..72,650&family=Source+Sans+3:wght@400;500;600;700&display=swap - **Heading Font**: Literata - **Letter Spacing**: -0.005em - **Line Height**: 1.62 - **Mono Font**: IBM Plex Mono - **Scale Ratio**: 1.22 ## Rules ### Composition Build screens around a dominant reading surface, a persistent reference rail, and compact footnote plates; command surfaces sit inline with text rather than above it. ### Density Text can be dense inside the reading column, but surrounding whitespace and rail grouping must keep the screen calm and scannable. ### Hierarchy Use Literata for article titles and section heads, Source Sans 3 for interface text, IBM Plex Mono for IDs; hierarchy comes from measure, rule weight, spacing, and small caps labels. ### Signature Patterns - Thread stitch: replies and contextual notes use a continuous left rule with numbered knots and indented body copy. - Command links: actions appear as underlined text buttons with tiny mono glyph prefixes and blue-violet focus halos. - Reference rail: citations, sources, and memory fragments live in a right rail with pinned tabs and short provenance captions. - Footnote plates: compact metrics and tables use caption-top cards, tabular numerals, and horizontal rules instead of dashboard tiles. - Context weave lines: selected passages draw thin connector rules toward related references without arrows or decorative diagrams. ## Layout ### Breakpoints Desktop 1200+, tablet 768-1199 stacks rail below active text, mobile under 640 uses single column with collapsible reference groups. ### Grid Desktop uses a 12-column page with a 68ch manuscript column, 280px reference rail, and elastic outer margins. ### Whitespace Whitespace is generous around groups and narrow inside text: 32-48px section gaps, 16px paragraph rhythm, and 24px rail clusters. ## Guidance ### Do - Lead with readable paragraphs, threads, citations, and inline commands before showing metrics. - Keep accent color scarce and tied to provenance, selection, or primary command links. - Use hairline rules and margin notes to reveal relationships between text and context. - Make compact modules look like footnotes or editorial plates, not analytics dashboards. ### Don't - Do not turn AYA into a KPI dashboard or fill the canvas with equal metric cards. - Do not use gradients, glassmorphism, heavy shadows, or arbitrary rounded pill surfaces. - Do not color-code every status; use labels, rules, and text hierarchy first. - Do not let reference links float without visible attachment to the reading context. ### Accessibility Maintain high contrast ink on warm paper, visible 2px focus rings, 16px minimum body text, non-color status labels, and readable line lengths between 58ch and 72ch. ### Usage Context Best for AI knowledge workspaces, research notebooks, legal or policy analysis tools, editorial review systems, and context-heavy collaboration products where reading and synthesis are the core tasks.
DESIGN.md
---
version: "alpha"
name: "AYA Threaded Manuscript"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#5D6FAE"
background: "#F7F3EA"
border: "#D8D0C2"
error: "#A44E3F"
info: "#5D6FAE"
muted: "#80776B"
primary: "#24211D"
secondary: "#6F685F"
success: "#5D7D64"
surface: "#FFFCF4"
text: "#24211D"
warning: "#A97835"
typography:
headline-lg:
fontFamily: "Literata"
fontSize: "1.816rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.005em"
headline-md:
fontFamily: "Literata"
fontSize: "1.488rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.005em"
body-md:
fontFamily: "Source Sans 3"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.62
letterSpacing: "-0.005em"
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: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
step-8: "96px"
components:
color-reference-accent:
backgroundColor: "{colors.accent}"
color-reference-background:
backgroundColor: "{colors.background}"
color-reference-border:
backgroundColor: "{colors.border}"
color-reference-error:
backgroundColor: "{colors.error}"
color-reference-info:
backgroundColor: "{colors.info}"
color-reference-muted:
backgroundColor: "{colors.muted}"
color-reference-primary:
backgroundColor: "{colors.primary}"
color-reference-secondary:
backgroundColor: "{colors.secondary}"
color-reference-success:
backgroundColor: "{colors.success}"
color-reference-surface:
backgroundColor: "{colors.surface}"
color-reference-text:
backgroundColor: "{colors.text}"
color-reference-warning:
backgroundColor: "{colors.warning}"
button-primary:
backgroundColor: "{colors.primary}"
textColor: "#ffffff"
typography: "{typography.label-md}"
rounded: "{rounded.md}"
padding: "{spacing.md}"
card-surface:
backgroundColor: "{colors.surface}"
textColor: "{colors.text}"
rounded: "{rounded.md}"
padding: "{spacing.md}"
input-default:
backgroundColor: "{colors.surface}"
textColor: "{colors.text}"
rounded: "{rounded.md}"
height: "44px"
---
# AYA Threaded Manuscript
## Overview
AYA Threaded Manuscript treats a knowledge workspace as a calm annotated reading room: long text is primary, references are woven in at the margin, and commands feel like editorial marks rather than dashboard controls.
### Values
- long-form readability before widget density
- context links that feel attached to sentences
- quiet hierarchy from measure, rules, and margin rhythm
- restrained accent color used only for action and provenance
### Anti-Values
- dashboard-first metric walls
- generic SaaS card grids
- colorful status confetti
- floating glass panels detached from text
### Visual Character
- Use a two-column manuscript grid with a 68ch reading column and a narrow reference rail separated by a hairline vertical rule.
- Render threads as indented editorial blocks with left-side stitch rules, small sequence numerals, and clipped quote headers.
- Use flat warm paper surfaces, one-pixel stone borders, square-to-small radii, and no decorative drop shadows on primary text areas.
- Apply a muted blue-violet accent only to command links, active tabs, reference pins, and focus outlines while most UI remains ink and paper.
- Place compact data modules as footnote plates with tabular lining numerals and top caption rules instead of bright dashboard cards.
## 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 | `#5D6FAE` |
| background | `#F7F3EA` |
| border | `#D8D0C2` |
| error | `#A44E3F` |
| info | `#5D6FAE` |
| muted | `#80776B` |
| primary | `#24211D` |
| secondary | `#6F685F` |
| success | `#5D7D64` |
| surface | `#FFFCF4` |
| text | `#24211D` |
| warning | `#A97835` |
## Typography
- **Headline-Lg**: Literata, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Literata, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Source Sans 3, 16px, weight 400, line-height 1.62.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
- **Step-8**: `96px`
### Breakpoints
Desktop 1200+, tablet 768-1199 stacks rail below active text, mobile under 640 uses single column with collapsible reference groups.
### Grid
Desktop uses a 12-column page with a 68ch manuscript column, 280px reference rail, and elastic outer margins.
### Whitespace
Whitespace is generous around groups and narrow inside text: 32-48px section gaps, 16px paragraph rhythm, and 24px rail clusters.
## Elevation & Depth
### Shadows
- **Lg**: 0 24px 60px rgba(36,33,29,0.08)
- **Md**: 0 10px 24px rgba(36,33,29,0.06)
- **Sm**: 0 1px 0 rgba(36,33,29,0.05)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `10px`
- **Md**: `6px`
- **None**: `0px`
- **Sm**: `3px`
### Surfaces
- **Bg Pattern**: subtle linear paper grain and faint vertical manuscript guides
- **Card Style**: flat editorial plates with one-pixel borders, caption bars, and small square radii
- **Treatment**: warm neutral canvas with matte paper panels and no glass effects
### Borders
- **Accent Width**: 2px
- **Character**: quiet print-like rules that bind text, margin notes, and command affordances
- **Default Width**: 1px
- **Style**: solid hairlines with occasional double-rule separators
## Components
### Composition
Build screens around a dominant reading surface, a persistent reference rail, and compact footnote plates; command surfaces sit inline with text rather than above it.
### Density
Text can be dense inside the reading column, but surrounding whitespace and rail grouping must keep the screen calm and scannable.
### Hierarchy
Use Literata for article titles and section heads, Source Sans 3 for interface text, IBM Plex Mono for IDs; hierarchy comes from measure, rule weight, spacing, and small caps labels.
### Signature Patterns
- Thread stitch: replies and contextual notes use a continuous left rule with numbered knots and indented body copy.
- Command links: actions appear as underlined text buttons with tiny mono glyph prefixes and blue-violet focus halos.
- Reference rail: citations, sources, and memory fragments live in a right rail with pinned tabs and short provenance captions.
- Footnote plates: compact metrics and tables use caption-top cards, tabular numerals, and horizontal rules instead of dashboard tiles.
- Context weave lines: selected passages draw thin connector rules toward related references without arrows or decorative diagrams.
## shadcn/ui Usage
When the target app uses shadcn/ui, copy DESIGN.md with shadcn instead of the plain DESIGN.md. It contains the same Katagami design-language source plus the shadcn/ui primitives, imports, theme variables, component recipes, and preview-shot guidance.
DESIGN.md with shadcn: `/language/en-019edab3-1d86-7021-a170-46c5dfb0f76d/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 Lead with readable paragraphs, threads, citations, and inline commands before showing metrics.
- Do Keep accent color scarce and tied to provenance, selection, or primary command links.
- Do Use hairline rules and margin notes to reveal relationships between text and context.
- Do Make compact modules look like footnotes or editorial plates, not analytics dashboards.
- Don't Do not turn AYA into a KPI dashboard or fill the canvas with equal metric cards.
- Don't Do not use gradients, glassmorphism, heavy shadows, or arbitrary rounded pill surfaces.
- Don't Do not color-code every status; use labels, rules, and text hierarchy first.
- Don't Do not let reference links float without visible attachment to the reading context.
### Accessibility
Maintain high contrast ink on warm paper, visible 2px focus rings, 16px minimum body text, non-color status labels, and readable line lengths between 58ch and 72ch.
### Usage Context
Best for AI knowledge workspaces, research notebooks, legal or policy analysis tools, editorial review systems, and context-heavy collaboration products where reading and synthesis are the core tasks.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "aya-threaded-manuscript",
"type": "registry:theme",
"title": "AYA Threaded Manuscript shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F7F3EA",
"foreground": "#24211D",
"card": "#FFFCF4",
"card-foreground": "#24211D",
"popover": "#FFFCF4",
"popover-foreground": "#24211D",
"primary": "#24211D",
"primary-foreground": "#ffffff",
"secondary": "#6F685F",
"secondary-foreground": "#ffffff",
"muted": "#80776B",
"muted-foreground": "#24211D",
"accent": "#5D6FAE",
"accent-foreground": "#ffffff",
"destructive": "#A44E3F",
"border": "#D8D0C2",
"input": "#D8D0C2",
"ring": "#5D6FAE",
"chart-1": "#24211D",
"chart-2": "#6F685F",
"chart-3": "#5D6FAE",
"chart-4": "#5D7D64",
"chart-5": "#A97835",
"sidebar": "#FFFCF4",
"sidebar-foreground": "#24211D",
"sidebar-primary": "#24211D",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#5D6FAE",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#D8D0C2",
"sidebar-ring": "#5D6FAE",
"radius": "6px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#24211D",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#5D6FAE",
"accent-foreground": "#ffffff",
"destructive": "#A44E3F",
"border": "#303642",
"input": "#303642",
"ring": "#5D6FAE",
"chart-1": "#24211D",
"chart-2": "#6F685F",
"chart-3": "#5D6FAE",
"chart-4": "#5D7D64",
"chart-5": "#A97835",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#24211D",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#5D6FAE",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#5D6FAE",
"radius": "6px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019edab3-1d86-7021-a170-46c5dfb0f76d",
"slug": "aya-threaded-manuscript",
"componentManifest": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"nativeTokenNames": {
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"colors": [
"accent",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"motion": [
"duration",
"easing",
"philosophy"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"spacing": [
"base",
"scale"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
]
}
}
}
```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
- base8px
- xs4px
- sm8px
- md12px
- lg16px
- xl24px
- 2xl32px
- 3xl48px
- 4xl64px
- step-896px
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: #F7F3EA;
--foreground: #24211D;
--card: #FFFCF4;
--card-foreground: #24211D;
--popover: #FFFCF4;
--popover-foreground: #24211D;
--primary: #24211D;
--primary-foreground: #ffffff;
--secondary: #6F685F;
--secondary-foreground: #ffffff;
--muted: #80776B;
--muted-foreground: #24211D;
--accent: #5D6FAE;
--accent-foreground: #ffffff;
--destructive: #A44E3F;
--border: #D8D0C2;
--input: #D8D0C2;
--ring: #5D6FAE;
--chart-1: #24211D;
--chart-2: #6F685F;
--chart-3: #5D6FAE;
--chart-4: #5D7D64;
--chart-5: #A97835;
--sidebar: #FFFCF4;
--sidebar-foreground: #24211D;
--sidebar-primary: #24211D;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #5D6FAE;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #D8D0C2;
--sidebar-ring: #5D6FAE;
--radius: 6px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #24211D;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #5D6FAE;
--accent-foreground: #ffffff;
--destructive: #A44E3F;
--border: #303642;
--input: #303642;
--ring: #5D6FAE;
--chart-1: #24211D;
--chart-2: #6F685F;
--chart-3: #5D6FAE;
--chart-4: #5D7D64;
--chart-5: #A97835;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #24211D;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #5D6FAE;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #5D6FAE;
--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 AyaThreadedManuscriptShadcnKit() {
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">AYA Threaded Manuscript</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": "aya-threaded-manuscript",
"type": "registry:theme",
"title": "AYA Threaded Manuscript shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F7F3EA",
"foreground": "#24211D",
"card": "#FFFCF4",
"card-foreground": "#24211D",
"popover": "#FFFCF4",
"popover-foreground": "#24211D",
"primary": "#24211D",
"primary-foreground": "#ffffff",
"secondary": "#6F685F",
"secondary-foreground": "#ffffff",
"muted": "#80776B",
"muted-foreground": "#24211D",
"accent": "#5D6FAE",
"accent-foreground": "#ffffff",
"destructive": "#A44E3F",
"border": "#D8D0C2",
"input": "#D8D0C2",
"ring": "#5D6FAE",
"chart-1": "#24211D",
"chart-2": "#6F685F",
"chart-3": "#5D6FAE",
"chart-4": "#5D7D64",
"chart-5": "#A97835",
"sidebar": "#FFFCF4",
"sidebar-foreground": "#24211D",
"sidebar-primary": "#24211D",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#5D6FAE",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#D8D0C2",
"sidebar-ring": "#5D6FAE",
"radius": "6px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#24211D",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#5D6FAE",
"accent-foreground": "#ffffff",
"destructive": "#A44E3F",
"border": "#303642",
"input": "#303642",
"ring": "#5D6FAE",
"chart-1": "#24211D",
"chart-2": "#6F685F",
"chart-3": "#5D6FAE",
"chart-4": "#5D7D64",
"chart-5": "#A97835",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#24211D",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#5D6FAE",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#5D6FAE",
"radius": "6px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019edab3-1d86-7021-a170-46c5dfb0f76d",
"slug": "aya-threaded-manuscript",
"componentManifest": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"nativeTokenNames": {
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"colors": [
"accent",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"motion": [
"duration",
"easing",
"philosophy"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"spacing": [
"base",
"scale"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
]
}
}
}
# AYA Threaded Manuscript shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019edab3-1d86-7021-a170-46c5dfb0f76d`
Slug: `aya-threaded-manuscript`
## Intent
AYA Threaded Manuscript treats a knowledge workspace as a calm annotated reading room: long text is primary, references are woven in at the margin, and commands feel like editorial marks rather than dashboard controls.
## 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": "#5D6FAE",
"background": "#F7F3EA",
"border": "#D8D0C2",
"error": "#A44E3F",
"info": "#5D6FAE",
"muted": "#80776B",
"primary": "#24211D",
"secondary": "#6F685F",
"success": "#5D7D64",
"surface": "#FFFCF4",
"text": "#24211D",
"warning": "#A97835"
}
Typography:
{
"base_size": "16px",
"body_font": "Source Sans 3",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&family=Literata:opsz,wght@7..72,500;7..72,650&family=Source+Sans+3:wght@400;500;600;700&display=swap",
"heading_font": "Literata",
"letter_spacing": "-0.005em",
"line_height": 1.62,
"mono_font": "IBM Plex Mono",
"scale_ratio": 1.22
}
## Visual character to preserve
- Use a two-column manuscript grid with a 68ch reading column and a narrow reference rail separated by a hairline vertical rule.
- Render threads as indented editorial blocks with left-side stitch rules, small sequence numerals, and clipped quote headers.
- Use flat warm paper surfaces, one-pixel stone borders, square-to-small radii, and no decorative drop shadows on primary text areas.
- Apply a muted blue-violet accent only to command links, active tabs, reference pins, and focus outlines while most UI remains ink and paper.
- Place compact data modules as footnote plates with tabular lining numerals and top caption rules instead of bright dashboard cards.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "default",
"border": "solid",
"underlay": false,
"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/aya-threaded-manuscript/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: Lead with readable paragraphs, threads, citations, and inline commands before showing metrics.; Keep accent color scarce and tied to provenance, selection, or primary command links.; Use hairline rules and margin notes to reveal relationships between text and context.; Make compact modules look like footnotes or editorial plates, not analytics dashboards.
- Do not: Do not turn AYA into a KPI dashboard or fill the canvas with equal metric cards.; Do not use gradients, glassmorphism, heavy shadows, or arbitrary rounded pill surfaces.; Do not color-code every status; use labels, rules, and text hierarchy first.; Do not let reference links float without visible attachment to the reading context.
## 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 AyaThreadedManuscriptShadcnKit() {
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">AYA Threaded Manuscript</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
```
## Layout notes
{
"breakpoints": "Desktop 1200+, tablet 768-1199 stacks rail below active text, mobile under 640 uses single column with collapsible reference groups.",
"grid": "Desktop uses a 12-column page with a 68ch manuscript column, 280px reference rail, and elastic outer margins.",
"whitespace": "Whitespace is generous around groups and narrow inside text: 32-48px section gaps, 16px paragraph rhythm, and 24px rail clusters."
}
{
"artifact": "katagami:shadcn-preview-shots",
"version": "preview-shots-v1",
"generator": "katagami-ui-compatibility-projection",
"generatedBy": "katagami-ui-projection",
"requiresVisualProfile": true,
"schema": "katagami:shadcn-preview-shots/renderable-v1",
"renderable": true,
"language": {
"id": "en-019edab3-1d86-7021-a170-46c5dfb0f76d",
"name": "AYA Threaded Manuscript",
"slug": "aya-threaded-manuscript"
},
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"primitives": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"identityNotes": [
"Use a two-column manuscript grid with a 68ch reading column and a narrow reference rail separated by a hairline vertical rule.",
"Render threads as indented editorial blocks with left-side stitch rules, small sequence numerals, and clipped quote headers.",
"Use flat warm paper surfaces, one-pixel stone borders, square-to-small radii, and no decorative drop shadows on primary text areas.",
"Apply a muted blue-violet accent only to command links, active tabs, reference pins, and focus outlines while most UI remains ink and paper.",
"Place compact data modules as footnote plates with tabular lining numerals and top caption rules instead of bright dashboard cards."
],
"visualProfile": {
"family": "paper-collage",
"material": "paper",
"contour": "default",
"border": "solid",
"underlay": false,
"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": "AYA Threaded Manuscript 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": [
"Lead with readable paragraphs, threads, citations, and inline commands before showing metrics.",
"Keep accent color scarce and tied to provenance, selection, or primary command links.",
"Use hairline rules and margin notes to reveal relationships between text and context.",
"Make compact modules look like footnotes or editorial plates, not analytics dashboards."
],
"dont": [
"Do not turn AYA into a KPI dashboard or fill the canvas with equal metric cards.",
"Do not use gradients, glassmorphism, heavy shadows, or arbitrary rounded pill surfaces.",
"Do not color-code every status; use labels, rules, and text hierarchy first.",
"Do not let reference links float without visible attachment to the reading context."
]
}
}