back to gallery
design language·prism-notation-product-ui

Prism Notation Product UI

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.

the spec

specification

philosophy
summary
A premium white product interface where color behaves like optical notation: three restrained spectral accents mark intent, intervention, and proof across an otherwise calm surface. The language is clean and Apple-like, but its identity comes from precise color-theory decisions embedded in controls, charts, selection states, and content hierarchy rather than from decorative rainbow treatment.
values
product-first white spacestructural color theoryoptical precisionquiet premium materialstate clarity without dashboard clutter
anti-values
×rainbow palettes or color used only to prove colorfulness×square grids, repeated dotted notebooks, and decorative card side rails×generic admin dashboards or component catalog scenes
tokens
borders4 items
accent width
2px
character
Hairline warm-neutral borders by default; accent borders appear as full focus rings or aperture outlines, never as left rails.
default width
1px
style
solid
colors12 items
accent
#C7F044
background
#FBFAF7
border
#E4E0D8
error
#D83B2D
info
#2764D8
muted
#6E7480
primary
#1E5BFF
secondary
#FF5A3D
success
#2E9F68
surface
#FFFFFF
text
#101318
warning
#B98000
motion3 items
duration
180ms
easing
cubic-bezier(0.2, 0.8, 0.2, 1)
philosophy
Controls brighten and lift by 2px while color rings expand subtly, expressing optical calibration instead of generic fading.
radii5 items
full
9999px
lg
30px
md
18px
none
0
sm
10px
shadows3 items
lg
0 36px 90px rgba(16, 19, 24, 0.10), 0 10px 32px rgba(255, 90, 61, 0.10)
md
0 18px 50px rgba(30, 91, 255, 0.08), 0 6px 18px rgba(16, 19, 24, 0.05)
sm
0 1px 2px rgba(16, 19, 24, 0.05)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
Plain warm white ambient field with rare oversized radial prism washes behind the primary work area; no square grids and no dotted notebook texture.
card style
White or ivory rounded plates, 1px warm neutral borders, selective inset spectral glows on active states, and no sideline accents.
treatment
Warm white optical plates with translucent radial color washes clipped inside rounded rectangles, never full-background patterning.
typography8 items
base size
16px
body font
Inter
google fonts url
https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,500;9..144,650&family=IBM+Plex+Mono:wght@500;600&family=Inter:wght@400;500;600;700&display=swap
heading font
Fraunces
letter spacing
-0.018em
line height
1.5
mono font
IBM Plex Mono
scale ratio
1.24
rules
composition
Anchor the screen around one dominant product work surface, then orbit supporting details in compact optical plates with large white gaps between unrelated groups.
density

Medium-low density with tight internal component grouping and very large inter-section whitespace so the product feels calm rather than administrative.

hierarchy

Use Fraunces for major decisions and measured numeric emphasis, Inter for product operations, and IBM Plex Mono for spectral codes, swatches, and state stamps.

signature patterns
Spectral notation pills appear above headings, selected tabs, and status rows; each pill uses a full rounded fill and matching focus ring to establish meaning.Prism aperture cards use radial-gradient underlays clipped to the card interior, revealing color behind charts and controls only where product attention is required.Color states map consistently: blue means intent or primary action, vermilion means human intervention, and citron means confirmed proof or successful measurement.Interactive components use full perimeter optical rings on focus and selection, avoiding side rails while making the accent structurally visible.
layout
breakpoints

Desktop 1200px uses three zones, tablet stacks evidence under the work surface at 768px, mobile becomes a single column with sticky action tray.

grid

Asymmetric product canvas: wide narrative rail plus a dominant optical work surface and compact evidence column; never use square grid backgrounds.

whitespace

Use 12px for internal label grouping, 24px inside cards, 48px between product regions, and 72px around the main stage when space allows.

guidance
do
  • Use only the three spectral accents for structural meaning and let white/neutral surfaces carry most of the interface.
  • Make every accent appear as a pill, ring, filled state, chart aperture, or data mark with an explicit product meaning.
  • Keep backgrounds clean and premium; use radial light washes only behind the primary work or active component clusters.
  • Use specific product scenes such as color calibration, creative review, instrumentation, or image QA where color is meaningful.
avoid
  • Do not create rainbow navigation, arbitrary confetti, startup blobs, neon cyberpunk glow, or textbook color-wheel decoration.
  • Do not use square grids, repeated dotted notebook texture, or decorative side-rail/stripe accents on cards, buttons, rows, or panels.
  • Do not turn the language into a generic SaaS dashboard; content must include product-specific measurements, states, and decisions.
  • Do not introduce additional accent hues unless they are semantic error/success/warning/info states required for accessibility.
katagami spec
# Prism Notation Product UI

## Philosophy

A premium white product interface where color behaves like optical notation: three restrained spectral accents mark intent, intervention, and proof across an otherwise calm surface. The language is clean and Apple-like, but its identity comes from precise color-theory decisions embedded in controls, charts, selection states, and content hierarchy rather than from decorative rainbow treatment.

### Values

- product-first white space
- structural color theory
- optical precision
- quiet premium material
- state clarity without dashboard clutter

### Anti-Values

- rainbow palettes or color used only to prove colorfulness
- square grids, repeated dotted notebooks, and decorative card side rails
- generic admin dashboards or component catalog scenes

### Visual Character

- Use a warm white page with slightly off-white glass cards, 1px neutral borders, and generous 40px to 72px spatial gaps instead of patterned backgrounds.
- Place three spectral colors as compact rounded notation pills, focus rings, selected fills, and chart apertures so color creates hierarchy rather than trim.
- Create large hero and work surfaces from layered radial light washes behind content, clipped to soft rounded rectangles with no square grid texture.
- Use a dual typographic voice: editorial serif numerals/headlines paired with precise sans interface labels for a product-lab feeling.
- Treat important panels as optical plates with translucent color halos, hairline borders, and measured shadows that lift only on interaction.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Hairline warm-neutral borders by default; accent borders appear as full focus rings or aperture outlines, never as left rails.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#C7F044` |
| background | `#FBFAF7` |
| border | `#E4E0D8` |
| error | `#D83B2D` |
| info | `#2764D8` |
| muted | `#6E7480` |
| primary | `#1E5BFF` |
| secondary | `#FF5A3D` |
| success | `#2E9F68` |
| surface | `#FFFFFF` |
| text | `#101318` |
| warning | `#B98000` |

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1)
- **Philosophy**: Controls brighten and lift by 2px while color rings expand subtly, expressing optical calibration instead of generic fading.

### Radii

- **Full**: 9999px
- **Lg**: 30px
- **Md**: 18px
- **None**: 0
- **Sm**: 10px

### Shadows

- **Lg**: 0 36px 90px rgba(16, 19, 24, 0.10), 0 10px 32px rgba(255, 90, 61, 0.10)
- **Md**: 0 18px 50px rgba(30, 91, 255, 0.08), 0 6px 18px rgba(16, 19, 24, 0.05)
- **Sm**: 0 1px 2px rgba(16, 19, 24, 0.05)

### Spacing

- **Base**: 8px
- **Scale**: [4,8,12,16,24,32,48,64]

### Surfaces

- **Bg Pattern**: Plain warm white ambient field with rare oversized radial prism washes behind the primary work area; no square grids and no dotted notebook texture.
- **Card Style**: White or ivory rounded plates, 1px warm neutral borders, selective inset spectral glows on active states, and no sideline accents.
- **Treatment**: Warm white optical plates with translucent radial color washes clipped inside rounded rectangles, never full-background patterning.

### Typography

- **Base Size**: 16px
- **Body Font**: Inter
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,500;9..144,650&family=IBM+Plex+Mono:wght@500;600&family=Inter:wght@400;500;600;700&display=swap
- **Heading Font**: Fraunces
- **Letter Spacing**: -0.018em
- **Line Height**: 1.5
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.24

## Rules

### Composition

Anchor the screen around one dominant product work surface, then orbit supporting details in compact optical plates with large white gaps between unrelated groups.

### Density

Medium-low density with tight internal component grouping and very large inter-section whitespace so the product feels calm rather than administrative.

### Hierarchy

Use Fraunces for major decisions and measured numeric emphasis, Inter for product operations, and IBM Plex Mono for spectral codes, swatches, and state stamps.

### Signature Patterns

- Spectral notation pills appear above headings, selected tabs, and status rows; each pill uses a full rounded fill and matching focus ring to establish meaning.
- Prism aperture cards use radial-gradient underlays clipped to the card interior, revealing color behind charts and controls only where product attention is required.
- Color states map consistently: blue means intent or primary action, vermilion means human intervention, and citron means confirmed proof or successful measurement.
- Interactive components use full perimeter optical rings on focus and selection, avoiding side rails while making the accent structurally visible.

## Layout

### Breakpoints

Desktop 1200px uses three zones, tablet stacks evidence under the work surface at 768px, mobile becomes a single column with sticky action tray.

### Grid

Asymmetric product canvas: wide narrative rail plus a dominant optical work surface and compact evidence column; never use square grid backgrounds.

### Whitespace

Use 12px for internal label grouping, 24px inside cards, 48px between product regions, and 72px around the main stage when space allows.

## Guidance

### Do

- Use only the three spectral accents for structural meaning and let white/neutral surfaces carry most of the interface.
- Make every accent appear as a pill, ring, filled state, chart aperture, or data mark with an explicit product meaning.
- Keep backgrounds clean and premium; use radial light washes only behind the primary work or active component clusters.
- Use specific product scenes such as color calibration, creative review, instrumentation, or image QA where color is meaningful.

### Don't

- Do not create rainbow navigation, arbitrary confetti, startup blobs, neon cyberpunk glow, or textbook color-wheel decoration.
- Do not use square grids, repeated dotted notebook texture, or decorative side-rail/stripe accents on cards, buttons, rows, or panels.
- Do not turn the language into a generic SaaS dashboard; content must include product-specific measurements, states, and decisions.
- Do not introduce additional accent hues unless they are semantic error/success/warning/info states required for accessibility.
DESIGN.md
---
version: "alpha"
name: "Prism Notation Product UI"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#C7F044"
  background: "#FBFAF7"
  border: "#E4E0D8"
  error: "#D83B2D"
  info: "#2764D8"
  muted: "#6E7480"
  primary: "#1E5BFF"
  secondary: "#FF5A3D"
  success: "#2E9F68"
  surface: "#FFFFFF"
  text: "#101318"
  warning: "#B98000"
typography:
  headline-lg:
    fontFamily: "Fraunces"
    fontSize: "1.907rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.018em"
  headline-md:
    fontFamily: "Fraunces"
    fontSize: "1.538rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.018em"
  body-md:
    fontFamily: "Inter"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "-0.018em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "30px"
  md: "18px"
  none: "0px"
  sm: "10px"
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"
---

# Prism Notation Product UI

## Overview

A premium white product interface where color behaves like optical notation: three restrained spectral accents mark intent, intervention, and proof across an otherwise calm surface. The language is clean and Apple-like, but its identity comes from precise color-theory decisions embedded in controls, charts, selection states, and content hierarchy rather than from decorative rainbow treatment.

### Values

- product-first white space
- structural color theory
- optical precision
- quiet premium material
- state clarity without dashboard clutter

### Anti-Values

- rainbow palettes or color used only to prove colorfulness
- square grids, repeated dotted notebooks, and decorative card side rails
- generic admin dashboards or component catalog scenes

### Visual Character

- Use a warm white page with slightly off-white glass cards, 1px neutral borders, and generous 40px to 72px spatial gaps instead of patterned backgrounds.
- Place three spectral colors as compact rounded notation pills, focus rings, selected fills, and chart apertures so color creates hierarchy rather than trim.
- Create large hero and work surfaces from layered radial light washes behind content, clipped to soft rounded rectangles with no square grid texture.
- Use a dual typographic voice: editorial serif numerals/headlines paired with precise sans interface labels for a product-lab feeling.
- Treat important panels as optical plates with translucent color halos, hairline borders, and measured shadows that lift only on interaction.

## 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 | `#C7F044` |
| background | `#FBFAF7` |
| border | `#E4E0D8` |
| error | `#D83B2D` |
| info | `#2764D8` |
| muted | `#6E7480` |
| primary | `#1E5BFF` |
| secondary | `#FF5A3D` |
| success | `#2E9F68` |
| surface | `#FFFFFF` |
| text | `#101318` |
| warning | `#B98000` |

## Typography

- **Headline-Lg**: Fraunces, 1.907rem, weight 700, line-height 1.1.
- **Headline-Md**: Fraunces, 1.538rem, weight 600, line-height 1.15.
- **Body-Md**: Inter, 16px, weight 400, line-height 1.5.
- **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 uses three zones, tablet stacks evidence under the work surface at 768px, mobile becomes a single column with sticky action tray.

### Grid

Asymmetric product canvas: wide narrative rail plus a dominant optical work surface and compact evidence column; never use square grid backgrounds.

### Whitespace

Use 12px for internal label grouping, 24px inside cards, 48px between product regions, and 72px around the main stage when space allows.

## Elevation & Depth

### Shadows

- **Lg**: 0 36px 90px rgba(16, 19, 24, 0.10), 0 10px 32px rgba(255, 90, 61, 0.10)
- **Md**: 0 18px 50px rgba(30, 91, 255, 0.08), 0 6px 18px rgba(16, 19, 24, 0.05)
- **Sm**: 0 1px 2px rgba(16, 19, 24, 0.05)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `30px`
- **Md**: `18px`
- **None**: `0px`
- **Sm**: `10px`

### Surfaces

- **Bg Pattern**: Plain warm white ambient field with rare oversized radial prism washes behind the primary work area; no square grids and no dotted notebook texture.
- **Card Style**: White or ivory rounded plates, 1px warm neutral borders, selective inset spectral glows on active states, and no sideline accents.
- **Treatment**: Warm white optical plates with translucent radial color washes clipped inside rounded rectangles, never full-background patterning.

### Borders

- **Accent Width**: 2px
- **Character**: Hairline warm-neutral borders by default; accent borders appear as full focus rings or aperture outlines, never as left rails.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Anchor the screen around one dominant product work surface, then orbit supporting details in compact optical plates with large white gaps between unrelated groups.

### Density

Medium-low density with tight internal component grouping and very large inter-section whitespace so the product feels calm rather than administrative.

### Hierarchy

Use Fraunces for major decisions and measured numeric emphasis, Inter for product operations, and IBM Plex Mono for spectral codes, swatches, and state stamps.

### Signature Patterns

- Spectral notation pills appear above headings, selected tabs, and status rows; each pill uses a full rounded fill and matching focus ring to establish meaning.
- Prism aperture cards use radial-gradient underlays clipped to the card interior, revealing color behind charts and controls only where product attention is required.
- Color states map consistently: blue means intent or primary action, vermilion means human intervention, and citron means confirmed proof or successful measurement.
- Interactive components use full perimeter optical rings on focus and selection, avoiding side rails while making the accent structurally visible.

## 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-019e464b-e3ce-77c1-9322-9381d413c423/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 only the three spectral accents for structural meaning and let white/neutral surfaces carry most of the interface.
- Do Make every accent appear as a pill, ring, filled state, chart aperture, or data mark with an explicit product meaning.
- Do Keep backgrounds clean and premium; use radial light washes only behind the primary work or active component clusters.
- Do Use specific product scenes such as color calibration, creative review, instrumentation, or image QA where color is meaningful.
- Don't Do not create rainbow navigation, arbitrary confetti, startup blobs, neon cyberpunk glow, or textbook color-wheel decoration.
- Don't Do not use square grids, repeated dotted notebook texture, or decorative side-rail/stripe accents on cards, buttons, rows, or panels.
- Don't Do not turn the language into a generic SaaS dashboard; content must include product-specific measurements, states, and decisions.
- Don't Do not introduce additional accent hues unless they are semantic error/success/warning/info states required for accessibility.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "prism-notation-product-ui",
  "type": "registry:theme",
  "title": "Prism Notation Product UI shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FBFAF7",
      "foreground": "#101318",
      "card": "#FFFFFF",
      "card-foreground": "#101318",
      "popover": "#FFFFFF",
      "popover-foreground": "#101318",
      "primary": "#1E5BFF",
      "primary-foreground": "#ffffff",
      "secondary": "#FF5A3D",
      "secondary-foreground": "#ffffff",
      "muted": "#6E7480",
      "muted-foreground": "#101318",
      "accent": "#C7F044",
      "accent-foreground": "#111111",
      "destructive": "#D83B2D",
      "border": "#E4E0D8",
      "input": "#E4E0D8",
      "ring": "#C7F044",
      "chart-1": "#1E5BFF",
      "chart-2": "#FF5A3D",
      "chart-3": "#C7F044",
      "chart-4": "#2E9F68",
      "chart-5": "#B98000",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#101318",
      "sidebar-primary": "#1E5BFF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#2764D8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#E4E0D8",
      "sidebar-ring": "#C7F044",
      "radius": "18px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1E5BFF",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#C7F044",
      "accent-foreground": "#111111",
      "destructive": "#D83B2D",
      "border": "#303642",
      "input": "#303642",
      "ring": "#C7F044",
      "chart-1": "#1E5BFF",
      "chart-2": "#FF5A3D",
      "chart-3": "#C7F044",
      "chart-4": "#2E9F68",
      "chart-5": "#B98000",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1E5BFF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#C7F044",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#C7F044",
      "radius": "18px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e464b-e3ce-77c1-9322-9381d413c423",
    "slug": "prism-notation-product-ui",
    "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"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · prism-notation-product-ui
DESIGN.md

at a glance

Palette

Typography

headline-lgFraunces · 31px · 700

The quick brown fox jumps

headline-mdFraunces · 25px · 600

The quick brown fox jumps

body-mdInter · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

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

full9999px
lg30px
md18px
none0px
sm10px
shadcn/ui

implementation kit

needs agent-authored kitcompatibility fallback
shadcn compatibility only
The generated theme variables are available, but the polished shadcn component recipes and shots have not been authored by the Katagami agent yet.
fallbackprimitives render
Compatibility proof
Local shadcn-style primitives accept the generated theme variables.
primaryaccentsurfacemutedwarningerror
table rhythm
buttonok
cardok
inputok
recommendedcompatibility fallback

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
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #FBFAF7;
  --foreground: #101318;
  --card: #FFFFFF;
  --card-foreground: #101318;
  --popover: #FFFFFF;
  --popover-foreground: #101318;
  --primary: #1E5BFF;
  --primary-foreground: #ffffff;
  --secondary: #FF5A3D;
  --secondary-foreground: #ffffff;
  --muted: #6E7480;
  --muted-foreground: #101318;
  --accent: #C7F044;
  --accent-foreground: #111111;
  --destructive: #D83B2D;
  --border: #E4E0D8;
  --input: #E4E0D8;
  --ring: #C7F044;
  --chart-1: #1E5BFF;
  --chart-2: #FF5A3D;
  --chart-3: #C7F044;
  --chart-4: #2E9F68;
  --chart-5: #B98000;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #101318;
  --sidebar-primary: #1E5BFF;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #2764D8;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #E4E0D8;
  --sidebar-ring: #C7F044;
  --radius: 18px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #1E5BFF;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #C7F044;
  --accent-foreground: #111111;
  --destructive: #D83B2D;
  --border: #303642;
  --input: #303642;
  --ring: #C7F044;
  --chart-1: #1E5BFF;
  --chart-2: #FF5A3D;
  --chart-3: #C7F044;
  --chart-4: #2E9F68;
  --chart-5: #B98000;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #1E5BFF;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #C7F044;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #C7F044;
  --radius: 18px;
}
tsx starter
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 PrismNotationProductUiShadcnKit() {
  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 Notation Product UI</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>
  );
}
theme JSONstored + verified
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "cssVars": {
    "dark": {
      "accent": "#C7F044",
      "accent-foreground": "#111111",
      "background": "#0f1115",
      "border": "#303642",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "chart-1": "#1E5BFF",
      "chart-2": "#FF5A3D",
      "chart-3": "#C7F044",
      "chart-4": "#2E9F68",
      "chart-5": "#B98000",
      "destructive": "#D83B2D",
      "foreground": "#f8fafc",
      "input": "#303642",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1E5BFF",
      "primary-foreground": "#ffffff",
      "radius": "18px",
      "ring": "#C7F044",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "sidebar": "#181b22",
      "sidebar-accent": "#C7F044",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1E5BFF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#C7F044"
    },
    "light": {
      "accent": "#C7F044",
      "accent-foreground": "#111111",
      "background": "#FBFAF7",
      "border": "#E4E0D8",
      "card": "#FFFFFF",
      "card-foreground": "#101318",
      "chart-1": "#1E5BFF",
      "chart-2": "#FF5A3D",
      "chart-3": "#C7F044",
      "chart-4": "#2E9F68",
      "chart-5": "#B98000",
      "destructive": "#D83B2D",
      "foreground": "#101318",
      "input": "#E4E0D8",
      "muted": "#6E7480",
      "muted-foreground": "#101318",
      "popover": "#FFFFFF",
      "popover-foreground": "#101318",
      "primary": "#1E5BFF",
      "primary-foreground": "#ffffff",
      "radius": "18px",
      "ring": "#C7F044",
      "secondary": "#FF5A3D",
      "secondary-foreground": "#ffffff",
      "sidebar": "#FFFFFF",
      "sidebar-accent": "#2764D8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#E4E0D8",
      "sidebar-foreground": "#101318",
      "sidebar-primary": "#1E5BFF",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#C7F044"
    },
    "theme": {}
  },
  "meta": {
    "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",
    "languageId": "en-019e464b-e3ce-77c1-9322-9381d413c423",
    "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"
      ]
    },
    "slug": "prism-notation-product-ui",
    "source": "katagami"
  },
  "name": "prism-notation-product-ui",
  "title": "Prism Notation Product UI shadcn Theme",
  "type": "registry:theme"
}
component recipescompatibility fallback
# Prism Notation Product UI shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e464b-e3ce-77c1-9322-9381d413c423`
Slug: `prism-notation-product-ui`

## Intent

A premium white product interface where color behaves like optical notation: three restrained spectral accents mark intent, intervention, and proof across an otherwise calm surface. The language is clean and Apple-like, but its identity comes from precise color-theory decisions embedded in controls, charts, selection states, and content hierarchy rather than from decorative rainbow treatment.

## 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": "#C7F044",
  "background": "#FBFAF7",
  "border": "#E4E0D8",
  "error": "#D83B2D",
  "info": "#2764D8",
  "muted": "#6E7480",
  "primary": "#1E5BFF",
  "secondary": "#FF5A3D",
  "success": "#2E9F68",
  "surface": "#FFFFFF",
  "text": "#101318",
  "warning": "#B98000"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Inter",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,500;9..144,650&family=IBM+Plex+Mono:wght@500;600&family=Inter:wght@400;500;600;700&display=swap",
  "heading_font": "Fraunces",
  "letter_spacing": "-0.018em",
  "line_height": 1.5,
  "mono_font": "IBM Plex Mono",
  "scale_ratio": 1.24
}

## Visual character to preserve

- Use a warm white page with slightly off-white glass cards, 1px neutral borders, and generous 40px to 72px spatial gaps instead of patterned backgrounds.
- Place three spectral colors as compact rounded notation pills, focus rings, selected fills, and chart apertures so color creates hierarchy rather than trim.
- Create large hero and work surfaces from layered radial light washes behind content, clipped to soft rounded rectangles with no square grid texture.
- Use a dual typographic voice: editorial serif numerals/headlines paired with precise sans interface labels for a product-lab feeling.
- Treat important panels as optical plates with translucent color halos, hairline borders, and measured shadows that lift only on interaction.

## ShadSync visual profile

{
  "family": "editorial",
  "material": "flat",
  "contour": "pebble",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "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-notation-product-ui/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 only the three spectral accents for structural meaning and let white/neutral surfaces carry most of the interface.; Make every accent appear as a pill, ring, filled state, chart aperture, or data mark with an explicit product meaning.; Keep backgrounds clean and premium; use radial light washes only behind the primary work or active component clusters.; Use specific product scenes such as color calibration, creative review, instrumentation, or image QA where color is meaningful.
- Do not: Do not create rainbow navigation, arbitrary confetti, startup blobs, neon cyberpunk glow, or textbook color-wheel decoration.; Do not use square grids, repeated dotted notebook texture, or decorative side-rail/stripe accents on cards, buttons, rows, or panels.; Do not turn the language into a generic SaaS dashboard; content must include product-specific measurements, states, and decisions.; Do not introduce additional accent hues unless they are semantic error/success/warning/info states required for accessibility.

## 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 PrismNotationProductUiShadcnKit() {
  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 Notation Product UI</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 uses three zones, tablet stacks evidence under the work surface at 768px, mobile becomes a single column with sticky action tray.",
  "grid": "Asymmetric product canvas: wide narrative rail plus a dominant optical work surface and compact evidence column; never use square grid backgrounds.",
  "whitespace": "Use 12px for internal label grouping, 24px inside cards, 48px between product regions, and 72px around the main stage when space allows."
}
preview shotscompatibility fallback
{
  "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-019e464b-e3ce-77c1-9322-9381d413c423",
    "name": "Prism Notation Product UI",
    "slug": "prism-notation-product-ui"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "Use a warm white page with slightly off-white glass cards, 1px neutral borders, and generous 40px to 72px spatial gaps instead of patterned backgrounds.",
    "Place three spectral colors as compact rounded notation pills, focus rings, selected fills, and chart apertures so color creates hierarchy rather than trim.",
    "Create large hero and work surfaces from layered radial light washes behind content, clipped to soft rounded rectangles with no square grid texture.",
    "Use a dual typographic voice: editorial serif numerals/headlines paired with precise sans interface labels for a product-lab feeling.",
    "Treat important panels as optical plates with translucent color halos, hairline borders, and measured shadows that lift only on interaction."
  ],
  "visualProfile": {
    "family": "editorial",
    "material": "flat",
    "contour": "pebble",
    "border": "solid",
    "underlay": true,
    "grain": true,
    "stickerBadges": false,
    "motion": "lift",
    "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 Notation Product UI 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 only the three spectral accents for structural meaning and let white/neutral surfaces carry most of the interface.",
      "Make every accent appear as a pill, ring, filled state, chart aperture, or data mark with an explicit product meaning.",
      "Keep backgrounds clean and premium; use radial light washes only behind the primary work or active component clusters.",
      "Use specific product scenes such as color calibration, creative review, instrumentation, or image QA where color is meaningful."
    ],
    "dont": [
      "Do not create rainbow navigation, arbitrary confetti, startup blobs, neon cyberpunk glow, or textbook color-wheel decoration.",
      "Do not use square grids, repeated dotted notebook texture, or decorative side-rail/stripe accents on cards, buttons, rows, or panels.",
      "Do not turn the language into a generic SaaS dashboard; content must include product-specific measurements, states, and decisions.",
      "Do not introduce additional accent hues unless they are semantic error/success/warning/info states required for accessibility."
    ]
  }
}
related

More like this