Optic Shellcode Pearl Grid
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
- 1px
- character
- near-invisible rgba hairlines plus detached bracket corners, never chunky outlines
- default width
- 1px
- style
- solid
colors12 items
motion3 items
- duration
- 220ms
- easing
- cubic-bezier(.16,1,.3,1)
- philosophy
- Motion is optical acquisition: slight line brightening, tiny translate shifts, and scan opacity changes rather than bouncy movement.
radii5 items
- full
- 9999px
- lg
- 0px
- md
- 0px
- none
- 0px
- sm
- 0px
shadows3 items
- lg
- 0 40px 140px rgba(142,217,232,0.12), 0 0 0 1px rgba(255,255,255,0.12)
- md
- 0 24px 80px rgba(0,0,0,0.38), inset 0 1px 0 rgba(255,255,255,0.48)
- sm
- 0 0 0 1px rgba(255,255,255,0.08)
spacing2 items
- base
- 8px
- scale
- 2, 4, 8, 12, 16, 24, 32, 48, 64, 96, 128
surfaces3 items
- bg pattern
- Subtle scan grid from linear gradients at 32px intervals, masked so it appears in diagnostic zones only.
- card style
- Square-edged glass panes with hairline white borders, bracket pseudo-elements, and cropped terminal labels.
- treatment
- Ink black base with flat white manga slabs and translucent pearl overlays using backdrop-filter: blur(18px) saturate(120%).
typography8 items
- base size
- 16px
- body font
- IBM Plex Sans
- google fonts url
- https://fonts.googleapis.com/css2?family=Saira+Condensed:wght@500;600;700&family=IBM+Plex+Sans:wght@400;500;600&family=Fragment+Mono:ital@0;1&display=swap
- heading font
- Saira Condensed
- letter spacing
- -0.02em
- line height
- 1.55
- mono font
- Fragment Mono
- scale ratio
- 1.22
rules
Use a 12-column field with one oversized quiet void, one dense command rail, one cropped manga-white slab, and several floating diagnostic panes. Break the grid with a vertical identity aperture or a full-height code strip. Keep major alignment exact while allowing content windows to crop at edges as if captured by a surveillance camera.
Overall density is low, but density clusters into terminal rails and cyberbrain diagrams. The language needs an 8:1 spacing rhythm: 4px tick gaps beside 96px voids, compact diagnostics beside broad empty manga panels.
Hierarchy is built from scale contrast and luminance: condensed title-card headings at large sizes, small uppercase technical labels, mono command fragments, then quiet body copy. Cyan is reserved for active terminal data and recognition states. Red appears only as single-pixel warnings or status glyphs.
layout
- desktop
- 1024px+
- mobile
- 0-639px
- tablet
- 640-1023px
Low global density with deliberate high-density islands. The primary viewport should feel more like an intercepted cinematic interface than a dashboard.
Desktop uses 12 columns with 24px gutters and max-width 1360px; tablet collapses to 8 columns; mobile becomes a single stacked scan with the command rail moving below the hero.
Maintain the signature bracket corners and scan grids at all sizes; reduce title-card scale and stack translucent panes without turning them into equal cards.
Preserve 64px to 128px quiet zones around the identity aperture; use 4px to 12px gaps only inside diagnostics and shell logs.
guidance
- Use square-edged translucent panels over ink black or flat white manga fields.
- Reserve pale cyan for active terminal states, command prompts, scan lines, and node highlights.
- Compose asymmetrically with one dominant void and one dense diagnostic strip.
- Build bracket corners as detached thin rules so the interface feels like recognition optics.
- Crop code windows and captions at panel edges to imply a larger machine outside the frame.
- Use condensed anime title-card typography sparingly for scene naming and system identity.
- Keep body copy short, technical, and existential rather than promotional.
- Favor hairline borders, hard rectangular cuts, and frosted blur over rounded cards.
- Do not use purple, magenta, lime, or rainbow cyberpunk palettes.
- Do not create three equal cards in a row or a generic SaaS dashboard grid.
- Do not mix rounded radii; this language is square except for tiny circular nodes.
- Do not fill every void with decoration, data, or illustration.
- Do not use thick grey borders, heavy shadows, gradient buttons, or glowing CTAs.
- Do not make code decorative wallpaper; every command fragment should read like system evidence.
- Do not soften the tone with playful icons, friendly copy, or consumer onboarding patterns.
- Do not combine one-sided accent borders with rounded surfaces.
katagami spec
# Optic Shellcode Pearl Grid ## Philosophy Optic Shellcode Pearl Grid is a restrained cinematic interface language for synthetic-body systems that feel watched rather than decorated. It translates Ghost-in-the-Shell shellcode minimalism into polished product structure: black manga fields, translucent pearl panels, pale cyan command overlays, recognition brackets, and diagnostic typography that leaves large areas of silence. The system treats every element as evidence inside a surveillance aperture; surfaces are glassy but almost colorless, code is present but sparse, and composition favors philosophical pause over cyberpunk spectacle. ### Values - Silence as signal: large black and white fields are allowed to remain empty so the few interface marks feel deliberate. - Synthetic embodiment: panels behave like frosted optical camouflage over a body, map, or network rather than generic cards. - Forensic precision: brackets, crosshair ticks, node links, and scan grids align to a strict coordinate system. - Low-saturation glow: cyan is used as terminal luminance, not as neon decoration or marketing color. - Manga-panel severity: black ink blocks and thin white rules provide narrative rhythm without illustration clutter. - Operational melancholy: labels sound like logs, shells, and identity checks, implying a larger system beyond the screen. ### Anti-Values - No rainbow cyberpunk, saturated neon triads, purple-pink nightclub gradients, or excessive bloom. - No generic analytics dashboard cards, rounded SaaS widgets, or equal-weight component catalog layouts. - No decorative code waterfalls; command fragments must be sparse, cropped, and tied to interface function. - No warm lifestyle softness, emoji tone, playful blobs, or consumer app friendliness. ### Visual Character - Asymmetric 12-column precision grid with one dominant black manga field and smaller translucent panels offset across it. - Frosted pearl glass surfaces using backdrop-filter blur, near-white translucency, and hairline rgba borders over ink black. - Recognition-bracket corner marks built from absolutely positioned thin vector lines around panels and identity targets. - Sparse terminal fragments in a dedicated monospace rail with pale cyan text, cropped overflow, and tiny red warning pixels. - Optical camouflage fades created by masked scan grids, low-opacity contour lines, and clipped white panels dissolving into black. ## Tokens ### Borders - **Accent Width**: 1px - **Character**: near-invisible rgba hairlines plus detached bracket corners, never chunky outlines - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#8ED9E8` | | background | `#030506` | | border | `#FFFFFF` | | error | `#C64D52` | | info | `#8ED9E8` | | muted | `#829296` | | primary | `#EAF7FA` | | secondary | `#9FB8BD` | | success | `#A7C8BE` | | surface | `#F5F8F7` | | text | `#F7FAF9` | | warning | `#C8B981` | ### Motion - **Duration**: 220ms - **Easing**: cubic-bezier(.16,1,.3,1) - **Philosophy**: Motion is optical acquisition: slight line brightening, tiny translate shifts, and scan opacity changes rather than bouncy movement. ### Radii - **Full**: 9999px - **Lg**: 0px - **Md**: 0px - **None**: 0px - **Sm**: 0px ### Shadows - **Lg**: 0 40px 140px rgba(142,217,232,0.12), 0 0 0 1px rgba(255,255,255,0.12) - **Md**: 0 24px 80px rgba(0,0,0,0.38), inset 0 1px 0 rgba(255,255,255,0.48) - **Sm**: 0 0 0 1px rgba(255,255,255,0.08) ### Spacing - **Base**: 8px - **Scale**: [2,4,8,12,16,24,32,48,64,96,128] ### Surfaces - **Bg Pattern**: Subtle scan grid from linear gradients at 32px intervals, masked so it appears in diagnostic zones only. - **Card Style**: Square-edged glass panes with hairline white borders, bracket pseudo-elements, and cropped terminal labels. - **Treatment**: Ink black base with flat white manga slabs and translucent pearl overlays using backdrop-filter: blur(18px) saturate(120%). ### Typography - **Base Size**: 16px - **Body Font**: IBM Plex Sans - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Saira+Condensed:wght@500;600;700&family=IBM+Plex+Sans:wght@400;500;600&family=Fragment+Mono:ital@0;1&display=swap - **Heading Font**: Saira Condensed - **Letter Spacing**: -0.02em - **Line Height**: 1.55 - **Mono Font**: Fragment Mono - **Scale Ratio**: 1.22 ## Rules ### Composition Use a 12-column field with one oversized quiet void, one dense command rail, one cropped manga-white slab, and several floating diagnostic panes. Break the grid with a vertical identity aperture or a full-height code strip. Keep major alignment exact while allowing content windows to crop at edges as if captured by a surveillance camera. ### Density Overall density is low, but density clusters into terminal rails and cyberbrain diagrams. The language needs an 8:1 spacing rhythm: 4px tick gaps beside 96px voids, compact diagnostics beside broad empty manga panels. ### Hierarchy Hierarchy is built from scale contrast and luminance: condensed title-card headings at large sizes, small uppercase technical labels, mono command fragments, then quiet body copy. Cyan is reserved for active terminal data and recognition states. Red appears only as single-pixel warnings or status glyphs. ### Signature Patterns - Bracketed glass panes: each major surface receives detached L-shaped corner rules made with pseudo-elements instead of ordinary card borders. - Camouflage dissolve masks: pearl panels fade through repeating scan lines and clipped white overlays that appear to dematerialize into black. - Shellcode rail: a narrow cropped terminal column uses pale cyan monospace commands, line numbers, and overflow hidden as a permanent compositional spine. - Cyberbrain node diagram: thin vector lines connect small hollow nodes inside a quiet panel, with one red pixel interrupting the network. - Manga surveillance aperture: a dominant black or white rectangular field is crossed by tiny recognition ticks and sparse coordinate captions. ## Layout ### Breakpoints - **Desktop**: 1024px+ - **Mobile**: 0-639px - **Tablet**: 640-1023px ### Density Low global density with deliberate high-density islands. The primary viewport should feel more like an intercepted cinematic interface than a dashboard. ### Grid Desktop uses 12 columns with 24px gutters and max-width 1360px; tablet collapses to 8 columns; mobile becomes a single stacked scan with the command rail moving below the hero. ### Responsive Maintain the signature bracket corners and scan grids at all sizes; reduce title-card scale and stack translucent panes without turning them into equal cards. ### Whitespace Preserve 64px to 128px quiet zones around the identity aperture; use 4px to 12px gaps only inside diagnostics and shell logs. ## Guidance ### Do - Use square-edged translucent panels over ink black or flat white manga fields. - Reserve pale cyan for active terminal states, command prompts, scan lines, and node highlights. - Compose asymmetrically with one dominant void and one dense diagnostic strip. - Build bracket corners as detached thin rules so the interface feels like recognition optics. - Crop code windows and captions at panel edges to imply a larger machine outside the frame. - Use condensed anime title-card typography sparingly for scene naming and system identity. - Keep body copy short, technical, and existential rather than promotional. - Favor hairline borders, hard rectangular cuts, and frosted blur over rounded cards. ### Don't - Do not use purple, magenta, lime, or rainbow cyberpunk palettes. - Do not create three equal cards in a row or a generic SaaS dashboard grid. - Do not mix rounded radii; this language is square except for tiny circular nodes. - Do not fill every void with decoration, data, or illustration. - Do not use thick grey borders, heavy shadows, gradient buttons, or glowing CTAs. - Do not make code decorative wallpaper; every command fragment should read like system evidence. - Do not soften the tone with playful icons, friendly copy, or consumer onboarding patterns. - Do not combine one-sided accent borders with rounded surfaces. ### Accessibility Maintain crisp contrast between pearl panels and black fields, keep cyan text above AA contrast on dark surfaces, never rely on red alone for alerts, and preserve readable 15-16px body sizes. ### Usage Context Best for cinematic security tools, cybernetic identity checks, shell terminals, AI embodiment research, network surveillance maps, and experimental editorial screens about synthetic life.
DESIGN.md
---
version: "alpha"
name: "Optic Shellcode Pearl Grid"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#8ED9E8"
background: "#030506"
border: "#FFFFFF"
error: "#C64D52"
info: "#8ED9E8"
muted: "#829296"
primary: "#EAF7FA"
secondary: "#9FB8BD"
success: "#A7C8BE"
surface: "#F5F8F7"
text: "#F7FAF9"
warning: "#C8B981"
typography:
headline-lg:
fontFamily: "Saira Condensed"
fontSize: "1.816rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.02em"
headline-md:
fontFamily: "Saira Condensed"
fontSize: "1.488rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.02em"
body-md:
fontFamily: "IBM Plex Sans"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.55
letterSpacing: "-0.02em"
label-md:
fontFamily: "Fragment Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
full: "9999px"
lg: "0px"
md: "0px"
none: "0px"
sm: "0px"
spacing:
base: "8px"
xs: "2px"
sm: "4px"
md: "8px"
lg: "12px"
xl: "16px"
2xl: "24px"
3xl: "32px"
4xl: "48px"
step-8: "64px"
step-9: "96px"
step-10: "128px"
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: "#000000"
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"
---
# Optic Shellcode Pearl Grid
## Overview
Optic Shellcode Pearl Grid is a restrained cinematic interface language for synthetic-body systems that feel watched rather than decorated. It translates Ghost-in-the-Shell shellcode minimalism into polished product structure: black manga fields, translucent pearl panels, pale cyan command overlays, recognition brackets, and diagnostic typography that leaves large areas of silence. The system treats every element as evidence inside a surveillance aperture; surfaces are glassy but almost colorless, code is present but sparse, and composition favors philosophical pause over cyberpunk spectacle.
### Values
- Silence as signal: large black and white fields are allowed to remain empty so the few interface marks feel deliberate.
- Synthetic embodiment: panels behave like frosted optical camouflage over a body, map, or network rather than generic cards.
- Forensic precision: brackets, crosshair ticks, node links, and scan grids align to a strict coordinate system.
- Low-saturation glow: cyan is used as terminal luminance, not as neon decoration or marketing color.
- Manga-panel severity: black ink blocks and thin white rules provide narrative rhythm without illustration clutter.
- Operational melancholy: labels sound like logs, shells, and identity checks, implying a larger system beyond the screen.
### Anti-Values
- No rainbow cyberpunk, saturated neon triads, purple-pink nightclub gradients, or excessive bloom.
- No generic analytics dashboard cards, rounded SaaS widgets, or equal-weight component catalog layouts.
- No decorative code waterfalls; command fragments must be sparse, cropped, and tied to interface function.
- No warm lifestyle softness, emoji tone, playful blobs, or consumer app friendliness.
### Visual Character
- Asymmetric 12-column precision grid with one dominant black manga field and smaller translucent panels offset across it.
- Frosted pearl glass surfaces using backdrop-filter blur, near-white translucency, and hairline rgba borders over ink black.
- Recognition-bracket corner marks built from absolutely positioned thin vector lines around panels and identity targets.
- Sparse terminal fragments in a dedicated monospace rail with pale cyan text, cropped overflow, and tiny red warning pixels.
- Optical camouflage fades created by masked scan grids, low-opacity contour lines, and clipped white panels dissolving into black.
## 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 | `#8ED9E8` |
| background | `#030506` |
| border | `#FFFFFF` |
| error | `#C64D52` |
| info | `#8ED9E8` |
| muted | `#829296` |
| primary | `#EAF7FA` |
| secondary | `#9FB8BD` |
| success | `#A7C8BE` |
| surface | `#F5F8F7` |
| text | `#F7FAF9` |
| warning | `#C8B981` |
## Typography
- **Headline-Lg**: Saira Condensed, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Saira Condensed, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans, 16px, weight 400, line-height 1.55.
- **Label-Md**: Fragment Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `2px`
- **Sm**: `4px`
- **Md**: `8px`
- **Lg**: `12px`
- **Xl**: `16px`
- **2xl**: `24px`
- **3xl**: `32px`
- **4xl**: `48px`
- **Step-8**: `64px`
- **Step-9**: `96px`
- **Step-10**: `128px`
### Breakpoints
- **Desktop**: 1024px+
- **Mobile**: 0-639px
- **Tablet**: 640-1023px
### Density
Low global density with deliberate high-density islands. The primary viewport should feel more like an intercepted cinematic interface than a dashboard.
### Grid
Desktop uses 12 columns with 24px gutters and max-width 1360px; tablet collapses to 8 columns; mobile becomes a single stacked scan with the command rail moving below the hero.
### Responsive
Maintain the signature bracket corners and scan grids at all sizes; reduce title-card scale and stack translucent panes without turning them into equal cards.
### Whitespace
Preserve 64px to 128px quiet zones around the identity aperture; use 4px to 12px gaps only inside diagnostics and shell logs.
## Elevation & Depth
### Shadows
- **Lg**: 0 40px 140px rgba(142,217,232,0.12), 0 0 0 1px rgba(255,255,255,0.12)
- **Md**: 0 24px 80px rgba(0,0,0,0.38), inset 0 1px 0 rgba(255,255,255,0.48)
- **Sm**: 0 0 0 1px rgba(255,255,255,0.08)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `0px`
- **Md**: `0px`
- **None**: `0px`
- **Sm**: `0px`
### Surfaces
- **Bg Pattern**: Subtle scan grid from linear gradients at 32px intervals, masked so it appears in diagnostic zones only.
- **Card Style**: Square-edged glass panes with hairline white borders, bracket pseudo-elements, and cropped terminal labels.
- **Treatment**: Ink black base with flat white manga slabs and translucent pearl overlays using backdrop-filter: blur(18px) saturate(120%).
### Borders
- **Accent Width**: 1px
- **Character**: near-invisible rgba hairlines plus detached bracket corners, never chunky outlines
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Use a 12-column field with one oversized quiet void, one dense command rail, one cropped manga-white slab, and several floating diagnostic panes. Break the grid with a vertical identity aperture or a full-height code strip. Keep major alignment exact while allowing content windows to crop at edges as if captured by a surveillance camera.
### Density
Overall density is low, but density clusters into terminal rails and cyberbrain diagrams. The language needs an 8:1 spacing rhythm: 4px tick gaps beside 96px voids, compact diagnostics beside broad empty manga panels.
### Hierarchy
Hierarchy is built from scale contrast and luminance: condensed title-card headings at large sizes, small uppercase technical labels, mono command fragments, then quiet body copy. Cyan is reserved for active terminal data and recognition states. Red appears only as single-pixel warnings or status glyphs.
### Signature Patterns
- Bracketed glass panes: each major surface receives detached L-shaped corner rules made with pseudo-elements instead of ordinary card borders.
- Camouflage dissolve masks: pearl panels fade through repeating scan lines and clipped white overlays that appear to dematerialize into black.
- Shellcode rail: a narrow cropped terminal column uses pale cyan monospace commands, line numbers, and overflow hidden as a permanent compositional spine.
- Cyberbrain node diagram: thin vector lines connect small hollow nodes inside a quiet panel, with one red pixel interrupting the network.
- Manga surveillance aperture: a dominant black or white rectangular field is crossed by tiny recognition ticks and sparse coordinate captions.
## 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/optic-shellcode-pearl-grid/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 square-edged translucent panels over ink black or flat white manga fields.
- Do Reserve pale cyan for active terminal states, command prompts, scan lines, and node highlights.
- Do Compose asymmetrically with one dominant void and one dense diagnostic strip.
- Do Build bracket corners as detached thin rules so the interface feels like recognition optics.
- Do Crop code windows and captions at panel edges to imply a larger machine outside the frame.
- Do Use condensed anime title-card typography sparingly for scene naming and system identity.
- Do Keep body copy short, technical, and existential rather than promotional.
- Do Favor hairline borders, hard rectangular cuts, and frosted blur over rounded cards.
- Don't Do not use purple, magenta, lime, or rainbow cyberpunk palettes.
- Don't Do not create three equal cards in a row or a generic SaaS dashboard grid.
- Don't Do not mix rounded radii; this language is square except for tiny circular nodes.
- Don't Do not fill every void with decoration, data, or illustration.
- Don't Do not use thick grey borders, heavy shadows, gradient buttons, or glowing CTAs.
- Don't Do not make code decorative wallpaper; every command fragment should read like system evidence.
- Don't Do not soften the tone with playful icons, friendly copy, or consumer onboarding patterns.
- Don't Do not combine one-sided accent borders with rounded surfaces.
### Accessibility
Maintain crisp contrast between pearl panels and black fields, keep cyan text above AA contrast on dark surfaces, never rely on red alone for alerts, and preserve readable 15-16px body sizes.
### Usage Context
Best for cinematic security tools, cybernetic identity checks, shell terminals, AI embodiment research, network surveillance maps, and experimental editorial screens about synthetic life.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "optic-shellcode-pearl-grid",
"type": "registry:theme",
"title": "Optic Shellcode Pearl Grid shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#030506",
"foreground": "#F7FAF9",
"card": "#F5F8F7",
"card-foreground": "#F7FAF9",
"popover": "#F5F8F7",
"popover-foreground": "#F7FAF9",
"primary": "#EAF7FA",
"primary-foreground": "#111111",
"secondary": "#9FB8BD",
"secondary-foreground": "#ffffff",
"muted": "#829296",
"muted-foreground": "#F7FAF9",
"accent": "#8ED9E8",
"accent-foreground": "#111111",
"destructive": "#C64D52",
"border": "#FFFFFF",
"input": "#FFFFFF",
"ring": "#8ED9E8",
"chart-1": "#EAF7FA",
"chart-2": "#9FB8BD",
"chart-3": "#8ED9E8",
"chart-4": "#A7C8BE",
"chart-5": "#C8B981",
"sidebar": "#F5F8F7",
"sidebar-foreground": "#F7FAF9",
"sidebar-primary": "#EAF7FA",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#8ED9E8",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#FFFFFF",
"sidebar-ring": "#8ED9E8",
"radius": "0px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#EAF7FA",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#8ED9E8",
"accent-foreground": "#111111",
"destructive": "#C64D52",
"border": "#303642",
"input": "#303642",
"ring": "#8ED9E8",
"chart-1": "#EAF7FA",
"chart-2": "#9FB8BD",
"chart-3": "#8ED9E8",
"chart-4": "#A7C8BE",
"chart-5": "#C8B981",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#EAF7FA",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#8ED9E8",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#8ED9E8",
"radius": "0px"
}
},
"meta": {
"source": "katagami",
"languageId": "optic-shellcode-pearl-grid",
"slug": "optic-shellcode-pearl-grid",
"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
- xs2px
- sm4px
- md8px
- lg12px
- xl16px
- 2xl24px
- 3xl32px
- 4xl48px
- step-864px
- step-996px
- step-10128px
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: #030506;
--foreground: #F7FAF9;
--card: #F5F8F7;
--card-foreground: #F7FAF9;
--popover: #F5F8F7;
--popover-foreground: #F7FAF9;
--primary: #EAF7FA;
--primary-foreground: #111111;
--secondary: #9FB8BD;
--secondary-foreground: #ffffff;
--muted: #829296;
--muted-foreground: #F7FAF9;
--accent: #8ED9E8;
--accent-foreground: #111111;
--destructive: #C64D52;
--border: #FFFFFF;
--input: #FFFFFF;
--ring: #8ED9E8;
--chart-1: #EAF7FA;
--chart-2: #9FB8BD;
--chart-3: #8ED9E8;
--chart-4: #A7C8BE;
--chart-5: #C8B981;
--sidebar: #F5F8F7;
--sidebar-foreground: #F7FAF9;
--sidebar-primary: #EAF7FA;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #8ED9E8;
--sidebar-accent-foreground: #111111;
--sidebar-border: #FFFFFF;
--sidebar-ring: #8ED9E8;
--radius: 0px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #EAF7FA;
--primary-foreground: #111111;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #8ED9E8;
--accent-foreground: #111111;
--destructive: #C64D52;
--border: #303642;
--input: #303642;
--ring: #8ED9E8;
--chart-1: #EAF7FA;
--chart-2: #9FB8BD;
--chart-3: #8ED9E8;
--chart-4: #A7C8BE;
--chart-5: #C8B981;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #EAF7FA;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #8ED9E8;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #8ED9E8;
--radius: 0px;
}
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 OpticShellcodePearlGridShadcnKit() {
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">Optic Shellcode Pearl Grid</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",
"name": "optic-shellcode-pearl-grid",
"type": "registry:theme",
"title": "Optic Shellcode Pearl Grid shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#030506",
"foreground": "#F7FAF9",
"card": "#F5F8F7",
"card-foreground": "#F7FAF9",
"popover": "#F5F8F7",
"popover-foreground": "#F7FAF9",
"primary": "#EAF7FA",
"primary-foreground": "#111111",
"secondary": "#9FB8BD",
"secondary-foreground": "#ffffff",
"muted": "#829296",
"muted-foreground": "#F7FAF9",
"accent": "#8ED9E8",
"accent-foreground": "#111111",
"destructive": "#C64D52",
"border": "#FFFFFF",
"input": "#FFFFFF",
"ring": "#8ED9E8",
"chart-1": "#EAF7FA",
"chart-2": "#9FB8BD",
"chart-3": "#8ED9E8",
"chart-4": "#A7C8BE",
"chart-5": "#C8B981",
"sidebar": "#F5F8F7",
"sidebar-foreground": "#F7FAF9",
"sidebar-primary": "#EAF7FA",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#8ED9E8",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#FFFFFF",
"sidebar-ring": "#8ED9E8",
"radius": "0px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#EAF7FA",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#8ED9E8",
"accent-foreground": "#111111",
"destructive": "#C64D52",
"border": "#303642",
"input": "#303642",
"ring": "#8ED9E8",
"chart-1": "#EAF7FA",
"chart-2": "#9FB8BD",
"chart-3": "#8ED9E8",
"chart-4": "#A7C8BE",
"chart-5": "#C8B981",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#EAF7FA",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#8ED9E8",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#8ED9E8",
"radius": "0px"
}
},
"meta": {
"source": "katagami",
"languageId": "optic-shellcode-pearl-grid",
"slug": "optic-shellcode-pearl-grid",
"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"
]
}
}
}
# Optic Shellcode Pearl Grid shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `optic-shellcode-pearl-grid`
Slug: `optic-shellcode-pearl-grid`
## Intent
Optic Shellcode Pearl Grid is a restrained cinematic interface language for synthetic-body systems that feel watched rather than decorated. It translates Ghost-in-the-Shell shellcode minimalism into polished product structure: black manga fields, translucent pearl panels, pale cyan command overlays, recognition brackets, and diagnostic typography that leaves large areas of silence. The system treats every element as evidence inside a surveillance aperture; surfaces are glassy but almost colorless, code is present but sparse, and composition favors philosophical pause over cyberpunk spectacle.
## 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": "#8ED9E8",
"background": "#030506",
"border": "#FFFFFF",
"error": "#C64D52",
"info": "#8ED9E8",
"muted": "#829296",
"primary": "#EAF7FA",
"secondary": "#9FB8BD",
"success": "#A7C8BE",
"surface": "#F5F8F7",
"text": "#F7FAF9",
"warning": "#C8B981"
}
Typography:
{
"base_size": "16px",
"body_font": "IBM Plex Sans",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Saira+Condensed:wght@500;600;700&family=IBM+Plex+Sans:wght@400;500;600&family=Fragment+Mono:ital@0;1&display=swap",
"heading_font": "Saira Condensed",
"letter_spacing": "-0.02em",
"line_height": 1.55,
"mono_font": "Fragment Mono",
"scale_ratio": 1.22
}
## Visual character to preserve
- Asymmetric 12-column precision grid with one dominant black manga field and smaller translucent panels offset across it.
- Frosted pearl glass surfaces using backdrop-filter blur, near-white translucency, and hairline rgba borders over ink black.
- Recognition-bracket corner marks built from absolutely positioned thin vector lines around panels and identity targets.
- Sparse terminal fragments in a dedicated monospace rail with pale cyan text, cropped overflow, and tiny red warning pixels.
- Optical camouflage fades created by masked scan grids, low-opacity contour lines, and clipped white panels dissolving into black.
## ShadSync visual profile
{
"family": "brutalist",
"material": "ink",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": false,
"stickerBadges": false,
"motion": "still",
"density": "balanced",
"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/optic-shellcode-pearl-grid/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 square-edged translucent panels over ink black or flat white manga fields.; Reserve pale cyan for active terminal states, command prompts, scan lines, and node highlights.; Compose asymmetrically with one dominant void and one dense diagnostic strip.; Build bracket corners as detached thin rules so the interface feels like recognition optics.; Crop code windows and captions at panel edges to imply a larger machine outside the frame.; Use condensed anime title-card typography sparingly for scene naming and system identity.; Keep body copy short, technical, and existential rather than promotional.; Favor hairline borders, hard rectangular cuts, and frosted blur over rounded cards.
- Do not: Do not use purple, magenta, lime, or rainbow cyberpunk palettes.; Do not create three equal cards in a row or a generic SaaS dashboard grid.; Do not mix rounded radii; this language is square except for tiny circular nodes.; Do not fill every void with decoration, data, or illustration.; Do not use thick grey borders, heavy shadows, gradient buttons, or glowing CTAs.; Do not make code decorative wallpaper; every command fragment should read like system evidence.; Do not soften the tone with playful icons, friendly copy, or consumer onboarding patterns.; Do not combine one-sided accent borders with rounded surfaces.
## 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 OpticShellcodePearlGridShadcnKit() {
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">Optic Shellcode Pearl Grid</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
```
## Layout notes
{
"breakpoints": {
"desktop": "1024px+",
"mobile": "0-639px",
"tablet": "640-1023px"
},
"density": "Low global density with deliberate high-density islands. The primary viewport should feel more like an intercepted cinematic interface than a dashboard.",
"grid": "Desktop uses 12 columns with 24px gutters and max-width 1360px; tablet collapses to 8 columns; mobile becomes a single stacked scan with the command rail moving below the hero.",
"responsive": "Maintain the signature bracket corners and scan grids at all sizes; reduce title-card scale and stack translucent panes without turning them into equal cards.",
"whitespace": "Preserve 64px to 128px quiet zones around the identity aperture; use 4px to 12px gaps only inside diagnostics and shell logs."
}
{
"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": "optic-shellcode-pearl-grid",
"name": "Optic Shellcode Pearl Grid",
"slug": "optic-shellcode-pearl-grid"
},
"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": [
"Asymmetric 12-column precision grid with one dominant black manga field and smaller translucent panels offset across it.",
"Frosted pearl glass surfaces using backdrop-filter blur, near-white translucency, and hairline rgba borders over ink black.",
"Recognition-bracket corner marks built from absolutely positioned thin vector lines around panels and identity targets.",
"Sparse terminal fragments in a dedicated monospace rail with pale cyan text, cropped overflow, and tiny red warning pixels.",
"Optical camouflage fades created by masked scan grids, low-opacity contour lines, and clipped white panels dissolving into black."
],
"visualProfile": {
"family": "brutalist",
"material": "ink",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": false,
"stickerBadges": false,
"motion": "still",
"density": "balanced",
"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": "Optic Shellcode Pearl Grid 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 square-edged translucent panels over ink black or flat white manga fields.",
"Reserve pale cyan for active terminal states, command prompts, scan lines, and node highlights.",
"Compose asymmetrically with one dominant void and one dense diagnostic strip.",
"Build bracket corners as detached thin rules so the interface feels like recognition optics.",
"Crop code windows and captions at panel edges to imply a larger machine outside the frame.",
"Use condensed anime title-card typography sparingly for scene naming and system identity.",
"Keep body copy short, technical, and existential rather than promotional.",
"Favor hairline borders, hard rectangular cuts, and frosted blur over rounded cards."
],
"dont": [
"Do not use purple, magenta, lime, or rainbow cyberpunk palettes.",
"Do not create three equal cards in a row or a generic SaaS dashboard grid.",
"Do not mix rounded radii; this language is square except for tiny circular nodes.",
"Do not fill every void with decoration, data, or illustration.",
"Do not use thick grey borders, heavy shadows, gradient buttons, or glowing CTAs.",
"Do not make code decorative wallpaper; every command fragment should read like system evidence.",
"Do not soften the tone with playful icons, friendly copy, or consumer onboarding patterns.",
"Do not combine one-sided accent borders with rounded surfaces."
]
}
}