Prism Ledger Minimal
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
- near-invisible ink alpha borders for structure, with green or blue rails used only for role-specific interaction states
- default width
- 1px
- style
- solid
colors12 items
motion3 items
- duration
- 180ms
- easing
- cubic-bezier(0.2, 0, 0, 1)
- philosophy
- short functional motion: rails slide 4px, focus halos fade in, and panels lift minimally without playful bounce
radii5 items
- full
- 9999px
- lg
- 24px
- md
- 16px
- none
- 0
- sm
- 0
shadows3 items
- lg
- 0 32px 96px rgba(23,25,22,0.12)
- md
- 0 18px 48px rgba(23,25,22,0.08)
- sm
- 0 1px 0 rgba(23,25,22,0.06)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64, 80, 96
surfaces3 items
- bg pattern
- subtle 32px ledger ruling made from rgba(23,25,22,0.025) linear gradients only on wide background zones
- card style
- white rectangular sheets with 16px radius, 1px rgba ink borders, and optional 3px accent rails for selected or primary states
- treatment
- flat neutral surface ladder with no gradients; depth comes from whitespace, white sheets, and alpha borders
typography8 items
- base size
- 16px
- body font
- Hanken Grotesk
- google fonts url
- https://fonts.googleapis.com/css2?family=Fragment+Mono:ital@0;1&family=Hanken+Grotesk:wght@400;500;600;700;800&display=swap
- heading font
- Hanken Grotesk
- letter spacing
- -0.02em
- line height
- 1.55
- mono font
- Fragment Mono
- scale ratio
- 1.22
rules
Use one dominant workspace sheet, one compact decision strip, and one low-profile navigation rail. Break the grid with an oversized neutral summary band or full-width table region rather than repeating equal cards. Keep color in small role markers so the layout remains recognizable in grayscale.
Medium-high product density is allowed inside ledger tables and forms, but each dense cluster needs 48-96px separation from unrelated zones and at least one spacious neutral summary moment.
Start with large tight Hanken Grotesk display headings at -0.04em, then medium-weight section labels, then readable 16px body copy at -0.02em. Use mono captions for IDs, categories, and token-like values, not for long paragraphs. Accent rails outrank fill color for interaction hierarchy.
layout
mobile < 640px, tablet 640px-1023px, desktop >= 1024px, wide >= 1280px
Optimized for clean application screens with real controls, lists, and feedback; density comes from compact rows, not from reducing type size below 15px.
Desktop uses a 12-column grid with a 7-column workspace, 3-column decision strip, and 2-column navigation/metadata rail inside a 1280px max width. Tablet collapses to two stacked columns; mobile becomes a single column with sticky compact actions.
Preserve the rail motif at all sizes: leading rails on desktop become top rails on stacked mobile cards, while decision strips move below the workspace.
Use 4-12px gaps inside field groups and ledger rows, 24-32px inside sheets, and 64-96px between major screen regions so the spacing ratio is visibly at least 8:1.
guidance
- Use warm neutral backgrounds and white sheets before introducing any accent color.
- Reserve green for primary actions, active navigation, selected rows, and positive forward states.
- Reserve blue for links, focus rings, evidence selections, and informational feedback.
- Pair every non-semantic category color with a text label or icon so color is never the only cue.
- Use near-invisible rgba borders rather than solid gray strokes.
- Vary section weight with one dominant workspace and smaller support panels.
- Keep body text at 16px with -0.02em tracking and clear AA contrast.
- Use Fragment Mono sparingly for tokens, IDs, and tiny labels.
- Do not apply bright fills to entire pages, cards, or decorative backgrounds.
- Do not introduce a third brand accent or synthetic rainbow category system.
- Do not create three equal dashboard cards as the primary composition.
- Do not rely on shadows for hierarchy when spacing and rails can do the work.
- Do not use color-only states; selected, focus, error, and success need shape or label reinforcement.
- Do not use default form controls or unstyled browser buttons.
- Do not reduce tables below readable spacing just to show more rows.
- Do not mix arbitrary radii outside the 0/16/24/full scale.
katagami spec
# Prism Ledger Minimal ## Philosophy A restrained application design language for operational tools that need neutral calm plus unmistakable action color. It treats color as a role-based instrument: quiet surfaces do the daily work, a fresh green marks primary forward motion, and a tempered blue appears only for links, focus, and selected evidence. ### Values - Neutral surfaces carry content without decorative noise or false depth. - Accent color is assigned by role, not mood, so users learn a predictable interaction grammar. - Typography and spacing create hierarchy before borders, shadows, or saturated color appear. - Every bright hue must earn its place as an action, link, focus ring, selected state, or category marker. - Interfaces should feel fresh and current while remaining durable enough for daily product work. - Status colors stay semantic and separate from brand accents so feedback remains understandable. ### Anti-Values - Decorative gradients, synthetic rainbow palettes, and accent color used to fill empty space. - Generic SaaS card dashboards with identical three-column modules and heavy gray borders. - Low-contrast pale text, tiny body sizes, and color-only meaning for critical states. - Rounded friendly blobs that undermine the ledger-like precision of the system. ### Visual Character - Page backgrounds use a three-step neutral surface ladder: warm white canvas, lightly tinted panels, and crisp white raised sheets separated by 6 percent alpha borders. - Primary actions, active navigation, and selected rows carry a slim fresh-green left or top rail instead of flooding whole containers with bright fill. - Links, focus rings, and evidence highlights use a tempered blue outline treatment that remains distinct from the green action accent. - Dense application areas are arranged as asymmetric ledger grids with one dominant workspace column and compact right-side decision strips. - Category markers appear as tiny square swatches and uppercase mono labels, keeping non-semantic accent color restrained to small repeatable anchors. ## Tokens ### Borders - **Accent Width**: 3px - **Character**: near-invisible ink alpha borders for structure, with green or blue rails used only for role-specific interaction states - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#8BE063` | | background | `#F7F7F2` | | border | `#171916` | | error | `#B84A43` | | info | `#2F78D8` | | muted | `#687065` | | primary | `#5FB83E` | | secondary | `#2F78D8` | | success | `#3F8F55` | | surface | `#FFFFFF` | | text | `#171916` | | warning | `#A36F12` | ### Motion - **Duration**: 180ms - **Easing**: cubic-bezier(0.2, 0, 0, 1) - **Philosophy**: short functional motion: rails slide 4px, focus halos fade in, and panels lift minimally without playful bounce ### Radii - **Full**: 9999px - **Lg**: 24px - **Md**: 16px - **None**: 0 - **Sm**: 0 ### Shadows - **Lg**: 0 32px 96px rgba(23,25,22,0.12) - **Md**: 0 18px 48px rgba(23,25,22,0.08) - **Sm**: 0 1px 0 rgba(23,25,22,0.06) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64,80,96] ### Surfaces - **Bg Pattern**: subtle 32px ledger ruling made from rgba(23,25,22,0.025) linear gradients only on wide background zones - **Card Style**: white rectangular sheets with 16px radius, 1px rgba ink borders, and optional 3px accent rails for selected or primary states - **Treatment**: flat neutral surface ladder with no gradients; depth comes from whitespace, white sheets, and alpha borders ### Typography - **Base Size**: 16px - **Body Font**: Hanken Grotesk - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Fragment+Mono:ital@0;1&family=Hanken+Grotesk:wght@400;500;600;700;800&display=swap - **Heading Font**: Hanken Grotesk - **Letter Spacing**: -0.02em - **Line Height**: 1.55 - **Mono Font**: Fragment Mono - **Scale Ratio**: 1.22 ## Rules ### Composition Use one dominant workspace sheet, one compact decision strip, and one low-profile navigation rail. Break the grid with an oversized neutral summary band or full-width table region rather than repeating equal cards. Keep color in small role markers so the layout remains recognizable in grayscale. ### Density Medium-high product density is allowed inside ledger tables and forms, but each dense cluster needs 48-96px separation from unrelated zones and at least one spacious neutral summary moment. ### Hierarchy Start with large tight Hanken Grotesk display headings at -0.04em, then medium-weight section labels, then readable 16px body copy at -0.02em. Use mono captions for IDs, categories, and token-like values, not for long paragraphs. Accent rails outrank fill color for interaction hierarchy. ### Signature Patterns - Use .rail-primary and .rail-selected classes that draw 3px green inset rails on the leading edge of active rows, buttons, and navigation items without coloring the whole surface. - Use blue focus halos with outline-offset and box-shadow rings on inputs, filter pills, and evidence links so keyboard and selected evidence states have a separate color role. - Build category labels from an 8px square swatch plus uppercase Fragment Mono text, limiting non-semantic accent colors to tiny repeatable markers. - Render major surfaces on a faint ledger-rule background created with linear-gradient stripes, making the system recognizable without illustrations or decorative gradients. - Create asymmetric application grids where a wide work sheet is paired with a narrow decision strip, avoiding equal card rows and generic dashboard rhythm. ## Layout ### Breakpoints mobile < 640px, tablet 640px-1023px, desktop >= 1024px, wide >= 1280px ### Density Optimized for clean application screens with real controls, lists, and feedback; density comes from compact rows, not from reducing type size below 15px. ### Grid Desktop uses a 12-column grid with a 7-column workspace, 3-column decision strip, and 2-column navigation/metadata rail inside a 1280px max width. Tablet collapses to two stacked columns; mobile becomes a single column with sticky compact actions. ### Responsive Preserve the rail motif at all sizes: leading rails on desktop become top rails on stacked mobile cards, while decision strips move below the workspace. ### Whitespace Use 4-12px gaps inside field groups and ledger rows, 24-32px inside sheets, and 64-96px between major screen regions so the spacing ratio is visibly at least 8:1. ## Guidance ### Do - Use warm neutral backgrounds and white sheets before introducing any accent color. - Reserve green for primary actions, active navigation, selected rows, and positive forward states. - Reserve blue for links, focus rings, evidence selections, and informational feedback. - Pair every non-semantic category color with a text label or icon so color is never the only cue. - Use near-invisible rgba borders rather than solid gray strokes. - Vary section weight with one dominant workspace and smaller support panels. - Keep body text at 16px with -0.02em tracking and clear AA contrast. - Use Fragment Mono sparingly for tokens, IDs, and tiny labels. ### Don't - Do not apply bright fills to entire pages, cards, or decorative backgrounds. - Do not introduce a third brand accent or synthetic rainbow category system. - Do not create three equal dashboard cards as the primary composition. - Do not rely on shadows for hierarchy when spacing and rails can do the work. - Do not use color-only states; selected, focus, error, and success need shape or label reinforcement. - Do not use default form controls or unstyled browser buttons. - Do not reduce tables below readable spacing just to show more rows. - Do not mix arbitrary radii outside the 0/16/24/full scale. ### Accessibility All text tokens are selected for WCAG AA on their intended surfaces; focus is visible through blue outline plus offset halo; semantic colors are not reused as decorative brand accents. ### Usage Context Best for product operations, admin review tools, finance, sustainability, compliance, and internal applications that require clarity without visual coldness.
DESIGN.md
---
version: "alpha"
name: "Prism Ledger Minimal"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#8BE063"
background: "#F7F7F2"
border: "#171916"
error: "#B84A43"
info: "#2F78D8"
muted: "#687065"
primary: "#5FB83E"
secondary: "#2F78D8"
success: "#3F8F55"
surface: "#FFFFFF"
text: "#171916"
warning: "#A36F12"
typography:
headline-lg:
fontFamily: "Hanken Grotesk"
fontSize: "1.816rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.02em"
headline-md:
fontFamily: "Hanken Grotesk"
fontSize: "1.488rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.02em"
body-md:
fontFamily: "Hanken Grotesk"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.55
letterSpacing: "-0.02em"
label-md:
fontFamily: "Fragment Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "24px"
md: "16px"
none: "0px"
sm: "0px"
spacing:
base: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
step-8: "80px"
step-9: "96px"
components:
color-reference-accent:
backgroundColor: "{colors.accent}"
color-reference-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: "#000000"
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"
---
# Prism Ledger Minimal
## Overview
A restrained application design language for operational tools that need neutral calm plus unmistakable action color. It treats color as a role-based instrument: quiet surfaces do the daily work, a fresh green marks primary forward motion, and a tempered blue appears only for links, focus, and selected evidence.
### Values
- Neutral surfaces carry content without decorative noise or false depth.
- Accent color is assigned by role, not mood, so users learn a predictable interaction grammar.
- Typography and spacing create hierarchy before borders, shadows, or saturated color appear.
- Every bright hue must earn its place as an action, link, focus ring, selected state, or category marker.
- Interfaces should feel fresh and current while remaining durable enough for daily product work.
- Status colors stay semantic and separate from brand accents so feedback remains understandable.
### Anti-Values
- Decorative gradients, synthetic rainbow palettes, and accent color used to fill empty space.
- Generic SaaS card dashboards with identical three-column modules and heavy gray borders.
- Low-contrast pale text, tiny body sizes, and color-only meaning for critical states.
- Rounded friendly blobs that undermine the ledger-like precision of the system.
### Visual Character
- Page backgrounds use a three-step neutral surface ladder: warm white canvas, lightly tinted panels, and crisp white raised sheets separated by 6 percent alpha borders.
- Primary actions, active navigation, and selected rows carry a slim fresh-green left or top rail instead of flooding whole containers with bright fill.
- Links, focus rings, and evidence highlights use a tempered blue outline treatment that remains distinct from the green action accent.
- Dense application areas are arranged as asymmetric ledger grids with one dominant workspace column and compact right-side decision strips.
- Category markers appear as tiny square swatches and uppercase mono labels, keeping non-semantic accent color restrained to small repeatable anchors.
## 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 | `#8BE063` |
| background | `#F7F7F2` |
| border | `#171916` |
| error | `#B84A43` |
| info | `#2F78D8` |
| muted | `#687065` |
| primary | `#5FB83E` |
| secondary | `#2F78D8` |
| success | `#3F8F55` |
| surface | `#FFFFFF` |
| text | `#171916` |
| warning | `#A36F12` |
## Typography
- **Headline-Lg**: Hanken Grotesk, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Hanken Grotesk, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Hanken Grotesk, 16px, weight 400, line-height 1.55.
- **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`
- **Step-8**: `80px`
- **Step-9**: `96px`
### Breakpoints
mobile < 640px, tablet 640px-1023px, desktop >= 1024px, wide >= 1280px
### Density
Optimized for clean application screens with real controls, lists, and feedback; density comes from compact rows, not from reducing type size below 15px.
### Grid
Desktop uses a 12-column grid with a 7-column workspace, 3-column decision strip, and 2-column navigation/metadata rail inside a 1280px max width. Tablet collapses to two stacked columns; mobile becomes a single column with sticky compact actions.
### Responsive
Preserve the rail motif at all sizes: leading rails on desktop become top rails on stacked mobile cards, while decision strips move below the workspace.
### Whitespace
Use 4-12px gaps inside field groups and ledger rows, 24-32px inside sheets, and 64-96px between major screen regions so the spacing ratio is visibly at least 8:1.
## Elevation & Depth
### Shadows
- **Lg**: 0 32px 96px rgba(23,25,22,0.12)
- **Md**: 0 18px 48px rgba(23,25,22,0.08)
- **Sm**: 0 1px 0 rgba(23,25,22,0.06)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `24px`
- **Md**: `16px`
- **None**: `0px`
- **Sm**: `0px`
### Surfaces
- **Bg Pattern**: subtle 32px ledger ruling made from rgba(23,25,22,0.025) linear gradients only on wide background zones
- **Card Style**: white rectangular sheets with 16px radius, 1px rgba ink borders, and optional 3px accent rails for selected or primary states
- **Treatment**: flat neutral surface ladder with no gradients; depth comes from whitespace, white sheets, and alpha borders
### Borders
- **Accent Width**: 3px
- **Character**: near-invisible ink alpha borders for structure, with green or blue rails used only for role-specific interaction states
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Use one dominant workspace sheet, one compact decision strip, and one low-profile navigation rail. Break the grid with an oversized neutral summary band or full-width table region rather than repeating equal cards. Keep color in small role markers so the layout remains recognizable in grayscale.
### Density
Medium-high product density is allowed inside ledger tables and forms, but each dense cluster needs 48-96px separation from unrelated zones and at least one spacious neutral summary moment.
### Hierarchy
Start with large tight Hanken Grotesk display headings at -0.04em, then medium-weight section labels, then readable 16px body copy at -0.02em. Use mono captions for IDs, categories, and token-like values, not for long paragraphs. Accent rails outrank fill color for interaction hierarchy.
### Signature Patterns
- Use .rail-primary and .rail-selected classes that draw 3px green inset rails on the leading edge of active rows, buttons, and navigation items without coloring the whole surface.
- Use blue focus halos with outline-offset and box-shadow rings on inputs, filter pills, and evidence links so keyboard and selected evidence states have a separate color role.
- Build category labels from an 8px square swatch plus uppercase Fragment Mono text, limiting non-semantic accent colors to tiny repeatable markers.
- Render major surfaces on a faint ledger-rule background created with linear-gradient stripes, making the system recognizable without illustrations or decorative gradients.
- Create asymmetric application grids where a wide work sheet is paired with a narrow decision strip, avoiding equal card rows and generic dashboard rhythm.
## 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/prism-ledger-minimal/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 warm neutral backgrounds and white sheets before introducing any accent color.
- Do Reserve green for primary actions, active navigation, selected rows, and positive forward states.
- Do Reserve blue for links, focus rings, evidence selections, and informational feedback.
- Do Pair every non-semantic category color with a text label or icon so color is never the only cue.
- Do Use near-invisible rgba borders rather than solid gray strokes.
- Do Vary section weight with one dominant workspace and smaller support panels.
- Do Keep body text at 16px with -0.02em tracking and clear AA contrast.
- Do Use Fragment Mono sparingly for tokens, IDs, and tiny labels.
- Don't Do not apply bright fills to entire pages, cards, or decorative backgrounds.
- Don't Do not introduce a third brand accent or synthetic rainbow category system.
- Don't Do not create three equal dashboard cards as the primary composition.
- Don't Do not rely on shadows for hierarchy when spacing and rails can do the work.
- Don't Do not use color-only states; selected, focus, error, and success need shape or label reinforcement.
- Don't Do not use default form controls or unstyled browser buttons.
- Don't Do not reduce tables below readable spacing just to show more rows.
- Don't Do not mix arbitrary radii outside the 0/16/24/full scale.
### Accessibility
All text tokens are selected for WCAG AA on their intended surfaces; focus is visible through blue outline plus offset halo; semantic colors are not reused as decorative brand accents.
### Usage Context
Best for product operations, admin review tools, finance, sustainability, compliance, and internal applications that require clarity without visual coldness.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "prism-ledger-minimal",
"type": "registry:theme",
"title": "Prism Ledger Minimal shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F7F7F2",
"foreground": "#171916",
"card": "#FFFFFF",
"card-foreground": "#171916",
"popover": "#FFFFFF",
"popover-foreground": "#171916",
"primary": "#5FB83E",
"primary-foreground": "#ffffff",
"secondary": "#2F78D8",
"secondary-foreground": "#ffffff",
"muted": "#687065",
"muted-foreground": "#171916",
"accent": "#8BE063",
"accent-foreground": "#111111",
"destructive": "#B84A43",
"border": "#171916",
"input": "#171916",
"ring": "#8BE063",
"chart-1": "#5FB83E",
"chart-2": "#2F78D8",
"chart-3": "#8BE063",
"chart-4": "#3F8F55",
"chart-5": "#A36F12",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#171916",
"sidebar-primary": "#5FB83E",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#2F78D8",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#171916",
"sidebar-ring": "#8BE063",
"radius": "16px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#5FB83E",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#8BE063",
"accent-foreground": "#111111",
"destructive": "#B84A43",
"border": "#303642",
"input": "#303642",
"ring": "#8BE063",
"chart-1": "#5FB83E",
"chart-2": "#2F78D8",
"chart-3": "#8BE063",
"chart-4": "#3F8F55",
"chart-5": "#A36F12",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#5FB83E",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#8BE063",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#8BE063",
"radius": "16px"
}
},
"meta": {
"source": "katagami",
"languageId": "prism-ledger-minimal",
"slug": "prism-ledger-minimal",
"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-880px
- step-996px
Shape
implementation kit
DESIGN.md with shadcn
Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.
advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #F7F7F2;
--foreground: #171916;
--card: #FFFFFF;
--card-foreground: #171916;
--popover: #FFFFFF;
--popover-foreground: #171916;
--primary: #5FB83E;
--primary-foreground: #ffffff;
--secondary: #2F78D8;
--secondary-foreground: #ffffff;
--muted: #687065;
--muted-foreground: #171916;
--accent: #8BE063;
--accent-foreground: #111111;
--destructive: #B84A43;
--border: #171916;
--input: #171916;
--ring: #8BE063;
--chart-1: #5FB83E;
--chart-2: #2F78D8;
--chart-3: #8BE063;
--chart-4: #3F8F55;
--chart-5: #A36F12;
--sidebar: #FFFFFF;
--sidebar-foreground: #171916;
--sidebar-primary: #5FB83E;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #2F78D8;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #171916;
--sidebar-ring: #8BE063;
--radius: 16px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #5FB83E;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #8BE063;
--accent-foreground: #111111;
--destructive: #B84A43;
--border: #303642;
--input: #303642;
--ring: #8BE063;
--chart-1: #5FB83E;
--chart-2: #2F78D8;
--chart-3: #8BE063;
--chart-4: #3F8F55;
--chart-5: #A36F12;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #5FB83E;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #8BE063;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #8BE063;
--radius: 16px;
}
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 PrismLedgerMinimalShadcnKit() {
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">Prism Ledger Minimal</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": "prism-ledger-minimal",
"type": "registry:theme",
"title": "Prism Ledger Minimal shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F7F7F2",
"foreground": "#171916",
"card": "#FFFFFF",
"card-foreground": "#171916",
"popover": "#FFFFFF",
"popover-foreground": "#171916",
"primary": "#5FB83E",
"primary-foreground": "#ffffff",
"secondary": "#2F78D8",
"secondary-foreground": "#ffffff",
"muted": "#687065",
"muted-foreground": "#171916",
"accent": "#8BE063",
"accent-foreground": "#111111",
"destructive": "#B84A43",
"border": "#171916",
"input": "#171916",
"ring": "#8BE063",
"chart-1": "#5FB83E",
"chart-2": "#2F78D8",
"chart-3": "#8BE063",
"chart-4": "#3F8F55",
"chart-5": "#A36F12",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#171916",
"sidebar-primary": "#5FB83E",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#2F78D8",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#171916",
"sidebar-ring": "#8BE063",
"radius": "16px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#5FB83E",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#8BE063",
"accent-foreground": "#111111",
"destructive": "#B84A43",
"border": "#303642",
"input": "#303642",
"ring": "#8BE063",
"chart-1": "#5FB83E",
"chart-2": "#2F78D8",
"chart-3": "#8BE063",
"chart-4": "#3F8F55",
"chart-5": "#A36F12",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#5FB83E",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#8BE063",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#8BE063",
"radius": "16px"
}
},
"meta": {
"source": "katagami",
"languageId": "prism-ledger-minimal",
"slug": "prism-ledger-minimal",
"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"
]
}
}
}
# Prism Ledger Minimal shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `prism-ledger-minimal`
Slug: `prism-ledger-minimal`
## Intent
A restrained application design language for operational tools that need neutral calm plus unmistakable action color. It treats color as a role-based instrument: quiet surfaces do the daily work, a fresh green marks primary forward motion, and a tempered blue appears only for links, focus, and selected evidence.
## 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": "#8BE063",
"background": "#F7F7F2",
"border": "#171916",
"error": "#B84A43",
"info": "#2F78D8",
"muted": "#687065",
"primary": "#5FB83E",
"secondary": "#2F78D8",
"success": "#3F8F55",
"surface": "#FFFFFF",
"text": "#171916",
"warning": "#A36F12"
}
Typography:
{
"base_size": "16px",
"body_font": "Hanken Grotesk",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Fragment+Mono:ital@0;1&family=Hanken+Grotesk:wght@400;500;600;700;800&display=swap",
"heading_font": "Hanken Grotesk",
"letter_spacing": "-0.02em",
"line_height": 1.55,
"mono_font": "Fragment Mono",
"scale_ratio": 1.22
}
## Visual character to preserve
- Page backgrounds use a three-step neutral surface ladder: warm white canvas, lightly tinted panels, and crisp white raised sheets separated by 6 percent alpha borders.
- Primary actions, active navigation, and selected rows carry a slim fresh-green left or top rail instead of flooding whole containers with bright fill.
- Links, focus rings, and evidence highlights use a tempered blue outline treatment that remains distinct from the green action accent.
- Dense application areas are arranged as asymmetric ledger grids with one dominant workspace column and compact right-side decision strips.
- Category markers appear as tiny square swatches and uppercase mono labels, keeping non-semantic accent color restrained to small repeatable anchors.
## ShadSync visual profile
{
"family": "system",
"material": "flat",
"contour": "pebble",
"border": "solid",
"underlay": true,
"grain": false,
"stickerBadges": false,
"motion": "lift",
"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/prism-ledger-minimal/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 warm neutral backgrounds and white sheets before introducing any accent color.; Reserve green for primary actions, active navigation, selected rows, and positive forward states.; Reserve blue for links, focus rings, evidence selections, and informational feedback.; Pair every non-semantic category color with a text label or icon so color is never the only cue.; Use near-invisible rgba borders rather than solid gray strokes.; Vary section weight with one dominant workspace and smaller support panels.; Keep body text at 16px with -0.02em tracking and clear AA contrast.; Use Fragment Mono sparingly for tokens, IDs, and tiny labels.
- Do not: Do not apply bright fills to entire pages, cards, or decorative backgrounds.; Do not introduce a third brand accent or synthetic rainbow category system.; Do not create three equal dashboard cards as the primary composition.; Do not rely on shadows for hierarchy when spacing and rails can do the work.; Do not use color-only states; selected, focus, error, and success need shape or label reinforcement.; Do not use default form controls or unstyled browser buttons.; Do not reduce tables below readable spacing just to show more rows.; Do not mix arbitrary radii outside the 0/16/24/full scale.
## 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 PrismLedgerMinimalShadcnKit() {
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">Prism Ledger Minimal</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 640px-1023px, desktop >= 1024px, wide >= 1280px",
"density": "Optimized for clean application screens with real controls, lists, and feedback; density comes from compact rows, not from reducing type size below 15px.",
"grid": "Desktop uses a 12-column grid with a 7-column workspace, 3-column decision strip, and 2-column navigation/metadata rail inside a 1280px max width. Tablet collapses to two stacked columns; mobile becomes a single column with sticky compact actions.",
"responsive": "Preserve the rail motif at all sizes: leading rails on desktop become top rails on stacked mobile cards, while decision strips move below the workspace.",
"whitespace": "Use 4-12px gaps inside field groups and ledger rows, 24-32px inside sheets, and 64-96px between major screen regions so the spacing ratio is visibly at least 8:1."
}
{
"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": "prism-ledger-minimal",
"name": "Prism Ledger Minimal",
"slug": "prism-ledger-minimal"
},
"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": [
"Page backgrounds use a three-step neutral surface ladder: warm white canvas, lightly tinted panels, and crisp white raised sheets separated by 6 percent alpha borders.",
"Primary actions, active navigation, and selected rows carry a slim fresh-green left or top rail instead of flooding whole containers with bright fill.",
"Links, focus rings, and evidence highlights use a tempered blue outline treatment that remains distinct from the green action accent.",
"Dense application areas are arranged as asymmetric ledger grids with one dominant workspace column and compact right-side decision strips.",
"Category markers appear as tiny square swatches and uppercase mono labels, keeping non-semantic accent color restrained to small repeatable anchors."
],
"visualProfile": {
"family": "system",
"material": "flat",
"contour": "pebble",
"border": "solid",
"underlay": true,
"grain": false,
"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": "Prism Ledger Minimal 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 warm neutral backgrounds and white sheets before introducing any accent color.",
"Reserve green for primary actions, active navigation, selected rows, and positive forward states.",
"Reserve blue for links, focus rings, evidence selections, and informational feedback.",
"Pair every non-semantic category color with a text label or icon so color is never the only cue.",
"Use near-invisible rgba borders rather than solid gray strokes.",
"Vary section weight with one dominant workspace and smaller support panels.",
"Keep body text at 16px with -0.02em tracking and clear AA contrast.",
"Use Fragment Mono sparingly for tokens, IDs, and tiny labels."
],
"dont": [
"Do not apply bright fills to entire pages, cards, or decorative backgrounds.",
"Do not introduce a third brand accent or synthetic rainbow category system.",
"Do not create three equal dashboard cards as the primary composition.",
"Do not rely on shadows for hierarchy when spacing and rails can do the work.",
"Do not use color-only states; selected, focus, error, and success need shape or label reinforcement.",
"Do not use default form controls or unstyled browser buttons.",
"Do not reduce tables below readable spacing just to show more rows.",
"Do not mix arbitrary radii outside the 0/16/24/full scale."
]
}
}