back to gallery
design language·forensic-memory-glass-consoles

Forensic Memory Glass Consoles

A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.

Download DESIGN.md

Portable DESIGN.md source of truth for most agents and apps.

the spec

specification

philosophy
summary
Forensic Memory Glass Consoles is a clinical cybernetic language for acquiring, verifying, and reading volatile evidence through pale optical material. It treats the interface as a lens over a memory image: most of the screen stays white, quiet, and almost empty while smoked contours, blue-white specular edges, and tiny red/orange exception marks identify what must be handled with legal or medical care. The mood is not hacker spectacle; it is a sterile chain-of-custody room where every line exists because evidence integrity depends on it.
values
Evidence before expression: decorative marks are removed unless they clarify acquisition, provenance, hash integrity, or exception handling.Optical calm: frosted whites, translucent overlays, and high negative space make the console feel like calibrated glass rather than a glowing dashboard.Procedural trust: every status has a label, timestamp, hash fragment, and visible verification relationship rather than relying on color alone.Manga-structural precision: black contour lines, registration ticks, cutaway brackets, and numbered callouts create technical drama without character art.Low-refresh seriousness: motion is stepped, brief, and diagnostic, suitable for e-ink, wearable optics, fixed-resolution canvases, and medical consoles.Sparse signal color: blue-white is reserved for optical focus and active evidence paths; red/orange appears only for legal hold, anomaly, or clinical risk.
anti-values
×No green matrix rain, terminal cosplay, neon cyberpunk glow, or generic hacker dashboard density.×No SaaS card grids, equal analytics tiles, sales charts, or decorative data walls that confuse evidence procedure with business intelligence.×No character fan art, dramatic avatars, or illustrative cyberpunk scenes; the console itself is the protagonist.×No rainbow status palettes or gratuitous gradients; every hue must belong to the optical-white forensic palette.
tokens
borders4 items
accent width
2px
character
Hairline smoked black structural contours with blue-white specular top rails and tiny red/orange exception cuts.
default width
1px
style
solid
colors12 items
accent
#AEEBFF
background
#F8FAFB
border
#CBD5DC
error
#C8462C
info
#77DDF5
muted
#6D7A83
primary
#111820
secondary
#DDE6EC
success
#566B62
surface
#FFFFFF
text
#111820
warning
#D36B1F
motion3 items
duration
120ms
easing
steps(2, end)
philosophy
Motion behaves like low-refresh diagnostic confirmation: stepped focus changes, no swoops, no parallax spectacle, and reduced-motion safe by default.
radii5 items
full
9999px
lg
24px
md
16px
none
0px
sm
0px
shadows3 items
lg
0 36px 110px rgba(17,24,32,0.12)
md
0 22px 70px rgba(17,24,32,0.08)
sm
0 1px 0 rgba(255,255,255,0.86) inset
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64, 96, 128
surfaces3 items
bg pattern
Nearly invisible 32px grid plus sparse registration ticks and contour leaders, never a busy data wall.
card style
No generic cards; use evidence lenses with squared smoked corner brackets, 1px borders, inset highlights, and visible hash labels.
treatment
Optical white background, frosted acrylic slabs at rgba(255,255,255,0.68), smoked contour overlays, and restrained backdrop blur.
typography9 items
base size
16px
body font
Afacad
display letter spacing
-0.04em
google fonts url
https://fonts.googleapis.com/css2?family=Afacad:wght@400;500;600&family=Saira+Condensed:wght@500;600;700&family=Spline+Sans+Mono:wght@400;500;600&display=swap
heading font
Saira Condensed
letter spacing
-0.02em
line height
1.56
mono font
Spline Sans Mono
scale ratio
1.22
rules
composition
Use an asymmetric forensic workstation rather than a dashboard: one oversized memory-lens pane owns the page, a thin chain-of-custody rail hugs one side, and smaller diagnostic strips interrupt the grid. Preserve one large empty quarantine field. Let contour lines cross from the pane into labels so structure, not color, organizes the scene. Never arrange three equal cards; subordinate panes must differ in scale, density, and placement.
density
Overall density is low, with 60-70 percent quiet optical white. Dense information may appear only in procedure rails, hash bands, or memory offset tables. Tight 4px tick spacing can coexist with 96px quarantine whitespace so the system feels procedural instead of uniformly padded.
hierarchy
The display voice is condensed, uppercase, and tightly tracked for case titles and acquisition states. Body copy is calm, 15-16px, and sparse. Monospace appears only for hashes, offsets, timestamps, evidence IDs, and checksum fragments. Active hierarchy is shown through position, line weight, and blue-white edge glints; legal or medical exceptions use a small red/orange mark plus a text label.
signature patterns
Evidence-lens panels use ::before and ::after corner brackets, inset white highlights, backdrop-filter blur, and a smoked contour border to read as frosted glass over memory.Specular chain rails are 1px blue-white lines that connect active evidence nodes and stop at verification labels, creating optical HUD depth without neon blocks.Manga schematic leaders extend across panels as absolute hairlines with tiny numbered capsules, turning empty space into a technical cutaway drawing.Exception micro-marks are 6px red/orange slivers or dots attached to legal/medical labels, never full warning banners or large colored cards.Low-refresh diagnostics render as stepped segmented bars, hash grids, and offset ticks that look frozen and auditable rather than animated or gamified.
layout
breakpoints
desktop
1024px+
mobile
0-599px
tablet
600-1023px
density

Low-density optical shell with one dense rail and one dense hash band; the contrast between 4px tick clusters and 96px white fields is mandatory.

grid
Desktop uses a 12-column max-width 1320px grid with 24px gutters: dominant lens spans 7-8 columns, custody rail spans 3, and procedure strips break across columns. Tablet collapses to 6 columns; mobile becomes a single column with the custody rail after the primary lens.
responsive
Maintain the dominant memory pane first, then stack procedure, exceptions, and offset tables. Hide decorative continuation lines on narrow screens while preserving labels and borders.
whitespace
Whitespace is evidence quarantine, not blank filler. Leave wide empty fields around critical panes and use tiny labels at the edges to prove the emptiness is intentional.
guidance
do
  • Start from optical white and frosted translucent overlays; make the interface feel like a calibrated forensic lens.
  • Use smoked black contours, corner brackets, leader lines, and registration ticks as the primary structural signature.
  • Reserve blue-white accent for active focus rails, verified evidence paths, and specular panel edges.
  • Use red/orange only for legal hold, medical exception, anomaly, or anti-forensic risk and always pair it with text.
  • Show hashes, offsets, timestamps, custody states, acquisition mode, and integrity verification as first-class content.
  • Create asymmetric compositions with one dominant pane and one dense procedural rail, never equal SaaS cards.
  • Keep motion stepped and minimal so the language works for e-ink, wearable optics, and low-refresh diagnostic displays.
  • Let high negative space carry authority; do not fill blank areas with charts or decorative telemetry.
avoid
  • Do not use green matrix rain, terminal wallpaper, neon cyberpunk gradients, or hacker-room atmosphere.
  • Do not build generic analytics dashboards, CRM summaries, KPI cards, or three equal feature tiles.
  • Do not use character illustrations, fan art, avatars, or manga figures; manga influence must be structural linework only.
  • Do not add busy data walls, rainbow status systems, large warning panels, or decorative map noise.
  • Do not round every element into soft SaaS cards; radii are either square/zero or deliberate 16/24px glass containers.
  • Do not rely on color alone for state; legal, clinical, and integrity conditions need labels and structural changes.
  • Do not use broad glow effects; blue-white appears as hairline glints and rails, not neon tubes.
katagami spec
# Forensic Memory Glass Consoles

## Philosophy

Forensic Memory Glass Consoles is a clinical cybernetic language for acquiring, verifying, and reading volatile evidence through pale optical material. It treats the interface as a lens over a memory image: most of the screen stays white, quiet, and almost empty while smoked contours, blue-white specular edges, and tiny red/orange exception marks identify what must be handled with legal or medical care. The mood is not hacker spectacle; it is a sterile chain-of-custody room where every line exists because evidence integrity depends on it.

### Values

- Evidence before expression: decorative marks are removed unless they clarify acquisition, provenance, hash integrity, or exception handling.
- Optical calm: frosted whites, translucent overlays, and high negative space make the console feel like calibrated glass rather than a glowing dashboard.
- Procedural trust: every status has a label, timestamp, hash fragment, and visible verification relationship rather than relying on color alone.
- Manga-structural precision: black contour lines, registration ticks, cutaway brackets, and numbered callouts create technical drama without character art.
- Low-refresh seriousness: motion is stepped, brief, and diagnostic, suitable for e-ink, wearable optics, fixed-resolution canvases, and medical consoles.
- Sparse signal color: blue-white is reserved for optical focus and active evidence paths; red/orange appears only for legal hold, anomaly, or clinical risk.

### Anti-Values

- No green matrix rain, terminal cosplay, neon cyberpunk glow, or generic hacker dashboard density.
- No SaaS card grids, equal analytics tiles, sales charts, or decorative data walls that confuse evidence procedure with business intelligence.
- No character fan art, dramatic avatars, or illustrative cyberpunk scenes; the console itself is the protagonist.
- No rainbow status palettes or gratuitous gradients; every hue must belong to the optical-white forensic palette.

### Visual Character

- Large optical-white canvas with fixed-position translucent glass slabs using backdrop-filter blur, inset white highlights, and no more than one faint shadow layer.
- Smoked black contour rules draw bracketed evidence compartments, crosshair registration ticks, and manga-style leader lines that continue across panel boundaries.
- Blue-white specular edges appear as 1px top borders, focus rails, and thin glints on active memory paths rather than broad neon fills or glowing blocks.
- Tiny red/orange exception chips are constrained to 6-10px marks, legal badges, and short underline fragments paired with text labels and hash references.
- Asymmetric evidence-lens layout: one dominant memory pane is offset against narrow procedure rails, leaving a deliberate empty quarantine field.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Hairline smoked black structural contours with blue-white specular top rails and tiny red/orange exception cuts.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#AEEBFF` |
| background | `#F8FAFB` |
| border | `#CBD5DC` |
| error | `#C8462C` |
| info | `#77DDF5` |
| muted | `#6D7A83` |
| primary | `#111820` |
| secondary | `#DDE6EC` |
| success | `#566B62` |
| surface | `#FFFFFF` |
| text | `#111820` |
| warning | `#D36B1F` |

### Motion

- **Duration**: 120ms
- **Easing**: steps(2, end)
- **Philosophy**: Motion behaves like low-refresh diagnostic confirmation: stepped focus changes, no swoops, no parallax spectacle, and reduced-motion safe by default.

### Radii

- **Full**: 9999px
- **Lg**: 24px
- **Md**: 16px
- **None**: 0px
- **Sm**: 0px

### Shadows

- **Lg**: 0 36px 110px rgba(17,24,32,0.12)
- **Md**: 0 22px 70px rgba(17,24,32,0.08)
- **Sm**: 0 1px 0 rgba(255,255,255,0.86) inset

### Spacing

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

### Surfaces

- **Bg Pattern**: Nearly invisible 32px grid plus sparse registration ticks and contour leaders, never a busy data wall.
- **Card Style**: No generic cards; use evidence lenses with squared smoked corner brackets, 1px borders, inset highlights, and visible hash labels.
- **Treatment**: Optical white background, frosted acrylic slabs at rgba(255,255,255,0.68), smoked contour overlays, and restrained backdrop blur.

### Typography

- **Base Size**: 16px
- **Body Font**: Afacad
- **Display Letter Spacing**: -0.04em
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Afacad:wght@400;500;600&family=Saira+Condensed:wght@500;600;700&family=Spline+Sans+Mono:wght@400;500;600&display=swap
- **Heading Font**: Saira Condensed
- **Letter Spacing**: -0.02em
- **Line Height**: 1.56
- **Mono Font**: Spline Sans Mono
- **Scale Ratio**: 1.22

## Rules

### Composition

Use an asymmetric forensic workstation rather than a dashboard: one oversized memory-lens pane owns the page, a thin chain-of-custody rail hugs one side, and smaller diagnostic strips interrupt the grid. Preserve one large empty quarantine field. Let contour lines cross from the pane into labels so structure, not color, organizes the scene. Never arrange three equal cards; subordinate panes must differ in scale, density, and placement.

### Density

Overall density is low, with 60-70 percent quiet optical white. Dense information may appear only in procedure rails, hash bands, or memory offset tables. Tight 4px tick spacing can coexist with 96px quarantine whitespace so the system feels procedural instead of uniformly padded.

### Hierarchy

The display voice is condensed, uppercase, and tightly tracked for case titles and acquisition states. Body copy is calm, 15-16px, and sparse. Monospace appears only for hashes, offsets, timestamps, evidence IDs, and checksum fragments. Active hierarchy is shown through position, line weight, and blue-white edge glints; legal or medical exceptions use a small red/orange mark plus a text label.

### Signature Patterns

- Evidence-lens panels use ::before and ::after corner brackets, inset white highlights, backdrop-filter blur, and a smoked contour border to read as frosted glass over memory.
- Specular chain rails are 1px blue-white lines that connect active evidence nodes and stop at verification labels, creating optical HUD depth without neon blocks.
- Manga schematic leaders extend across panels as absolute hairlines with tiny numbered capsules, turning empty space into a technical cutaway drawing.
- Exception micro-marks are 6px red/orange slivers or dots attached to legal/medical labels, never full warning banners or large colored cards.
- Low-refresh diagnostics render as stepped segmented bars, hash grids, and offset ticks that look frozen and auditable rather than animated or gamified.

## Layout

### Breakpoints

- **Desktop**: 1024px+
- **Mobile**: 0-599px
- **Tablet**: 600-1023px

### Density

Low-density optical shell with one dense rail and one dense hash band; the contrast between 4px tick clusters and 96px white fields is mandatory.

### Grid

Desktop uses a 12-column max-width 1320px grid with 24px gutters: dominant lens spans 7-8 columns, custody rail spans 3, and procedure strips break across columns. Tablet collapses to 6 columns; mobile becomes a single column with the custody rail after the primary lens.

### Responsive

Maintain the dominant memory pane first, then stack procedure, exceptions, and offset tables. Hide decorative continuation lines on narrow screens while preserving labels and borders.

### Whitespace

Whitespace is evidence quarantine, not blank filler. Leave wide empty fields around critical panes and use tiny labels at the edges to prove the emptiness is intentional.

## Guidance

### Do

- Start from optical white and frosted translucent overlays; make the interface feel like a calibrated forensic lens.
- Use smoked black contours, corner brackets, leader lines, and registration ticks as the primary structural signature.
- Reserve blue-white accent for active focus rails, verified evidence paths, and specular panel edges.
- Use red/orange only for legal hold, medical exception, anomaly, or anti-forensic risk and always pair it with text.
- Show hashes, offsets, timestamps, custody states, acquisition mode, and integrity verification as first-class content.
- Create asymmetric compositions with one dominant pane and one dense procedural rail, never equal SaaS cards.
- Keep motion stepped and minimal so the language works for e-ink, wearable optics, and low-refresh diagnostic displays.
- Let high negative space carry authority; do not fill blank areas with charts or decorative telemetry.

### Don't

- Do not use green matrix rain, terminal wallpaper, neon cyberpunk gradients, or hacker-room atmosphere.
- Do not build generic analytics dashboards, CRM summaries, KPI cards, or three equal feature tiles.
- Do not use character illustrations, fan art, avatars, or manga figures; manga influence must be structural linework only.
- Do not add busy data walls, rainbow status systems, large warning panels, or decorative map noise.
- Do not round every element into soft SaaS cards; radii are either square/zero or deliberate 16/24px glass containers.
- Do not rely on color alone for state; legal, clinical, and integrity conditions need labels and structural changes.
- Do not use broad glow effects; blue-white appears as hairline glints and rails, not neon tubes.

### Accessibility

Body text remains 15-16px with strong smoked-black contrast on white. Blue-white and red/orange state marks are always paired with text, icons, line weight, or placement. Focus outlines use dark contour plus cyan rail. Reduced motion disables all transitions because the stepped diagnostic state must still be understandable when static.

### Usage Context

Best for forensic memory acquisition tools, cold archive readers, post-human medical consoles, wearable evidence HUDs, chain-of-custody review stations, and austere identity operating systems where precision and restraint matter more than spectacle.
DESIGN.md
---
version: "alpha"
name: "Forensic Memory Glass Consoles"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#AEEBFF"
  background: "#F8FAFB"
  border: "#CBD5DC"
  error: "#C8462C"
  info: "#77DDF5"
  muted: "#6D7A83"
  primary: "#111820"
  secondary: "#DDE6EC"
  success: "#566B62"
  surface: "#FFFFFF"
  text: "#111820"
  warning: "#D36B1F"
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: "Afacad"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.56
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "Spline Sans Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "24px"
  md: "16px"
  none: "0px"
  sm: "0px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
  step-8: "96px"
  step-9: "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: "#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"
---

# Forensic Memory Glass Consoles

## Overview

Forensic Memory Glass Consoles is a clinical cybernetic language for acquiring, verifying, and reading volatile evidence through pale optical material. It treats the interface as a lens over a memory image: most of the screen stays white, quiet, and almost empty while smoked contours, blue-white specular edges, and tiny red/orange exception marks identify what must be handled with legal or medical care. The mood is not hacker spectacle; it is a sterile chain-of-custody room where every line exists because evidence integrity depends on it.

### Values

- Evidence before expression: decorative marks are removed unless they clarify acquisition, provenance, hash integrity, or exception handling.
- Optical calm: frosted whites, translucent overlays, and high negative space make the console feel like calibrated glass rather than a glowing dashboard.
- Procedural trust: every status has a label, timestamp, hash fragment, and visible verification relationship rather than relying on color alone.
- Manga-structural precision: black contour lines, registration ticks, cutaway brackets, and numbered callouts create technical drama without character art.
- Low-refresh seriousness: motion is stepped, brief, and diagnostic, suitable for e-ink, wearable optics, fixed-resolution canvases, and medical consoles.
- Sparse signal color: blue-white is reserved for optical focus and active evidence paths; red/orange appears only for legal hold, anomaly, or clinical risk.

### Anti-Values

- No green matrix rain, terminal cosplay, neon cyberpunk glow, or generic hacker dashboard density.
- No SaaS card grids, equal analytics tiles, sales charts, or decorative data walls that confuse evidence procedure with business intelligence.
- No character fan art, dramatic avatars, or illustrative cyberpunk scenes; the console itself is the protagonist.
- No rainbow status palettes or gratuitous gradients; every hue must belong to the optical-white forensic palette.

### Visual Character

- Large optical-white canvas with fixed-position translucent glass slabs using backdrop-filter blur, inset white highlights, and no more than one faint shadow layer.
- Smoked black contour rules draw bracketed evidence compartments, crosshair registration ticks, and manga-style leader lines that continue across panel boundaries.
- Blue-white specular edges appear as 1px top borders, focus rails, and thin glints on active memory paths rather than broad neon fills or glowing blocks.
- Tiny red/orange exception chips are constrained to 6-10px marks, legal badges, and short underline fragments paired with text labels and hash references.
- Asymmetric evidence-lens layout: one dominant memory pane is offset against narrow procedure rails, leaving a deliberate empty quarantine field.

## 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 | `#AEEBFF` |
| background | `#F8FAFB` |
| border | `#CBD5DC` |
| error | `#C8462C` |
| info | `#77DDF5` |
| muted | `#6D7A83` |
| primary | `#111820` |
| secondary | `#DDE6EC` |
| success | `#566B62` |
| surface | `#FFFFFF` |
| text | `#111820` |
| warning | `#D36B1F` |

## 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**: Afacad, 16px, weight 400, line-height 1.56.
- **Label-Md**: Spline Sans Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

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

### Breakpoints

- **Desktop**: 1024px+
- **Mobile**: 0-599px
- **Tablet**: 600-1023px

### Density

Low-density optical shell with one dense rail and one dense hash band; the contrast between 4px tick clusters and 96px white fields is mandatory.

### Grid

Desktop uses a 12-column max-width 1320px grid with 24px gutters: dominant lens spans 7-8 columns, custody rail spans 3, and procedure strips break across columns. Tablet collapses to 6 columns; mobile becomes a single column with the custody rail after the primary lens.

### Responsive

Maintain the dominant memory pane first, then stack procedure, exceptions, and offset tables. Hide decorative continuation lines on narrow screens while preserving labels and borders.

### Whitespace

Whitespace is evidence quarantine, not blank filler. Leave wide empty fields around critical panes and use tiny labels at the edges to prove the emptiness is intentional.

## Elevation & Depth

### Shadows

- **Lg**: 0 36px 110px rgba(17,24,32,0.12)
- **Md**: 0 22px 70px rgba(17,24,32,0.08)
- **Sm**: 0 1px 0 rgba(255,255,255,0.86) inset

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `24px`
- **Md**: `16px`
- **None**: `0px`
- **Sm**: `0px`

### Surfaces

- **Bg Pattern**: Nearly invisible 32px grid plus sparse registration ticks and contour leaders, never a busy data wall.
- **Card Style**: No generic cards; use evidence lenses with squared smoked corner brackets, 1px borders, inset highlights, and visible hash labels.
- **Treatment**: Optical white background, frosted acrylic slabs at rgba(255,255,255,0.68), smoked contour overlays, and restrained backdrop blur.

### Borders

- **Accent Width**: 2px
- **Character**: Hairline smoked black structural contours with blue-white specular top rails and tiny red/orange exception cuts.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Use an asymmetric forensic workstation rather than a dashboard: one oversized memory-lens pane owns the page, a thin chain-of-custody rail hugs one side, and smaller diagnostic strips interrupt the grid. Preserve one large empty quarantine field. Let contour lines cross from the pane into labels so structure, not color, organizes the scene. Never arrange three equal cards; subordinate panes must differ in scale, density, and placement.

### Density

Overall density is low, with 60-70 percent quiet optical white. Dense information may appear only in procedure rails, hash bands, or memory offset tables. Tight 4px tick spacing can coexist with 96px quarantine whitespace so the system feels procedural instead of uniformly padded.

### Hierarchy

The display voice is condensed, uppercase, and tightly tracked for case titles and acquisition states. Body copy is calm, 15-16px, and sparse. Monospace appears only for hashes, offsets, timestamps, evidence IDs, and checksum fragments. Active hierarchy is shown through position, line weight, and blue-white edge glints; legal or medical exceptions use a small red/orange mark plus a text label.

### Signature Patterns

- Evidence-lens panels use ::before and ::after corner brackets, inset white highlights, backdrop-filter blur, and a smoked contour border to read as frosted glass over memory.
- Specular chain rails are 1px blue-white lines that connect active evidence nodes and stop at verification labels, creating optical HUD depth without neon blocks.
- Manga schematic leaders extend across panels as absolute hairlines with tiny numbered capsules, turning empty space into a technical cutaway drawing.
- Exception micro-marks are 6px red/orange slivers or dots attached to legal/medical labels, never full warning banners or large colored cards.
- Low-refresh diagnostics render as stepped segmented bars, hash grids, and offset ticks that look frozen and auditable rather than animated or gamified.

## 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/forensic-memory-glass-consoles/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 Start from optical white and frosted translucent overlays; make the interface feel like a calibrated forensic lens.
- Do Use smoked black contours, corner brackets, leader lines, and registration ticks as the primary structural signature.
- Do Reserve blue-white accent for active focus rails, verified evidence paths, and specular panel edges.
- Do Use red/orange only for legal hold, medical exception, anomaly, or anti-forensic risk and always pair it with text.
- Do Show hashes, offsets, timestamps, custody states, acquisition mode, and integrity verification as first-class content.
- Do Create asymmetric compositions with one dominant pane and one dense procedural rail, never equal SaaS cards.
- Do Keep motion stepped and minimal so the language works for e-ink, wearable optics, and low-refresh diagnostic displays.
- Do Let high negative space carry authority; do not fill blank areas with charts or decorative telemetry.
- Don't Do not use green matrix rain, terminal wallpaper, neon cyberpunk gradients, or hacker-room atmosphere.
- Don't Do not build generic analytics dashboards, CRM summaries, KPI cards, or three equal feature tiles.
- Don't Do not use character illustrations, fan art, avatars, or manga figures; manga influence must be structural linework only.
- Don't Do not add busy data walls, rainbow status systems, large warning panels, or decorative map noise.
- Don't Do not round every element into soft SaaS cards; radii are either square/zero or deliberate 16/24px glass containers.
- Don't Do not rely on color alone for state; legal, clinical, and integrity conditions need labels and structural changes.
- Don't Do not use broad glow effects; blue-white appears as hairline glints and rails, not neon tubes.

### Accessibility

Body text remains 15-16px with strong smoked-black contrast on white. Blue-white and red/orange state marks are always paired with text, icons, line weight, or placement. Focus outlines use dark contour plus cyan rail. Reduced motion disables all transitions because the stepped diagnostic state must still be understandable when static.

### Usage Context

Best for forensic memory acquisition tools, cold archive readers, post-human medical consoles, wearable evidence HUDs, chain-of-custody review stations, and austere identity operating systems where precision and restraint matter more than spectacle.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "forensic-memory-glass-consoles",
  "type": "registry:theme",
  "title": "Forensic Memory Glass Consoles shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F8FAFB",
      "foreground": "#111820",
      "card": "#FFFFFF",
      "card-foreground": "#111820",
      "popover": "#FFFFFF",
      "popover-foreground": "#111820",
      "primary": "#111820",
      "primary-foreground": "#ffffff",
      "secondary": "#DDE6EC",
      "secondary-foreground": "#111111",
      "muted": "#6D7A83",
      "muted-foreground": "#111820",
      "accent": "#AEEBFF",
      "accent-foreground": "#111111",
      "destructive": "#C8462C",
      "border": "#CBD5DC",
      "input": "#CBD5DC",
      "ring": "#AEEBFF",
      "chart-1": "#111820",
      "chart-2": "#DDE6EC",
      "chart-3": "#AEEBFF",
      "chart-4": "#566B62",
      "chart-5": "#D36B1F",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#111820",
      "sidebar-primary": "#111820",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#77DDF5",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#CBD5DC",
      "sidebar-ring": "#AEEBFF",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111820",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#AEEBFF",
      "accent-foreground": "#111111",
      "destructive": "#C8462C",
      "border": "#303642",
      "input": "#303642",
      "ring": "#AEEBFF",
      "chart-1": "#111820",
      "chart-2": "#DDE6EC",
      "chart-3": "#AEEBFF",
      "chart-4": "#566B62",
      "chart-5": "#D36B1F",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111820",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#AEEBFF",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#AEEBFF",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "forensic-memory-glass-consoles",
    "slug": "forensic-memory-glass-consoles",
    "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",
        "display_letter_spacing",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · forensic-memory-glass-consoles
DESIGN.md

at a glance

Palette

Typography

headline-lgSaira Condensed · 29px · 700

The quick brown fox jumps

headline-mdSaira Condensed · 24px · 600

The quick brown fox jumps

body-mdAfacad · 16px · 400

The quick brown fox jumps

label-mdSpline Sans Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

Components rendered with this language’s tokens — colors, type, and rounded corners as specified.

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl48px
  • 4xl64px
  • step-896px
  • step-9128px

Shape

full9999px
lg24px
md16px
none0px
sm0px
shadcn/ui

implementation kit

needs agent-authored kitcompatibility fallback
shadcn compatibility only
The generated theme variables are available, but the polished shadcn component recipes and shots have not been authored by the Katagami agent yet.
fallbackprimitives render
Compatibility proof
Local shadcn-style primitives accept the generated theme variables.
primaryaccentsurfacemutedwarningerror
table rhythm
buttonok
cardok
inputok
recommendedcompatibility fallback

DESIGN.md with shadcn

Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.

advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #F8FAFB;
  --foreground: #111820;
  --card: #FFFFFF;
  --card-foreground: #111820;
  --popover: #FFFFFF;
  --popover-foreground: #111820;
  --primary: #111820;
  --primary-foreground: #ffffff;
  --secondary: #DDE6EC;
  --secondary-foreground: #111111;
  --muted: #6D7A83;
  --muted-foreground: #111820;
  --accent: #AEEBFF;
  --accent-foreground: #111111;
  --destructive: #C8462C;
  --border: #CBD5DC;
  --input: #CBD5DC;
  --ring: #AEEBFF;
  --chart-1: #111820;
  --chart-2: #DDE6EC;
  --chart-3: #AEEBFF;
  --chart-4: #566B62;
  --chart-5: #D36B1F;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #111820;
  --sidebar-primary: #111820;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #77DDF5;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #CBD5DC;
  --sidebar-ring: #AEEBFF;
  --radius: 16px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #111820;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #AEEBFF;
  --accent-foreground: #111111;
  --destructive: #C8462C;
  --border: #303642;
  --input: #303642;
  --ring: #AEEBFF;
  --chart-1: #111820;
  --chart-2: #DDE6EC;
  --chart-3: #AEEBFF;
  --chart-4: #566B62;
  --chart-5: #D36B1F;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #111820;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #AEEBFF;
  --sidebar-accent-foreground: #111111;
  --sidebar-border: #303642;
  --sidebar-ring: #AEEBFF;
  --radius: 16px;
}
tsx starter
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
  Card,
  CardContent,
  CardDescription,
  CardFooter,
  CardHeader,
  CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";

export function ForensicMemoryGlassConsolesShadcnKit() {
  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">Forensic Memory Glass Consoles</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

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

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
theme JSONcompatibility fallback
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "forensic-memory-glass-consoles",
  "type": "registry:theme",
  "title": "Forensic Memory Glass Consoles shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F8FAFB",
      "foreground": "#111820",
      "card": "#FFFFFF",
      "card-foreground": "#111820",
      "popover": "#FFFFFF",
      "popover-foreground": "#111820",
      "primary": "#111820",
      "primary-foreground": "#ffffff",
      "secondary": "#DDE6EC",
      "secondary-foreground": "#111111",
      "muted": "#6D7A83",
      "muted-foreground": "#111820",
      "accent": "#AEEBFF",
      "accent-foreground": "#111111",
      "destructive": "#C8462C",
      "border": "#CBD5DC",
      "input": "#CBD5DC",
      "ring": "#AEEBFF",
      "chart-1": "#111820",
      "chart-2": "#DDE6EC",
      "chart-3": "#AEEBFF",
      "chart-4": "#566B62",
      "chart-5": "#D36B1F",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#111820",
      "sidebar-primary": "#111820",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#77DDF5",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#CBD5DC",
      "sidebar-ring": "#AEEBFF",
      "radius": "16px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#111820",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#AEEBFF",
      "accent-foreground": "#111111",
      "destructive": "#C8462C",
      "border": "#303642",
      "input": "#303642",
      "ring": "#AEEBFF",
      "chart-1": "#111820",
      "chart-2": "#DDE6EC",
      "chart-3": "#AEEBFF",
      "chart-4": "#566B62",
      "chart-5": "#D36B1F",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#111820",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#AEEBFF",
      "sidebar-accent-foreground": "#111111",
      "sidebar-border": "#303642",
      "sidebar-ring": "#AEEBFF",
      "radius": "16px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "forensic-memory-glass-consoles",
    "slug": "forensic-memory-glass-consoles",
    "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",
        "display_letter_spacing",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
component recipescompatibility fallback
# Forensic Memory Glass Consoles shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `forensic-memory-glass-consoles`
Slug: `forensic-memory-glass-consoles`

## Intent

Forensic Memory Glass Consoles is a clinical cybernetic language for acquiring, verifying, and reading volatile evidence through pale optical material. It treats the interface as a lens over a memory image: most of the screen stays white, quiet, and almost empty while smoked contours, blue-white specular edges, and tiny red/orange exception marks identify what must be handled with legal or medical care. The mood is not hacker spectacle; it is a sterile chain-of-custody room where every line exists because evidence integrity depends on it.

## 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": "#AEEBFF",
  "background": "#F8FAFB",
  "border": "#CBD5DC",
  "error": "#C8462C",
  "info": "#77DDF5",
  "muted": "#6D7A83",
  "primary": "#111820",
  "secondary": "#DDE6EC",
  "success": "#566B62",
  "surface": "#FFFFFF",
  "text": "#111820",
  "warning": "#D36B1F"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Afacad",
  "display_letter_spacing": "-0.04em",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Afacad:wght@400;500;600&family=Saira+Condensed:wght@500;600;700&family=Spline+Sans+Mono:wght@400;500;600&display=swap",
  "heading_font": "Saira Condensed",
  "letter_spacing": "-0.02em",
  "line_height": 1.56,
  "mono_font": "Spline Sans Mono",
  "scale_ratio": 1.22
}

## Visual character to preserve

- Large optical-white canvas with fixed-position translucent glass slabs using backdrop-filter blur, inset white highlights, and no more than one faint shadow layer.
- Smoked black contour rules draw bracketed evidence compartments, crosshair registration ticks, and manga-style leader lines that continue across panel boundaries.
- Blue-white specular edges appear as 1px top borders, focus rails, and thin glints on active memory paths rather than broad neon fills or glowing blocks.
- Tiny red/orange exception chips are constrained to 6-10px marks, legal badges, and short underline fragments paired with text labels and hash references.
- Asymmetric evidence-lens layout: one dominant memory pane is offset against narrow procedure rails, leaving a deliberate empty quarantine field.

## ShadSync visual profile

{
  "family": "system",
  "material": "flat",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": false,
  "stickerBadges": true,
  "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/forensic-memory-glass-consoles/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: Start from optical white and frosted translucent overlays; make the interface feel like a calibrated forensic lens.; Use smoked black contours, corner brackets, leader lines, and registration ticks as the primary structural signature.; Reserve blue-white accent for active focus rails, verified evidence paths, and specular panel edges.; Use red/orange only for legal hold, medical exception, anomaly, or anti-forensic risk and always pair it with text.; Show hashes, offsets, timestamps, custody states, acquisition mode, and integrity verification as first-class content.; Create asymmetric compositions with one dominant pane and one dense procedural rail, never equal SaaS cards.; Keep motion stepped and minimal so the language works for e-ink, wearable optics, and low-refresh diagnostic displays.; Let high negative space carry authority; do not fill blank areas with charts or decorative telemetry.
- Do not: Do not use green matrix rain, terminal wallpaper, neon cyberpunk gradients, or hacker-room atmosphere.; Do not build generic analytics dashboards, CRM summaries, KPI cards, or three equal feature tiles.; Do not use character illustrations, fan art, avatars, or manga figures; manga influence must be structural linework only.; Do not add busy data walls, rainbow status systems, large warning panels, or decorative map noise.; Do not round every element into soft SaaS cards; radii are either square/zero or deliberate 16/24px glass containers.; Do not rely on color alone for state; legal, clinical, and integrity conditions need labels and structural changes.; Do not use broad glow effects; blue-white appears as hairline glints and rails, not neon tubes.

## 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 ForensicMemoryGlassConsolesShadcnKit() {
  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">Forensic Memory Glass Consoles</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-599px",
    "tablet": "600-1023px"
  },
  "density": "Low-density optical shell with one dense rail and one dense hash band; the contrast between 4px tick clusters and 96px white fields is mandatory.",
  "grid": "Desktop uses a 12-column max-width 1320px grid with 24px gutters: dominant lens spans 7-8 columns, custody rail spans 3, and procedure strips break across columns. Tablet collapses to 6 columns; mobile becomes a single column with the custody rail after the primary lens.",
  "responsive": "Maintain the dominant memory pane first, then stack procedure, exceptions, and offset tables. Hide decorative continuation lines on narrow screens while preserving labels and borders.",
  "whitespace": "Whitespace is evidence quarantine, not blank filler. Leave wide empty fields around critical panes and use tiny labels at the edges to prove the emptiness is intentional."
}
preview shotscompatibility fallback
{
  "artifact": "katagami:shadcn-preview-shots",
  "version": "preview-shots-v1",
  "generator": "katagami-ui-compatibility-projection",
  "generatedBy": "katagami-ui-projection",
  "requiresVisualProfile": true,
  "schema": "katagami:shadcn-preview-shots/renderable-v1",
  "renderable": true,
  "language": {
    "id": "forensic-memory-glass-consoles",
    "name": "Forensic Memory Glass Consoles",
    "slug": "forensic-memory-glass-consoles"
  },
  "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": [
    "Large optical-white canvas with fixed-position translucent glass slabs using backdrop-filter blur, inset white highlights, and no more than one faint shadow layer.",
    "Smoked black contour rules draw bracketed evidence compartments, crosshair registration ticks, and manga-style leader lines that continue across panel boundaries.",
    "Blue-white specular edges appear as 1px top borders, focus rails, and thin glints on active memory paths rather than broad neon fills or glowing blocks.",
    "Tiny red/orange exception chips are constrained to 6-10px marks, legal badges, and short underline fragments paired with text labels and hash references.",
    "Asymmetric evidence-lens layout: one dominant memory pane is offset against narrow procedure rails, leaving a deliberate empty quarantine field."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": false,
    "stickerBadges": true,
    "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": "Forensic Memory Glass Consoles 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": [
      "Start from optical white and frosted translucent overlays; make the interface feel like a calibrated forensic lens.",
      "Use smoked black contours, corner brackets, leader lines, and registration ticks as the primary structural signature.",
      "Reserve blue-white accent for active focus rails, verified evidence paths, and specular panel edges.",
      "Use red/orange only for legal hold, medical exception, anomaly, or anti-forensic risk and always pair it with text.",
      "Show hashes, offsets, timestamps, custody states, acquisition mode, and integrity verification as first-class content.",
      "Create asymmetric compositions with one dominant pane and one dense procedural rail, never equal SaaS cards.",
      "Keep motion stepped and minimal so the language works for e-ink, wearable optics, and low-refresh diagnostic displays.",
      "Let high negative space carry authority; do not fill blank areas with charts or decorative telemetry."
    ],
    "dont": [
      "Do not use green matrix rain, terminal wallpaper, neon cyberpunk gradients, or hacker-room atmosphere.",
      "Do not build generic analytics dashboards, CRM summaries, KPI cards, or three equal feature tiles.",
      "Do not use character illustrations, fan art, avatars, or manga figures; manga influence must be structural linework only.",
      "Do not add busy data walls, rainbow status systems, large warning panels, or decorative map noise.",
      "Do not round every element into soft SaaS cards; radii are either square/zero or deliberate 16/24px glass containers.",
      "Do not rely on color alone for state; legal, clinical, and integrity conditions need labels and structural changes.",
      "Do not use broad glow effects; blue-white appears as hairline glints and rails, not neon tubes."
    ]
  }
}
related

More like this