Signal Ledger Spectrum
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
- 3px
- character
- precision enterprise borders; color accents indicate role but never replace labels
- default width
- 1px
- style
- solid with optional dashed forecast and dotted secondary-series variants
colors12 items
motion3 items
- duration
- 160ms
- easing
- cubic-bezier(.2,.8,.2,1)
- philosophy
- short confirmation motion for filters, live status pulse only for active incidents, no animated chart values by default
palette_roles3 items
- charts
- categorical ["#1D4ED8","#0F766E","#7C3AED","#D97706","#0891B2","#9333EA","#475569","#16A34A"]·diverging ["#B42318","#F97316","#F8FAFC","#0EA5E9","#1D4ED8"]·sequential blue ["#EFF6FF","#DBEAFE","#93C5FD","#3B82F6","#1D4ED8","#1E3A8A"]·sequential green ["#ECFDF5","#BBF7D0","#4ADE80","#16A34A","#087443"]
- semantic
- error #B42318·info #0B65C2·neutral #64748B·success #087443·warning #B54708
- ui
- blue #1D4ED8·chrome #172033·teal #0F766E·violet #7C3AED·wash #EEF4FF
radii5 items
- full
- 9999px
- lg
- 16px
- md
- 10px
- none
- 0
- sm
- 6px
shadows3 items
- lg
- 0 24px 60px rgba(23,32,51,0.14)
- md
- 0 10px 24px rgba(23,32,51,0.10)
- sm
- 0 1px 2px rgba(23,32,51,0.06)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- linear grid using rgba(29,78,216,.055) at 32px intervals plus sparse violet insight glows
- card style
- flat cards with 1px cool border, subtle top highlight, and semantic left rail when stateful
- treatment
- matte white dashboard panels over a cool blue-gray canvas with faint analytical grid lines
typography8 items
- base size
- 16px
- body font
- Source Sans 3
- google fonts url
- https://fonts.googleapis.com/css2?family=Sora:wght@500;600;700&family=Source+Sans+3:wght@400;500;600;700&family=IBM+Plex+Mono:wght@500;600&display=swap
- heading font
- Sora
- letter spacing
- -0.015em
- line height
- 1.52
- mono font
- IBM Plex Mono
- scale ratio
- 1.2
rules
Lead with a command dashboard: KPI row, status queue, analytical chart, and operational table in a 12-column grid. Keep controls in a narrow filter rail or top command strip.
Medium-high density with 16px gutters, compact table rows, and strong grouping; every dense region needs one calm blank margin or legend column.
Use Sora for concise metric labels and section headings, Source Sans 3 for explanatory business copy, and mono numerals for deltas, timestamps, thresholds, and chart axes.
layout
desktop 1200px+, tablet 768-1199px with 6 columns, mobile below 640px stacking KPI cards and tables into readable cards
12-column desktop dashboard grid with 24px page margins, 16px gutters, and nested 4-column chart/card zones.
Whitespace is functional: 24px between dashboard zones, 12px inside dense controls, extra breathing room around legends and semantic explanations.
guidance
- Separate UI chrome colors from semantic status colors and from chart scales in names, legends, and CSS variables.
- Pair every red, amber, green, or blue state with text, icon geometry, and border or pattern reinforcement.
- Use categorical palettes for peers, sequential ramps for magnitude, and diverging scales only when a meaningful midpoint exists.
- Keep dashboard backgrounds pale and low contrast so chart colors retain authority.
- Do not use rainbow scales for business metrics or mix semantic red/green into categorical chart series without explicit status meaning.
- Do not place saturated violet, teal, and blue gradients behind small text or table values.
- Do not rely on color alone for alerts, row health, chart series, or selected filters.
- Do not let decorative brand color override contrast requirements for controls and focus states.
katagami spec
# Signal Ledger Spectrum
## Philosophy
A dashboard-first enterprise language that separates neutral product chrome, semantic operational status, and analytical chart palettes so business data reads as trustworthy evidence rather than decoration.
### Values
- Operational clarity before ornament
- Accessible status meaning with text and shape redundancy
- Calm trustworthy blues balanced by green progress and violet insight
- Data visualization scales that preserve hierarchy under dense executive dashboards
### Anti-Values
- Color-only alerts or KPI states without labels, icons, patterns, or contrast support
- Decorative gradients that compete with chart encodings or imply false precision
- Consumer-app saturation in enterprise analytics surfaces
### Visual Character
- CSS custom properties split into --ui, --semantic, and --chart namespaces, with product chrome restricted to slate, blue, and low-chroma surfaces.
- Dashboard cards use quiet white panels, 1px cool-gray borders, and a left status rail so status remains visible independent of fill color.
- Charts combine solid categorical swatches with dot, stripe, and dash marker classes so series remain distinguishable when color perception or printing fails.
- Sequential data blocks use stepped blue-to-violet lightness ramps on pale grid backgrounds rather than rainbow hues, preserving readable labels and business seriousness.
- Critical semantic states pair color with icon geometry, badge text, and border pattern: check for success, triangle for warning, octagon for error, pulse ring for live info.
## Tokens
### Borders
- **Accent Width**: 3px
- **Character**: precision enterprise borders; color accents indicate role but never replace labels
- **Default Width**: 1px
- **Style**: solid with optional dashed forecast and dotted secondary-series variants
### Colors
| Name | Value |
|------|-------|
| accent | `#7C3AED` |
| background | `#F6F8FC` |
| border | `#D9E2EF` |
| error | `#B42318` |
| info | `#0B65C2` |
| muted | `#64748B` |
| primary | `#1D4ED8` |
| secondary | `#0F766E` |
| success | `#087443` |
| surface | `#FFFFFF` |
| text | `#172033` |
| warning | `#B54708` |
### Motion
- **Duration**: 160ms
- **Easing**: cubic-bezier(.2,.8,.2,1)
- **Philosophy**: short confirmation motion for filters, live status pulse only for active incidents, no animated chart values by default
### Palette Roles
- **Charts**: {"categorical":["#1D4ED8","#0F766E","#7C3AED","#D97706","#0891B2","#9333EA","#475569","#16A34A"],"diverging":["#B42318","#F97316","#F8FAFC","#0EA5E9","#1D4ED8"],"sequential_blue":["#EFF6FF","#DBEAFE","#93C5FD","#3B82F6","#1D4ED8","#1E3A8A"],"sequential_green":["#ECFDF5","#BBF7D0","#4ADE80","#16A34A","#087443"]}
- **Semantic**: {"error":"#B42318","info":"#0B65C2","neutral":"#64748B","success":"#087443","warning":"#B54708"}
- **Ui**: {"blue":"#1D4ED8","chrome":"#172033","teal":"#0F766E","violet":"#7C3AED","wash":"#EEF4FF"}
### Radii
- **Full**: 9999px
- **Lg**: 16px
- **Md**: 10px
- **None**: 0
- **Sm**: 6px
### Shadows
- **Lg**: 0 24px 60px rgba(23,32,51,0.14)
- **Md**: 0 10px 24px rgba(23,32,51,0.10)
- **Sm**: 0 1px 2px rgba(23,32,51,0.06)
### Spacing
- **Base**: 8px
- **Scale**: [4,8,12,16,24,32,48,64]
### Surfaces
- **Bg Pattern**: linear grid using rgba(29,78,216,.055) at 32px intervals plus sparse violet insight glows
- **Card Style**: flat cards with 1px cool border, subtle top highlight, and semantic left rail when stateful
- **Treatment**: matte white dashboard panels over a cool blue-gray canvas with faint analytical grid lines
### Typography
- **Base Size**: 16px
- **Body Font**: Source Sans 3
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Sora:wght@500;600;700&family=Source+Sans+3:wght@400;500;600;700&family=IBM+Plex+Mono:wght@500;600&display=swap
- **Heading Font**: Sora
- **Letter Spacing**: -0.015em
- **Line Height**: 1.52
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.2
## Rules
### Composition
Lead with a command dashboard: KPI row, status queue, analytical chart, and operational table in a 12-column grid. Keep controls in a narrow filter rail or top command strip.
### Density
Medium-high density with 16px gutters, compact table rows, and strong grouping; every dense region needs one calm blank margin or legend column.
### Hierarchy
Use Sora for concise metric labels and section headings, Source Sans 3 for explanatory business copy, and mono numerals for deltas, timestamps, thresholds, and chart axes.
### Signature Patterns
- Three-lane color token model: UI blues and slates, semantic status hues, and chart scales are shown as visibly separate CSS namespaces in legends.
- Status rail cards combine a 3px left border, geometric icon chip, uppercase state label, and microcopy remediation line for non-color redundancy.
- Chart legends use paired swatch plus pattern glyphs: solid square, dotted circle, striped tile, dashed line, and triangle marker classes.
- Forecast and uncertainty regions are rendered as dashed violet outlines with translucent blue fills, distinguishing projected data from actuals without new hues.
- Tables reserve the first column for operational identity and the final column for text status badges, preventing color-only interpretation of row health.
## Layout
### Breakpoints
desktop 1200px+, tablet 768-1199px with 6 columns, mobile below 640px stacking KPI cards and tables into readable cards
### Grid
12-column desktop dashboard grid with 24px page margins, 16px gutters, and nested 4-column chart/card zones.
### Whitespace
Whitespace is functional: 24px between dashboard zones, 12px inside dense controls, extra breathing room around legends and semantic explanations.
## Guidance
### Do
- Separate UI chrome colors from semantic status colors and from chart scales in names, legends, and CSS variables.
- Pair every red, amber, green, or blue state with text, icon geometry, and border or pattern reinforcement.
- Use categorical palettes for peers, sequential ramps for magnitude, and diverging scales only when a meaningful midpoint exists.
- Keep dashboard backgrounds pale and low contrast so chart colors retain authority.
### Don't
- Do not use rainbow scales for business metrics or mix semantic red/green into categorical chart series without explicit status meaning.
- Do not place saturated violet, teal, and blue gradients behind small text or table values.
- Do not rely on color alone for alerts, row health, chart series, or selected filters.
- Do not let decorative brand color override contrast requirements for controls and focus states.
DESIGN.md
---
version: "alpha"
name: "Signal Ledger Spectrum"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#7C3AED"
background: "#F6F8FC"
border: "#D9E2EF"
error: "#B42318"
info: "#0B65C2"
muted: "#64748B"
primary: "#1D4ED8"
secondary: "#0F766E"
success: "#087443"
surface: "#FFFFFF"
text: "#172033"
warning: "#B54708"
typography:
headline-lg:
fontFamily: "Sora"
fontSize: "1.728rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.015em"
headline-md:
fontFamily: "Sora"
fontSize: "1.44rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.015em"
body-md:
fontFamily: "Source Sans 3"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.52
letterSpacing: "-0.015em"
label-md:
fontFamily: "IBM Plex Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "16px"
md: "10px"
none: "0px"
sm: "6px"
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 Ledger Spectrum
## Overview
A dashboard-first enterprise language that separates neutral product chrome, semantic operational status, and analytical chart palettes so business data reads as trustworthy evidence rather than decoration.
### Values
- Operational clarity before ornament
- Accessible status meaning with text and shape redundancy
- Calm trustworthy blues balanced by green progress and violet insight
- Data visualization scales that preserve hierarchy under dense executive dashboards
### Anti-Values
- Color-only alerts or KPI states without labels, icons, patterns, or contrast support
- Decorative gradients that compete with chart encodings or imply false precision
- Consumer-app saturation in enterprise analytics surfaces
### Visual Character
- CSS custom properties split into --ui, --semantic, and --chart namespaces, with product chrome restricted to slate, blue, and low-chroma surfaces.
- Dashboard cards use quiet white panels, 1px cool-gray borders, and a left status rail so status remains visible independent of fill color.
- Charts combine solid categorical swatches with dot, stripe, and dash marker classes so series remain distinguishable when color perception or printing fails.
- Sequential data blocks use stepped blue-to-violet lightness ramps on pale grid backgrounds rather than rainbow hues, preserving readable labels and business seriousness.
- Critical semantic states pair color with icon geometry, badge text, and border pattern: check for success, triangle for warning, octagon for error, pulse ring for live info.
## 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 | `#7C3AED` |
| background | `#F6F8FC` |
| border | `#D9E2EF` |
| error | `#B42318` |
| info | `#0B65C2` |
| muted | `#64748B` |
| primary | `#1D4ED8` |
| secondary | `#0F766E` |
| success | `#087443` |
| surface | `#FFFFFF` |
| text | `#172033` |
| warning | `#B54708` |
## Typography
- **Headline-Lg**: Sora, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Sora, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: Source Sans 3, 16px, weight 400, line-height 1.52.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
### Breakpoints
desktop 1200px+, tablet 768-1199px with 6 columns, mobile below 640px stacking KPI cards and tables into readable cards
### Grid
12-column desktop dashboard grid with 24px page margins, 16px gutters, and nested 4-column chart/card zones.
### Whitespace
Whitespace is functional: 24px between dashboard zones, 12px inside dense controls, extra breathing room around legends and semantic explanations.
## Elevation & Depth
### Shadows
- **Lg**: 0 24px 60px rgba(23,32,51,0.14)
- **Md**: 0 10px 24px rgba(23,32,51,0.10)
- **Sm**: 0 1px 2px rgba(23,32,51,0.06)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `16px`
- **Md**: `10px`
- **None**: `0px`
- **Sm**: `6px`
### Surfaces
- **Bg Pattern**: linear grid using rgba(29,78,216,.055) at 32px intervals plus sparse violet insight glows
- **Card Style**: flat cards with 1px cool border, subtle top highlight, and semantic left rail when stateful
- **Treatment**: matte white dashboard panels over a cool blue-gray canvas with faint analytical grid lines
### Borders
- **Accent Width**: 3px
- **Character**: precision enterprise borders; color accents indicate role but never replace labels
- **Default Width**: 1px
- **Style**: solid with optional dashed forecast and dotted secondary-series variants
## Components
### Composition
Lead with a command dashboard: KPI row, status queue, analytical chart, and operational table in a 12-column grid. Keep controls in a narrow filter rail or top command strip.
### Density
Medium-high density with 16px gutters, compact table rows, and strong grouping; every dense region needs one calm blank margin or legend column.
### Hierarchy
Use Sora for concise metric labels and section headings, Source Sans 3 for explanatory business copy, and mono numerals for deltas, timestamps, thresholds, and chart axes.
### Signature Patterns
- Three-lane color token model: UI blues and slates, semantic status hues, and chart scales are shown as visibly separate CSS namespaces in legends.
- Status rail cards combine a 3px left border, geometric icon chip, uppercase state label, and microcopy remediation line for non-color redundancy.
- Chart legends use paired swatch plus pattern glyphs: solid square, dotted circle, striped tile, dashed line, and triangle marker classes.
- Forecast and uncertainty regions are rendered as dashed violet outlines with translucent blue fills, distinguishing projected data from actuals without new hues.
- Tables reserve the first column for operational identity and the final column for text status badges, preventing color-only interpretation of row health.
## 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-019ea9a3-d725-7ca2-a244-3df470fb362e/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 Separate UI chrome colors from semantic status colors and from chart scales in names, legends, and CSS variables.
- Do Pair every red, amber, green, or blue state with text, icon geometry, and border or pattern reinforcement.
- Do Use categorical palettes for peers, sequential ramps for magnitude, and diverging scales only when a meaningful midpoint exists.
- Do Keep dashboard backgrounds pale and low contrast so chart colors retain authority.
- Don't Do not use rainbow scales for business metrics or mix semantic red/green into categorical chart series without explicit status meaning.
- Don't Do not place saturated violet, teal, and blue gradients behind small text or table values.
- Don't Do not rely on color alone for alerts, row health, chart series, or selected filters.
- Don't Do not let decorative brand color override contrast requirements for controls and focus states.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "signal-ledger-spectrum",
"type": "registry:theme",
"title": "Signal Ledger Spectrum shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F6F8FC",
"foreground": "#172033",
"card": "#FFFFFF",
"card-foreground": "#172033",
"popover": "#FFFFFF",
"popover-foreground": "#172033",
"primary": "#1D4ED8",
"primary-foreground": "#ffffff",
"secondary": "#0F766E",
"secondary-foreground": "#ffffff",
"muted": "#64748B",
"muted-foreground": "#172033",
"accent": "#7C3AED",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#D9E2EF",
"input": "#D9E2EF",
"ring": "#7C3AED",
"chart-1": "#1D4ED8",
"chart-2": "#0F766E",
"chart-3": "#7C3AED",
"chart-4": "#087443",
"chart-5": "#B54708",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#172033",
"sidebar-primary": "#1D4ED8",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#0B65C2",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#D9E2EF",
"sidebar-ring": "#7C3AED",
"radius": "10px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#1D4ED8",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#7C3AED",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#303642",
"input": "#303642",
"ring": "#7C3AED",
"chart-1": "#1D4ED8",
"chart-2": "#0F766E",
"chart-3": "#7C3AED",
"chart-4": "#087443",
"chart-5": "#B54708",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#1D4ED8",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#7C3AED",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#7C3AED",
"radius": "10px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019ea9a3-d725-7ca2-a244-3df470fb362e",
"slug": "signal-ledger-spectrum",
"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"
],
"palette_roles": [
"charts",
"semantic",
"ui"
],
"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: #F6F8FC;
--foreground: #172033;
--card: #FFFFFF;
--card-foreground: #172033;
--popover: #FFFFFF;
--popover-foreground: #172033;
--primary: #1D4ED8;
--primary-foreground: #ffffff;
--secondary: #0F766E;
--secondary-foreground: #ffffff;
--muted: #64748B;
--muted-foreground: #172033;
--accent: #7C3AED;
--accent-foreground: #ffffff;
--destructive: #B42318;
--border: #D9E2EF;
--input: #D9E2EF;
--ring: #7C3AED;
--chart-1: #1D4ED8;
--chart-2: #0F766E;
--chart-3: #7C3AED;
--chart-4: #087443;
--chart-5: #B54708;
--sidebar: #FFFFFF;
--sidebar-foreground: #172033;
--sidebar-primary: #1D4ED8;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #0B65C2;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #D9E2EF;
--sidebar-ring: #7C3AED;
--radius: 10px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #1D4ED8;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #7C3AED;
--accent-foreground: #ffffff;
--destructive: #B42318;
--border: #303642;
--input: #303642;
--ring: #7C3AED;
--chart-1: #1D4ED8;
--chart-2: #0F766E;
--chart-3: #7C3AED;
--chart-4: #087443;
--chart-5: #B54708;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #1D4ED8;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #7C3AED;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #7C3AED;
--radius: 10px;
}
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 SignalLedgerSpectrumShadcnKit() {
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 Ledger Spectrum</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-ledger-spectrum",
"type": "registry:theme",
"title": "Signal Ledger Spectrum shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F6F8FC",
"foreground": "#172033",
"card": "#FFFFFF",
"card-foreground": "#172033",
"popover": "#FFFFFF",
"popover-foreground": "#172033",
"primary": "#1D4ED8",
"primary-foreground": "#ffffff",
"secondary": "#0F766E",
"secondary-foreground": "#ffffff",
"muted": "#64748B",
"muted-foreground": "#172033",
"accent": "#7C3AED",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#D9E2EF",
"input": "#D9E2EF",
"ring": "#7C3AED",
"chart-1": "#1D4ED8",
"chart-2": "#0F766E",
"chart-3": "#7C3AED",
"chart-4": "#087443",
"chart-5": "#B54708",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#172033",
"sidebar-primary": "#1D4ED8",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#0B65C2",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#D9E2EF",
"sidebar-ring": "#7C3AED",
"radius": "10px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#1D4ED8",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#7C3AED",
"accent-foreground": "#ffffff",
"destructive": "#B42318",
"border": "#303642",
"input": "#303642",
"ring": "#7C3AED",
"chart-1": "#1D4ED8",
"chart-2": "#0F766E",
"chart-3": "#7C3AED",
"chart-4": "#087443",
"chart-5": "#B54708",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#1D4ED8",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#7C3AED",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#7C3AED",
"radius": "10px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019ea9a3-d725-7ca2-a244-3df470fb362e",
"slug": "signal-ledger-spectrum",
"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"
],
"palette_roles": [
"charts",
"semantic",
"ui"
],
"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 Ledger Spectrum shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019ea9a3-d725-7ca2-a244-3df470fb362e`
Slug: `signal-ledger-spectrum`
## Intent
A dashboard-first enterprise language that separates neutral product chrome, semantic operational status, and analytical chart palettes so business data reads as trustworthy evidence rather than decoration.
## 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": "#7C3AED",
"background": "#F6F8FC",
"border": "#D9E2EF",
"error": "#B42318",
"info": "#0B65C2",
"muted": "#64748B",
"primary": "#1D4ED8",
"secondary": "#0F766E",
"success": "#087443",
"surface": "#FFFFFF",
"text": "#172033",
"warning": "#B54708"
}
Typography:
{
"base_size": "16px",
"body_font": "Source Sans 3",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Sora:wght@500;600;700&family=Source+Sans+3:wght@400;500;600;700&family=IBM+Plex+Mono:wght@500;600&display=swap",
"heading_font": "Sora",
"letter_spacing": "-0.015em",
"line_height": 1.52,
"mono_font": "IBM Plex Mono",
"scale_ratio": 1.2
}
## Visual character to preserve
- CSS custom properties split into --ui, --semantic, and --chart namespaces, with product chrome restricted to slate, blue, and low-chroma surfaces.
- Dashboard cards use quiet white panels, 1px cool-gray borders, and a left status rail so status remains visible independent of fill color.
- Charts combine solid categorical swatches with dot, stripe, and dash marker classes so series remain distinguishable when color perception or printing fails.
- Sequential data blocks use stepped blue-to-violet lightness ramps on pale grid backgrounds rather than rainbow hues, preserving readable labels and business seriousness.
- Critical semantic states pair color with icon geometry, badge text, and border pattern: check for success, triangle for warning, octagon for error, pulse ring for live info.
## ShadSync visual profile
{
"family": "system",
"material": "flat",
"contour": "default",
"border": "dashed",
"underlay": false,
"grain": false,
"stickerBadges": true,
"motion": "still",
"density": "balanced",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
}
## Signature component recipes
### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.
### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.
### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.
### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.
### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.
## Preview shots
- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.
## Implementation contract
- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/signal-ledger-spectrum/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: Separate UI chrome colors from semantic status colors and from chart scales in names, legends, and CSS variables.; Pair every red, amber, green, or blue state with text, icon geometry, and border or pattern reinforcement.; Use categorical palettes for peers, sequential ramps for magnitude, and diverging scales only when a meaningful midpoint exists.; Keep dashboard backgrounds pale and low contrast so chart colors retain authority.
- Do not: Do not use rainbow scales for business metrics or mix semantic red/green into categorical chart series without explicit status meaning.; Do not place saturated violet, teal, and blue gradients behind small text or table values.; Do not rely on color alone for alerts, row health, chart series, or selected filters.; Do not let decorative brand color override contrast requirements for controls and focus states.
## 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 SignalLedgerSpectrumShadcnKit() {
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 Ledger Spectrum</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 1200px+, tablet 768-1199px with 6 columns, mobile below 640px stacking KPI cards and tables into readable cards",
"grid": "12-column desktop dashboard grid with 24px page margins, 16px gutters, and nested 4-column chart/card zones.",
"whitespace": "Whitespace is functional: 24px between dashboard zones, 12px inside dense controls, extra breathing room around legends and semantic explanations."
}
{
"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-019ea9a3-d725-7ca2-a244-3df470fb362e",
"name": "Signal Ledger Spectrum",
"slug": "signal-ledger-spectrum"
},
"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": [
"CSS custom properties split into --ui, --semantic, and --chart namespaces, with product chrome restricted to slate, blue, and low-chroma surfaces.",
"Dashboard cards use quiet white panels, 1px cool-gray borders, and a left status rail so status remains visible independent of fill color.",
"Charts combine solid categorical swatches with dot, stripe, and dash marker classes so series remain distinguishable when color perception or printing fails.",
"Sequential data blocks use stepped blue-to-violet lightness ramps on pale grid backgrounds rather than rainbow hues, preserving readable labels and business seriousness.",
"Critical semantic states pair color with icon geometry, badge text, and border pattern: check for success, triangle for warning, octagon for error, pulse ring for live info."
],
"visualProfile": {
"family": "system",
"material": "flat",
"contour": "default",
"border": "dashed",
"underlay": false,
"grain": false,
"stickerBadges": true,
"motion": "still",
"density": "balanced",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "Signal Ledger Spectrum 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": [
"Separate UI chrome colors from semantic status colors and from chart scales in names, legends, and CSS variables.",
"Pair every red, amber, green, or blue state with text, icon geometry, and border or pattern reinforcement.",
"Use categorical palettes for peers, sequential ramps for magnitude, and diverging scales only when a meaningful midpoint exists.",
"Keep dashboard backgrounds pale and low contrast so chart colors retain authority."
],
"dont": [
"Do not use rainbow scales for business metrics or mix semantic red/green into categorical chart series without explicit status meaning.",
"Do not place saturated violet, teal, and blue gradients behind small text or table values.",
"Do not rely on color alone for alerts, row health, chart series, or selected filters.",
"Do not let decorative brand color override contrast requirements for controls and focus states."
]
}
}