Prism Step Product UI
A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.
Download DESIGN.md
Portable DESIGN.md source of truth for most agents and apps.
specification
philosophy
tokens
borders4 items
- accent width
- 2px
- character
- Lavender-gray hairlines for structure; active states add small bracket corners and never use decorative side rails.
- default width
- 1px
- style
- solid
colors12 items
motion3 items
- duration
- 160ms
- easing
- cubic-bezier(.2,.8,.2,1)
- philosophy
- Interaction snaps in 4px increments: hover lifts 2px, active pixels translate 4px, focus brackets draw in quickly without generic fading.
radii5 items
- full
- 9999px
- lg
- 18px
- md
- 10px
- none
- 0
- sm
- 6px
shadows3 items
- lg
- 0 2px 0 rgba(58,37,88,0.10), 0 28px 72px rgba(36,27,47,0.11)
- md
- 0 1px 0 rgba(58,37,88,0.10), 0 18px 42px rgba(36,27,47,0.08)
- sm
- 0 1px 0 rgba(58,37,88,0.08), 0 8px 18px rgba(36,27,47,0.04)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- No square grid and no default dots; optional sparse three-chip pixel constellations may appear beside hero or empty-state headings only.
- card style
- White cards with plum-tinted hairline borders, 18px radius, stepped top-right clip-path notch, and very soft vertical shadow.
- treatment
- Warm neutral page field with white matte product panels; accent appears as tiny chips, focus brackets, and isolated metric glints only.
typography8 items
- base size
- 16px
- body font
- IBM Plex Sans
- google fonts url
- https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,600;9..144,700&family=Fragment+Mono:ital@0;1&family=IBM+Plex+Sans:wght@400;500;600;700&display=swap
- heading font
- Fraunces
- letter spacing
- -0.015em
- line height
- 1.5
- mono font
- Fragment Mono
- scale ratio
- 1.22
rules
Use one dominant working artifact: a calibration board or editor canvas framed by quiet navigation, a compact inspector, and grouped evidence cards on white surfaces.
Balanced product density with generous outer whitespace, compact controls, and clearly grouped rows; pixel motifs are sparse and never fill backgrounds.
Fraunces headings introduce human warmth, IBM Plex Sans carries product controls, and Fragment Mono labels precise values, color codes, and small status readings.
layout
mobile 375px stacks nav, artifact, and inspector; tablet 768px uses two-column content; desktop 1200px+ restores full shell.
Twelve-column desktop shell with a large central artifact, narrow inspector, and a collapsible left navigation; internal spacing follows 8px baseline with 4px motif offsets.
Outer whitespace is broad and warm, while controls use compact vertical rhythm; accents sit in whitespace pockets rather than becoming decoration.
guidance
- Use accent chips to identify priority, focus, calibration, and meaningful state transitions.
- Keep backgrounds clean white or warm neutral; let panel geometry and type voices create identity.
- Apply micro-pixel motifs to icons, focus brackets, small illustrations, and selected component details only.
- Use the split-complement accent logic deliberately: lime for active priority, periwinkle for guidance, coral for exceptions.
- Do not use square grid wallpapers, dotted notebook fields by default, or repeated pixel texture behind content.
- Do not use colored side rails or decorative stripes on cards, rows, buttons, or panels.
- Do not expand the palette into a rainbow or make the screen resemble an arcade, retro game, or blocky toy interface.
- Do not rely on generic dashboard charts; build scenes around a specific product artifact and real working states.
katagami spec
# Prism Step Product UI ## Philosophy Prism Step Product UI is a premium white product interface language where color-theory accents appear as tiny calibrated pixel steps: distinctive enough to be remembered, quiet enough to keep complex work screens usable. ### Values - White and warm-neutral surfaces carry the product work while saturated accents are reserved for priority, focus, and measurement. - Micro-pixel influence appears as stepped corners, quantized icon details, and small color chips rather than a retro game skin. - Color choices are relational: a deep plum anchor, a bright yellow-green highlight, and a restrained coral/blue opposition create useful hierarchy. - Every motif must perform a product job: selection, status, grouping, focus, or annotation. ### Anti-Values - No full rainbow systems, confetti, neon cyberpunk, arcade nostalgia, or Minecraft-like blockiness. - No square-grid wallpaper, dotted default texture, decorative left rails, or colored side stripes on cards and rows. - No generic SaaS dashboard reliance where charts and status colors carry all of the identity. ### Visual Character - Cards use white matte surfaces with one-pixel plum hairlines and a tiny stepped notch cut from the top-right corner via clip-path. - Primary actions use compact pill geometry with two 4px square highlight pixels positioned on the trailing edge instead of full-width color fills. - Navigation and tabs use quiet text hierarchy plus small quantized accent chips that snap to a 4px internal rhythm without forming a background grid. - Data rows and controls use thin lavender-gray borders, warm off-white insets, and pixel-sized focus brackets that appear only on active or selected items. - Illustrative moments are sparse micro-mosaics made of three to seven rectilinear color chips placed near headings, empty states, and key metrics. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: Lavender-gray hairlines for structure; active states add small bracket corners and never use decorative side rails. - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#C8FF2E` | | background | `#F8F7F2` | | border | `#DDD8E7` | | error | `#D94A5A` | | info | `#4E73D9` | | muted | `#7B7286` | | primary | `#3A2558` | | secondary | `#6E8BFF` | | success | `#3F9E68` | | surface | `#FFFFFF` | | text | `#241B2F` | | warning | `#D88B22` | ### Motion - **Duration**: 160ms - **Easing**: cubic-bezier(.2,.8,.2,1) - **Philosophy**: Interaction snaps in 4px increments: hover lifts 2px, active pixels translate 4px, focus brackets draw in quickly without generic fading. ### Radii - **Full**: 9999px - **Lg**: 18px - **Md**: 10px - **None**: 0 - **Sm**: 6px ### Shadows - **Lg**: 0 2px 0 rgba(58,37,88,0.10), 0 28px 72px rgba(36,27,47,0.11) - **Md**: 0 1px 0 rgba(58,37,88,0.10), 0 18px 42px rgba(36,27,47,0.08) - **Sm**: 0 1px 0 rgba(58,37,88,0.08), 0 8px 18px rgba(36,27,47,0.04) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: No square grid and no default dots; optional sparse three-chip pixel constellations may appear beside hero or empty-state headings only. - **Card Style**: White cards with plum-tinted hairline borders, 18px radius, stepped top-right clip-path notch, and very soft vertical shadow. - **Treatment**: Warm neutral page field with white matte product panels; accent appears as tiny chips, focus brackets, and isolated metric glints only. ### Typography - **Base Size**: 16px - **Body Font**: IBM Plex Sans - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,600;9..144,700&family=Fragment+Mono:ital@0;1&family=IBM+Plex+Sans:wght@400;500;600;700&display=swap - **Heading Font**: Fraunces - **Letter Spacing**: -0.015em - **Line Height**: 1.5 - **Mono Font**: Fragment Mono - **Scale Ratio**: 1.22 ## Rules ### Composition Use one dominant working artifact: a calibration board or editor canvas framed by quiet navigation, a compact inspector, and grouped evidence cards on white surfaces. ### Density Balanced product density with generous outer whitespace, compact controls, and clearly grouped rows; pixel motifs are sparse and never fill backgrounds. ### Hierarchy Fraunces headings introduce human warmth, IBM Plex Sans carries product controls, and Fragment Mono labels precise values, color codes, and small status readings. ### Signature Patterns - Stepped-card notch appears on major panels and dialogs to mark authored surfaces while preserving normal rectangular content alignment. - Pixel focus brackets appear on selected tabs, active inputs, checked controls, and table selection, creating state hierarchy without side stripes. - Triad-chip accents pair one bright yellow-green square with either periwinkle or coral microchips to signal priority, contrast, or completion. - Quantized icon corners simplify glyphs into one or two square cuts at 4px scale while leaving labels and hit targets conventional. ## Layout ### Breakpoints mobile 375px stacks nav, artifact, and inspector; tablet 768px uses two-column content; desktop 1200px+ restores full shell. ### Grid Twelve-column desktop shell with a large central artifact, narrow inspector, and a collapsible left navigation; internal spacing follows 8px baseline with 4px motif offsets. ### Whitespace Outer whitespace is broad and warm, while controls use compact vertical rhythm; accents sit in whitespace pockets rather than becoming decoration. ## Guidance ### Do - Use accent chips to identify priority, focus, calibration, and meaningful state transitions. - Keep backgrounds clean white or warm neutral; let panel geometry and type voices create identity. - Apply micro-pixel motifs to icons, focus brackets, small illustrations, and selected component details only. - Use the split-complement accent logic deliberately: lime for active priority, periwinkle for guidance, coral for exceptions. ### Don't - Do not use square grid wallpapers, dotted notebook fields by default, or repeated pixel texture behind content. - Do not use colored side rails or decorative stripes on cards, rows, buttons, or panels. - Do not expand the palette into a rainbow or make the screen resemble an arcade, retro game, or blocky toy interface. - Do not rely on generic dashboard charts; build scenes around a specific product artifact and real working states.
DESIGN.md
---
version: "alpha"
name: "Prism Step Product UI"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#C8FF2E"
background: "#F8F7F2"
border: "#DDD8E7"
error: "#D94A5A"
info: "#4E73D9"
muted: "#7B7286"
primary: "#3A2558"
secondary: "#6E8BFF"
success: "#3F9E68"
surface: "#FFFFFF"
text: "#241B2F"
warning: "#D88B22"
typography:
headline-lg:
fontFamily: "Fraunces"
fontSize: "1.816rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.015em"
headline-md:
fontFamily: "Fraunces"
fontSize: "1.488rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.015em"
body-md:
fontFamily: "IBM Plex Sans"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.5
letterSpacing: "-0.015em"
label-md:
fontFamily: "Fragment Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "18px"
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"
---
# Prism Step Product UI
## Overview
Prism Step Product UI is a premium white product interface language where color-theory accents appear as tiny calibrated pixel steps: distinctive enough to be remembered, quiet enough to keep complex work screens usable.
### Values
- White and warm-neutral surfaces carry the product work while saturated accents are reserved for priority, focus, and measurement.
- Micro-pixel influence appears as stepped corners, quantized icon details, and small color chips rather than a retro game skin.
- Color choices are relational: a deep plum anchor, a bright yellow-green highlight, and a restrained coral/blue opposition create useful hierarchy.
- Every motif must perform a product job: selection, status, grouping, focus, or annotation.
### Anti-Values
- No full rainbow systems, confetti, neon cyberpunk, arcade nostalgia, or Minecraft-like blockiness.
- No square-grid wallpaper, dotted default texture, decorative left rails, or colored side stripes on cards and rows.
- No generic SaaS dashboard reliance where charts and status colors carry all of the identity.
### Visual Character
- Cards use white matte surfaces with one-pixel plum hairlines and a tiny stepped notch cut from the top-right corner via clip-path.
- Primary actions use compact pill geometry with two 4px square highlight pixels positioned on the trailing edge instead of full-width color fills.
- Navigation and tabs use quiet text hierarchy plus small quantized accent chips that snap to a 4px internal rhythm without forming a background grid.
- Data rows and controls use thin lavender-gray borders, warm off-white insets, and pixel-sized focus brackets that appear only on active or selected items.
- Illustrative moments are sparse micro-mosaics made of three to seven rectilinear color chips placed near headings, empty states, and key metrics.
## 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 | `#C8FF2E` |
| background | `#F8F7F2` |
| border | `#DDD8E7` |
| error | `#D94A5A` |
| info | `#4E73D9` |
| muted | `#7B7286` |
| primary | `#3A2558` |
| secondary | `#6E8BFF` |
| success | `#3F9E68` |
| surface | `#FFFFFF` |
| text | `#241B2F` |
| warning | `#D88B22` |
## Typography
- **Headline-Lg**: Fraunces, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Fraunces, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans, 16px, weight 400, line-height 1.5.
- **Label-Md**: Fragment Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
### Breakpoints
mobile 375px stacks nav, artifact, and inspector; tablet 768px uses two-column content; desktop 1200px+ restores full shell.
### Grid
Twelve-column desktop shell with a large central artifact, narrow inspector, and a collapsible left navigation; internal spacing follows 8px baseline with 4px motif offsets.
### Whitespace
Outer whitespace is broad and warm, while controls use compact vertical rhythm; accents sit in whitespace pockets rather than becoming decoration.
## Elevation & Depth
### Shadows
- **Lg**: 0 2px 0 rgba(58,37,88,0.10), 0 28px 72px rgba(36,27,47,0.11)
- **Md**: 0 1px 0 rgba(58,37,88,0.10), 0 18px 42px rgba(36,27,47,0.08)
- **Sm**: 0 1px 0 rgba(58,37,88,0.08), 0 8px 18px rgba(36,27,47,0.04)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `18px`
- **Md**: `10px`
- **None**: `0px`
- **Sm**: `6px`
### Surfaces
- **Bg Pattern**: No square grid and no default dots; optional sparse three-chip pixel constellations may appear beside hero or empty-state headings only.
- **Card Style**: White cards with plum-tinted hairline borders, 18px radius, stepped top-right clip-path notch, and very soft vertical shadow.
- **Treatment**: Warm neutral page field with white matte product panels; accent appears as tiny chips, focus brackets, and isolated metric glints only.
### Borders
- **Accent Width**: 2px
- **Character**: Lavender-gray hairlines for structure; active states add small bracket corners and never use decorative side rails.
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Use one dominant working artifact: a calibration board or editor canvas framed by quiet navigation, a compact inspector, and grouped evidence cards on white surfaces.
### Density
Balanced product density with generous outer whitespace, compact controls, and clearly grouped rows; pixel motifs are sparse and never fill backgrounds.
### Hierarchy
Fraunces headings introduce human warmth, IBM Plex Sans carries product controls, and Fragment Mono labels precise values, color codes, and small status readings.
### Signature Patterns
- Stepped-card notch appears on major panels and dialogs to mark authored surfaces while preserving normal rectangular content alignment.
- Pixel focus brackets appear on selected tabs, active inputs, checked controls, and table selection, creating state hierarchy without side stripes.
- Triad-chip accents pair one bright yellow-green square with either periwinkle or coral microchips to signal priority, contrast, or completion.
- Quantized icon corners simplify glyphs into one or two square cuts at 4px scale while leaving labels and hit targets conventional.
## 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-019e4685-d6b8-7ce0-8e2f-4a2fd926da64/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 accent chips to identify priority, focus, calibration, and meaningful state transitions.
- Do Keep backgrounds clean white or warm neutral; let panel geometry and type voices create identity.
- Do Apply micro-pixel motifs to icons, focus brackets, small illustrations, and selected component details only.
- Do Use the split-complement accent logic deliberately: lime for active priority, periwinkle for guidance, coral for exceptions.
- Don't Do not use square grid wallpapers, dotted notebook fields by default, or repeated pixel texture behind content.
- Don't Do not use colored side rails or decorative stripes on cards, rows, buttons, or panels.
- Don't Do not expand the palette into a rainbow or make the screen resemble an arcade, retro game, or blocky toy interface.
- Don't Do not rely on generic dashboard charts; build scenes around a specific product artifact and real working states.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "prism-step-product-ui",
"type": "registry:theme",
"title": "Prism Step Product UI shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F8F7F2",
"foreground": "#241B2F",
"card": "#FFFFFF",
"card-foreground": "#241B2F",
"popover": "#FFFFFF",
"popover-foreground": "#241B2F",
"primary": "#3A2558",
"primary-foreground": "#ffffff",
"secondary": "#6E8BFF",
"secondary-foreground": "#ffffff",
"muted": "#7B7286",
"muted-foreground": "#241B2F",
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"destructive": "#D94A5A",
"border": "#DDD8E7",
"input": "#DDD8E7",
"ring": "#C8FF2E",
"chart-1": "#3A2558",
"chart-2": "#6E8BFF",
"chart-3": "#C8FF2E",
"chart-4": "#3F9E68",
"chart-5": "#D88B22",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#241B2F",
"sidebar-primary": "#3A2558",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#4E73D9",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#DDD8E7",
"sidebar-ring": "#C8FF2E",
"radius": "10px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#3A2558",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"destructive": "#D94A5A",
"border": "#303642",
"input": "#303642",
"ring": "#C8FF2E",
"chart-1": "#3A2558",
"chart-2": "#6E8BFF",
"chart-3": "#C8FF2E",
"chart-4": "#3F9E68",
"chart-5": "#D88B22",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#3A2558",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#C8FF2E",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#C8FF2E",
"radius": "10px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e4685-d6b8-7ce0-8e2f-4a2fd926da64",
"slug": "prism-step-product-ui",
"componentManifest": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"nativeTokenNames": {
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"colors": [
"accent",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"motion": [
"duration",
"easing",
"philosophy"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"spacing": [
"base",
"scale"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
]
}
}
}
```embodiments
at a glance
Typography
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Components
Components rendered with this language’s tokens — colors, type, and rounded corners as specified.
Spacing
- base8px
- xs4px
- sm8px
- md12px
- lg16px
- xl24px
- 2xl32px
- 3xl48px
- 4xl64px
Shape
implementation kit
DESIGN.md with shadcn
Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.
advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #F8F7F2;
--foreground: #241B2F;
--card: #FFFFFF;
--card-foreground: #241B2F;
--popover: #FFFFFF;
--popover-foreground: #241B2F;
--primary: #3A2558;
--primary-foreground: #ffffff;
--secondary: #6E8BFF;
--secondary-foreground: #ffffff;
--muted: #7B7286;
--muted-foreground: #241B2F;
--accent: #C8FF2E;
--accent-foreground: #111111;
--destructive: #D94A5A;
--border: #DDD8E7;
--input: #DDD8E7;
--ring: #C8FF2E;
--chart-1: #3A2558;
--chart-2: #6E8BFF;
--chart-3: #C8FF2E;
--chart-4: #3F9E68;
--chart-5: #D88B22;
--sidebar: #FFFFFF;
--sidebar-foreground: #241B2F;
--sidebar-primary: #3A2558;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #4E73D9;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #DDD8E7;
--sidebar-ring: #C8FF2E;
--radius: 10px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #3A2558;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #C8FF2E;
--accent-foreground: #111111;
--destructive: #D94A5A;
--border: #303642;
--input: #303642;
--ring: #C8FF2E;
--chart-1: #3A2558;
--chart-2: #6E8BFF;
--chart-3: #C8FF2E;
--chart-4: #3F9E68;
--chart-5: #D88B22;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #3A2558;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #C8FF2E;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #C8FF2E;
--radius: 10px;
}
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
Card,
CardContent,
CardDescription,
CardFooter,
CardHeader,
CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";
export function PrismStepProductUiShadcnKit() {
return (
<section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
<div className="flex items-start justify-between gap-4">
<div>
<Badge variant="outline">shadcn/ui</Badge>
<h2 className="mt-3 text-2xl font-semibold tracking-tight">Prism Step Product UI</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"cssVars": {
"dark": {
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"background": "#0f1115",
"border": "#303642",
"card": "#181b22",
"card-foreground": "#f8fafc",
"chart-1": "#3A2558",
"chart-2": "#6E8BFF",
"chart-3": "#C8FF2E",
"chart-4": "#3F9E68",
"chart-5": "#D88B22",
"destructive": "#D94A5A",
"foreground": "#f8fafc",
"input": "#303642",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#3A2558",
"primary-foreground": "#ffffff",
"radius": "10px",
"ring": "#C8FF2E",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"sidebar": "#181b22",
"sidebar-accent": "#C8FF2E",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#3A2558",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#C8FF2E"
},
"light": {
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"background": "#F8F7F2",
"border": "#DDD8E7",
"card": "#FFFFFF",
"card-foreground": "#241B2F",
"chart-1": "#3A2558",
"chart-2": "#6E8BFF",
"chart-3": "#C8FF2E",
"chart-4": "#3F9E68",
"chart-5": "#D88B22",
"destructive": "#D94A5A",
"foreground": "#241B2F",
"input": "#DDD8E7",
"muted": "#7B7286",
"muted-foreground": "#241B2F",
"popover": "#FFFFFF",
"popover-foreground": "#241B2F",
"primary": "#3A2558",
"primary-foreground": "#ffffff",
"radius": "10px",
"ring": "#C8FF2E",
"secondary": "#6E8BFF",
"secondary-foreground": "#ffffff",
"sidebar": "#FFFFFF",
"sidebar-accent": "#4E73D9",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#DDD8E7",
"sidebar-foreground": "#241B2F",
"sidebar-primary": "#3A2558",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#C8FF2E"
},
"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-019e4685-d6b8-7ce0-8e2f-4a2fd926da64",
"nativeTokenNames": {
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"colors": [
"accent",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"motion": [
"duration",
"easing",
"philosophy"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"spacing": [
"base",
"scale"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
]
},
"slug": "prism-step-product-ui",
"source": "katagami"
},
"name": "prism-step-product-ui",
"title": "Prism Step Product UI shadcn Theme",
"type": "registry:theme"
}
# Prism Step Product UI shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4685-d6b8-7ce0-8e2f-4a2fd926da64`
Slug: `prism-step-product-ui`
## Intent
Prism Step Product UI is a premium white product interface language where color-theory accents appear as tiny calibrated pixel steps: distinctive enough to be remembered, quiet enough to keep complex work screens usable.
## 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": "#C8FF2E",
"background": "#F8F7F2",
"border": "#DDD8E7",
"error": "#D94A5A",
"info": "#4E73D9",
"muted": "#7B7286",
"primary": "#3A2558",
"secondary": "#6E8BFF",
"success": "#3F9E68",
"surface": "#FFFFFF",
"text": "#241B2F",
"warning": "#D88B22"
}
Typography:
{
"base_size": "16px",
"body_font": "IBM Plex Sans",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,600;9..144,700&family=Fragment+Mono:ital@0;1&family=IBM+Plex+Sans:wght@400;500;600;700&display=swap",
"heading_font": "Fraunces",
"letter_spacing": "-0.015em",
"line_height": 1.5,
"mono_font": "Fragment Mono",
"scale_ratio": 1.22
}
## Visual character to preserve
- Cards use white matte surfaces with one-pixel plum hairlines and a tiny stepped notch cut from the top-right corner via clip-path.
- Primary actions use compact pill geometry with two 4px square highlight pixels positioned on the trailing edge instead of full-width color fills.
- Navigation and tabs use quiet text hierarchy plus small quantized accent chips that snap to a 4px internal rhythm without forming a background grid.
- Data rows and controls use thin lavender-gray borders, warm off-white insets, and pixel-sized focus brackets that appear only on active or selected items.
- Illustrative moments are sparse micro-mosaics made of three to seven rectilinear color chips placed near headings, empty states, and key metrics.
## ShadSync visual profile
{
"family": "system",
"material": "flat",
"contour": "pebble",
"border": "solid",
"underlay": false,
"grain": false,
"stickerBadges": false,
"motion": "lift",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
}
## Signature component recipes
### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.
### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.
### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.
### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.
### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.
## Preview shots
- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.
## Implementation contract
- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/prism-step-product-ui/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use accent chips to identify priority, focus, calibration, and meaningful state transitions.; Keep backgrounds clean white or warm neutral; let panel geometry and type voices create identity.; Apply micro-pixel motifs to icons, focus brackets, small illustrations, and selected component details only.; Use the split-complement accent logic deliberately: lime for active priority, periwinkle for guidance, coral for exceptions.
- Do not: Do not use square grid wallpapers, dotted notebook fields by default, or repeated pixel texture behind content.; Do not use colored side rails or decorative stripes on cards, rows, buttons, or panels.; Do not expand the palette into a rainbow or make the screen resemble an arcade, retro game, or blocky toy interface.; Do not rely on generic dashboard charts; build scenes around a specific product artifact and real working states.
## Copy-paste component example
This generated starter proves the import shape. Production Katagami agents should replace it with a language-specific product composition.
```tsx
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
Card,
CardContent,
CardDescription,
CardFooter,
CardHeader,
CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";
export function PrismStepProductUiShadcnKit() {
return (
<section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
<div className="flex items-start justify-between gap-4">
<div>
<Badge variant="outline">shadcn/ui</Badge>
<h2 className="mt-3 text-2xl font-semibold tracking-tight">Prism Step Product UI</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
```
## Layout notes
{
"breakpoints": "mobile 375px stacks nav, artifact, and inspector; tablet 768px uses two-column content; desktop 1200px+ restores full shell.",
"grid": "Twelve-column desktop shell with a large central artifact, narrow inspector, and a collapsible left navigation; internal spacing follows 8px baseline with 4px motif offsets.",
"whitespace": "Outer whitespace is broad and warm, while controls use compact vertical rhythm; accents sit in whitespace pockets rather than becoming decoration."
}
{
"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-019e4685-d6b8-7ce0-8e2f-4a2fd926da64",
"name": "Prism Step Product UI",
"slug": "prism-step-product-ui"
},
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"primitives": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"identityNotes": [
"Cards use white matte surfaces with one-pixel plum hairlines and a tiny stepped notch cut from the top-right corner via clip-path.",
"Primary actions use compact pill geometry with two 4px square highlight pixels positioned on the trailing edge instead of full-width color fills.",
"Navigation and tabs use quiet text hierarchy plus small quantized accent chips that snap to a 4px internal rhythm without forming a background grid.",
"Data rows and controls use thin lavender-gray borders, warm off-white insets, and pixel-sized focus brackets that appear only on active or selected items.",
"Illustrative moments are sparse micro-mosaics made of three to seven rectilinear color chips placed near headings, empty states, and key metrics."
],
"visualProfile": {
"family": "system",
"material": "flat",
"contour": "pebble",
"border": "solid",
"underlay": false,
"grain": false,
"stickerBadges": false,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "Prism Step Product UI launch room",
"description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
"primaryAction": "Apply theme",
"secondaryAction": "Review states",
"stats": [
{
"label": "components",
"value": "16",
"tone": "accent"
},
{
"label": "states",
"value": "ready"
},
{
"label": "density",
"value": "balanced",
"tone": "warning"
}
],
"rows": [
{
"label": "Primary flow",
"value": "mapped",
"status": "active"
},
{
"label": "Token coverage",
"value": "semantic",
"status": "synced"
},
{
"label": "Responsive proof",
"value": "queued",
"status": "review"
}
],
"statuses": [
"Active",
"Synced",
"Draft"
]
}
},
{
"id": "detail-editor",
"title": "Detail editor",
"viewport": "tablet",
"primitives": [
"button",
"card",
"input",
"textarea",
"select",
"checkbox",
"switch",
"slider",
"dialog",
"sheet"
],
"composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
"mustShow": [
"focus ring",
"error or destructive state",
"dialog or sheet treatment",
"written guidance content"
],
"avoid": [
"unstyled browser controls",
"floating cards inside cards",
"missing labels"
],
"scene": {
"eyebrow": "editing flow",
"headline": "Language recipe editor",
"description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
"primaryAction": "Save recipe",
"secondaryAction": "Open sheet",
"fields": [
{
"label": "Component family",
"value": "Narrative cards"
},
{
"label": "State treatment",
"value": "Visible focus + validation"
},
{
"label": "Motion",
"value": "Small lift, no opacity-only fade"
}
],
"statuses": [
"Focus",
"Invalid",
"Confirmed"
]
}
},
{
"id": "data-operations",
"title": "Data operations",
"viewport": "mobile",
"primitives": [
"button",
"tabs",
"badge",
"dropdown-menu",
"table",
"tooltip",
"separator"
],
"composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
"mustShow": [
"responsive reflow",
"dense row styling",
"menu affordance",
"status badge system"
],
"avoid": [
"desktop-only tables",
"text overflow",
"default shadcn spacing without Katagami character"
],
"scene": {
"eyebrow": "operations",
"headline": "Compact review queue",
"description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
"primaryAction": "Resolve",
"secondaryAction": "Filter",
"rows": [
{
"label": "Button hierarchy",
"value": "approved",
"status": "ok"
},
{
"label": "Table rhythm",
"value": "needs pass",
"status": "watch"
},
{
"label": "Empty state",
"value": "designed",
"status": "done"
}
],
"statuses": [
"Queued",
"Blocked",
"Done"
]
}
}
],
"componentRecipes": [
{
"primitive": "button",
"intent": "Prove action hierarchy, focus, disabled, and destructive states."
},
{
"primitive": "card",
"intent": "Carry the language surface, border, elevation, and density rules."
},
{
"primitive": "input",
"intent": "Show labels, focus rings, validation, and spacing rhythm."
},
{
"primitive": "textarea",
"intent": "Show longer guidance, validation copy, and writing density."
},
{
"primitive": "select",
"intent": "Show filtering, selection contrast, and menu trigger styling."
},
{
"primitive": "dialog",
"intent": "Show centered decision states and overlay treatment."
},
{
"primitive": "sheet",
"intent": "Show contextual side panels and responsive editing."
},
{
"primitive": "tabs",
"intent": "Show navigational structure and active/inactive contrast."
},
{
"primitive": "badge",
"intent": "Show compact status vocabulary and semantic colors."
},
{
"primitive": "separator",
"intent": "Show section rhythm without generic gray dividers."
},
{
"primitive": "checkbox",
"intent": "Show binary selection with visible focus and checked states."
},
{
"primitive": "switch",
"intent": "Show settings toggles and on/off contrast."
},
{
"primitive": "slider",
"intent": "Show numeric adjustment with track/thumb styling."
},
{
"primitive": "tooltip",
"intent": "Show concise explanation styling above compact controls."
},
{
"primitive": "dropdown-menu",
"intent": "Show action menus, destructive items, and grouped choices."
},
{
"primitive": "table",
"intent": "Show dense operational data, separators, row states, and responsive behavior."
}
],
"qualityRules": {
"do": [
"Use accent chips to identify priority, focus, calibration, and meaningful state transitions.",
"Keep backgrounds clean white or warm neutral; let panel geometry and type voices create identity.",
"Apply micro-pixel motifs to icons, focus brackets, small illustrations, and selected component details only.",
"Use the split-complement accent logic deliberately: lime for active priority, periwinkle for guidance, coral for exceptions."
],
"dont": [
"Do not use square grid wallpapers, dotted notebook fields by default, or repeated pixel texture behind content.",
"Do not use colored side rails or decorative stripes on cards, rows, buttons, or panels.",
"Do not expand the palette into a rainbow or make the screen resemble an arcade, retro game, or blocky toy interface.",
"Do not rely on generic dashboard charts; build scenes around a specific product artifact and real working states."
]
}
}