Signal Folio Workstation
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
- High-contrast editorial rules and hardware nameplate outlines; accent weight encloses selected controls rather than decorating one side.
- default width
- 1px
- style
- solid ink rules with occasional double-rule separators for folio section breaks
colors12 items
motion3 items
- duration
- 140ms
- easing
- cubic-bezier(.2,.7,.2,1)
- philosophy
- Interactions snap like keyed broadcast switches: focus thickens the rule, buttons depress by 1px, and tabs exchange filled label caps without opacity-only fades.
radii5 items
- full
- 9999px
- lg
- 6px
- md
- 3px
- none
- 0
- sm
- 3px
shadows3 items
- lg
- 0 22px 60px rgba(23,32,42,0.16)
- md
- 0 12px 28px rgba(23,32,42,0.10)
- sm
- 0 1px 0 rgba(20,20,20,0.18)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- Plain warm field; optional horizontal registration bands only within metering/transport components, never full-page dots or square grids.
- card style
- Squared folio panels with 1px dark ink rules, inset top label caps, and dense content aligned to typographic baselines.
- treatment
- Flat warm editorial paper surfaces with occasional solid broadcast key fields; no glass, glow, or gradient wash.
typography8 items
- base size
- 16px
- body font
- Afacad
- google fonts url
- https://fonts.googleapis.com/css2?family=Afacad:wght@400;500;600;700&family=Fragment+Mono:ital@0;1&family=Literata:opsz,wght@7..72,500;7..72,650;7..72,750&display=swap
- heading font
- Literata
- letter spacing
- -0.02em
- line height
- 1.48
- mono font
- Fragment Mono
- scale ratio
- 1.25
rules
Build screens as folio workstations: a dominant reading/decision surface, a narrower operations stack, and one intentional baseline break for active work.
High information density is allowed when grouped by proximity, label caps, and rule weight; quiet zones must be dramatically larger than internal gaps.
Use serif headlines for editorial priority, mono numerals for machine facts, sans labels for action scaffolding, and large color fields only for currently keyed decisions.
layout
mobile <= 640px, tablet 641px-1024px, desktop >= 1025px
Asymmetric column system: desktop uses a 1.55fr editorial column plus a 0.85fr operations column; tablet stacks operations below; mobile becomes single-column folio cards.
Internal label gaps stay tight at 4-12px while section breaks jump to 48-64px, satisfying dramatic spacing range without filler decoration.
guidance
- Use color only for keyed state, semantic status, or a major broadcast decision area.
- Keep corners squared and rule weights intentional so the interface feels like a premium workstation rather than soft SaaS.
- Let typographic voice separate editorial meaning, machine readings, and action labels.
- Use one dominant product artifact per screen, such as a routing decision, clearance folio, or compliance cutover.
- Do not use square-grid backgrounds, dotted default textures, vaporwave gradients, or arcade neon.
- Do not add decorative left rails, one-sided card stripes, or colored row accents as garnish.
- Do not make three equal cards the main composition; one element must dominate.
- Do not use color as confetti or create a rainbow broadcast package.
katagami spec
# Signal Folio Workstation ## Philosophy Signal Folio Workstation translates 1980s editorial broadcast intelligence into a premium 2026 product interface: crisp folio composition, cue-card hierarchy, hardware-grade input states, and restrained color blocking that clarifies operational decisions without becoming a retro skin. ### Values - composition before ornament - semantic color blocks only - editorial hierarchy with workstation precision - dense but calm operational reading ### Anti-Values - vaporwave nostalgia - square-grid wallpaper - decorative card stripes or side rails - rainbow broadcast sprawl - generic SaaS dashboard templates ### Visual Character - Asymmetric folio shell uses one wide editorial column, one narrow operations column, and a deliberate broken baseline panel for the primary decision surface. - Header typography pairs high-contrast serif display with compact humanist sans labels and tabular mono numerals for distinct editorial, product, and machine voices. - Surfaces are flat warm ivory and bone panels with 1px ink rules, squared 3px corners, and inset label caps that behave like hardware nameplates. - Color appears as large keyed broadcast fields or compact semantic chips, never as thin decorative side stripes on cards, rows, panels, or buttons. - Fine horizontal registration bands appear only inside measurement and transport areas to suggest scan discipline without using dotted texture or square grids. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: High-contrast editorial rules and hardware nameplate outlines; accent weight encloses selected controls rather than decorating one side. - **Default Width**: 1px - **Style**: solid ink rules with occasional double-rule separators for folio section breaks ### Colors | Name | Value | |------|-------| | accent | `#B54A2F` | | background | `#F5F0E6` | | border | `#2A2925` | | error | `#A9352A` | | info | `#315F86` | | muted | `#6F675B` | | primary | `#17202A` | | secondary | `#E7D9B8` | | success | `#2F7054` | | surface | `#FFFBF1` | | text | `#141414` | | warning | `#B88724` | ### Motion - **Duration**: 140ms - **Easing**: cubic-bezier(.2,.7,.2,1) - **Philosophy**: Interactions snap like keyed broadcast switches: focus thickens the rule, buttons depress by 1px, and tabs exchange filled label caps without opacity-only fades. ### Radii - **Full**: 9999px - **Lg**: 6px - **Md**: 3px - **None**: 0 - **Sm**: 3px ### Shadows - **Lg**: 0 22px 60px rgba(23,32,42,0.16) - **Md**: 0 12px 28px rgba(23,32,42,0.10) - **Sm**: 0 1px 0 rgba(20,20,20,0.18) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: Plain warm field; optional horizontal registration bands only within metering/transport components, never full-page dots or square grids. - **Card Style**: Squared folio panels with 1px dark ink rules, inset top label caps, and dense content aligned to typographic baselines. - **Treatment**: Flat warm editorial paper surfaces with occasional solid broadcast key fields; no glass, glow, or gradient wash. ### Typography - **Base Size**: 16px - **Body Font**: Afacad - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Afacad:wght@400;500;600;700&family=Fragment+Mono:ital@0;1&family=Literata:opsz,wght@7..72,500;7..72,650;7..72,750&display=swap - **Heading Font**: Literata - **Letter Spacing**: -0.02em - **Line Height**: 1.48 - **Mono Font**: Fragment Mono - **Scale Ratio**: 1.25 ## Rules ### Composition Build screens as folio workstations: a dominant reading/decision surface, a narrower operations stack, and one intentional baseline break for active work. ### Density High information density is allowed when grouped by proximity, label caps, and rule weight; quiet zones must be dramatically larger than internal gaps. ### Hierarchy Use serif headlines for editorial priority, mono numerals for machine facts, sans labels for action scaffolding, and large color fields only for currently keyed decisions. ### Signature Patterns - Inset label caps sit on top edges of panels and controls, naming the module while interrupting the border like an industrial broadcast nameplate. - Keyed decision fields use full rectangular color blocks with near-white text and tabular metadata, appearing only for active route, warning, or confirmation states. - Transport meters use subtle horizontal registration bands and stepped tick labels inside the component, never as page wallpaper or decorative texture. - Folio break panels intentionally offset one primary module from the column rhythm to create editorial tension without using a visible square grid. ## Layout ### Breakpoints mobile <= 640px, tablet 641px-1024px, desktop >= 1025px ### Grid Asymmetric column system: desktop uses a 1.55fr editorial column plus a 0.85fr operations column; tablet stacks operations below; mobile becomes single-column folio cards. ### Whitespace Internal label gaps stay tight at 4-12px while section breaks jump to 48-64px, satisfying dramatic spacing range without filler decoration. ## Guidance ### Do - Use color only for keyed state, semantic status, or a major broadcast decision area. - Keep corners squared and rule weights intentional so the interface feels like a premium workstation rather than soft SaaS. - Let typographic voice separate editorial meaning, machine readings, and action labels. - Use one dominant product artifact per screen, such as a routing decision, clearance folio, or compliance cutover. ### Don't - Do not use square-grid backgrounds, dotted default textures, vaporwave gradients, or arcade neon. - Do not add decorative left rails, one-sided card stripes, or colored row accents as garnish. - Do not make three equal cards the main composition; one element must dominate. - Do not use color as confetti or create a rainbow broadcast package.
DESIGN.md
---
version: "alpha"
name: "Signal Folio Workstation"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#B54A2F"
background: "#F5F0E6"
border: "#2A2925"
error: "#A9352A"
info: "#315F86"
muted: "#6F675B"
primary: "#17202A"
secondary: "#E7D9B8"
success: "#2F7054"
surface: "#FFFBF1"
text: "#141414"
warning: "#B88724"
typography:
headline-lg:
fontFamily: "Literata"
fontSize: "1.953rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.02em"
headline-md:
fontFamily: "Literata"
fontSize: "1.563rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.02em"
body-md:
fontFamily: "Afacad"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.48
letterSpacing: "-0.02em"
label-md:
fontFamily: "Fragment Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "6px"
md: "3px"
none: "0px"
sm: "3px"
spacing:
base: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
components:
color-reference-accent:
backgroundColor: "{colors.accent}"
color-reference-background:
backgroundColor: "{colors.background}"
color-reference-border:
backgroundColor: "{colors.border}"
color-reference-error:
backgroundColor: "{colors.error}"
color-reference-info:
backgroundColor: "{colors.info}"
color-reference-muted:
backgroundColor: "{colors.muted}"
color-reference-primary:
backgroundColor: "{colors.primary}"
color-reference-secondary:
backgroundColor: "{colors.secondary}"
color-reference-success:
backgroundColor: "{colors.success}"
color-reference-surface:
backgroundColor: "{colors.surface}"
color-reference-text:
backgroundColor: "{colors.text}"
color-reference-warning:
backgroundColor: "{colors.warning}"
button-primary:
backgroundColor: "{colors.primary}"
textColor: "#ffffff"
typography: "{typography.label-md}"
rounded: "{rounded.md}"
padding: "{spacing.md}"
card-surface:
backgroundColor: "{colors.surface}"
textColor: "{colors.text}"
rounded: "{rounded.md}"
padding: "{spacing.md}"
input-default:
backgroundColor: "{colors.surface}"
textColor: "{colors.text}"
rounded: "{rounded.md}"
height: "44px"
---
# Signal Folio Workstation
## Overview
Signal Folio Workstation translates 1980s editorial broadcast intelligence into a premium 2026 product interface: crisp folio composition, cue-card hierarchy, hardware-grade input states, and restrained color blocking that clarifies operational decisions without becoming a retro skin.
### Values
- composition before ornament
- semantic color blocks only
- editorial hierarchy with workstation precision
- dense but calm operational reading
### Anti-Values
- vaporwave nostalgia
- square-grid wallpaper
- decorative card stripes or side rails
- rainbow broadcast sprawl
- generic SaaS dashboard templates
### Visual Character
- Asymmetric folio shell uses one wide editorial column, one narrow operations column, and a deliberate broken baseline panel for the primary decision surface.
- Header typography pairs high-contrast serif display with compact humanist sans labels and tabular mono numerals for distinct editorial, product, and machine voices.
- Surfaces are flat warm ivory and bone panels with 1px ink rules, squared 3px corners, and inset label caps that behave like hardware nameplates.
- Color appears as large keyed broadcast fields or compact semantic chips, never as thin decorative side stripes on cards, rows, panels, or buttons.
- Fine horizontal registration bands appear only inside measurement and transport areas to suggest scan discipline without using dotted texture or square grids.
## 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 | `#B54A2F` |
| background | `#F5F0E6` |
| border | `#2A2925` |
| error | `#A9352A` |
| info | `#315F86` |
| muted | `#6F675B` |
| primary | `#17202A` |
| secondary | `#E7D9B8` |
| success | `#2F7054` |
| surface | `#FFFBF1` |
| text | `#141414` |
| warning | `#B88724` |
## Typography
- **Headline-Lg**: Literata, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Literata, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Afacad, 16px, weight 400, line-height 1.48.
- **Label-Md**: Fragment Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
### Breakpoints
mobile <= 640px, tablet 641px-1024px, desktop >= 1025px
### Grid
Asymmetric column system: desktop uses a 1.55fr editorial column plus a 0.85fr operations column; tablet stacks operations below; mobile becomes single-column folio cards.
### Whitespace
Internal label gaps stay tight at 4-12px while section breaks jump to 48-64px, satisfying dramatic spacing range without filler decoration.
## Elevation & Depth
### Shadows
- **Lg**: 0 22px 60px rgba(23,32,42,0.16)
- **Md**: 0 12px 28px rgba(23,32,42,0.10)
- **Sm**: 0 1px 0 rgba(20,20,20,0.18)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `6px`
- **Md**: `3px`
- **None**: `0px`
- **Sm**: `3px`
### Surfaces
- **Bg Pattern**: Plain warm field; optional horizontal registration bands only within metering/transport components, never full-page dots or square grids.
- **Card Style**: Squared folio panels with 1px dark ink rules, inset top label caps, and dense content aligned to typographic baselines.
- **Treatment**: Flat warm editorial paper surfaces with occasional solid broadcast key fields; no glass, glow, or gradient wash.
### Borders
- **Accent Width**: 2px
- **Character**: High-contrast editorial rules and hardware nameplate outlines; accent weight encloses selected controls rather than decorating one side.
- **Default Width**: 1px
- **Style**: solid ink rules with occasional double-rule separators for folio section breaks
## Components
### Composition
Build screens as folio workstations: a dominant reading/decision surface, a narrower operations stack, and one intentional baseline break for active work.
### Density
High information density is allowed when grouped by proximity, label caps, and rule weight; quiet zones must be dramatically larger than internal gaps.
### Hierarchy
Use serif headlines for editorial priority, mono numerals for machine facts, sans labels for action scaffolding, and large color fields only for currently keyed decisions.
### Signature Patterns
- Inset label caps sit on top edges of panels and controls, naming the module while interrupting the border like an industrial broadcast nameplate.
- Keyed decision fields use full rectangular color blocks with near-white text and tabular metadata, appearing only for active route, warning, or confirmation states.
- Transport meters use subtle horizontal registration bands and stepped tick labels inside the component, never as page wallpaper or decorative texture.
- Folio break panels intentionally offset one primary module from the column rhythm to create editorial tension without using a visible square grid.
## 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-019e4695-09c9-77e3-bf45-20a7f12d9638/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 Use color only for keyed state, semantic status, or a major broadcast decision area.
- Do Keep corners squared and rule weights intentional so the interface feels like a premium workstation rather than soft SaaS.
- Do Let typographic voice separate editorial meaning, machine readings, and action labels.
- Do Use one dominant product artifact per screen, such as a routing decision, clearance folio, or compliance cutover.
- Don't Do not use square-grid backgrounds, dotted default textures, vaporwave gradients, or arcade neon.
- Don't Do not add decorative left rails, one-sided card stripes, or colored row accents as garnish.
- Don't Do not make three equal cards the main composition; one element must dominate.
- Don't Do not use color as confetti or create a rainbow broadcast package.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "signal-folio-workstation",
"type": "registry:theme",
"title": "Signal Folio Workstation shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F5F0E6",
"foreground": "#141414",
"card": "#FFFBF1",
"card-foreground": "#141414",
"popover": "#FFFBF1",
"popover-foreground": "#141414",
"primary": "#17202A",
"primary-foreground": "#ffffff",
"secondary": "#E7D9B8",
"secondary-foreground": "#111111",
"muted": "#6F675B",
"muted-foreground": "#141414",
"accent": "#B54A2F",
"accent-foreground": "#ffffff",
"destructive": "#A9352A",
"border": "#2A2925",
"input": "#2A2925",
"ring": "#B54A2F",
"chart-1": "#17202A",
"chart-2": "#E7D9B8",
"chart-3": "#B54A2F",
"chart-4": "#2F7054",
"chart-5": "#B88724",
"sidebar": "#FFFBF1",
"sidebar-foreground": "#141414",
"sidebar-primary": "#17202A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#315F86",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#2A2925",
"sidebar-ring": "#B54A2F",
"radius": "3px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#17202A",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#B54A2F",
"accent-foreground": "#ffffff",
"destructive": "#A9352A",
"border": "#303642",
"input": "#303642",
"ring": "#B54A2F",
"chart-1": "#17202A",
"chart-2": "#E7D9B8",
"chart-3": "#B54A2F",
"chart-4": "#2F7054",
"chart-5": "#B88724",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#17202A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#B54A2F",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#B54A2F",
"radius": "3px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e4695-09c9-77e3-bf45-20a7f12d9638",
"slug": "signal-folio-workstation",
"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
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: #F5F0E6;
--foreground: #141414;
--card: #FFFBF1;
--card-foreground: #141414;
--popover: #FFFBF1;
--popover-foreground: #141414;
--primary: #17202A;
--primary-foreground: #ffffff;
--secondary: #E7D9B8;
--secondary-foreground: #111111;
--muted: #6F675B;
--muted-foreground: #141414;
--accent: #B54A2F;
--accent-foreground: #ffffff;
--destructive: #A9352A;
--border: #2A2925;
--input: #2A2925;
--ring: #B54A2F;
--chart-1: #17202A;
--chart-2: #E7D9B8;
--chart-3: #B54A2F;
--chart-4: #2F7054;
--chart-5: #B88724;
--sidebar: #FFFBF1;
--sidebar-foreground: #141414;
--sidebar-primary: #17202A;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #315F86;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #2A2925;
--sidebar-ring: #B54A2F;
--radius: 3px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #17202A;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #B54A2F;
--accent-foreground: #ffffff;
--destructive: #A9352A;
--border: #303642;
--input: #303642;
--ring: #B54A2F;
--chart-1: #17202A;
--chart-2: #E7D9B8;
--chart-3: #B54A2F;
--chart-4: #2F7054;
--chart-5: #B88724;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #17202A;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #B54A2F;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #B54A2F;
--radius: 3px;
}
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 SignalFolioWorkstationShadcnKit() {
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">Signal Folio Workstation</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": "signal-folio-workstation",
"type": "registry:theme",
"title": "Signal Folio Workstation shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F5F0E6",
"foreground": "#141414",
"card": "#FFFBF1",
"card-foreground": "#141414",
"popover": "#FFFBF1",
"popover-foreground": "#141414",
"primary": "#17202A",
"primary-foreground": "#ffffff",
"secondary": "#E7D9B8",
"secondary-foreground": "#111111",
"muted": "#6F675B",
"muted-foreground": "#141414",
"accent": "#B54A2F",
"accent-foreground": "#ffffff",
"destructive": "#A9352A",
"border": "#2A2925",
"input": "#2A2925",
"ring": "#B54A2F",
"chart-1": "#17202A",
"chart-2": "#E7D9B8",
"chart-3": "#B54A2F",
"chart-4": "#2F7054",
"chart-5": "#B88724",
"sidebar": "#FFFBF1",
"sidebar-foreground": "#141414",
"sidebar-primary": "#17202A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#315F86",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#2A2925",
"sidebar-ring": "#B54A2F",
"radius": "3px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#17202A",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#B54A2F",
"accent-foreground": "#ffffff",
"destructive": "#A9352A",
"border": "#303642",
"input": "#303642",
"ring": "#B54A2F",
"chart-1": "#17202A",
"chart-2": "#E7D9B8",
"chart-3": "#B54A2F",
"chart-4": "#2F7054",
"chart-5": "#B88724",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#17202A",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#B54A2F",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#B54A2F",
"radius": "3px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e4695-09c9-77e3-bf45-20a7f12d9638",
"slug": "signal-folio-workstation",
"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"
]
}
}
}
# Signal Folio Workstation shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4695-09c9-77e3-bf45-20a7f12d9638`
Slug: `signal-folio-workstation`
## Intent
Signal Folio Workstation translates 1980s editorial broadcast intelligence into a premium 2026 product interface: crisp folio composition, cue-card hierarchy, hardware-grade input states, and restrained color blocking that clarifies operational decisions without becoming a retro skin.
## 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": "#B54A2F",
"background": "#F5F0E6",
"border": "#2A2925",
"error": "#A9352A",
"info": "#315F86",
"muted": "#6F675B",
"primary": "#17202A",
"secondary": "#E7D9B8",
"success": "#2F7054",
"surface": "#FFFBF1",
"text": "#141414",
"warning": "#B88724"
}
Typography:
{
"base_size": "16px",
"body_font": "Afacad",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Afacad:wght@400;500;600;700&family=Fragment+Mono:ital@0;1&family=Literata:opsz,wght@7..72,500;7..72,650;7..72,750&display=swap",
"heading_font": "Literata",
"letter_spacing": "-0.02em",
"line_height": 1.48,
"mono_font": "Fragment Mono",
"scale_ratio": 1.25
}
## Visual character to preserve
- Asymmetric folio shell uses one wide editorial column, one narrow operations column, and a deliberate broken baseline panel for the primary decision surface.
- Header typography pairs high-contrast serif display with compact humanist sans labels and tabular mono numerals for distinct editorial, product, and machine voices.
- Surfaces are flat warm ivory and bone panels with 1px ink rules, squared 3px corners, and inset label caps that behave like hardware nameplates.
- Color appears as large keyed broadcast fields or compact semantic chips, never as thin decorative side stripes on cards, rows, panels, or buttons.
- Fine horizontal registration bands appear only inside measurement and transport areas to suggest scan discipline without using dotted texture or square grids.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "default",
"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/signal-folio-workstation/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: Use color only for keyed state, semantic status, or a major broadcast decision area.; Keep corners squared and rule weights intentional so the interface feels like a premium workstation rather than soft SaaS.; Let typographic voice separate editorial meaning, machine readings, and action labels.; Use one dominant product artifact per screen, such as a routing decision, clearance folio, or compliance cutover.
- Do not: Do not use square-grid backgrounds, dotted default textures, vaporwave gradients, or arcade neon.; Do not add decorative left rails, one-sided card stripes, or colored row accents as garnish.; Do not make three equal cards the main composition; one element must dominate.; Do not use color as confetti or create a rainbow broadcast package.
## 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 SignalFolioWorkstationShadcnKit() {
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">Signal Folio Workstation</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, tablet 641px-1024px, desktop >= 1025px",
"grid": "Asymmetric column system: desktop uses a 1.55fr editorial column plus a 0.85fr operations column; tablet stacks operations below; mobile becomes single-column folio cards.",
"whitespace": "Internal label gaps stay tight at 4-12px while section breaks jump to 48-64px, satisfying dramatic spacing range without filler decoration."
}
{
"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-019e4695-09c9-77e3-bf45-20a7f12d9638",
"name": "Signal Folio Workstation",
"slug": "signal-folio-workstation"
},
"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": [
"Asymmetric folio shell uses one wide editorial column, one narrow operations column, and a deliberate broken baseline panel for the primary decision surface.",
"Header typography pairs high-contrast serif display with compact humanist sans labels and tabular mono numerals for distinct editorial, product, and machine voices.",
"Surfaces are flat warm ivory and bone panels with 1px ink rules, squared 3px corners, and inset label caps that behave like hardware nameplates.",
"Color appears as large keyed broadcast fields or compact semantic chips, never as thin decorative side stripes on cards, rows, panels, or buttons.",
"Fine horizontal registration bands appear only inside measurement and transport areas to suggest scan discipline without using dotted texture or square grids."
],
"visualProfile": {
"family": "paper-collage",
"material": "paper",
"contour": "default",
"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": "Signal Folio Workstation 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": [
"Use color only for keyed state, semantic status, or a major broadcast decision area.",
"Keep corners squared and rule weights intentional so the interface feels like a premium workstation rather than soft SaaS.",
"Let typographic voice separate editorial meaning, machine readings, and action labels.",
"Use one dominant product artifact per screen, such as a routing decision, clearance folio, or compliance cutover."
],
"dont": [
"Do not use square-grid backgrounds, dotted default textures, vaporwave gradients, or arcade neon.",
"Do not add decorative left rails, one-sided card stripes, or colored row accents as garnish.",
"Do not make three equal cards the main composition; one element must dominate.",
"Do not use color as confetti or create a rainbow broadcast package."
]
}
}