back to gallery
design language·signal-porcelain-pixel

Signal Porcelain Pixel

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
Signal Porcelain Pixel is a premium white product interface language where color behaves like authored evidence: small, bright, meaningful pixel-signals organize priority, state, and next action without turning the product into a retro game skin.
values
White porcelain calm as the default material so dense product work stays readable and premium.Bright accent color assigned to semantic channels rather than applied as garnish.Minimal pixel influence expressed through tiny edge chips, quantized icons, and state marks only.Clear editorial hierarchy for real product workflows instead of generic dashboard decoration.
anti-values
×No square grid wallpaper, no dotted texture by default, and no retro arcade or block-game theming.×No rainbow palette, decorative confetti, neon cyberpunk glow, or colored side rails on cards and rows.×No arbitrary mixed roundness; geometry must read as one disciplined product system.
tokens
borders4 items
accent width
2px
character
Cool-gray porcelain hairlines; accent borders appear as short corner ticks or focus steps, never long decorative stripes.
default width
1px
style
solid
colors12 items
accent
#D7FF42
background
#FCFCFA
border
#DDE1E8
error
#E33D5F
info
#16A3D8
muted
#6D7280
primary
#2447F2
secondary
#F5F1E8
success
#0E9F6E
surface
#FFFFFF
text
#15161A
warning
#F59E0B
motion3 items
duration
160ms
easing
cubic-bezier(0.2, 0.8, 0.2, 1)
philosophy
Motion is restrained product confirmation: controls lift by 1px, pixel chips snap into place, and focus steps appear instantly enough to feel precise.
radii5 items
full
9999px
lg
14px
md
10px
none
0
sm
6px
shadows3 items
lg
0 26px 70px rgba(21,22,26,0.10), 0 0 0 1px rgba(221,225,232,0.92)
md
0 12px 34px rgba(21,22,26,0.07), 0 0 0 1px rgba(221,225,232,0.86)
sm
0 1px 2px rgba(21,22,26,0.04), 0 0 0 1px rgba(221,225,232,0.72)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
No square grid and no default dotted texture; use plain neutral background with occasional isolated 2x2 pixel constellations only when they label a state.
card style
Cards are radius-14 rectangles with a clipped 10px corner notch option and small semantic pixel chips inside the card header, never as side rails.
treatment
Porcelain white planes over a warm chalk background, separated by crisp cool-gray hairlines and very soft ambient shadow.
typography8 items
base size
16px
body font
Schibsted Grotesk
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Schibsted+Grotesk:wght@400;500;600;700;800&display=swap
heading font
Schibsted Grotesk
letter spacing
-0.018em
line height
1.52
mono font
IBM Plex Mono
scale ratio
1.22
rules
composition
Compose screens as calm product workbenches: a narrow context rail, a generous central document or decision surface, and a compact inspector that appears only when it adds workflow value.
density

Balanced professional density with tight controls inside spacious porcelain sections; lists may be compact but each decision surface needs breathing room.

hierarchy
Use large confident headings, small mono state labels, and semantic color chips to reveal what matters; never let accent color compete with primary reading order.
signature patterns
Porcelain cards may use a CSS clipped-corner mask at one corner plus a 2px semantic tick placed inside the corner as a meaningful state marker.Four-square pixel glyphs built from tiny CSS blocks identify state categories such as proof, risk, ready, and blocked without becoming decorative wallpaper.Interactive focus uses a stair-step underline made from box-shadow offsets and accent color, replacing generic blue glows with an authored pixel rhythm.Selected content receives small rectangular highlight fragments behind key words, using citron for action and ultramarine for navigation meaning.Data rows group by quiet whitespace and hairlines, with no colored side rails; state appears as compact in-cell chips and quantized badges.
layout
breakpoints

mobile 375px, tablet 768px, desktop 1200px, wide 1440px

grid

Desktop uses a 12-column shell with a 76px tool rail, central 7-column canvas, and 4-column inspector; tablet collapses to stacked inspector cards.

whitespace

Preserve large outer margins and 24px section gaps; dense forms use 12px internal rhythm so the white surface remains intentional rather than empty.

guidance
do
  • Use one bright primary blue for navigation and one citron action accent for the most authored moment on the screen.
  • Let pixel art appear as tiny semantic glyphs, clipped corners, focus steps, and micro-illustrations that support the product task.
  • Keep product scenes specific: editors, approvals, release notes, evidence review, and operational decision surfaces.
  • Maintain WCAG AA contrast by pairing citron with dark text or using it as a background chip rather than tiny text.
avoid
  • Do not use square-grid backgrounds, repeated dotted notebook textures, colored side rails, or rainbow highlight systems.
  • Do not make buttons, cards, or rows look like arcade tiles, Minecraft blocks, or retro game HUD elements.
  • Do not decorate empty space with confetti; every bright mark must communicate state, grouping, priority, or action.
  • Do not mix arbitrary radii, heavy shadows, glossy gradients, or browser-default form styling.
katagami spec
# Signal Porcelain Pixel

## Philosophy

Signal Porcelain Pixel is a premium white product interface language where color behaves like authored evidence: small, bright, meaningful pixel-signals organize priority, state, and next action without turning the product into a retro game skin.

### Values

- White porcelain calm as the default material so dense product work stays readable and premium.
- Bright accent color assigned to semantic channels rather than applied as garnish.
- Minimal pixel influence expressed through tiny edge chips, quantized icons, and state marks only.
- Clear editorial hierarchy for real product workflows instead of generic dashboard decoration.

### Anti-Values

- No square grid wallpaper, no dotted texture by default, and no retro arcade or block-game theming.
- No rainbow palette, decorative confetti, neon cyberpunk glow, or colored side rails on cards and rows.
- No arbitrary mixed roundness; geometry must read as one disciplined product system.

### Visual Character

- Use white and warm-neutral full-page surfaces with isolated porcelain cards, 1px cool-gray borders, and a single committed 14px radius family.
- Place semantic color as 6px to 14px quantized pixel chips, corner ticks, icon cells, and selected-word highlights rather than wide rails or stripes.
- Build hierarchy with Schibsted Grotesk headings, measured body text, compact uppercase metadata, and generous whitespace around dense controls.
- Create pixel influence through CSS step motifs: clipped corner masks, four-square status glyphs, and stair-stepped focus underlines on interactive elements.
- Keep shadows nearly invisible and material porcelain-like: soft ambient elevation, crisp border contrast, and no glossy gradients or heavy neon glow.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Cool-gray porcelain hairlines; accent borders appear as short corner ticks or focus steps, never long decorative stripes.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#D7FF42` |
| background | `#FCFCFA` |
| border | `#DDE1E8` |
| error | `#E33D5F` |
| info | `#16A3D8` |
| muted | `#6D7280` |
| primary | `#2447F2` |
| secondary | `#F5F1E8` |
| success | `#0E9F6E` |
| surface | `#FFFFFF` |
| text | `#15161A` |
| warning | `#F59E0B` |

### Motion

- **Duration**: 160ms
- **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1)
- **Philosophy**: Motion is restrained product confirmation: controls lift by 1px, pixel chips snap into place, and focus steps appear instantly enough to feel precise.

### Radii

- **Full**: 9999px
- **Lg**: 14px
- **Md**: 10px
- **None**: 0
- **Sm**: 6px

### Shadows

- **Lg**: 0 26px 70px rgba(21,22,26,0.10), 0 0 0 1px rgba(221,225,232,0.92)
- **Md**: 0 12px 34px rgba(21,22,26,0.07), 0 0 0 1px rgba(221,225,232,0.86)
- **Sm**: 0 1px 2px rgba(21,22,26,0.04), 0 0 0 1px rgba(221,225,232,0.72)

### Spacing

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

### Surfaces

- **Bg Pattern**: No square grid and no default dotted texture; use plain neutral background with occasional isolated 2x2 pixel constellations only when they label a state.
- **Card Style**: Cards are radius-14 rectangles with a clipped 10px corner notch option and small semantic pixel chips inside the card header, never as side rails.
- **Treatment**: Porcelain white planes over a warm chalk background, separated by crisp cool-gray hairlines and very soft ambient shadow.

### Typography

- **Base Size**: 16px
- **Body Font**: Schibsted Grotesk
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Schibsted+Grotesk:wght@400;500;600;700;800&display=swap
- **Heading Font**: Schibsted Grotesk
- **Letter Spacing**: -0.018em
- **Line Height**: 1.52
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.22

## Rules

### Composition

Compose screens as calm product workbenches: a narrow context rail, a generous central document or decision surface, and a compact inspector that appears only when it adds workflow value.

### Density

Balanced professional density with tight controls inside spacious porcelain sections; lists may be compact but each decision surface needs breathing room.

### Hierarchy

Use large confident headings, small mono state labels, and semantic color chips to reveal what matters; never let accent color compete with primary reading order.

### Signature Patterns

- Porcelain cards may use a CSS clipped-corner mask at one corner plus a 2px semantic tick placed inside the corner as a meaningful state marker.
- Four-square pixel glyphs built from tiny CSS blocks identify state categories such as proof, risk, ready, and blocked without becoming decorative wallpaper.
- Interactive focus uses a stair-step underline made from box-shadow offsets and accent color, replacing generic blue glows with an authored pixel rhythm.
- Selected content receives small rectangular highlight fragments behind key words, using citron for action and ultramarine for navigation meaning.
- Data rows group by quiet whitespace and hairlines, with no colored side rails; state appears as compact in-cell chips and quantized badges.

## Layout

### Breakpoints

mobile 375px, tablet 768px, desktop 1200px, wide 1440px

### Grid

Desktop uses a 12-column shell with a 76px tool rail, central 7-column canvas, and 4-column inspector; tablet collapses to stacked inspector cards.

### Whitespace

Preserve large outer margins and 24px section gaps; dense forms use 12px internal rhythm so the white surface remains intentional rather than empty.

## Guidance

### Do

- Use one bright primary blue for navigation and one citron action accent for the most authored moment on the screen.
- Let pixel art appear as tiny semantic glyphs, clipped corners, focus steps, and micro-illustrations that support the product task.
- Keep product scenes specific: editors, approvals, release notes, evidence review, and operational decision surfaces.
- Maintain WCAG AA contrast by pairing citron with dark text or using it as a background chip rather than tiny text.

### Don't

- Do not use square-grid backgrounds, repeated dotted notebook textures, colored side rails, or rainbow highlight systems.
- Do not make buttons, cards, or rows look like arcade tiles, Minecraft blocks, or retro game HUD elements.
- Do not decorate empty space with confetti; every bright mark must communicate state, grouping, priority, or action.
- Do not mix arbitrary radii, heavy shadows, glossy gradients, or browser-default form styling.
DESIGN.md
---
version: "alpha"
name: "Signal Porcelain Pixel"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#D7FF42"
  background: "#FCFCFA"
  border: "#DDE1E8"
  error: "#E33D5F"
  info: "#16A3D8"
  muted: "#6D7280"
  primary: "#2447F2"
  secondary: "#F5F1E8"
  success: "#0E9F6E"
  surface: "#FFFFFF"
  text: "#15161A"
  warning: "#F59E0B"
typography:
  headline-lg:
    fontFamily: "Schibsted Grotesk"
    fontSize: "1.816rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.018em"
  headline-md:
    fontFamily: "Schibsted Grotesk"
    fontSize: "1.488rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.018em"
  body-md:
    fontFamily: "Schibsted Grotesk"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.52
    letterSpacing: "-0.018em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "14px"
  md: "10px"
  none: "0px"
  sm: "6px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#ffffff"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  card-surface:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  input-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    height: "44px"
---

# Signal Porcelain Pixel

## Overview

Signal Porcelain Pixel is a premium white product interface language where color behaves like authored evidence: small, bright, meaningful pixel-signals organize priority, state, and next action without turning the product into a retro game skin.

### Values

- White porcelain calm as the default material so dense product work stays readable and premium.
- Bright accent color assigned to semantic channels rather than applied as garnish.
- Minimal pixel influence expressed through tiny edge chips, quantized icons, and state marks only.
- Clear editorial hierarchy for real product workflows instead of generic dashboard decoration.

### Anti-Values

- No square grid wallpaper, no dotted texture by default, and no retro arcade or block-game theming.
- No rainbow palette, decorative confetti, neon cyberpunk glow, or colored side rails on cards and rows.
- No arbitrary mixed roundness; geometry must read as one disciplined product system.

### Visual Character

- Use white and warm-neutral full-page surfaces with isolated porcelain cards, 1px cool-gray borders, and a single committed 14px radius family.
- Place semantic color as 6px to 14px quantized pixel chips, corner ticks, icon cells, and selected-word highlights rather than wide rails or stripes.
- Build hierarchy with Schibsted Grotesk headings, measured body text, compact uppercase metadata, and generous whitespace around dense controls.
- Create pixel influence through CSS step motifs: clipped corner masks, four-square status glyphs, and stair-stepped focus underlines on interactive elements.
- Keep shadows nearly invisible and material porcelain-like: soft ambient elevation, crisp border contrast, and no glossy gradients or heavy neon glow.

## 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 | `#D7FF42` |
| background | `#FCFCFA` |
| border | `#DDE1E8` |
| error | `#E33D5F` |
| info | `#16A3D8` |
| muted | `#6D7280` |
| primary | `#2447F2` |
| secondary | `#F5F1E8` |
| success | `#0E9F6E` |
| surface | `#FFFFFF` |
| text | `#15161A` |
| warning | `#F59E0B` |

## Typography

- **Headline-Lg**: Schibsted Grotesk, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Schibsted Grotesk, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Schibsted Grotesk, 16px, weight 400, line-height 1.52.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`

### Breakpoints

mobile 375px, tablet 768px, desktop 1200px, wide 1440px

### Grid

Desktop uses a 12-column shell with a 76px tool rail, central 7-column canvas, and 4-column inspector; tablet collapses to stacked inspector cards.

### Whitespace

Preserve large outer margins and 24px section gaps; dense forms use 12px internal rhythm so the white surface remains intentional rather than empty.

## Elevation & Depth

### Shadows

- **Lg**: 0 26px 70px rgba(21,22,26,0.10), 0 0 0 1px rgba(221,225,232,0.92)
- **Md**: 0 12px 34px rgba(21,22,26,0.07), 0 0 0 1px rgba(221,225,232,0.86)
- **Sm**: 0 1px 2px rgba(21,22,26,0.04), 0 0 0 1px rgba(221,225,232,0.72)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `14px`
- **Md**: `10px`
- **None**: `0px`
- **Sm**: `6px`

### Surfaces

- **Bg Pattern**: No square grid and no default dotted texture; use plain neutral background with occasional isolated 2x2 pixel constellations only when they label a state.
- **Card Style**: Cards are radius-14 rectangles with a clipped 10px corner notch option and small semantic pixel chips inside the card header, never as side rails.
- **Treatment**: Porcelain white planes over a warm chalk background, separated by crisp cool-gray hairlines and very soft ambient shadow.

### Borders

- **Accent Width**: 2px
- **Character**: Cool-gray porcelain hairlines; accent borders appear as short corner ticks or focus steps, never long decorative stripes.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Compose screens as calm product workbenches: a narrow context rail, a generous central document or decision surface, and a compact inspector that appears only when it adds workflow value.

### Density

Balanced professional density with tight controls inside spacious porcelain sections; lists may be compact but each decision surface needs breathing room.

### Hierarchy

Use large confident headings, small mono state labels, and semantic color chips to reveal what matters; never let accent color compete with primary reading order.

### Signature Patterns

- Porcelain cards may use a CSS clipped-corner mask at one corner plus a 2px semantic tick placed inside the corner as a meaningful state marker.
- Four-square pixel glyphs built from tiny CSS blocks identify state categories such as proof, risk, ready, and blocked without becoming decorative wallpaper.
- Interactive focus uses a stair-step underline made from box-shadow offsets and accent color, replacing generic blue glows with an authored pixel rhythm.
- Selected content receives small rectangular highlight fragments behind key words, using citron for action and ultramarine for navigation meaning.
- Data rows group by quiet whitespace and hairlines, with no colored side rails; state appears as compact in-cell chips and quantized badges.

## 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-019e4683-fba8-7193-aa4d-14ac1095fa64/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 one bright primary blue for navigation and one citron action accent for the most authored moment on the screen.
- Do Let pixel art appear as tiny semantic glyphs, clipped corners, focus steps, and micro-illustrations that support the product task.
- Do Keep product scenes specific: editors, approvals, release notes, evidence review, and operational decision surfaces.
- Do Maintain WCAG AA contrast by pairing citron with dark text or using it as a background chip rather than tiny text.
- Don't Do not use square-grid backgrounds, repeated dotted notebook textures, colored side rails, or rainbow highlight systems.
- Don't Do not make buttons, cards, or rows look like arcade tiles, Minecraft blocks, or retro game HUD elements.
- Don't Do not decorate empty space with confetti; every bright mark must communicate state, grouping, priority, or action.
- Don't Do not mix arbitrary radii, heavy shadows, glossy gradients, or browser-default form styling.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "signal-porcelain-pixel",
  "type": "registry:theme",
  "title": "Signal Porcelain Pixel shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FCFCFA",
      "foreground": "#15161A",
      "card": "#FFFFFF",
      "card-foreground": "#15161A",
      "popover": "#FFFFFF",
      "popover-foreground": "#15161A",
      "primary": "#2447F2",
      "primary-foreground": "#ffffff",
      "secondary": "#F5F1E8",
      "secondary-foreground": "#111111",
      "muted": "#6D7280",
      "muted-foreground": "#15161A",
      "accent": "#D7FF42",
      "accent-foreground": "#111111",
      "destructive": "#E33D5F",
      "border": "#DDE1E8",
      "input": "#DDE1E8",
      "ring": "#D7FF42",
      "chart-1": "#2447F2",
      "chart-2": "#F5F1E8",
      "chart-3": "#D7FF42",
      "chart-4": "#0E9F6E",
      "chart-5": "#F59E0B",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#15161A",
      "sidebar-primary": "#2447F2",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#16A3D8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#DDE1E8",
      "sidebar-ring": "#D7FF42",
      "radius": "10px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2447F2",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#D7FF42",
      "accent-foreground": "#111111",
      "destructive": "#E33D5F",
      "border": "#303642",
      "input": "#303642",
      "ring": "#D7FF42",
      "chart-1": "#2447F2",
      "chart-2": "#F5F1E8",
      "chart-3": "#D7FF42",
      "chart-4": "#0E9F6E",
      "chart-5": "#F59E0B",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2447F2",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#D7FF42",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#D7FF42",
      "radius": "10px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e4683-fba8-7193-aa4d-14ac1095fa64",
    "slug": "signal-porcelain-pixel",
    "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 · signal-porcelain-pixel
DESIGN.md

at a glance

Palette

Typography

headline-lgSchibsted Grotesk · 29px · 700

The quick brown fox jumps

headline-mdSchibsted Grotesk · 24px · 600

The quick brown fox jumps

body-mdSchibsted Grotesk · 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
lg14px
md10px
none0px
sm6px
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: #FCFCFA;
  --foreground: #15161A;
  --card: #FFFFFF;
  --card-foreground: #15161A;
  --popover: #FFFFFF;
  --popover-foreground: #15161A;
  --primary: #2447F2;
  --primary-foreground: #ffffff;
  --secondary: #F5F1E8;
  --secondary-foreground: #111111;
  --muted: #6D7280;
  --muted-foreground: #15161A;
  --accent: #D7FF42;
  --accent-foreground: #111111;
  --destructive: #E33D5F;
  --border: #DDE1E8;
  --input: #DDE1E8;
  --ring: #D7FF42;
  --chart-1: #2447F2;
  --chart-2: #F5F1E8;
  --chart-3: #D7FF42;
  --chart-4: #0E9F6E;
  --chart-5: #F59E0B;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #15161A;
  --sidebar-primary: #2447F2;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #16A3D8;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #DDE1E8;
  --sidebar-ring: #D7FF42;
  --radius: 10px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #2447F2;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #D7FF42;
  --accent-foreground: #111111;
  --destructive: #E33D5F;
  --border: #303642;
  --input: #303642;
  --ring: #D7FF42;
  --chart-1: #2447F2;
  --chart-2: #F5F1E8;
  --chart-3: #D7FF42;
  --chart-4: #0E9F6E;
  --chart-5: #F59E0B;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #2447F2;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #D7FF42;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #D7FF42;
  --radius: 10px;
}
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 SignalPorcelainPixelShadcnKit() {
  return (
    <section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
      <div className="flex items-start justify-between gap-4">
        <div>
          <Badge variant="outline">shadcn/ui</Badge>
          <h2 className="mt-3 text-2xl font-semibold tracking-tight">Signal Porcelain Pixel</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": "#D7FF42",
      "accent-foreground": "#111111",
      "background": "#0f1115",
      "border": "#303642",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "chart-1": "#2447F2",
      "chart-2": "#F5F1E8",
      "chart-3": "#D7FF42",
      "chart-4": "#0E9F6E",
      "chart-5": "#F59E0B",
      "destructive": "#E33D5F",
      "foreground": "#f8fafc",
      "input": "#303642",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2447F2",
      "primary-foreground": "#ffffff",
      "radius": "10px",
      "ring": "#D7FF42",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "sidebar": "#181b22",
      "sidebar-accent": "#D7FF42",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2447F2",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#D7FF42"
    },
    "light": {
      "accent": "#D7FF42",
      "accent-foreground": "#111111",
      "background": "#FCFCFA",
      "border": "#DDE1E8",
      "card": "#FFFFFF",
      "card-foreground": "#15161A",
      "chart-1": "#2447F2",
      "chart-2": "#F5F1E8",
      "chart-3": "#D7FF42",
      "chart-4": "#0E9F6E",
      "chart-5": "#F59E0B",
      "destructive": "#E33D5F",
      "foreground": "#15161A",
      "input": "#DDE1E8",
      "muted": "#6D7280",
      "muted-foreground": "#15161A",
      "popover": "#FFFFFF",
      "popover-foreground": "#15161A",
      "primary": "#2447F2",
      "primary-foreground": "#ffffff",
      "radius": "10px",
      "ring": "#D7FF42",
      "secondary": "#F5F1E8",
      "secondary-foreground": "#111111",
      "sidebar": "#FFFFFF",
      "sidebar-accent": "#16A3D8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#DDE1E8",
      "sidebar-foreground": "#15161A",
      "sidebar-primary": "#2447F2",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#D7FF42"
    },
    "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-019e4683-fba8-7193-aa4d-14ac1095fa64",
    "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": "signal-porcelain-pixel",
    "source": "katagami"
  },
  "name": "signal-porcelain-pixel",
  "title": "Signal Porcelain Pixel shadcn Theme",
  "type": "registry:theme"
}
component recipescompatibility fallback
# Signal Porcelain Pixel shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4683-fba8-7193-aa4d-14ac1095fa64`
Slug: `signal-porcelain-pixel`

## Intent

Signal Porcelain Pixel is a premium white product interface language where color behaves like authored evidence: small, bright, meaningful pixel-signals organize priority, state, and next action without turning the product into a retro game skin.

## Required primitives

- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Install with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

## Token cues

Colors:

{
  "accent": "#D7FF42",
  "background": "#FCFCFA",
  "border": "#DDE1E8",
  "error": "#E33D5F",
  "info": "#16A3D8",
  "muted": "#6D7280",
  "primary": "#2447F2",
  "secondary": "#F5F1E8",
  "success": "#0E9F6E",
  "surface": "#FFFFFF",
  "text": "#15161A",
  "warning": "#F59E0B"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Schibsted Grotesk",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Schibsted+Grotesk:wght@400;500;600;700;800&display=swap",
  "heading_font": "Schibsted Grotesk",
  "letter_spacing": "-0.018em",
  "line_height": 1.52,
  "mono_font": "IBM Plex Mono",
  "scale_ratio": 1.22
}

## Visual character to preserve

- Use white and warm-neutral full-page surfaces with isolated porcelain cards, 1px cool-gray borders, and a single committed 14px radius family.
- Place semantic color as 6px to 14px quantized pixel chips, corner ticks, icon cells, and selected-word highlights rather than wide rails or stripes.
- Build hierarchy with Schibsted Grotesk headings, measured body text, compact uppercase metadata, and generous whitespace around dense controls.
- Create pixel influence through CSS step motifs: clipped corner masks, four-square status glyphs, and stair-stepped focus underlines on interactive elements.
- Keep shadows nearly invisible and material porcelain-like: soft ambient elevation, crisp border contrast, and no glossy gradients or heavy neon glow.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "stickerBadges": true,
  "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/signal-porcelain-pixel/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 one bright primary blue for navigation and one citron action accent for the most authored moment on the screen.; Let pixel art appear as tiny semantic glyphs, clipped corners, focus steps, and micro-illustrations that support the product task.; Keep product scenes specific: editors, approvals, release notes, evidence review, and operational decision surfaces.; Maintain WCAG AA contrast by pairing citron with dark text or using it as a background chip rather than tiny text.
- Do not: Do not use square-grid backgrounds, repeated dotted notebook textures, colored side rails, or rainbow highlight systems.; Do not make buttons, cards, or rows look like arcade tiles, Minecraft blocks, or retro game HUD elements.; Do not decorate empty space with confetti; every bright mark must communicate state, grouping, priority, or action.; Do not mix arbitrary radii, heavy shadows, glossy gradients, or browser-default form styling.

## 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 SignalPorcelainPixelShadcnKit() {
  return (
    <section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
      <div className="flex items-start justify-between gap-4">
        <div>
          <Badge variant="outline">shadcn/ui</Badge>
          <h2 className="mt-3 text-2xl font-semibold tracking-tight">Signal Porcelain Pixel</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 375px, tablet 768px, desktop 1200px, wide 1440px",
  "grid": "Desktop uses a 12-column shell with a 76px tool rail, central 7-column canvas, and 4-column inspector; tablet collapses to stacked inspector cards.",
  "whitespace": "Preserve large outer margins and 24px section gaps; dense forms use 12px internal rhythm so the white surface remains intentional rather than empty."
}
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-019e4683-fba8-7193-aa4d-14ac1095fa64",
    "name": "Signal Porcelain Pixel",
    "slug": "signal-porcelain-pixel"
  },
  "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 white and warm-neutral full-page surfaces with isolated porcelain cards, 1px cool-gray borders, and a single committed 14px radius family.",
    "Place semantic color as 6px to 14px quantized pixel chips, corner ticks, icon cells, and selected-word highlights rather than wide rails or stripes.",
    "Build hierarchy with Schibsted Grotesk headings, measured body text, compact uppercase metadata, and generous whitespace around dense controls.",
    "Create pixel influence through CSS step motifs: clipped corner masks, four-square status glyphs, and stair-stepped focus underlines on interactive elements.",
    "Keep shadows nearly invisible and material porcelain-like: soft ambient elevation, crisp border contrast, and no glossy gradients or heavy neon glow."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": true,
    "stickerBadges": true,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Signal Porcelain Pixel 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 one bright primary blue for navigation and one citron action accent for the most authored moment on the screen.",
      "Let pixel art appear as tiny semantic glyphs, clipped corners, focus steps, and micro-illustrations that support the product task.",
      "Keep product scenes specific: editors, approvals, release notes, evidence review, and operational decision surfaces.",
      "Maintain WCAG AA contrast by pairing citron with dark text or using it as a background chip rather than tiny text."
    ],
    "dont": [
      "Do not use square-grid backgrounds, repeated dotted notebook textures, colored side rails, or rainbow highlight systems.",
      "Do not make buttons, cards, or rows look like arcade tiles, Minecraft blocks, or retro game HUD elements.",
      "Do not decorate empty space with confetti; every bright mark must communicate state, grouping, priority, or action.",
      "Do not mix arbitrary radii, heavy shadows, glossy gradients, or browser-default form styling."
    ]
  }
}
related

More like this