Prism Register Studio
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
- Cool-gray hairlines define surfaces; accent borders appear only as short corner ticks, focus outlines, or selected object handles.
- default width
- 1px
- style
- solid
colors12 items
motion3 items
- duration
- 150ms
- easing
- cubic-bezier(0.2, 0.8, 0.2, 1)
- philosophy
- Controls respond with exact one-pixel snaps, fast opacity changes, and tiny chromatic offsets so motion feels like registration alignment rather than entertainment.
radii5 items
- full
- 9999px
- lg
- 16px
- md
- 10px
- none
- 0
- sm
- 4px
shadows3 items
- lg
- 0 2px 0 rgba(23,24,28,0.08), 0 28px 70px rgba(23,24,28,0.10)
- md
- 0 1px 0 rgba(23,24,28,0.08), 0 14px 36px rgba(23,24,28,0.08)
- sm
- 0 1px 0 rgba(23,24,28,0.06), 0 4px 12px rgba(23,24,28,0.05)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- None by default; if a preview requires registration marks, use a few isolated 6px pixel ticks near handles, never a repeated square grid.
- card style
- 1px bordered white modules with 10px radius, minimal shadow, compact title rows, and internal pixel chips for state.
- treatment
- Clean warm-white application shell with opaque white panels, faint neutral canvas blocks, and no background grid or dotted texture.
token_logic1
typography8 items
- base size
- 16px
- body font
- Inter
- google fonts url
- https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Inter:wght@400;500;600;700&family=Sora:wght@500;600;700&display=swap
- heading font
- Sora
- letter spacing
- -0.018em
- line height
- 1.48
- mono font
- IBM Plex Mono
- scale ratio
- 1.22
rules
Compose screens as a creative workstation: slim tool rail, precise left controls, generous white preview canvas, right inspector, and a compact activity strip with no decorative side stripes.
Balanced-high density for professional creative tools: compact controls and data rows around a calm preview field with deliberate breathing room.
Use Sora for compressed confident headings, Inter for product copy and controls, and IBM Plex Mono for coordinates, layer numbers, percentages, and version stamps.
layout
mobile <= 640px, tablet 641px-1024px, desktop >= 1025px
Desktop uses a 72px tool rail, minmax(260px, 320px) control column, fluid preview canvas, and 300px inspector; tablet stacks inspector below canvas; mobile turns rails into segmented top controls.
Whitespace is calm around previews and tighter around controls; preserve 24px panel gaps on desktop and 16px gaps on smaller screens so color sparks stay meaningful.
guidance
- Use bright accents as functional pixels for active tools, annotations, focus, progress, and edit deltas.
- Keep surfaces white, warm neutral, and opaque with exact hairline borders and committed radius geometry.
- Let mono labels, handles, layer chips, and preview metadata carry the subtle pixel-art influence.
- Design real creative-product scenes with layers, tools, previews, comments, versions, and coordinates.
- Do not use square-grid backgrounds, rainbow sprawl, arbitrary confetti, neon cyberpunk, or retro arcade motifs.
- Do not put decorative colored side rails or stripes on cards, buttons, rows, or panels.
- Do not make every icon blocky or oversized; pixel details must remain small, sparse, and useful.
- Do not rely on color alone for state; pair accents with labels, outlines, handles, or icons.
katagami spec
# Prism Register Studio ## Philosophy Prism Register Studio is a clean creative-tool interface language for exact controls, preview work, layers, and annotations on calm white surfaces. It rejects rainbow decoration by treating bright color as registered pixel sparks: small calibrated markers that identify state, focus, and authored changes. ### Values - Precision first: controls, panels, and annotations should feel measured rather than playful. - Color earns a job: bright accents identify active tools, delta states, preview regions, or collaboration events. - Pixel influence stays miniature and functional through icon edges, small chips, quantized handles, and preview markers. - White and neutral surfaces carry the product while vivid chroma appears as high-taste sparks. ### Anti-Values - No retro arcade skin, square-grid wallpaper, Minecraft blockiness, or full-rainbow confetti. - No decorative side rails or colored stripes on cards, buttons, rows, or panels. - No generic SaaS dashboard scene without creative-tool artifacts, exact controls, or preview grammar. ### Visual Character - Use layered white and warm-neutral panels with 1px cool-gray borders, compact 14px control rows, and a right-side preview canvas rather than heavy card stacks. - Place accent color only in small registered pixel chips, 6px square handles, mini swatches, focus ticks, and annotation glyphs aligned to content edges, never as side rails. - Build icons and status marks from stepped rectilinear SVG/CSS shapes with clipped inside corners while keeping containers mostly 10px rounded rectangles. - Use thin black typographic hierarchy with a technical sans body, mono numeric labels, and tight negative heading tracking for a premium creative-product feel. - Create hover and active states with tiny chromatic offset shadows and one-pixel positional snaps instead of large glows, gradients, or decorative confetti. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: Cool-gray hairlines define surfaces; accent borders appear only as short corner ticks, focus outlines, or selected object handles. - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#FF5B2E` | | background | `#F8F7F3` | | border | `#D9DDE5` | | error | `#D83A52` | | info | `#2774E8` | | muted | `#6D7280` | | primary | `#5236FF` | | secondary | `#00AFC7` | | success | `#10A36F` | | surface | `#FFFFFF` | | text | `#17181C` | | warning | `#D99000` | ### Motion - **Duration**: 150ms - **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1) - **Philosophy**: Controls respond with exact one-pixel snaps, fast opacity changes, and tiny chromatic offsets so motion feels like registration alignment rather than entertainment. ### Radii - **Full**: 9999px - **Lg**: 16px - **Md**: 10px - **None**: 0 - **Sm**: 4px ### Shadows - **Lg**: 0 2px 0 rgba(23,24,28,0.08), 0 28px 70px rgba(23,24,28,0.10) - **Md**: 0 1px 0 rgba(23,24,28,0.08), 0 14px 36px rgba(23,24,28,0.08) - **Sm**: 0 1px 0 rgba(23,24,28,0.06), 0 4px 12px rgba(23,24,28,0.05) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: None by default; if a preview requires registration marks, use a few isolated 6px pixel ticks near handles, never a repeated square grid. - **Card Style**: 1px bordered white modules with 10px radius, minimal shadow, compact title rows, and internal pixel chips for state. - **Treatment**: Clean warm-white application shell with opaque white panels, faint neutral canvas blocks, and no background grid or dotted texture. ### Token Logic The palette uses warm neutral grounds plus a split-complement-like accent system: violet primary for active tools, cyan secondary for previews/info, vermilion accent for edits and deltas, with success/warning/error kept semantic and less frequent. ### Typography - **Base Size**: 16px - **Body Font**: Inter - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Inter:wght@400;500;600;700&family=Sora:wght@500;600;700&display=swap - **Heading Font**: Sora - **Letter Spacing**: -0.018em - **Line Height**: 1.48 - **Mono Font**: IBM Plex Mono - **Scale Ratio**: 1.22 ## Rules ### Composition Compose screens as a creative workstation: slim tool rail, precise left controls, generous white preview canvas, right inspector, and a compact activity strip with no decorative side stripes. ### Density Balanced-high density for professional creative tools: compact controls and data rows around a calm preview field with deliberate breathing room. ### Hierarchy Use Sora for compressed confident headings, Inter for product copy and controls, and IBM Plex Mono for coordinates, layer numbers, percentages, and version stamps. ### Signature Patterns - Registered pixel sparks: 4px to 8px square accent chips positioned as state markers, annotation anchors, active handles, and change indicators only. - Quantized focus rings: selected controls use a 2px violet outline plus two tiny offset cyan/vermilion corner pixels instead of colored rails or glows. - Stepped icon cuts: tool icons and small badges use rectilinear stepped masks or SVG pixels while parent panels preserve the committed 10px radius geometry. - Micro preview handles: canvas objects show sparse 6px square handles and mono coordinate tags that communicate editability without forming a square-grid background. - Chromatic snap motion: hover and active states shift one pixel with a two-color miniature shadow, suggesting registration alignment rather than arcade animation. ## Layout ### Breakpoints mobile <= 640px, tablet 641px-1024px, desktop >= 1025px ### Grid Desktop uses a 72px tool rail, minmax(260px, 320px) control column, fluid preview canvas, and 300px inspector; tablet stacks inspector below canvas; mobile turns rails into segmented top controls. ### Whitespace Whitespace is calm around previews and tighter around controls; preserve 24px panel gaps on desktop and 16px gaps on smaller screens so color sparks stay meaningful. ## Guidance ### Do - Use bright accents as functional pixels for active tools, annotations, focus, progress, and edit deltas. - Keep surfaces white, warm neutral, and opaque with exact hairline borders and committed radius geometry. - Let mono labels, handles, layer chips, and preview metadata carry the subtle pixel-art influence. - Design real creative-product scenes with layers, tools, previews, comments, versions, and coordinates. ### Don't - Do not use square-grid backgrounds, rainbow sprawl, arbitrary confetti, neon cyberpunk, or retro arcade motifs. - Do not put decorative colored side rails or stripes on cards, buttons, rows, or panels. - Do not make every icon blocky or oversized; pixel details must remain small, sparse, and useful. - Do not rely on color alone for state; pair accents with labels, outlines, handles, or icons. ### Embodiment Ready Notes The embodiment should show a fictional creative tool with asset layers, annotation pins, transform controls, preview handles, an inspector, activity states, and enough components to prove the language across shell, forms, cards, tabs, badges, table rows, switches, and sliders. ### Layout Component Guidance Buttons are crisp rounded rectangles with mono shortcuts, cards are work modules with internal state chips, inputs are exact fields with coordinate-style labels, tabs act like tool modes, and tables emphasize asset/version operations rather than dashboard metrics.
DESIGN.md
---
version: "alpha"
name: "Prism Register Studio"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#FF5B2E"
background: "#F8F7F3"
border: "#D9DDE5"
error: "#D83A52"
info: "#2774E8"
muted: "#6D7280"
primary: "#5236FF"
secondary: "#00AFC7"
success: "#10A36F"
surface: "#FFFFFF"
text: "#17181C"
warning: "#D99000"
typography:
headline-lg:
fontFamily: "Sora"
fontSize: "1.816rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.018em"
headline-md:
fontFamily: "Sora"
fontSize: "1.488rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.018em"
body-md:
fontFamily: "Inter"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.48
letterSpacing: "-0.018em"
label-md:
fontFamily: "IBM Plex Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "16px"
md: "10px"
none: "0px"
sm: "4px"
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 Register Studio
## Overview
Prism Register Studio is a clean creative-tool interface language for exact controls, preview work, layers, and annotations on calm white surfaces. It rejects rainbow decoration by treating bright color as registered pixel sparks: small calibrated markers that identify state, focus, and authored changes.
### Values
- Precision first: controls, panels, and annotations should feel measured rather than playful.
- Color earns a job: bright accents identify active tools, delta states, preview regions, or collaboration events.
- Pixel influence stays miniature and functional through icon edges, small chips, quantized handles, and preview markers.
- White and neutral surfaces carry the product while vivid chroma appears as high-taste sparks.
### Anti-Values
- No retro arcade skin, square-grid wallpaper, Minecraft blockiness, or full-rainbow confetti.
- No decorative side rails or colored stripes on cards, buttons, rows, or panels.
- No generic SaaS dashboard scene without creative-tool artifacts, exact controls, or preview grammar.
### Visual Character
- Use layered white and warm-neutral panels with 1px cool-gray borders, compact 14px control rows, and a right-side preview canvas rather than heavy card stacks.
- Place accent color only in small registered pixel chips, 6px square handles, mini swatches, focus ticks, and annotation glyphs aligned to content edges, never as side rails.
- Build icons and status marks from stepped rectilinear SVG/CSS shapes with clipped inside corners while keeping containers mostly 10px rounded rectangles.
- Use thin black typographic hierarchy with a technical sans body, mono numeric labels, and tight negative heading tracking for a premium creative-product feel.
- Create hover and active states with tiny chromatic offset shadows and one-pixel positional snaps instead of large glows, gradients, or decorative confetti.
## 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 | `#FF5B2E` |
| background | `#F8F7F3` |
| border | `#D9DDE5` |
| error | `#D83A52` |
| info | `#2774E8` |
| muted | `#6D7280` |
| primary | `#5236FF` |
| secondary | `#00AFC7` |
| success | `#10A36F` |
| surface | `#FFFFFF` |
| text | `#17181C` |
| warning | `#D99000` |
## Typography
- **Headline-Lg**: Sora, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Sora, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Inter, 16px, weight 400, line-height 1.48.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
### Breakpoints
mobile <= 640px, tablet 641px-1024px, desktop >= 1025px
### Grid
Desktop uses a 72px tool rail, minmax(260px, 320px) control column, fluid preview canvas, and 300px inspector; tablet stacks inspector below canvas; mobile turns rails into segmented top controls.
### Whitespace
Whitespace is calm around previews and tighter around controls; preserve 24px panel gaps on desktop and 16px gaps on smaller screens so color sparks stay meaningful.
## Elevation & Depth
### Shadows
- **Lg**: 0 2px 0 rgba(23,24,28,0.08), 0 28px 70px rgba(23,24,28,0.10)
- **Md**: 0 1px 0 rgba(23,24,28,0.08), 0 14px 36px rgba(23,24,28,0.08)
- **Sm**: 0 1px 0 rgba(23,24,28,0.06), 0 4px 12px rgba(23,24,28,0.05)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `16px`
- **Md**: `10px`
- **None**: `0px`
- **Sm**: `4px`
### Surfaces
- **Bg Pattern**: None by default; if a preview requires registration marks, use a few isolated 6px pixel ticks near handles, never a repeated square grid.
- **Card Style**: 1px bordered white modules with 10px radius, minimal shadow, compact title rows, and internal pixel chips for state.
- **Treatment**: Clean warm-white application shell with opaque white panels, faint neutral canvas blocks, and no background grid or dotted texture.
### Borders
- **Accent Width**: 2px
- **Character**: Cool-gray hairlines define surfaces; accent borders appear only as short corner ticks, focus outlines, or selected object handles.
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Compose screens as a creative workstation: slim tool rail, precise left controls, generous white preview canvas, right inspector, and a compact activity strip with no decorative side stripes.
### Density
Balanced-high density for professional creative tools: compact controls and data rows around a calm preview field with deliberate breathing room.
### Hierarchy
Use Sora for compressed confident headings, Inter for product copy and controls, and IBM Plex Mono for coordinates, layer numbers, percentages, and version stamps.
### Signature Patterns
- Registered pixel sparks: 4px to 8px square accent chips positioned as state markers, annotation anchors, active handles, and change indicators only.
- Quantized focus rings: selected controls use a 2px violet outline plus two tiny offset cyan/vermilion corner pixels instead of colored rails or glows.
- Stepped icon cuts: tool icons and small badges use rectilinear stepped masks or SVG pixels while parent panels preserve the committed 10px radius geometry.
- Micro preview handles: canvas objects show sparse 6px square handles and mono coordinate tags that communicate editability without forming a square-grid background.
- Chromatic snap motion: hover and active states shift one pixel with a two-color miniature shadow, suggesting registration alignment rather than arcade animation.
## 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-019e4686-2b06-7c02-bbd2-cb00c978ec30/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 bright accents as functional pixels for active tools, annotations, focus, progress, and edit deltas.
- Do Keep surfaces white, warm neutral, and opaque with exact hairline borders and committed radius geometry.
- Do Let mono labels, handles, layer chips, and preview metadata carry the subtle pixel-art influence.
- Do Design real creative-product scenes with layers, tools, previews, comments, versions, and coordinates.
- Don't Do not use square-grid backgrounds, rainbow sprawl, arbitrary confetti, neon cyberpunk, or retro arcade motifs.
- Don't Do not put decorative colored side rails or stripes on cards, buttons, rows, or panels.
- Don't Do not make every icon blocky or oversized; pixel details must remain small, sparse, and useful.
- Don't Do not rely on color alone for state; pair accents with labels, outlines, handles, or icons.
### Embodiment Ready Notes
The embodiment should show a fictional creative tool with asset layers, annotation pins, transform controls, preview handles, an inspector, activity states, and enough components to prove the language across shell, forms, cards, tabs, badges, table rows, switches, and sliders.
### Layout Component Guidance
Buttons are crisp rounded rectangles with mono shortcuts, cards are work modules with internal state chips, inputs are exact fields with coordinate-style labels, tabs act like tool modes, and tables emphasize asset/version operations rather than dashboard metrics.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "prism-register-studio",
"type": "registry:theme",
"title": "Prism Register Studio shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F8F7F3",
"foreground": "#17181C",
"card": "#FFFFFF",
"card-foreground": "#17181C",
"popover": "#FFFFFF",
"popover-foreground": "#17181C",
"primary": "#5236FF",
"primary-foreground": "#ffffff",
"secondary": "#00AFC7",
"secondary-foreground": "#ffffff",
"muted": "#6D7280",
"muted-foreground": "#17181C",
"accent": "#FF5B2E",
"accent-foreground": "#ffffff",
"destructive": "#D83A52",
"border": "#D9DDE5",
"input": "#D9DDE5",
"ring": "#FF5B2E",
"chart-1": "#5236FF",
"chart-2": "#00AFC7",
"chart-3": "#FF5B2E",
"chart-4": "#10A36F",
"chart-5": "#D99000",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#17181C",
"sidebar-primary": "#5236FF",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#2774E8",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#D9DDE5",
"sidebar-ring": "#FF5B2E",
"radius": "10px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#5236FF",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#FF5B2E",
"accent-foreground": "#ffffff",
"destructive": "#D83A52",
"border": "#303642",
"input": "#303642",
"ring": "#FF5B2E",
"chart-1": "#5236FF",
"chart-2": "#00AFC7",
"chart-3": "#FF5B2E",
"chart-4": "#10A36F",
"chart-5": "#D99000",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#5236FF",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#FF5B2E",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#FF5B2E",
"radius": "10px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e4686-2b06-7c02-bbd2-cb00c978ec30",
"slug": "prism-register-studio",
"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: #F8F7F3;
--foreground: #17181C;
--card: #FFFFFF;
--card-foreground: #17181C;
--popover: #FFFFFF;
--popover-foreground: #17181C;
--primary: #5236FF;
--primary-foreground: #ffffff;
--secondary: #00AFC7;
--secondary-foreground: #ffffff;
--muted: #6D7280;
--muted-foreground: #17181C;
--accent: #FF5B2E;
--accent-foreground: #ffffff;
--destructive: #D83A52;
--border: #D9DDE5;
--input: #D9DDE5;
--ring: #FF5B2E;
--chart-1: #5236FF;
--chart-2: #00AFC7;
--chart-3: #FF5B2E;
--chart-4: #10A36F;
--chart-5: #D99000;
--sidebar: #FFFFFF;
--sidebar-foreground: #17181C;
--sidebar-primary: #5236FF;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #2774E8;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #D9DDE5;
--sidebar-ring: #FF5B2E;
--radius: 10px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #5236FF;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #FF5B2E;
--accent-foreground: #ffffff;
--destructive: #D83A52;
--border: #303642;
--input: #303642;
--ring: #FF5B2E;
--chart-1: #5236FF;
--chart-2: #00AFC7;
--chart-3: #FF5B2E;
--chart-4: #10A36F;
--chart-5: #D99000;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #5236FF;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #FF5B2E;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #FF5B2E;
--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 PrismRegisterStudioShadcnKit() {
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 Register Studio</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": "#FF5B2E",
"accent-foreground": "#ffffff",
"background": "#0f1115",
"border": "#303642",
"card": "#181b22",
"card-foreground": "#f8fafc",
"chart-1": "#5236FF",
"chart-2": "#00AFC7",
"chart-3": "#FF5B2E",
"chart-4": "#10A36F",
"chart-5": "#D99000",
"destructive": "#D83A52",
"foreground": "#f8fafc",
"input": "#303642",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#5236FF",
"primary-foreground": "#ffffff",
"radius": "10px",
"ring": "#FF5B2E",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"sidebar": "#181b22",
"sidebar-accent": "#FF5B2E",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#5236FF",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#FF5B2E"
},
"light": {
"accent": "#FF5B2E",
"accent-foreground": "#ffffff",
"background": "#F8F7F3",
"border": "#D9DDE5",
"card": "#FFFFFF",
"card-foreground": "#17181C",
"chart-1": "#5236FF",
"chart-2": "#00AFC7",
"chart-3": "#FF5B2E",
"chart-4": "#10A36F",
"chart-5": "#D99000",
"destructive": "#D83A52",
"foreground": "#17181C",
"input": "#D9DDE5",
"muted": "#6D7280",
"muted-foreground": "#17181C",
"popover": "#FFFFFF",
"popover-foreground": "#17181C",
"primary": "#5236FF",
"primary-foreground": "#ffffff",
"radius": "10px",
"ring": "#FF5B2E",
"secondary": "#00AFC7",
"secondary-foreground": "#ffffff",
"sidebar": "#FFFFFF",
"sidebar-accent": "#2774E8",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#D9DDE5",
"sidebar-foreground": "#17181C",
"sidebar-primary": "#5236FF",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#FF5B2E"
},
"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-019e4686-2b06-7c02-bbd2-cb00c978ec30",
"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-register-studio",
"source": "katagami"
},
"name": "prism-register-studio",
"title": "Prism Register Studio shadcn Theme",
"type": "registry:theme"
}
# Prism Register Studio shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4686-2b06-7c02-bbd2-cb00c978ec30`
Slug: `prism-register-studio`
## Intent
Prism Register Studio is a clean creative-tool interface language for exact controls, preview work, layers, and annotations on calm white surfaces. It rejects rainbow decoration by treating bright color as registered pixel sparks: small calibrated markers that identify state, focus, and authored changes.
## 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": "#FF5B2E",
"background": "#F8F7F3",
"border": "#D9DDE5",
"error": "#D83A52",
"info": "#2774E8",
"muted": "#6D7280",
"primary": "#5236FF",
"secondary": "#00AFC7",
"success": "#10A36F",
"surface": "#FFFFFF",
"text": "#17181C",
"warning": "#D99000"
}
Typography:
{
"base_size": "16px",
"body_font": "Inter",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=Inter:wght@400;500;600;700&family=Sora:wght@500;600;700&display=swap",
"heading_font": "Sora",
"letter_spacing": "-0.018em",
"line_height": 1.48,
"mono_font": "IBM Plex Mono",
"scale_ratio": 1.22
}
## Visual character to preserve
- Use layered white and warm-neutral panels with 1px cool-gray borders, compact 14px control rows, and a right-side preview canvas rather than heavy card stacks.
- Place accent color only in small registered pixel chips, 6px square handles, mini swatches, focus ticks, and annotation glyphs aligned to content edges, never as side rails.
- Build icons and status marks from stepped rectilinear SVG/CSS shapes with clipped inside corners while keeping containers mostly 10px rounded rectangles.
- Use thin black typographic hierarchy with a technical sans body, mono numeric labels, and tight negative heading tracking for a premium creative-product feel.
- Create hover and active states with tiny chromatic offset shadows and one-pixel positional snaps instead of large glows, gradients, or decorative confetti.
## ShadSync visual profile
{
"family": "system",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": true,
"motion": "still",
"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-register-studio/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 bright accents as functional pixels for active tools, annotations, focus, progress, and edit deltas.; Keep surfaces white, warm neutral, and opaque with exact hairline borders and committed radius geometry.; Let mono labels, handles, layer chips, and preview metadata carry the subtle pixel-art influence.; Design real creative-product scenes with layers, tools, previews, comments, versions, and coordinates.
- Do not: Do not use square-grid backgrounds, rainbow sprawl, arbitrary confetti, neon cyberpunk, or retro arcade motifs.; Do not put decorative colored side rails or stripes on cards, buttons, rows, or panels.; Do not make every icon blocky or oversized; pixel details must remain small, sparse, and useful.; Do not rely on color alone for state; pair accents with labels, outlines, handles, or icons.
## 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 PrismRegisterStudioShadcnKit() {
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 Register Studio</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-1024px, desktop >= 1025px",
"grid": "Desktop uses a 72px tool rail, minmax(260px, 320px) control column, fluid preview canvas, and 300px inspector; tablet stacks inspector below canvas; mobile turns rails into segmented top controls.",
"whitespace": "Whitespace is calm around previews and tighter around controls; preserve 24px panel gaps on desktop and 16px gaps on smaller screens so color sparks stay meaningful."
}
{
"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-019e4686-2b06-7c02-bbd2-cb00c978ec30",
"name": "Prism Register Studio",
"slug": "prism-register-studio"
},
"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 layered white and warm-neutral panels with 1px cool-gray borders, compact 14px control rows, and a right-side preview canvas rather than heavy card stacks.",
"Place accent color only in small registered pixel chips, 6px square handles, mini swatches, focus ticks, and annotation glyphs aligned to content edges, never as side rails.",
"Build icons and status marks from stepped rectilinear SVG/CSS shapes with clipped inside corners while keeping containers mostly 10px rounded rectangles.",
"Use thin black typographic hierarchy with a technical sans body, mono numeric labels, and tight negative heading tracking for a premium creative-product feel.",
"Create hover and active states with tiny chromatic offset shadows and one-pixel positional snaps instead of large glows, gradients, or decorative confetti."
],
"visualProfile": {
"family": "system",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": false,
"stickerBadges": true,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "Prism Register Studio 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 bright accents as functional pixels for active tools, annotations, focus, progress, and edit deltas.",
"Keep surfaces white, warm neutral, and opaque with exact hairline borders and committed radius geometry.",
"Let mono labels, handles, layer chips, and preview metadata carry the subtle pixel-art influence.",
"Design real creative-product scenes with layers, tools, previews, comments, versions, and coordinates."
],
"dont": [
"Do not use square-grid backgrounds, rainbow sprawl, arbitrary confetti, neon cyberpunk, or retro arcade motifs.",
"Do not put decorative colored side rails or stripes on cards, buttons, rows, or panels.",
"Do not make every icon blocky or oversized; pixel details must remain small, sparse, and useful.",
"Do not rely on color alone for state; pair accents with labels, outlines, handles, or icons."
]
}
}