back to gallerydo avoid
design language·white-room-intrusion-kit
White-Room Intrusion Kit
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
White-Room Intrusion Kit treats security assessment as a sterile diagnostic procedure rather than a heroic breach fantasy. The interface feels like a sealed lab appliance opened to reveal black schematic bones: off-white panels, absolute black hairlines, calibrated gutters, and tiny cyan evidence marks that appear only where an exploit hypothesis has touched the system. Its cultural references are disciplined rather than nostalgic: minimal black-and-white manga panel logic, late-1990s hardware manuals, quiet terminal windows, and speculative cybernetics translated into calm assessment tooling. The point of view is clinical restraint: no cyberpunk glow, no hacker costume, no generic monitoring dashboard, and no decorative color beyond semantic intrusion coordinates.
values
Evidence before drama: accent color is reserved for verified breach coordinates, active cursors, checksum ticks, and current probe focus.Appliance-like calm: surfaces should feel sealed, white, quiet, and engineered rather than expressive or entertainment-oriented.Schematic authority: hairline black rules, port maps, numeric strings, and ruler marks create credibility without ornamental dashboards.Hands-off diagnostics: the user is positioned as a researcher operating probes and checklists, not as a heroic hacker avatar.Black-and-white reproduction discipline: every screen must remain legible and distinctive if the cyan marks are removed or printed monochrome.Asymmetrical precision: manga-like panels and technical callouts create movement while retaining rational 2x grid spacing.Terminal restraint: command transcripts are quiet, sparse, and typographically modest instead of immersive green code theatrics.
anti-values
×No green matrix rain, violet neon, rainbow glow, or cyberpunk city ambience.×No hoodie hackers, skull malware mascots, anime fan art figures, or heroic character illustration.×No SaaS card grids, generic SOC dashboards, glossy status tiles, or decorative analytics widgets.×No techno display fonts, oversized glowing type, glassmorphism, or gradient spectacle.×No gratuitous red-alert panic; risk states remain measured, documented, and procedural.
tokens
borders4 items
- accent width
- 2px
- character
- absolute-black hairlines with occasional thick outer manga frames and clipped callout notches
- default width
- 1px
- style
- solid
colors12 items
accent
#00A9C7
background
#F6F2EA
border
#111111
error
#9B1C1C
info
#007E95
muted
#6F6A61
primary
#0B0B0B
secondary
#EEE8DE
success
#2F6B45
surface
#FFFDF8
text
#090909
warning
#9A6A12
motion3 items
- duration
- 160ms
- easing
- cubic-bezier(0.2, 0, 0, 1)
- philosophy
- motion behaves like a lab instrument confirming focus: short opacity steps and marker pips, never cinematic transitions or scanning effects
radii5 items
- full
- 9999px
- lg
- 24px
- md
- 16px
- none
- 0
- sm
- 0
shadows3 items
- lg
- 16px 16px 0 rgba(17,17,17,0.10)
- md
- 8px 8px 0 rgba(17,17,17,0.08)
- sm
- 0 1px 0 rgba(17,17,17,0.18)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64, 96
surfaces3 items
- bg pattern
- very sparse black calibration ticks and crop marks aligned to an 8px baseline
- card style
- square panels with 1px black hairline borders, white interiors, gray disabled wells, and no rounded corners except diagnostic pills
- treatment
- sealed off-white appliance shells with matte paper grain simulated through subtle repeating-linear-gradient texture
typography8 items
- base size
- 16px
- body font
- Archivo
- google fonts url
- https://fonts.googleapis.com/css2?family=Archivo:wght@400;500;600;700&family=Martian+Mono:wght@400;500;600&display=swap
- heading font
- Archivo
- letter spacing
- -0.02em
- line height
- 1.48
- mono font
- Martian Mono
- scale ratio
- 1.22
rules
composition
Use a 2x rational spacing grid but break symmetry with one dominant diagnostic bench, one narrow transcript rail, and several inset evidence panes. Anchor the page with a thick black outer frame, then subdivide it with 1px hairlines. Keep panels rectilinear and allow large off-white voids to act as sterile air around dense technical details. Place callouts on panel edges rather than floating decorative badges. Use cropped schematic fragments at the edges to imply a larger apparatus without becoming a dashboard.
density
Medium-high technical density is allowed inside designated diagnostic panes, while gutters and margins remain calm and spacious. The page should feel like a research bench with evidence isolated in trays, not a full-screen operations center.
hierarchy
Primary hierarchy comes from frame weight, panel scale, and label position, not color. Headings are small grotesk captions in uppercase or tight title case. Monospaced values, ports, hashes, and timestamps create secondary texture. Cyan is the final hierarchy layer and may indicate only the current exploit step, cursor position, breach coordinate, or checksum validation. Disabled and background information recedes into warm gray wells and lighter hairlines.
signature patterns
Air-gapped modal frame: a black rectangular outer frame surrounds separated white panels with deliberate 8px breaks that read as isolation gaps.Cyan intrusion pin grammar: tiny cyan dots, short crosshair ticks, and 1px connector stems appear only at active exploit evidence coordinates.Packet dissection ruler: horizontal and vertical black measurement rails with byte offsets, checksum beads, and small numeric ticks structure dense data.Clipped schematic callouts: panel corners use small black diagonal cuts or stepped notches that make the layout feel like hardware documentation.Quiet terminal transcript strips: command output lives in narrow bordered panes with low-contrast gray rows and one active cyan cursor pip.
layout
breakpoints
- desktop
- 1024px+ twelve-column asymmetrical instrument layout
- mobile
- 0-639px single column with horizontal rulers shortened
- tablet
- 640-1023px six-column reflow with transcript below bench
density
Use a deliberate contrast between open sterile margins and dense technical inserts; diagnostic content is grouped into trays so high detail never becomes dashboard clutter.
grid
Desktop uses a 12-column grid at max-width 1320px with 8px micro gutters and 24px macro gutters; the hero bench spans 7 columns, transcript rail spans 3, and evidence stack spans 2. Tablet collapses to 6 columns, mobile to a single framed column.
responsive
Keep the black outer appliance frame visible at every viewport. Stack panels vertically on mobile, reduce microtype density, hide nonessential ruler ticks, and retain at least three cyan evidence markers.
whitespace
Whitespace is sterile air: preserve 24-48px margins around the outer frame, 8px internal gutters between panels, and blank off-white zones around active cyan marks.
guidance
- Use off-white, black, warm gray, and a single cyan accent with strict semantic purpose.
- Make the signature visible through air-gapped frames, packet rulers, clipped callouts, and cyan intrusion pins.
- Write interface copy as assessment workflow: scope, probe, reproduce, isolate, validate, contain.
- Keep typography small, precise, and instrument-like with negative tracking across headings and body.
- Let large quiet surfaces balance technical density inside rulers, transcripts, and port maps.
- Maintain black-and-white legibility so printed or grayscale views still communicate the system.
- Use shadows sparingly as warm gray panel offsets, never as glossy depth or floating SaaS elevation.
- Prefer evidence trays, modal frames, and diagnostic probes over charts, cards, avatars, or marketing sections.
- Do not use green code, neon purple, cityscapes, glow effects, or cyberpunk spectacle.
- Do not show a hacker character, skull malware, anime fan-art portrait, or heroic intrusion metaphor.
- Do not build a generic SOC dashboard full of metric cards, donut charts, and alert feeds.
- Do not add extra accent colors; status colors are for rare semantic copy and should not decorate the embodiment.
- Do not round every panel or use glassmorphism, glossy gradients, soft blobs, or arbitrary shadows.
- Do not let terminal panes dominate the scene; they are quiet transcript evidence, not the identity itself.
- Do not use techno display fonts or oversized futuristic lettering.
- Do not place cyan on inactive labels, borders, or large backgrounds.
katagami spec
# White-Room Intrusion Kit ## Philosophy White-Room Intrusion Kit treats security assessment as a sterile diagnostic procedure rather than a heroic breach fantasy. The interface feels like a sealed lab appliance opened to reveal black schematic bones: off-white panels, absolute black hairlines, calibrated gutters, and tiny cyan evidence marks that appear only where an exploit hypothesis has touched the system. Its cultural references are disciplined rather than nostalgic: minimal black-and-white manga panel logic, late-1990s hardware manuals, quiet terminal windows, and speculative cybernetics translated into calm assessment tooling. The point of view is clinical restraint: no cyberpunk glow, no hacker costume, no generic monitoring dashboard, and no decorative color beyond semantic intrusion coordinates. ### Values - Evidence before drama: accent color is reserved for verified breach coordinates, active cursors, checksum ticks, and current probe focus. - Appliance-like calm: surfaces should feel sealed, white, quiet, and engineered rather than expressive or entertainment-oriented. - Schematic authority: hairline black rules, port maps, numeric strings, and ruler marks create credibility without ornamental dashboards. - Hands-off diagnostics: the user is positioned as a researcher operating probes and checklists, not as a heroic hacker avatar. - Black-and-white reproduction discipline: every screen must remain legible and distinctive if the cyan marks are removed or printed monochrome. - Asymmetrical precision: manga-like panels and technical callouts create movement while retaining rational 2x grid spacing. - Terminal restraint: command transcripts are quiet, sparse, and typographically modest instead of immersive green code theatrics. ### Anti-Values - No green matrix rain, violet neon, rainbow glow, or cyberpunk city ambience. - No hoodie hackers, skull malware mascots, anime fan art figures, or heroic character illustration. - No SaaS card grids, generic SOC dashboards, glossy status tiles, or decorative analytics widgets. - No techno display fonts, oversized glowing type, glassmorphism, or gradient spectacle. - No gratuitous red-alert panic; risk states remain measured, documented, and procedural. ### Visual Character - Use off-white full-bleed backgrounds with slightly warmer white inset panels separated by 1px absolute-black hairlines and 8px calibrated gutters. - Build asymmetrical manga-like panel compositions with thick outer black frames, narrow terminal panes, and clipped schematic callout corners. - Place tiny cyan markers as 6px dots, 1px coordinate pins, checksum beads, and cursor pips only on active evidence or exploit-chain focus points. - Layer black schematic bones inside panels: port-map ticks, packet rulers, vertical measurement rails, and thin connector lines rather than icons. - Set all labels in small monospaced research notation with restrained grotesk headings, narrow numeric strings, and uniformly negative tracking. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: absolute-black hairlines with occasional thick outer manga frames and clipped callout notches - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#00A9C7` | | background | `#F6F2EA` | | border | `#111111` | | error | `#9B1C1C` | | info | `#007E95` | | muted | `#6F6A61` | | primary | `#0B0B0B` | | secondary | `#EEE8DE` | | success | `#2F6B45` | | surface | `#FFFDF8` | | text | `#090909` | | warning | `#9A6A12` | ### Motion - **Duration**: 160ms - **Easing**: cubic-bezier(0.2, 0, 0, 1) - **Philosophy**: motion behaves like a lab instrument confirming focus: short opacity steps and marker pips, never cinematic transitions or scanning effects ### Radii - **Full**: 9999px - **Lg**: 24px - **Md**: 16px - **None**: 0 - **Sm**: 0 ### Shadows - **Lg**: 16px 16px 0 rgba(17,17,17,0.10) - **Md**: 8px 8px 0 rgba(17,17,17,0.08) - **Sm**: 0 1px 0 rgba(17,17,17,0.18) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64,96] ### Surfaces - **Bg Pattern**: very sparse black calibration ticks and crop marks aligned to an 8px baseline - **Card Style**: square panels with 1px black hairline borders, white interiors, gray disabled wells, and no rounded corners except diagnostic pills - **Treatment**: sealed off-white appliance shells with matte paper grain simulated through subtle repeating-linear-gradient texture ### Typography - **Base Size**: 16px - **Body Font**: Archivo - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Archivo:wght@400;500;600;700&family=Martian+Mono:wght@400;500;600&display=swap - **Heading Font**: Archivo - **Letter Spacing**: -0.02em - **Line Height**: 1.48 - **Mono Font**: Martian Mono - **Scale Ratio**: 1.22 ## Rules ### Composition Use a 2x rational spacing grid but break symmetry with one dominant diagnostic bench, one narrow transcript rail, and several inset evidence panes. Anchor the page with a thick black outer frame, then subdivide it with 1px hairlines. Keep panels rectilinear and allow large off-white voids to act as sterile air around dense technical details. Place callouts on panel edges rather than floating decorative badges. Use cropped schematic fragments at the edges to imply a larger apparatus without becoming a dashboard. ### Density Medium-high technical density is allowed inside designated diagnostic panes, while gutters and margins remain calm and spacious. The page should feel like a research bench with evidence isolated in trays, not a full-screen operations center. ### Hierarchy Primary hierarchy comes from frame weight, panel scale, and label position, not color. Headings are small grotesk captions in uppercase or tight title case. Monospaced values, ports, hashes, and timestamps create secondary texture. Cyan is the final hierarchy layer and may indicate only the current exploit step, cursor position, breach coordinate, or checksum validation. Disabled and background information recedes into warm gray wells and lighter hairlines. ### Signature Patterns - Air-gapped modal frame: a black rectangular outer frame surrounds separated white panels with deliberate 8px breaks that read as isolation gaps. - Cyan intrusion pin grammar: tiny cyan dots, short crosshair ticks, and 1px connector stems appear only at active exploit evidence coordinates. - Packet dissection ruler: horizontal and vertical black measurement rails with byte offsets, checksum beads, and small numeric ticks structure dense data. - Clipped schematic callouts: panel corners use small black diagonal cuts or stepped notches that make the layout feel like hardware documentation. - Quiet terminal transcript strips: command output lives in narrow bordered panes with low-contrast gray rows and one active cyan cursor pip. ## Layout ### Breakpoints - **Desktop**: 1024px+ twelve-column asymmetrical instrument layout - **Mobile**: 0-639px single column with horizontal rulers shortened - **Tablet**: 640-1023px six-column reflow with transcript below bench ### Density Use a deliberate contrast between open sterile margins and dense technical inserts; diagnostic content is grouped into trays so high detail never becomes dashboard clutter. ### Grid Desktop uses a 12-column grid at max-width 1320px with 8px micro gutters and 24px macro gutters; the hero bench spans 7 columns, transcript rail spans 3, and evidence stack spans 2. Tablet collapses to 6 columns, mobile to a single framed column. ### Responsive Keep the black outer appliance frame visible at every viewport. Stack panels vertically on mobile, reduce microtype density, hide nonessential ruler ticks, and retain at least three cyan evidence markers. ### Whitespace Whitespace is sterile air: preserve 24-48px margins around the outer frame, 8px internal gutters between panels, and blank off-white zones around active cyan marks. ## Guidance ### Do - Use off-white, black, warm gray, and a single cyan accent with strict semantic purpose. - Make the signature visible through air-gapped frames, packet rulers, clipped callouts, and cyan intrusion pins. - Write interface copy as assessment workflow: scope, probe, reproduce, isolate, validate, contain. - Keep typography small, precise, and instrument-like with negative tracking across headings and body. - Let large quiet surfaces balance technical density inside rulers, transcripts, and port maps. - Maintain black-and-white legibility so printed or grayscale views still communicate the system. - Use shadows sparingly as warm gray panel offsets, never as glossy depth or floating SaaS elevation. - Prefer evidence trays, modal frames, and diagnostic probes over charts, cards, avatars, or marketing sections. ### Don't - Do not use green code, neon purple, cityscapes, glow effects, or cyberpunk spectacle. - Do not show a hacker character, skull malware, anime fan-art portrait, or heroic intrusion metaphor. - Do not build a generic SOC dashboard full of metric cards, donut charts, and alert feeds. - Do not add extra accent colors; status colors are for rare semantic copy and should not decorate the embodiment. - Do not round every panel or use glassmorphism, glossy gradients, soft blobs, or arbitrary shadows. - Do not let terminal panes dominate the scene; they are quiet transcript evidence, not the identity itself. - Do not use techno display fonts or oversized futuristic lettering. - Do not place cyan on inactive labels, borders, or large backgrounds. ### Accessibility Text and structural lines maintain high contrast on off-white surfaces. Cyan markers are supplemental and paired with position, labels, or linework so color is never the only signal. Small mono labels must remain at least 11px with generous line-height, and mobile layouts should reduce density rather than shrinking content below legibility. ### Usage Context Best for security testing platforms, exploit assessment notebooks, research lab tooling, red-team methodology documentation, packet analysis utilities, and clinical vulnerability triage products that need credibility without hacker theatrics.
DESIGN.md
---
version: "alpha"
name: "White-Room Intrusion Kit"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#00A9C7"
background: "#F6F2EA"
border: "#111111"
error: "#9B1C1C"
info: "#007E95"
muted: "#6F6A61"
primary: "#0B0B0B"
secondary: "#EEE8DE"
success: "#2F6B45"
surface: "#FFFDF8"
text: "#090909"
warning: "#9A6A12"
typography:
headline-lg:
fontFamily: "Archivo"
fontSize: "1.816rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.02em"
headline-md:
fontFamily: "Archivo"
fontSize: "1.488rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.02em"
body-md:
fontFamily: "Archivo"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.48
letterSpacing: "-0.02em"
label-md:
fontFamily: "Martian 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"
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"
---
# White-Room Intrusion Kit
## Overview
White-Room Intrusion Kit treats security assessment as a sterile diagnostic procedure rather than a heroic breach fantasy. The interface feels like a sealed lab appliance opened to reveal black schematic bones: off-white panels, absolute black hairlines, calibrated gutters, and tiny cyan evidence marks that appear only where an exploit hypothesis has touched the system. Its cultural references are disciplined rather than nostalgic: minimal black-and-white manga panel logic, late-1990s hardware manuals, quiet terminal windows, and speculative cybernetics translated into calm assessment tooling. The point of view is clinical restraint: no cyberpunk glow, no hacker costume, no generic monitoring dashboard, and no decorative color beyond semantic intrusion coordinates.
### Values
- Evidence before drama: accent color is reserved for verified breach coordinates, active cursors, checksum ticks, and current probe focus.
- Appliance-like calm: surfaces should feel sealed, white, quiet, and engineered rather than expressive or entertainment-oriented.
- Schematic authority: hairline black rules, port maps, numeric strings, and ruler marks create credibility without ornamental dashboards.
- Hands-off diagnostics: the user is positioned as a researcher operating probes and checklists, not as a heroic hacker avatar.
- Black-and-white reproduction discipline: every screen must remain legible and distinctive if the cyan marks are removed or printed monochrome.
- Asymmetrical precision: manga-like panels and technical callouts create movement while retaining rational 2x grid spacing.
- Terminal restraint: command transcripts are quiet, sparse, and typographically modest instead of immersive green code theatrics.
### Anti-Values
- No green matrix rain, violet neon, rainbow glow, or cyberpunk city ambience.
- No hoodie hackers, skull malware mascots, anime fan art figures, or heroic character illustration.
- No SaaS card grids, generic SOC dashboards, glossy status tiles, or decorative analytics widgets.
- No techno display fonts, oversized glowing type, glassmorphism, or gradient spectacle.
- No gratuitous red-alert panic; risk states remain measured, documented, and procedural.
### Visual Character
- Use off-white full-bleed backgrounds with slightly warmer white inset panels separated by 1px absolute-black hairlines and 8px calibrated gutters.
- Build asymmetrical manga-like panel compositions with thick outer black frames, narrow terminal panes, and clipped schematic callout corners.
- Place tiny cyan markers as 6px dots, 1px coordinate pins, checksum beads, and cursor pips only on active evidence or exploit-chain focus points.
- Layer black schematic bones inside panels: port-map ticks, packet rulers, vertical measurement rails, and thin connector lines rather than icons.
- Set all labels in small monospaced research notation with restrained grotesk headings, narrow numeric strings, and uniformly negative tracking.
## 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 | `#00A9C7` |
| background | `#F6F2EA` |
| border | `#111111` |
| error | `#9B1C1C` |
| info | `#007E95` |
| muted | `#6F6A61` |
| primary | `#0B0B0B` |
| secondary | `#EEE8DE` |
| success | `#2F6B45` |
| surface | `#FFFDF8` |
| text | `#090909` |
| warning | `#9A6A12` |
## Typography
- **Headline-Lg**: Archivo, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Archivo, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Archivo, 16px, weight 400, line-height 1.48.
- **Label-Md**: Martian Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
- **Step-8**: `96px`
### Breakpoints
- **Desktop**: 1024px+ twelve-column asymmetrical instrument layout
- **Mobile**: 0-639px single column with horizontal rulers shortened
- **Tablet**: 640-1023px six-column reflow with transcript below bench
### Density
Use a deliberate contrast between open sterile margins and dense technical inserts; diagnostic content is grouped into trays so high detail never becomes dashboard clutter.
### Grid
Desktop uses a 12-column grid at max-width 1320px with 8px micro gutters and 24px macro gutters; the hero bench spans 7 columns, transcript rail spans 3, and evidence stack spans 2. Tablet collapses to 6 columns, mobile to a single framed column.
### Responsive
Keep the black outer appliance frame visible at every viewport. Stack panels vertically on mobile, reduce microtype density, hide nonessential ruler ticks, and retain at least three cyan evidence markers.
### Whitespace
Whitespace is sterile air: preserve 24-48px margins around the outer frame, 8px internal gutters between panels, and blank off-white zones around active cyan marks.
## Elevation & Depth
### Shadows
- **Lg**: 16px 16px 0 rgba(17,17,17,0.10)
- **Md**: 8px 8px 0 rgba(17,17,17,0.08)
- **Sm**: 0 1px 0 rgba(17,17,17,0.18)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `24px`
- **Md**: `16px`
- **None**: `0px`
- **Sm**: `0px`
### Surfaces
- **Bg Pattern**: very sparse black calibration ticks and crop marks aligned to an 8px baseline
- **Card Style**: square panels with 1px black hairline borders, white interiors, gray disabled wells, and no rounded corners except diagnostic pills
- **Treatment**: sealed off-white appliance shells with matte paper grain simulated through subtle repeating-linear-gradient texture
### Borders
- **Accent Width**: 2px
- **Character**: absolute-black hairlines with occasional thick outer manga frames and clipped callout notches
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Use a 2x rational spacing grid but break symmetry with one dominant diagnostic bench, one narrow transcript rail, and several inset evidence panes. Anchor the page with a thick black outer frame, then subdivide it with 1px hairlines. Keep panels rectilinear and allow large off-white voids to act as sterile air around dense technical details. Place callouts on panel edges rather than floating decorative badges. Use cropped schematic fragments at the edges to imply a larger apparatus without becoming a dashboard.
### Density
Medium-high technical density is allowed inside designated diagnostic panes, while gutters and margins remain calm and spacious. The page should feel like a research bench with evidence isolated in trays, not a full-screen operations center.
### Hierarchy
Primary hierarchy comes from frame weight, panel scale, and label position, not color. Headings are small grotesk captions in uppercase or tight title case. Monospaced values, ports, hashes, and timestamps create secondary texture. Cyan is the final hierarchy layer and may indicate only the current exploit step, cursor position, breach coordinate, or checksum validation. Disabled and background information recedes into warm gray wells and lighter hairlines.
### Signature Patterns
- Air-gapped modal frame: a black rectangular outer frame surrounds separated white panels with deliberate 8px breaks that read as isolation gaps.
- Cyan intrusion pin grammar: tiny cyan dots, short crosshair ticks, and 1px connector stems appear only at active exploit evidence coordinates.
- Packet dissection ruler: horizontal and vertical black measurement rails with byte offsets, checksum beads, and small numeric ticks structure dense data.
- Clipped schematic callouts: panel corners use small black diagonal cuts or stepped notches that make the layout feel like hardware documentation.
- Quiet terminal transcript strips: command output lives in narrow bordered panes with low-contrast gray rows and one active cyan cursor pip.
## shadcn/ui Usage
When the target app uses shadcn/ui, copy DESIGN.md with shadcn instead of the plain DESIGN.md. It contains the same Katagami design-language source plus the shadcn/ui primitives, imports, theme variables, component recipes, and preview-shot guidance.
DESIGN.md with shadcn: `/language/en-019e05cf-9547-7f53-8feb-8ff89728e08f/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 off-white, black, warm gray, and a single cyan accent with strict semantic purpose.
- Do Make the signature visible through air-gapped frames, packet rulers, clipped callouts, and cyan intrusion pins.
- Do Write interface copy as assessment workflow: scope, probe, reproduce, isolate, validate, contain.
- Do Keep typography small, precise, and instrument-like with negative tracking across headings and body.
- Do Let large quiet surfaces balance technical density inside rulers, transcripts, and port maps.
- Do Maintain black-and-white legibility so printed or grayscale views still communicate the system.
- Do Use shadows sparingly as warm gray panel offsets, never as glossy depth or floating SaaS elevation.
- Do Prefer evidence trays, modal frames, and diagnostic probes over charts, cards, avatars, or marketing sections.
- Don't Do not use green code, neon purple, cityscapes, glow effects, or cyberpunk spectacle.
- Don't Do not show a hacker character, skull malware, anime fan-art portrait, or heroic intrusion metaphor.
- Don't Do not build a generic SOC dashboard full of metric cards, donut charts, and alert feeds.
- Don't Do not add extra accent colors; status colors are for rare semantic copy and should not decorate the embodiment.
- Don't Do not round every panel or use glassmorphism, glossy gradients, soft blobs, or arbitrary shadows.
- Don't Do not let terminal panes dominate the scene; they are quiet transcript evidence, not the identity itself.
- Don't Do not use techno display fonts or oversized futuristic lettering.
- Don't Do not place cyan on inactive labels, borders, or large backgrounds.
### Accessibility
Text and structural lines maintain high contrast on off-white surfaces. Cyan markers are supplemental and paired with position, labels, or linework so color is never the only signal. Small mono labels must remain at least 11px with generous line-height, and mobile layouts should reduce density rather than shrinking content below legibility.
### Usage Context
Best for security testing platforms, exploit assessment notebooks, research lab tooling, red-team methodology documentation, packet analysis utilities, and clinical vulnerability triage products that need credibility without hacker theatrics.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "white-room-intrusion-kit",
"type": "registry:theme",
"title": "White-Room Intrusion Kit shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F6F2EA",
"foreground": "#090909",
"card": "#FFFDF8",
"card-foreground": "#090909",
"popover": "#FFFDF8",
"popover-foreground": "#090909",
"primary": "#0B0B0B",
"primary-foreground": "#ffffff",
"secondary": "#EEE8DE",
"secondary-foreground": "#111111",
"muted": "#6F6A61",
"muted-foreground": "#090909",
"accent": "#00A9C7",
"accent-foreground": "#ffffff",
"destructive": "#9B1C1C",
"border": "#111111",
"input": "#111111",
"ring": "#00A9C7",
"chart-1": "#0B0B0B",
"chart-2": "#EEE8DE",
"chart-3": "#00A9C7",
"chart-4": "#2F6B45",
"chart-5": "#9A6A12",
"sidebar": "#FFFDF8",
"sidebar-foreground": "#090909",
"sidebar-primary": "#0B0B0B",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#007E95",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#111111",
"sidebar-ring": "#00A9C7",
"radius": "16px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#0B0B0B",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#00A9C7",
"accent-foreground": "#ffffff",
"destructive": "#9B1C1C",
"border": "#303642",
"input": "#303642",
"ring": "#00A9C7",
"chart-1": "#0B0B0B",
"chart-2": "#EEE8DE",
"chart-3": "#00A9C7",
"chart-4": "#2F6B45",
"chart-5": "#9A6A12",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#0B0B0B",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#00A9C7",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#00A9C7",
"radius": "16px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e05cf-9547-7f53-8feb-8ff89728e08f",
"slug": "white-room-intrusion-kit",
"componentManifest": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"nativeTokenNames": {
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"colors": [
"accent",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"motion": [
"duration",
"easing",
"philosophy"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"spacing": [
"base",
"scale"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
]
}
}
}
```in the wild
embodiments
the full element showcase
embodiment · white-room-intrusion-kit
DESIGN.md
at a glance
Typography
headline-lgArchivo · 29px · 700
The quick brown fox jumps
headline-mdArchivo · 24px · 600
The quick brown fox jumps
body-mdArchivo · 16px · 400
The quick brown fox jumps
label-mdMartian Mono · 12px · 600
The quick brown fox jumps
Components
New
Card title
Components rendered with this language’s tokens — colors, type, and rounded corners as specified.
Spacing
- base8px
- xs4px
- sm8px
- md12px
- lg16px
- xl24px
- 2xl32px
- 3xl48px
- 4xl64px
- step-896px
Shape
full9999px
lg24px
md16px
none0px
sm0px
shadcn/ui
implementation kit
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 tabletheme css
:root {
--background: #F6F2EA;
--foreground: #090909;
--card: #FFFDF8;
--card-foreground: #090909;
--popover: #FFFDF8;
--popover-foreground: #090909;
--primary: #0B0B0B;
--primary-foreground: #ffffff;
--secondary: #EEE8DE;
--secondary-foreground: #111111;
--muted: #6F6A61;
--muted-foreground: #090909;
--accent: #00A9C7;
--accent-foreground: #ffffff;
--destructive: #9B1C1C;
--border: #111111;
--input: #111111;
--ring: #00A9C7;
--chart-1: #0B0B0B;
--chart-2: #EEE8DE;
--chart-3: #00A9C7;
--chart-4: #2F6B45;
--chart-5: #9A6A12;
--sidebar: #FFFDF8;
--sidebar-foreground: #090909;
--sidebar-primary: #0B0B0B;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #007E95;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #111111;
--sidebar-ring: #00A9C7;
--radius: 16px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #0B0B0B;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #00A9C7;
--accent-foreground: #ffffff;
--destructive: #9B1C1C;
--border: #303642;
--input: #303642;
--ring: #00A9C7;
--chart-1: #0B0B0B;
--chart-2: #EEE8DE;
--chart-3: #00A9C7;
--chart-4: #2F6B45;
--chart-5: #9A6A12;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #0B0B0B;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #00A9C7;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #00A9C7;
--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 WhiteRoomIntrusionKitShadcnKit() {
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">White-Room Intrusion Kit</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": "white-room-intrusion-kit",
"type": "registry:theme",
"title": "White-Room Intrusion Kit shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F6F2EA",
"foreground": "#090909",
"card": "#FFFDF8",
"card-foreground": "#090909",
"popover": "#FFFDF8",
"popover-foreground": "#090909",
"primary": "#0B0B0B",
"primary-foreground": "#ffffff",
"secondary": "#EEE8DE",
"secondary-foreground": "#111111",
"muted": "#6F6A61",
"muted-foreground": "#090909",
"accent": "#00A9C7",
"accent-foreground": "#ffffff",
"destructive": "#9B1C1C",
"border": "#111111",
"input": "#111111",
"ring": "#00A9C7",
"chart-1": "#0B0B0B",
"chart-2": "#EEE8DE",
"chart-3": "#00A9C7",
"chart-4": "#2F6B45",
"chart-5": "#9A6A12",
"sidebar": "#FFFDF8",
"sidebar-foreground": "#090909",
"sidebar-primary": "#0B0B0B",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#007E95",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#111111",
"sidebar-ring": "#00A9C7",
"radius": "16px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#0B0B0B",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#00A9C7",
"accent-foreground": "#ffffff",
"destructive": "#9B1C1C",
"border": "#303642",
"input": "#303642",
"ring": "#00A9C7",
"chart-1": "#0B0B0B",
"chart-2": "#EEE8DE",
"chart-3": "#00A9C7",
"chart-4": "#2F6B45",
"chart-5": "#9A6A12",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#0B0B0B",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#00A9C7",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#00A9C7",
"radius": "16px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e05cf-9547-7f53-8feb-8ff89728e08f",
"slug": "white-room-intrusion-kit",
"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"
]
}
}
}
component recipescompatibility fallback
# White-Room Intrusion Kit shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e05cf-9547-7f53-8feb-8ff89728e08f`
Slug: `white-room-intrusion-kit`
## Intent
White-Room Intrusion Kit treats security assessment as a sterile diagnostic procedure rather than a heroic breach fantasy. The interface feels like a sealed lab appliance opened to reveal black schematic bones: off-white panels, absolute black hairlines, calibrated gutters, and tiny cyan evidence marks that appear only where an exploit hypothesis has touched the system. Its cultural references are disciplined rather than nostalgic: minimal black-and-white manga panel logic, late-1990s hardware manuals, quiet terminal windows, and speculative cybernetics translated into calm assessment tooling. The point of view is clinical restraint: no cyberpunk glow, no hacker costume, no generic monitoring dashboard, and no decorative color beyond semantic intrusion coordinates.
## 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": "#00A9C7",
"background": "#F6F2EA",
"border": "#111111",
"error": "#9B1C1C",
"info": "#007E95",
"muted": "#6F6A61",
"primary": "#0B0B0B",
"secondary": "#EEE8DE",
"success": "#2F6B45",
"surface": "#FFFDF8",
"text": "#090909",
"warning": "#9A6A12"
}
Typography:
{
"base_size": "16px",
"body_font": "Archivo",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Archivo:wght@400;500;600;700&family=Martian+Mono:wght@400;500;600&display=swap",
"heading_font": "Archivo",
"letter_spacing": "-0.02em",
"line_height": 1.48,
"mono_font": "Martian Mono",
"scale_ratio": 1.22
}
## Visual character to preserve
- Use off-white full-bleed backgrounds with slightly warmer white inset panels separated by 1px absolute-black hairlines and 8px calibrated gutters.
- Build asymmetrical manga-like panel compositions with thick outer black frames, narrow terminal panes, and clipped schematic callout corners.
- Place tiny cyan markers as 6px dots, 1px coordinate pins, checksum beads, and cursor pips only on active evidence or exploit-chain focus points.
- Layer black schematic bones inside panels: port-map ticks, packet rulers, vertical measurement rails, and thin connector lines rather than icons.
- Set all labels in small monospaced research notation with restrained grotesk headings, narrow numeric strings, and uniformly negative tracking.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": false,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
}
## Signature component recipes
### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.
### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.
### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.
### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.
### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.
## Preview shots
- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.
## Implementation contract
- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/white-room-intrusion-kit/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 off-white, black, warm gray, and a single cyan accent with strict semantic purpose.; Make the signature visible through air-gapped frames, packet rulers, clipped callouts, and cyan intrusion pins.; Write interface copy as assessment workflow: scope, probe, reproduce, isolate, validate, contain.; Keep typography small, precise, and instrument-like with negative tracking across headings and body.; Let large quiet surfaces balance technical density inside rulers, transcripts, and port maps.; Maintain black-and-white legibility so printed or grayscale views still communicate the system.; Use shadows sparingly as warm gray panel offsets, never as glossy depth or floating SaaS elevation.; Prefer evidence trays, modal frames, and diagnostic probes over charts, cards, avatars, or marketing sections.
- Do not: Do not use green code, neon purple, cityscapes, glow effects, or cyberpunk spectacle.; Do not show a hacker character, skull malware, anime fan-art portrait, or heroic intrusion metaphor.; Do not build a generic SOC dashboard full of metric cards, donut charts, and alert feeds.; Do not add extra accent colors; status colors are for rare semantic copy and should not decorate the embodiment.; Do not round every panel or use glassmorphism, glossy gradients, soft blobs, or arbitrary shadows.; Do not let terminal panes dominate the scene; they are quiet transcript evidence, not the identity itself.; Do not use techno display fonts or oversized futuristic lettering.; Do not place cyan on inactive labels, borders, or large backgrounds.
## 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 WhiteRoomIntrusionKitShadcnKit() {
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">White-Room Intrusion Kit</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+ twelve-column asymmetrical instrument layout",
"mobile": "0-639px single column with horizontal rulers shortened",
"tablet": "640-1023px six-column reflow with transcript below bench"
},
"density": "Use a deliberate contrast between open sterile margins and dense technical inserts; diagnostic content is grouped into trays so high detail never becomes dashboard clutter.",
"grid": "Desktop uses a 12-column grid at max-width 1320px with 8px micro gutters and 24px macro gutters; the hero bench spans 7 columns, transcript rail spans 3, and evidence stack spans 2. Tablet collapses to 6 columns, mobile to a single framed column.",
"responsive": "Keep the black outer appliance frame visible at every viewport. Stack panels vertically on mobile, reduce microtype density, hide nonessential ruler ticks, and retain at least three cyan evidence markers.",
"whitespace": "Whitespace is sterile air: preserve 24-48px margins around the outer frame, 8px internal gutters between panels, and blank off-white zones around active cyan marks."
}
preview shotscompatibility fallback
{
"artifact": "katagami:shadcn-preview-shots",
"version": "preview-shots-v1",
"generator": "katagami-ui-compatibility-projection",
"generatedBy": "katagami-ui-projection",
"requiresVisualProfile": true,
"schema": "katagami:shadcn-preview-shots/renderable-v1",
"renderable": true,
"language": {
"id": "en-019e05cf-9547-7f53-8feb-8ff89728e08f",
"name": "White-Room Intrusion Kit",
"slug": "white-room-intrusion-kit"
},
"installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
"primitives": [
"button",
"card",
"input",
"textarea",
"select",
"dialog",
"sheet",
"tabs",
"badge",
"separator",
"checkbox",
"switch",
"slider",
"tooltip",
"dropdown-menu",
"table"
],
"identityNotes": [
"Use off-white full-bleed backgrounds with slightly warmer white inset panels separated by 1px absolute-black hairlines and 8px calibrated gutters.",
"Build asymmetrical manga-like panel compositions with thick outer black frames, narrow terminal panes, and clipped schematic callout corners.",
"Place tiny cyan markers as 6px dots, 1px coordinate pins, checksum beads, and cursor pips only on active evidence or exploit-chain focus points.",
"Layer black schematic bones inside panels: port-map ticks, packet rulers, vertical measurement rails, and thin connector lines rather than icons.",
"Set all labels in small monospaced research notation with restrained grotesk headings, narrow numeric strings, and uniformly negative tracking."
],
"visualProfile": {
"family": "brutalist",
"material": "ink",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": false,
"stickerBadges": false,
"motion": "still",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "White-Room Intrusion Kit 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 off-white, black, warm gray, and a single cyan accent with strict semantic purpose.",
"Make the signature visible through air-gapped frames, packet rulers, clipped callouts, and cyan intrusion pins.",
"Write interface copy as assessment workflow: scope, probe, reproduce, isolate, validate, contain.",
"Keep typography small, precise, and instrument-like with negative tracking across headings and body.",
"Let large quiet surfaces balance technical density inside rulers, transcripts, and port maps.",
"Maintain black-and-white legibility so printed or grayscale views still communicate the system.",
"Use shadows sparingly as warm gray panel offsets, never as glossy depth or floating SaaS elevation.",
"Prefer evidence trays, modal frames, and diagnostic probes over charts, cards, avatars, or marketing sections."
],
"dont": [
"Do not use green code, neon purple, cityscapes, glow effects, or cyberpunk spectacle.",
"Do not show a hacker character, skull malware, anime fan-art portrait, or heroic intrusion metaphor.",
"Do not build a generic SOC dashboard full of metric cards, donut charts, and alert feeds.",
"Do not add extra accent colors; status colors are for rare semantic copy and should not decorate the embodiment.",
"Do not round every panel or use glassmorphism, glossy gradients, soft blobs, or arbitrary shadows.",
"Do not let terminal panes dominate the scene; they are quiet transcript evidence, not the identity itself.",
"Do not use techno display fonts or oversized futuristic lettering.",
"Do not place cyan on inactive labels, borders, or large backgrounds."
]
}
}