back to gallery
design language·enterprise-mono-grid-interfaces

Enterprise Mono-Grid Interfaces

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
A restrained enterprise interface language built on disciplined monochrome grids, compact information density, and typographic contrast. It treats operational dashboards, review queues, and data workspaces as serious instruments: crisp white planes, graphite separators, steel-gray metadata, and a single electric-blue signal reserved for actionable state and analytical emphasis.
values
Operational clarity over decorative noveltyDense information presented with strict rhythm and legible contrastInterfaces that feel precise, dependable, and audit-ready
anti-values
×Playful softness, rounded consumer-app whimsy, or colorful abundance×Floating card chaos, vague hierarchy, and ornamental motion
tokens
colors12 items
primary
#20242b
secondary
#5e6877
accent
#2f6fff
background
#eef2f6
surface
#fbfdff
text
#15181d
muted
#7a8492
border
#b8c2cf
error
#c53b32
success
#1f7a55
warning
#a66a12
info
#2f6fff
typography8 items
heading font
Space Grotesk
body font
IBM Plex Sans
mono font
IBM Plex Mono
base size
16px
scale ratio
1.2
line height
1.5
letter spacing
0.01em
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600;700&family=Space+Grotesk:wght@500;700&display=swap
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
radii5 items
none
0
sm
0
md
2px
lg
4px
full
9999px
shadows3 items
sm
0 1px 0 rgba(21,24,29,0.06)
md
0 12px 30px rgba(21,24,29,0.06)
lg
0 24px 60px rgba(21,24,29,0.09)
surfaces3 items
treatment
flat
card style
Cool white panels with subtle top-to-bottom tonal shifts, internal divider rules, and occasional steel-gray header bands for dense operational grouping.
bg pattern
grid
borders4 items
default width
1px
accent width
2px
style
solid
character
Borders are infrastructural and ever-present: crisp graphite rules, table row dividers, and vertical separators that make the interface feel engineered.
motion3 items
duration
160ms
easing
cubic-bezier(0.2, 0.7, 0, 1)
philosophy
snappy
rules
composition
Compose screens as a command workspace with fixed rails, a dominant analytical center, and a supporting inspection column so users can scan, compare, and act without losing context.
hierarchy

Use uppercase module labels, oversized numeric or analytical headlines, and monospaced row metadata to separate strategic summary from transactional detail.

density

High-density but controlled, with compact rows and disciplined spacing increments.

signature patterns
Every major panel includes exposed header bands or label strips with uppercase titles and a bottom rule, making section boundaries visible without relying on shadows.Data tables use full-width row dividers, mono-aligned numeric columns, and a blue left inset or outline only for the currently active or anomalous record.Navigation, filters, and summaries snap to a visible modular grid using squared containers, vertical separators, and repeated minmax columns that reinforce enterprise order.Interactive controls invert minimally on hover and show a precise blue focus ring or underline, keeping the monochrome system intact while making state unmistakable.
layout
grid
Desktop uses a three-zone shell with narrow utility rail, wide central workspace, and inspection sidebar; interior sections rely on repeatable 12-column and split-grid modules.
breakpoints
1440 desktop maintains three columns, 768 tablet collapses the right sidebar below the main workspace, 375 mobile stacks all regions into a single scrolling command surface.
whitespace

Whitespace is economical and rhythmic, using small increments to preserve density while reserving larger spacing only for transitions between strategic modules.

guidance
do
  • Use blue only for meaningful interactive or analytical emphasis.
  • Keep row rules, column separators, and label strips visible so density feels organized.
  • Pair grotesk headlines with monospaced metadata to maintain a technical, audit-friendly tone.
avoid
  • Do not introduce soft rounded cards, pastel fills, or playful illustrations.
  • Do not remove grid lines in the name of minimalism; the structure is the identity.
  • Do not let accent blue become decorative background color or broad surface fill.
katagami spec
# Enterprise Mono-Grid Interfaces

## Philosophy

A restrained enterprise interface language built on disciplined monochrome grids, compact information density, and typographic contrast. It treats operational dashboards, review queues, and data workspaces as serious instruments: crisp white planes, graphite separators, steel-gray metadata, and a single electric-blue signal reserved for actionable state and analytical emphasis.

### Values

- Operational clarity over decorative novelty
- Dense information presented with strict rhythm and legible contrast
- Interfaces that feel precise, dependable, and audit-ready

### Anti-Values

- Playful softness, rounded consumer-app whimsy, or colorful abundance
- Floating card chaos, vague hierarchy, and ornamental motion

### Visual Character

- Thin but omnipresent 1px to 2px graphite grid lines divide every major region, creating spreadsheet-like structure across navigation rails, data panes, and summary blocks.
- Large uppercase grotesk headings pair with monospaced metadata rows, using hard typographic contrast rather than color to establish hierarchy and a controlled enterprise tone.
- Panels sit on cool white surfaces with subtle steel-gray banding and inset separators, while electric blue appears only in focused cells, links, selected rows, and live-state badges.
- Tables, stat strips, and filter bars align to a rigid modular column system with squared corners, compact padding, and visible row rules that make density feel deliberate instead of cramped.

## Tokens

### Colors

| Name | Value |
|------|-------|
| primary | `#20242b` |
| secondary | `#5e6877` |
| accent | `#2f6fff` |
| background | `#eef2f6` |
| surface | `#fbfdff` |
| text | `#15181d` |
| muted | `#7a8492` |
| border | `#b8c2cf` |
| error | `#c53b32` |
| success | `#1f7a55` |
| warning | `#a66a12` |
| info | `#2f6fff` |

### Typography

- **Heading Font**: Space Grotesk
- **Body Font**: IBM Plex Sans
- **Mono Font**: IBM Plex Mono
- **Base Size**: 16px
- **Scale Ratio**: 1.2
- **Line Height**: 1.5
- **Letter Spacing**: 0.01em
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600;700&family=Space+Grotesk:wght@500;700&display=swap

### Spacing

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

### Radii

- **None**: 0
- **Sm**: 0
- **Md**: 2px
- **Lg**: 4px
- **Full**: 9999px

### Shadows

- **Sm**: 0 1px 0 rgba(21,24,29,0.06)
- **Md**: 0 12px 30px rgba(21,24,29,0.06)
- **Lg**: 0 24px 60px rgba(21,24,29,0.09)

### Surfaces

- **Treatment**: flat
- **Card Style**: Cool white panels with subtle top-to-bottom tonal shifts, internal divider rules, and occasional steel-gray header bands for dense operational grouping.
- **Bg Pattern**: grid

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Borders are infrastructural and ever-present: crisp graphite rules, table row dividers, and vertical separators that make the interface feel engineered.

### Motion

- **Duration**: 160ms
- **Easing**: cubic-bezier(0.2, 0.7, 0, 1)
- **Philosophy**: snappy

## Rules

### Composition

Compose screens as a command workspace with fixed rails, a dominant analytical center, and a supporting inspection column so users can scan, compare, and act without losing context.

### Hierarchy

Use uppercase module labels, oversized numeric or analytical headlines, and monospaced row metadata to separate strategic summary from transactional detail.

### Density

High-density but controlled, with compact rows and disciplined spacing increments.

### Signature Patterns

- Every major panel includes exposed header bands or label strips with uppercase titles and a bottom rule, making section boundaries visible without relying on shadows.
- Data tables use full-width row dividers, mono-aligned numeric columns, and a blue left inset or outline only for the currently active or anomalous record.
- Navigation, filters, and summaries snap to a visible modular grid using squared containers, vertical separators, and repeated minmax columns that reinforce enterprise order.
- Interactive controls invert minimally on hover and show a precise blue focus ring or underline, keeping the monochrome system intact while making state unmistakable.

## Layout

### Grid

Desktop uses a three-zone shell with narrow utility rail, wide central workspace, and inspection sidebar; interior sections rely on repeatable 12-column and split-grid modules.

### Breakpoints

1440 desktop maintains three columns, 768 tablet collapses the right sidebar below the main workspace, 375 mobile stacks all regions into a single scrolling command surface.

### Whitespace

Whitespace is economical and rhythmic, using small increments to preserve density while reserving larger spacing only for transitions between strategic modules.

## Guidance

### Do

- Use blue only for meaningful interactive or analytical emphasis.
- Keep row rules, column separators, and label strips visible so density feels organized.
- Pair grotesk headlines with monospaced metadata to maintain a technical, audit-friendly tone.

### Don't

- Do not introduce soft rounded cards, pastel fills, or playful illustrations.
- Do not remove grid lines in the name of minimalism; the structure is the identity.
- Do not let accent blue become decorative background color or broad surface fill.
DESIGN.md
---
version: "alpha"
name: "Enterprise Mono-Grid Interfaces"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  primary: "#20242b"
  secondary: "#5e6877"
  accent: "#2f6fff"
  background: "#eef2f6"
  surface: "#fbfdff"
  text: "#15181d"
  muted: "#7a8492"
  border: "#b8c2cf"
  error: "#c53b32"
  success: "#1f7a55"
  warning: "#a66a12"
  info: "#2f6fff"
typography:
  headline-lg:
    fontFamily: "Space Grotesk"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "0.01em"
  headline-md:
    fontFamily: "Space Grotesk"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "0.01em"
  body-md:
    fontFamily: "IBM Plex Sans"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "0.01em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  none: "0px"
  sm: "0px"
  md: "2px"
  lg: "4px"
  full: "9999px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
components:
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  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"
---

# Enterprise Mono-Grid Interfaces

## Overview

A restrained enterprise interface language built on disciplined monochrome grids, compact information density, and typographic contrast. It treats operational dashboards, review queues, and data workspaces as serious instruments: crisp white planes, graphite separators, steel-gray metadata, and a single electric-blue signal reserved for actionable state and analytical emphasis.

### Values

- Operational clarity over decorative novelty
- Dense information presented with strict rhythm and legible contrast
- Interfaces that feel precise, dependable, and audit-ready

### Anti-Values

- Playful softness, rounded consumer-app whimsy, or colorful abundance
- Floating card chaos, vague hierarchy, and ornamental motion

### Visual Character

- Thin but omnipresent 1px to 2px graphite grid lines divide every major region, creating spreadsheet-like structure across navigation rails, data panes, and summary blocks.
- Large uppercase grotesk headings pair with monospaced metadata rows, using hard typographic contrast rather than color to establish hierarchy and a controlled enterprise tone.
- Panels sit on cool white surfaces with subtle steel-gray banding and inset separators, while electric blue appears only in focused cells, links, selected rows, and live-state badges.
- Tables, stat strips, and filter bars align to a rigid modular column system with squared corners, compact padding, and visible row rules that make density feel deliberate instead of cramped.

## Colors

Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.

| Token | Value |
|-------|-------|
| primary | `#20242b` |
| secondary | `#5e6877` |
| accent | `#2f6fff` |
| background | `#eef2f6` |
| surface | `#fbfdff` |
| text | `#15181d` |
| muted | `#7a8492` |
| border | `#b8c2cf` |
| error | `#c53b32` |
| success | `#1f7a55` |
| warning | `#a66a12` |
| info | `#2f6fff` |

## Typography

- **Headline-Lg**: Space Grotesk, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Space Grotesk, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: IBM Plex Sans, 16px, weight 400, line-height 1.5.
- **Label-Md**: IBM Plex Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

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

### Grid

Desktop uses a three-zone shell with narrow utility rail, wide central workspace, and inspection sidebar; interior sections rely on repeatable 12-column and split-grid modules.

### Breakpoints

1440 desktop maintains three columns, 768 tablet collapses the right sidebar below the main workspace, 375 mobile stacks all regions into a single scrolling command surface.

### Whitespace

Whitespace is economical and rhythmic, using small increments to preserve density while reserving larger spacing only for transitions between strategic modules.

## Elevation & Depth

### Shadows

- **Sm**: 0 1px 0 rgba(21,24,29,0.06)
- **Md**: 0 12px 30px rgba(21,24,29,0.06)
- **Lg**: 0 24px 60px rgba(21,24,29,0.09)

## Shapes

### Rounded

- **None**: `0px`
- **Sm**: `0px`
- **Md**: `2px`
- **Lg**: `4px`
- **Full**: `9999px`

### Surfaces

- **Treatment**: flat
- **Card Style**: Cool white panels with subtle top-to-bottom tonal shifts, internal divider rules, and occasional steel-gray header bands for dense operational grouping.
- **Bg Pattern**: grid

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Borders are infrastructural and ever-present: crisp graphite rules, table row dividers, and vertical separators that make the interface feel engineered.

## Components

### Composition

Compose screens as a command workspace with fixed rails, a dominant analytical center, and a supporting inspection column so users can scan, compare, and act without losing context.

### Hierarchy

Use uppercase module labels, oversized numeric or analytical headlines, and monospaced row metadata to separate strategic summary from transactional detail.

### Density

High-density but controlled, with compact rows and disciplined spacing increments.

### Signature Patterns

- Every major panel includes exposed header bands or label strips with uppercase titles and a bottom rule, making section boundaries visible without relying on shadows.
- Data tables use full-width row dividers, mono-aligned numeric columns, and a blue left inset or outline only for the currently active or anomalous record.
- Navigation, filters, and summaries snap to a visible modular grid using squared containers, vertical separators, and repeated minmax columns that reinforce enterprise order.
- Interactive controls invert minimally on hover and show a precise blue focus ring or underline, keeping the monochrome system intact while making state unmistakable.

## 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-019da325-be79-7850-bc40-cafd9f78cd89/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 blue only for meaningful interactive or analytical emphasis.
- Do Keep row rules, column separators, and label strips visible so density feels organized.
- Do Pair grotesk headlines with monospaced metadata to maintain a technical, audit-friendly tone.
- Don't Do not introduce soft rounded cards, pastel fills, or playful illustrations.
- Don't Do not remove grid lines in the name of minimalism; the structure is the identity.
- Don't Do not let accent blue become decorative background color or broad surface fill.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "enterprise-mono-grid-interfaces",
  "type": "registry:theme",
  "title": "Enterprise Mono-Grid Interfaces shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#eef2f6",
      "foreground": "#15181d",
      "card": "#fbfdff",
      "card-foreground": "#15181d",
      "popover": "#fbfdff",
      "popover-foreground": "#15181d",
      "primary": "#20242b",
      "primary-foreground": "#ffffff",
      "secondary": "#5e6877",
      "secondary-foreground": "#ffffff",
      "muted": "#7a8492",
      "muted-foreground": "#15181d",
      "accent": "#2f6fff",
      "accent-foreground": "#ffffff",
      "destructive": "#c53b32",
      "border": "#b8c2cf",
      "input": "#b8c2cf",
      "ring": "#2f6fff",
      "chart-1": "#20242b",
      "chart-2": "#5e6877",
      "chart-3": "#2f6fff",
      "chart-4": "#1f7a55",
      "chart-5": "#a66a12",
      "sidebar": "#fbfdff",
      "sidebar-foreground": "#15181d",
      "sidebar-primary": "#20242b",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#2f6fff",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#b8c2cf",
      "sidebar-ring": "#2f6fff",
      "radius": "2px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#20242b",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#2f6fff",
      "accent-foreground": "#ffffff",
      "destructive": "#c53b32",
      "border": "#303642",
      "input": "#303642",
      "ring": "#2f6fff",
      "chart-1": "#20242b",
      "chart-2": "#5e6877",
      "chart-3": "#2f6fff",
      "chart-4": "#1f7a55",
      "chart-5": "#a66a12",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#20242b",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#2f6fff",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#2f6fff",
      "radius": "2px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019da325-be79-7850-bc40-cafd9f78cd89",
    "slug": "enterprise-mono-grid-interfaces",
    "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": {
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · enterprise-mono-grid-interfaces
DESIGN.md

at a glance

Palette

Typography

headline-lgSpace Grotesk · 28px · 700

The quick brown fox jumps

headline-mdSpace Grotesk · 23px · 600

The quick brown fox jumps

body-mdIBM Plex Sans · 16px · 400

The quick brown fox jumps

label-mdIBM Plex 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

Shape

none0px
sm0px
md2px
lg4px
full9999px
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: #eef2f6;
  --foreground: #15181d;
  --card: #fbfdff;
  --card-foreground: #15181d;
  --popover: #fbfdff;
  --popover-foreground: #15181d;
  --primary: #20242b;
  --primary-foreground: #ffffff;
  --secondary: #5e6877;
  --secondary-foreground: #ffffff;
  --muted: #7a8492;
  --muted-foreground: #15181d;
  --accent: #2f6fff;
  --accent-foreground: #ffffff;
  --destructive: #c53b32;
  --border: #b8c2cf;
  --input: #b8c2cf;
  --ring: #2f6fff;
  --chart-1: #20242b;
  --chart-2: #5e6877;
  --chart-3: #2f6fff;
  --chart-4: #1f7a55;
  --chart-5: #a66a12;
  --sidebar: #fbfdff;
  --sidebar-foreground: #15181d;
  --sidebar-primary: #20242b;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #2f6fff;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #b8c2cf;
  --sidebar-ring: #2f6fff;
  --radius: 2px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #20242b;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #2f6fff;
  --accent-foreground: #ffffff;
  --destructive: #c53b32;
  --border: #303642;
  --input: #303642;
  --ring: #2f6fff;
  --chart-1: #20242b;
  --chart-2: #5e6877;
  --chart-3: #2f6fff;
  --chart-4: #1f7a55;
  --chart-5: #a66a12;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #20242b;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #2f6fff;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #2f6fff;
  --radius: 2px;
}
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 EnterpriseMonoGridInterfacesShadcnKit() {
  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">Enterprise Mono-Grid Interfaces</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": "enterprise-mono-grid-interfaces",
  "type": "registry:theme",
  "title": "Enterprise Mono-Grid Interfaces shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#eef2f6",
      "foreground": "#15181d",
      "card": "#fbfdff",
      "card-foreground": "#15181d",
      "popover": "#fbfdff",
      "popover-foreground": "#15181d",
      "primary": "#20242b",
      "primary-foreground": "#ffffff",
      "secondary": "#5e6877",
      "secondary-foreground": "#ffffff",
      "muted": "#7a8492",
      "muted-foreground": "#15181d",
      "accent": "#2f6fff",
      "accent-foreground": "#ffffff",
      "destructive": "#c53b32",
      "border": "#b8c2cf",
      "input": "#b8c2cf",
      "ring": "#2f6fff",
      "chart-1": "#20242b",
      "chart-2": "#5e6877",
      "chart-3": "#2f6fff",
      "chart-4": "#1f7a55",
      "chart-5": "#a66a12",
      "sidebar": "#fbfdff",
      "sidebar-foreground": "#15181d",
      "sidebar-primary": "#20242b",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#2f6fff",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#b8c2cf",
      "sidebar-ring": "#2f6fff",
      "radius": "2px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#20242b",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#2f6fff",
      "accent-foreground": "#ffffff",
      "destructive": "#c53b32",
      "border": "#303642",
      "input": "#303642",
      "ring": "#2f6fff",
      "chart-1": "#20242b",
      "chart-2": "#5e6877",
      "chart-3": "#2f6fff",
      "chart-4": "#1f7a55",
      "chart-5": "#a66a12",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#20242b",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#2f6fff",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#2f6fff",
      "radius": "2px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019da325-be79-7850-bc40-cafd9f78cd89",
    "slug": "enterprise-mono-grid-interfaces",
    "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": {
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ]
    }
  }
}
component recipescompatibility fallback
# Enterprise Mono-Grid Interfaces shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019da325-be79-7850-bc40-cafd9f78cd89`
Slug: `enterprise-mono-grid-interfaces`

## Intent

A restrained enterprise interface language built on disciplined monochrome grids, compact information density, and typographic contrast. It treats operational dashboards, review queues, and data workspaces as serious instruments: crisp white planes, graphite separators, steel-gray metadata, and a single electric-blue signal reserved for actionable state and analytical emphasis.

## 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:

{
  "primary": "#20242b",
  "secondary": "#5e6877",
  "accent": "#2f6fff",
  "background": "#eef2f6",
  "surface": "#fbfdff",
  "text": "#15181d",
  "muted": "#7a8492",
  "border": "#b8c2cf",
  "error": "#c53b32",
  "success": "#1f7a55",
  "warning": "#a66a12",
  "info": "#2f6fff"
}

Typography:

{
  "heading_font": "Space Grotesk",
  "body_font": "IBM Plex Sans",
  "mono_font": "IBM Plex Mono",
  "base_size": "16px",
  "scale_ratio": 1.2,
  "line_height": 1.5,
  "letter_spacing": "0.01em",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@400;500;600;700&family=Space+Grotesk:wght@500;700&display=swap"
}

## Visual character to preserve

- Thin but omnipresent 1px to 2px graphite grid lines divide every major region, creating spreadsheet-like structure across navigation rails, data panes, and summary blocks.
- Large uppercase grotesk headings pair with monospaced metadata rows, using hard typographic contrast rather than color to establish hierarchy and a controlled enterprise tone.
- Panels sit on cool white surfaces with subtle steel-gray banding and inset separators, while electric blue appears only in focused cells, links, selected rows, and live-state badges.
- Tables, stat strips, and filter bars align to a rigid modular column system with squared corners, compact padding, and visible row rules that make density feel deliberate instead of cramped.

## ShadSync visual profile

{
  "family": "system",
  "material": "flat",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": false,
  "stickerBadges": true,
  "motion": "still",
  "density": "dense",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.

### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.

### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.

### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.

### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.

## Preview shots

- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/enterprise-mono-grid-interfaces/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 blue only for meaningful interactive or analytical emphasis.; Keep row rules, column separators, and label strips visible so density feels organized.; Pair grotesk headlines with monospaced metadata to maintain a technical, audit-friendly tone.
- Do not: Do not introduce soft rounded cards, pastel fills, or playful illustrations.; Do not remove grid lines in the name of minimalism; the structure is the identity.; Do not let accent blue become decorative background color or broad surface fill.

## 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 EnterpriseMonoGridInterfacesShadcnKit() {
  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">Enterprise Mono-Grid Interfaces</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

{
  "grid": "Desktop uses a three-zone shell with narrow utility rail, wide central workspace, and inspection sidebar; interior sections rely on repeatable 12-column and split-grid modules.",
  "breakpoints": "1440 desktop maintains three columns, 768 tablet collapses the right sidebar below the main workspace, 375 mobile stacks all regions into a single scrolling command surface.",
  "whitespace": "Whitespace is economical and rhythmic, using small increments to preserve density while reserving larger spacing only for transitions between strategic modules."
}
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-019da325-be79-7850-bc40-cafd9f78cd89",
    "name": "Enterprise Mono-Grid Interfaces",
    "slug": "enterprise-mono-grid-interfaces"
  },
  "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": [
    "Thin but omnipresent 1px to 2px graphite grid lines divide every major region, creating spreadsheet-like structure across navigation rails, data panes, and summary blocks.",
    "Large uppercase grotesk headings pair with monospaced metadata rows, using hard typographic contrast rather than color to establish hierarchy and a controlled enterprise tone.",
    "Panels sit on cool white surfaces with subtle steel-gray banding and inset separators, while electric blue appears only in focused cells, links, selected rows, and live-state badges.",
    "Tables, stat strips, and filter bars align to a rigid modular column system with squared corners, compact padding, and visible row rules that make density feel deliberate instead of cramped."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": false,
    "stickerBadges": true,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Enterprise Mono-Grid Interfaces 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 blue only for meaningful interactive or analytical emphasis.",
      "Keep row rules, column separators, and label strips visible so density feels organized.",
      "Pair grotesk headlines with monospaced metadata to maintain a technical, audit-friendly tone."
    ],
    "dont": [
      "Do not introduce soft rounded cards, pastel fills, or playful illustrations.",
      "Do not remove grid lines in the name of minimalism; the structure is the identity.",
      "Do not let accent blue become decorative background color or broad surface fill."
    ]
  }
}
related

More like this