back to gallery
design language·porcelain-pixel-bloom

Porcelain Pixel Bloom

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
Porcelain Pixel Bloom is a premium consumer-app language for calm white interfaces where a few luminous, color-theory accents behave like tiny cut-glass pixels: useful signals, not nostalgic game decoration.
values
Keep the product surface quiet, breathable, and unmistakably usable before any identity cue appears.Use a split-complement accent family as semantic light: citron for positive momentum, iris for active focus, and coral only for urgent warmth.Let pixel art influence edge rhythm, icons, badges, and micro-illustrations without turning screens into retro game scenery.Make every bright mark attached to a state, choice, metric, or action so color never becomes garnish.Prefer premium consumer warmth over generic SaaS dashboards through editorial copy, tactile cards, and human daily-planning content.
anti-values
×No full rainbow palette, arcade nostalgia, Minecraft block overload, neon cyberpunk glow, or square-grid wallpaper.×No decorative side rails, colored stripes on cards or rows, confetti sprinkles, or color accents detached from product meaning.×No generic analytics dashboard, default form styling, arbitrary mixed radii, or childish icon stickers.
tokens
borders4 items
accent width
2px
character
Warm taupe separators for structure; iris two-step outlines for focus; citron/coral borders only for semantic states.
default width
1px
style
solid hairline with stepped focus outlines
colors12 items
accent
#FF6B4A
background
#FAFAF7
border
#DDD8CE
error
#D83A31
info
#3478F6
muted
#76716B
primary
#6757F6
secondary
#C7F23B
success
#4C8F46
surface
#FFFFFF
text
#1D1B20
warning
#C8871B
motion3 items
duration
170ms
easing
cubic-bezier(0.22, 1, 0.36, 1)
philosophy
Motion is a tiny pixel snap followed by calm porcelain lift: focus tiles step in, cards rise 2px, and progress pixels fill discretely.
radii5 items
full
9999px
lg
20px
md
14px
none
0
sm
8px
shadows3 items
lg
0 28px 80px rgba(38,34,28,0.14)
md
0 14px 36px rgba(38,34,28,0.10)
sm
0 1px 0 rgba(29,27,32,0.08)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64, 96
surfaces3 items
bg pattern
No repeated grid or dots by default; background remains calm with isolated pixel-bloom motifs only near meaningful hero and empty-state moments.
card style
White rounded cards with taupe hairlines, shallow object shadow, and one or two 4px clipped pixel nicks on identity-bearing modules.
treatment
Clean white porcelain surfaces on a warm neutral canvas with occasional offset underplates and crisp inner highlights.
typography8 items
base size
16px
body font
Onest
google fonts url
https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,600;9..144,700&family=Onest:wght@400;500;600;700&family=Space+Mono:wght@400;700&display=swap
heading font
Fraunces
letter spacing
-0.018em
line height
1.52
mono font
Space Mono
scale ratio
1.23
rules
composition
Use a consumer app scene with a spacious editorial header, one primary action island, a tactile detail sheet, and compact supporting modules; avoid equal dashboard card grids by varying card scale, depth, and density.
density
Medium-low density with generous white space, compact metadata rows, and focused clusters of controls; detail sheets may be denser but must preserve 16px readable body text.
hierarchy
Large Fraunces headlines and Onest labels establish calm premium hierarchy; bright pixels indicate the next meaningful choice, active item, or progress state rather than decorating every surface.
signature patterns
Pixel-bloom badges combine four to nine tiny square tiles in citron, iris, and rare coral, placed beside labels or inside icon glyphs as semantic state markers.Notched porcelain cards use CSS clip-path polygons to remove a 4px corner bite while preserving a 20px radius illusion through layered underplates.Stepped focus rings render as an iris outline plus a one-pixel offset citron tile shadow, making keyboard states visible without neon glow.Quantized progress bars fill as separated 8px cells with rounded containers, bridging pixel-art rhythm and premium product feedback.Micro-illustrations are built from sparse square and rounded-rectangle CSS tiles floating in empty states, never from full-scene pixel art.
layout
breakpoints

mobile <= 640px, tablet 641px-960px, desktop >= 961px

grid
Desktop uses a 12-column max-width 1180px canvas with a 7/5 hero split and varied supporting modules; tablet becomes 6 columns and mobile stacks into one column.
whitespace

Outer whitespace ranges from 24px mobile to 72px desktop; important cards keep 24-32px internal padding while pixel details stay in 4-8px increments.

guidance
do
  • Use a mostly white and warm-neutral field, then spend citron, iris, and coral only on meaningful state, progress, selection, and confirmation.
  • Keep pixel cues small: icon corners, tile clusters, progress cells, focus offsets, and empty-state micro-illustrations.
  • Choose one committed radius geometry and pair it with tiny notches rather than mixing many arbitrary soft-card shapes.
  • Make product scenes specific to consumer rituals such as planning, collecting, styling, saving, or wellness rather than generic dashboards.
avoid
  • Do not use square-grid or dotted wallpaper, full rainbow palettes, arcade fonts, game scenery, or blocky all-over theming.
  • Do not add colored side rails, left stripes, decorative confetti, or accent marks that do not communicate state or hierarchy.
  • Do not allow material or pixel metaphors to stop at decoration; they must shape controls, focus, badges, progress, and responsive composition.
  • Do not crowd the page with identical SaaS metric cards or default browser form controls.
katagami spec
# Porcelain Pixel Bloom

## Philosophy

Porcelain Pixel Bloom is a premium consumer-app language for calm white interfaces where a few luminous, color-theory accents behave like tiny cut-glass pixels: useful signals, not nostalgic game decoration.

### Values

- Keep the product surface quiet, breathable, and unmistakably usable before any identity cue appears.
- Use a split-complement accent family as semantic light: citron for positive momentum, iris for active focus, and coral only for urgent warmth.
- Let pixel art influence edge rhythm, icons, badges, and micro-illustrations without turning screens into retro game scenery.
- Make every bright mark attached to a state, choice, metric, or action so color never becomes garnish.
- Prefer premium consumer warmth over generic SaaS dashboards through editorial copy, tactile cards, and human daily-planning content.

### Anti-Values

- No full rainbow palette, arcade nostalgia, Minecraft block overload, neon cyberpunk glow, or square-grid wallpaper.
- No decorative side rails, colored stripes on cards or rows, confetti sprinkles, or color accents detached from product meaning.
- No generic analytics dashboard, default form styling, arbitrary mixed radii, or childish icon stickers.

### Visual Character

- Use porcelain-white and warm-neutral surfaces with 1px translucent taupe hairlines, one committed 20px outer radius, and tiny clipped 4px pixel nicks on selected corners via clip-path.
- Attach bright split-complement pixels as 2x2 or 3x3 tile clusters inside buttons, icons, progress marks, and badges; never repeat them as a page background or square grid.
- Build cards with floating offset underplates in pale neutral tones and crisp inner highlights, using shadow only as a shallow product-object lift rather than soft SaaS blur.
- Compose screens with large white breathing fields, asymmetric content islands, and compact pixel-motif metadata rows that create rhythm at edges and corners.
- Use rounded editorial typography paired with precise monospace numerals so the interface feels premium and measured while micro-details remain quantized.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Warm taupe separators for structure; iris two-step outlines for focus; citron/coral borders only for semantic states.
- **Default Width**: 1px
- **Style**: solid hairline with stepped focus outlines

### Colors

| Name | Value |
|------|-------|
| accent | `#FF6B4A` |
| background | `#FAFAF7` |
| border | `#DDD8CE` |
| error | `#D83A31` |
| info | `#3478F6` |
| muted | `#76716B` |
| primary | `#6757F6` |
| secondary | `#C7F23B` |
| success | `#4C8F46` |
| surface | `#FFFFFF` |
| text | `#1D1B20` |
| warning | `#C8871B` |

### Motion

- **Duration**: 170ms
- **Easing**: cubic-bezier(0.22, 1, 0.36, 1)
- **Philosophy**: Motion is a tiny pixel snap followed by calm porcelain lift: focus tiles step in, cards rise 2px, and progress pixels fill discretely.

### Radii

- **Full**: 9999px
- **Lg**: 20px
- **Md**: 14px
- **None**: 0
- **Sm**: 8px

### Shadows

- **Lg**: 0 28px 80px rgba(38,34,28,0.14)
- **Md**: 0 14px 36px rgba(38,34,28,0.10)
- **Sm**: 0 1px 0 rgba(29,27,32,0.08)

### Spacing

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

### Surfaces

- **Bg Pattern**: No repeated grid or dots by default; background remains calm with isolated pixel-bloom motifs only near meaningful hero and empty-state moments.
- **Card Style**: White rounded cards with taupe hairlines, shallow object shadow, and one or two 4px clipped pixel nicks on identity-bearing modules.
- **Treatment**: Clean white porcelain surfaces on a warm neutral canvas with occasional offset underplates and crisp inner highlights.

### Typography

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

## Rules

### Composition

Use a consumer app scene with a spacious editorial header, one primary action island, a tactile detail sheet, and compact supporting modules; avoid equal dashboard card grids by varying card scale, depth, and density.

### Density

Medium-low density with generous white space, compact metadata rows, and focused clusters of controls; detail sheets may be denser but must preserve 16px readable body text.

### Hierarchy

Large Fraunces headlines and Onest labels establish calm premium hierarchy; bright pixels indicate the next meaningful choice, active item, or progress state rather than decorating every surface.

### Signature Patterns

- Pixel-bloom badges combine four to nine tiny square tiles in citron, iris, and rare coral, placed beside labels or inside icon glyphs as semantic state markers.
- Notched porcelain cards use CSS clip-path polygons to remove a 4px corner bite while preserving a 20px radius illusion through layered underplates.
- Stepped focus rings render as an iris outline plus a one-pixel offset citron tile shadow, making keyboard states visible without neon glow.
- Quantized progress bars fill as separated 8px cells with rounded containers, bridging pixel-art rhythm and premium product feedback.
- Micro-illustrations are built from sparse square and rounded-rectangle CSS tiles floating in empty states, never from full-scene pixel art.

## Layout

### Breakpoints

mobile <= 640px, tablet 641px-960px, desktop >= 961px

### Grid

Desktop uses a 12-column max-width 1180px canvas with a 7/5 hero split and varied supporting modules; tablet becomes 6 columns and mobile stacks into one column.

### Whitespace

Outer whitespace ranges from 24px mobile to 72px desktop; important cards keep 24-32px internal padding while pixel details stay in 4-8px increments.

## Guidance

### Do

- Use a mostly white and warm-neutral field, then spend citron, iris, and coral only on meaningful state, progress, selection, and confirmation.
- Keep pixel cues small: icon corners, tile clusters, progress cells, focus offsets, and empty-state micro-illustrations.
- Choose one committed radius geometry and pair it with tiny notches rather than mixing many arbitrary soft-card shapes.
- Make product scenes specific to consumer rituals such as planning, collecting, styling, saving, or wellness rather than generic dashboards.

### Don't

- Do not use square-grid or dotted wallpaper, full rainbow palettes, arcade fonts, game scenery, or blocky all-over theming.
- Do not add colored side rails, left stripes, decorative confetti, or accent marks that do not communicate state or hierarchy.
- Do not allow material or pixel metaphors to stop at decoration; they must shape controls, focus, badges, progress, and responsive composition.
- Do not crowd the page with identical SaaS metric cards or default browser form controls.

### Accessibility

Maintain AA contrast for all text, pair color states with labels or icons, keep focus rings visible, and never rely on tiny pixel color alone to convey critical status.

### Usage Context

Best for premium consumer apps in personal planning, wardrobe, food, savings, wellness, collecting, and lifestyle tools that need memorable identity without sacrificing calm usability.
DESIGN.md
---
version: "alpha"
name: "Porcelain Pixel Bloom"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#FF6B4A"
  background: "#FAFAF7"
  border: "#DDD8CE"
  error: "#D83A31"
  info: "#3478F6"
  muted: "#76716B"
  primary: "#6757F6"
  secondary: "#C7F23B"
  success: "#4C8F46"
  surface: "#FFFFFF"
  text: "#1D1B20"
  warning: "#C8871B"
typography:
  headline-lg:
    fontFamily: "Fraunces"
    fontSize: "1.861rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.018em"
  headline-md:
    fontFamily: "Fraunces"
    fontSize: "1.513rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.018em"
  body-md:
    fontFamily: "Onest"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.52
    letterSpacing: "-0.018em"
  label-md:
    fontFamily: "Space Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "20px"
  md: "14px"
  none: "0px"
  sm: "8px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
  step-8: "96px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#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"
---

# Porcelain Pixel Bloom

## Overview

Porcelain Pixel Bloom is a premium consumer-app language for calm white interfaces where a few luminous, color-theory accents behave like tiny cut-glass pixels: useful signals, not nostalgic game decoration.

### Values

- Keep the product surface quiet, breathable, and unmistakably usable before any identity cue appears.
- Use a split-complement accent family as semantic light: citron for positive momentum, iris for active focus, and coral only for urgent warmth.
- Let pixel art influence edge rhythm, icons, badges, and micro-illustrations without turning screens into retro game scenery.
- Make every bright mark attached to a state, choice, metric, or action so color never becomes garnish.
- Prefer premium consumer warmth over generic SaaS dashboards through editorial copy, tactile cards, and human daily-planning content.

### Anti-Values

- No full rainbow palette, arcade nostalgia, Minecraft block overload, neon cyberpunk glow, or square-grid wallpaper.
- No decorative side rails, colored stripes on cards or rows, confetti sprinkles, or color accents detached from product meaning.
- No generic analytics dashboard, default form styling, arbitrary mixed radii, or childish icon stickers.

### Visual Character

- Use porcelain-white and warm-neutral surfaces with 1px translucent taupe hairlines, one committed 20px outer radius, and tiny clipped 4px pixel nicks on selected corners via clip-path.
- Attach bright split-complement pixels as 2x2 or 3x3 tile clusters inside buttons, icons, progress marks, and badges; never repeat them as a page background or square grid.
- Build cards with floating offset underplates in pale neutral tones and crisp inner highlights, using shadow only as a shallow product-object lift rather than soft SaaS blur.
- Compose screens with large white breathing fields, asymmetric content islands, and compact pixel-motif metadata rows that create rhythm at edges and corners.
- Use rounded editorial typography paired with precise monospace numerals so the interface feels premium and measured while micro-details remain quantized.

## 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 | `#FF6B4A` |
| background | `#FAFAF7` |
| border | `#DDD8CE` |
| error | `#D83A31` |
| info | `#3478F6` |
| muted | `#76716B` |
| primary | `#6757F6` |
| secondary | `#C7F23B` |
| success | `#4C8F46` |
| surface | `#FFFFFF` |
| text | `#1D1B20` |
| warning | `#C8871B` |

## Typography

- **Headline-Lg**: Fraunces, 1.861rem, weight 700, line-height 1.1.
- **Headline-Md**: Fraunces, 1.513rem, weight 600, line-height 1.15.
- **Body-Md**: Onest, 16px, weight 400, line-height 1.52.
- **Label-Md**: Space Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

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

### Breakpoints

mobile <= 640px, tablet 641px-960px, desktop >= 961px

### Grid

Desktop uses a 12-column max-width 1180px canvas with a 7/5 hero split and varied supporting modules; tablet becomes 6 columns and mobile stacks into one column.

### Whitespace

Outer whitespace ranges from 24px mobile to 72px desktop; important cards keep 24-32px internal padding while pixel details stay in 4-8px increments.

## Elevation & Depth

### Shadows

- **Lg**: 0 28px 80px rgba(38,34,28,0.14)
- **Md**: 0 14px 36px rgba(38,34,28,0.10)
- **Sm**: 0 1px 0 rgba(29,27,32,0.08)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `20px`
- **Md**: `14px`
- **None**: `0px`
- **Sm**: `8px`

### Surfaces

- **Bg Pattern**: No repeated grid or dots by default; background remains calm with isolated pixel-bloom motifs only near meaningful hero and empty-state moments.
- **Card Style**: White rounded cards with taupe hairlines, shallow object shadow, and one or two 4px clipped pixel nicks on identity-bearing modules.
- **Treatment**: Clean white porcelain surfaces on a warm neutral canvas with occasional offset underplates and crisp inner highlights.

### Borders

- **Accent Width**: 2px
- **Character**: Warm taupe separators for structure; iris two-step outlines for focus; citron/coral borders only for semantic states.
- **Default Width**: 1px
- **Style**: solid hairline with stepped focus outlines

## Components

### Composition

Use a consumer app scene with a spacious editorial header, one primary action island, a tactile detail sheet, and compact supporting modules; avoid equal dashboard card grids by varying card scale, depth, and density.

### Density

Medium-low density with generous white space, compact metadata rows, and focused clusters of controls; detail sheets may be denser but must preserve 16px readable body text.

### Hierarchy

Large Fraunces headlines and Onest labels establish calm premium hierarchy; bright pixels indicate the next meaningful choice, active item, or progress state rather than decorating every surface.

### Signature Patterns

- Pixel-bloom badges combine four to nine tiny square tiles in citron, iris, and rare coral, placed beside labels or inside icon glyphs as semantic state markers.
- Notched porcelain cards use CSS clip-path polygons to remove a 4px corner bite while preserving a 20px radius illusion through layered underplates.
- Stepped focus rings render as an iris outline plus a one-pixel offset citron tile shadow, making keyboard states visible without neon glow.
- Quantized progress bars fill as separated 8px cells with rounded containers, bridging pixel-art rhythm and premium product feedback.
- Micro-illustrations are built from sparse square and rounded-rectangle CSS tiles floating in empty states, never from full-scene pixel art.

## 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-019e4684-1c9a-7551-9e89-05fb4c9f0003/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 a mostly white and warm-neutral field, then spend citron, iris, and coral only on meaningful state, progress, selection, and confirmation.
- Do Keep pixel cues small: icon corners, tile clusters, progress cells, focus offsets, and empty-state micro-illustrations.
- Do Choose one committed radius geometry and pair it with tiny notches rather than mixing many arbitrary soft-card shapes.
- Do Make product scenes specific to consumer rituals such as planning, collecting, styling, saving, or wellness rather than generic dashboards.
- Don't Do not use square-grid or dotted wallpaper, full rainbow palettes, arcade fonts, game scenery, or blocky all-over theming.
- Don't Do not add colored side rails, left stripes, decorative confetti, or accent marks that do not communicate state or hierarchy.
- Don't Do not allow material or pixel metaphors to stop at decoration; they must shape controls, focus, badges, progress, and responsive composition.
- Don't Do not crowd the page with identical SaaS metric cards or default browser form controls.

### Accessibility

Maintain AA contrast for all text, pair color states with labels or icons, keep focus rings visible, and never rely on tiny pixel color alone to convey critical status.

### Usage Context

Best for premium consumer apps in personal planning, wardrobe, food, savings, wellness, collecting, and lifestyle tools that need memorable identity without sacrificing calm usability.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "porcelain-pixel-bloom",
  "type": "registry:theme",
  "title": "Porcelain Pixel Bloom shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FAFAF7",
      "foreground": "#1D1B20",
      "card": "#FFFFFF",
      "card-foreground": "#1D1B20",
      "popover": "#FFFFFF",
      "popover-foreground": "#1D1B20",
      "primary": "#6757F6",
      "primary-foreground": "#ffffff",
      "secondary": "#C7F23B",
      "secondary-foreground": "#111111",
      "muted": "#76716B",
      "muted-foreground": "#1D1B20",
      "accent": "#FF6B4A",
      "accent-foreground": "#ffffff",
      "destructive": "#D83A31",
      "border": "#DDD8CE",
      "input": "#DDD8CE",
      "ring": "#FF6B4A",
      "chart-1": "#6757F6",
      "chart-2": "#C7F23B",
      "chart-3": "#FF6B4A",
      "chart-4": "#4C8F46",
      "chart-5": "#C8871B",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#1D1B20",
      "sidebar-primary": "#6757F6",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#3478F6",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#DDD8CE",
      "sidebar-ring": "#FF6B4A",
      "radius": "14px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#6757F6",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#FF6B4A",
      "accent-foreground": "#ffffff",
      "destructive": "#D83A31",
      "border": "#303642",
      "input": "#303642",
      "ring": "#FF6B4A",
      "chart-1": "#6757F6",
      "chart-2": "#C7F23B",
      "chart-3": "#FF6B4A",
      "chart-4": "#4C8F46",
      "chart-5": "#C8871B",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#6757F6",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#FF6B4A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#FF6B4A",
      "radius": "14px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e4684-1c9a-7551-9e89-05fb4c9f0003",
    "slug": "porcelain-pixel-bloom",
    "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 · porcelain-pixel-bloom
DESIGN.md

at a glance

Palette

Typography

headline-lgFraunces · 30px · 700

The quick brown fox jumps

headline-mdFraunces · 24px · 600

The quick brown fox jumps

body-mdOnest · 16px · 400

The quick brown fox jumps

label-mdSpace 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
  • step-896px

Shape

full9999px
lg20px
md14px
none0px
sm8px
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: #FAFAF7;
  --foreground: #1D1B20;
  --card: #FFFFFF;
  --card-foreground: #1D1B20;
  --popover: #FFFFFF;
  --popover-foreground: #1D1B20;
  --primary: #6757F6;
  --primary-foreground: #ffffff;
  --secondary: #C7F23B;
  --secondary-foreground: #111111;
  --muted: #76716B;
  --muted-foreground: #1D1B20;
  --accent: #FF6B4A;
  --accent-foreground: #ffffff;
  --destructive: #D83A31;
  --border: #DDD8CE;
  --input: #DDD8CE;
  --ring: #FF6B4A;
  --chart-1: #6757F6;
  --chart-2: #C7F23B;
  --chart-3: #FF6B4A;
  --chart-4: #4C8F46;
  --chart-5: #C8871B;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #1D1B20;
  --sidebar-primary: #6757F6;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #3478F6;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #DDD8CE;
  --sidebar-ring: #FF6B4A;
  --radius: 14px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #6757F6;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #FF6B4A;
  --accent-foreground: #ffffff;
  --destructive: #D83A31;
  --border: #303642;
  --input: #303642;
  --ring: #FF6B4A;
  --chart-1: #6757F6;
  --chart-2: #C7F23B;
  --chart-3: #FF6B4A;
  --chart-4: #4C8F46;
  --chart-5: #C8871B;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #6757F6;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #FF6B4A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #FF6B4A;
  --radius: 14px;
}
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 PorcelainPixelBloomShadcnKit() {
  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">Porcelain Pixel Bloom</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": "#FF6B4A",
      "accent-foreground": "#ffffff",
      "background": "#0f1115",
      "border": "#303642",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "chart-1": "#6757F6",
      "chart-2": "#C7F23B",
      "chart-3": "#FF6B4A",
      "chart-4": "#4C8F46",
      "chart-5": "#C8871B",
      "destructive": "#D83A31",
      "foreground": "#f8fafc",
      "input": "#303642",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#6757F6",
      "primary-foreground": "#ffffff",
      "radius": "14px",
      "ring": "#FF6B4A",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "sidebar": "#181b22",
      "sidebar-accent": "#FF6B4A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#6757F6",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#FF6B4A"
    },
    "light": {
      "accent": "#FF6B4A",
      "accent-foreground": "#ffffff",
      "background": "#FAFAF7",
      "border": "#DDD8CE",
      "card": "#FFFFFF",
      "card-foreground": "#1D1B20",
      "chart-1": "#6757F6",
      "chart-2": "#C7F23B",
      "chart-3": "#FF6B4A",
      "chart-4": "#4C8F46",
      "chart-5": "#C8871B",
      "destructive": "#D83A31",
      "foreground": "#1D1B20",
      "input": "#DDD8CE",
      "muted": "#76716B",
      "muted-foreground": "#1D1B20",
      "popover": "#FFFFFF",
      "popover-foreground": "#1D1B20",
      "primary": "#6757F6",
      "primary-foreground": "#ffffff",
      "radius": "14px",
      "ring": "#FF6B4A",
      "secondary": "#C7F23B",
      "secondary-foreground": "#111111",
      "sidebar": "#FFFFFF",
      "sidebar-accent": "#3478F6",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#DDD8CE",
      "sidebar-foreground": "#1D1B20",
      "sidebar-primary": "#6757F6",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#FF6B4A"
    },
    "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-019e4684-1c9a-7551-9e89-05fb4c9f0003",
    "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": "porcelain-pixel-bloom",
    "source": "katagami"
  },
  "name": "porcelain-pixel-bloom",
  "title": "Porcelain Pixel Bloom shadcn Theme",
  "type": "registry:theme"
}
component recipescompatibility fallback
# Porcelain Pixel Bloom shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4684-1c9a-7551-9e89-05fb4c9f0003`
Slug: `porcelain-pixel-bloom`

## Intent

Porcelain Pixel Bloom is a premium consumer-app language for calm white interfaces where a few luminous, color-theory accents behave like tiny cut-glass pixels: useful signals, not nostalgic game decoration.

## Required primitives

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

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

## Token cues

Colors:

{
  "accent": "#FF6B4A",
  "background": "#FAFAF7",
  "border": "#DDD8CE",
  "error": "#D83A31",
  "info": "#3478F6",
  "muted": "#76716B",
  "primary": "#6757F6",
  "secondary": "#C7F23B",
  "success": "#4C8F46",
  "surface": "#FFFFFF",
  "text": "#1D1B20",
  "warning": "#C8871B"
}

Typography:

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

## Visual character to preserve

- Use porcelain-white and warm-neutral surfaces with 1px translucent taupe hairlines, one committed 20px outer radius, and tiny clipped 4px pixel nicks on selected corners via clip-path.
- Attach bright split-complement pixels as 2x2 or 3x3 tile clusters inside buttons, icons, progress marks, and badges; never repeat them as a page background or square grid.
- Build cards with floating offset underplates in pale neutral tones and crisp inner highlights, using shadow only as a shallow product-object lift rather than soft SaaS blur.
- Compose screens with large white breathing fields, asymmetric content islands, and compact pixel-motif metadata rows that create rhythm at edges and corners.
- Use rounded editorial typography paired with precise monospace numerals so the interface feels premium and measured while micro-details remain quantized.

## ShadSync visual profile

{
  "family": "editorial",
  "material": "flat",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": false,
  "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/porcelain-pixel-bloom/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 a mostly white and warm-neutral field, then spend citron, iris, and coral only on meaningful state, progress, selection, and confirmation.; Keep pixel cues small: icon corners, tile clusters, progress cells, focus offsets, and empty-state micro-illustrations.; Choose one committed radius geometry and pair it with tiny notches rather than mixing many arbitrary soft-card shapes.; Make product scenes specific to consumer rituals such as planning, collecting, styling, saving, or wellness rather than generic dashboards.
- Do not: Do not use square-grid or dotted wallpaper, full rainbow palettes, arcade fonts, game scenery, or blocky all-over theming.; Do not add colored side rails, left stripes, decorative confetti, or accent marks that do not communicate state or hierarchy.; Do not allow material or pixel metaphors to stop at decoration; they must shape controls, focus, badges, progress, and responsive composition.; Do not crowd the page with identical SaaS metric cards or default browser form controls.

## 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 PorcelainPixelBloomShadcnKit() {
  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">Porcelain Pixel Bloom</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

      <Tabs defaultValue="components">
        <TabsList>
          <TabsTrigger value="components">Components</TabsTrigger>
          <TabsTrigger value="states">States</TabsTrigger>
          <TabsTrigger value="export">Export</TabsTrigger>
        </TabsList>
      </Tabs>

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
```

## Layout notes

{
  "breakpoints": "mobile <= 640px, tablet 641px-960px, desktop >= 961px",
  "grid": "Desktop uses a 12-column max-width 1180px canvas with a 7/5 hero split and varied supporting modules; tablet becomes 6 columns and mobile stacks into one column.",
  "whitespace": "Outer whitespace ranges from 24px mobile to 72px desktop; important cards keep 24-32px internal padding while pixel details stay in 4-8px increments."
}
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-019e4684-1c9a-7551-9e89-05fb4c9f0003",
    "name": "Porcelain Pixel Bloom",
    "slug": "porcelain-pixel-bloom"
  },
  "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 porcelain-white and warm-neutral surfaces with 1px translucent taupe hairlines, one committed 20px outer radius, and tiny clipped 4px pixel nicks on selected corners via clip-path.",
    "Attach bright split-complement pixels as 2x2 or 3x3 tile clusters inside buttons, icons, progress marks, and badges; never repeat them as a page background or square grid.",
    "Build cards with floating offset underplates in pale neutral tones and crisp inner highlights, using shadow only as a shallow product-object lift rather than soft SaaS blur.",
    "Compose screens with large white breathing fields, asymmetric content islands, and compact pixel-motif metadata rows that create rhythm at edges and corners.",
    "Use rounded editorial typography paired with precise monospace numerals so the interface feels premium and measured while micro-details remain quantized."
  ],
  "visualProfile": {
    "family": "editorial",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": false,
    "stickerBadges": true,
    "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": "Porcelain Pixel Bloom 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 a mostly white and warm-neutral field, then spend citron, iris, and coral only on meaningful state, progress, selection, and confirmation.",
      "Keep pixel cues small: icon corners, tile clusters, progress cells, focus offsets, and empty-state micro-illustrations.",
      "Choose one committed radius geometry and pair it with tiny notches rather than mixing many arbitrary soft-card shapes.",
      "Make product scenes specific to consumer rituals such as planning, collecting, styling, saving, or wellness rather than generic dashboards."
    ],
    "dont": [
      "Do not use square-grid or dotted wallpaper, full rainbow palettes, arcade fonts, game scenery, or blocky all-over theming.",
      "Do not add colored side rails, left stripes, decorative confetti, or accent marks that do not communicate state or hierarchy.",
      "Do not allow material or pixel metaphors to stop at decoration; they must shape controls, focus, badges, progress, and responsive composition.",
      "Do not crowd the page with identical SaaS metric cards or default browser form controls."
    ]
  }
}
related

More like this