Anti-Design Brutalist Monochrome
A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.
Download DESIGN.md
Portable DESIGN.md source of truth for most agents and apps.
specification
philosophy
tokens
colors12 items
typography8 items
- heading font
- Archivo Black
- body font
- Azeret Mono
- mono font
- IBM Plex Mono
- base size
- 16px
- scale ratio
- 1.25
- line height
- 1.5
- letter spacing
- 0.01em
- google fonts url
- https://fonts.googleapis.com/css2?family=Archivo+Black&family=Azeret+Mono:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500;600;700&display=swap
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
radii5 items
- none
- 0
- sm
- 0
- md
- 0
- lg
- 0
- full
- 9999px
shadows3 items
- sm
- 4px 4px 0 rgba(0,0,0,0.7)
- md
- 8px 8px 0 rgba(0,0,0,0.82)
- lg
- 12px 12px 0 rgba(0,0,0,0.9)
surfaces3 items
- treatment
- paper
- card style
- Dirty off-white paper panels with black ruling lines, visible grain overlay, and layered black offset shadows that feel like stacked printed boards.
- bg pattern
- grid
borders4 items
- default width
- 3px
- accent width
- 4px
- style
- solid
- character
- Hard mechanical borders that feel stamped and uncompromising, always visible and often paired with offset duplicates or collision lines.
motion3 items
- duration
- 160ms
- easing
- cubic-bezier(0.2, 0.9, 0.2, 1)
- philosophy
- snappy
rules
Use an exposed editorial grid with oversized headline bands, stacked paper-like modules, and abrupt asymmetry. Layouts should look intentionally overbuilt, as if posters, tables, and utility strips were assembled by hand inside a browser window.
Primary hierarchy comes from typographic weight and border mass, not color. Massive uppercase headings, serial numbers, and stamped labels establish scanning order before body copy or iconography.
Medium-high density with tightly packed metadata, visible separators, and little ornamental breathing room. Space exists as structural gutters, not as airy luxury.
layout
Desktop uses a four-column exposed grid with a narrow serial rail, a dominant central work area, and stacked support modules. Tablet collapses to two columns, and mobile becomes a single brutal vertical stack.
Desktop 1440+, tablet 768-1023, mobile 375-767 with explicit reflow of headline bands, forms, and action groups.
Use tight but consistent gutters. Negative space should feel like production margin and crop marks, not soft luxury padding.
guidance
- Lead with enormous uppercase typography before introducing supporting copy.
- Keep borders, divider rules, and offset shadows visibly dominant in every module.
- Use monochrome contrast and texture shifts to separate layers instead of colorful decoration.
- Treat labels, timestamps, and status chips like stamped production metadata.
- Let small positional misalignments add tension without breaking usability.
- Do not round corners, blur surfaces, or introduce soft glassmorphic gradients.
- Do not rely on bright accent color to create hierarchy that typography and structure should handle.
- Do not center everything in a balanced startup-dashboard composition.
- Do not hide controls inside minimal ghost styling or invisible borders.
- Do not make the roughness so chaotic that scanning and interaction become unclear.
katagami spec
# Anti-Design Brutalist Monochrome ## Philosophy A confrontational monochrome interface language that borrows from anti-design websites, editorial brutalism, photocopied protest posters, and raw developer-built interfaces. It rejects polish in favor of visible structure, typographic aggression, and a deliberately awkward but still usable hierarchy. ### Values - Visible construction over seamless illusion - Typography as the primary navigational device - Utility, tension, and directness over comfort ### Anti-Values - Soft consumer-app friendliness - Decorative color-led delight without structural purpose - Invisible boundaries and floating ambiguity ### Visual Character - Every major container uses thick 3px to 4px soot-black borders, square corners, and slight rotational or positional offsets so the interface feels assembled from printed sheets pinned into a grid. - Headlines are oversized, condensed, uppercase blocks that dominate the viewport, often breaking onto abrupt lines and colliding with nearby rules so typography behaves like signage instead of gentle content chrome. - The background is a dirty off-white paper field with repeating grid lines, photocopy grain, and horizontal ruling marks that make the surface feel printed, handled, and slightly worn rather than digitally pristine. - Controls are stark black-on-off-white or inverted off-white-on-black slabs with hard underlines, stamped labels, and no rounded softness, creating a raw industrial form vocabulary. - Section metadata appears in compact monospace labels with aggressive letterspacing and boxed tags, giving the whole scene a marked-up production-sheet character. ## Tokens ### Colors | Name | Value | |------|-------| | primary | `#111111` | | secondary | `#2b2b2b` | | accent | `#6d6d6d` | | background | `#f1eee8` | | surface | `#f7f4ef` | | text | `#111111` | | muted | `#73706a` | | border | `#171717` | | error | `#2a2a2a` | | success | `#4d4d4d` | | warning | `#5a5a5a` | | info | `#858585` | ### Typography - **Heading Font**: Archivo Black - **Body Font**: Azeret Mono - **Mono Font**: IBM Plex Mono - **Base Size**: 16px - **Scale Ratio**: 1.25 - **Line Height**: 1.5 - **Letter Spacing**: 0.01em - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Archivo+Black&family=Azeret+Mono:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500;600;700&display=swap ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Radii - **None**: 0 - **Sm**: 0 - **Md**: 0 - **Lg**: 0 - **Full**: 9999px ### Shadows - **Sm**: 4px 4px 0 rgba(0,0,0,0.7) - **Md**: 8px 8px 0 rgba(0,0,0,0.82) - **Lg**: 12px 12px 0 rgba(0,0,0,0.9) ### Surfaces - **Treatment**: paper - **Card Style**: Dirty off-white paper panels with black ruling lines, visible grain overlay, and layered black offset shadows that feel like stacked printed boards. - **Bg Pattern**: grid ### Borders - **Default Width**: 3px - **Accent Width**: 4px - **Style**: solid - **Character**: Hard mechanical borders that feel stamped and uncompromising, always visible and often paired with offset duplicates or collision lines. ### Motion - **Duration**: 160ms - **Easing**: cubic-bezier(0.2, 0.9, 0.2, 1) - **Philosophy**: snappy ## Rules ### Composition Use an exposed editorial grid with oversized headline bands, stacked paper-like modules, and abrupt asymmetry. Layouts should look intentionally overbuilt, as if posters, tables, and utility strips were assembled by hand inside a browser window. ### Hierarchy Primary hierarchy comes from typographic weight and border mass, not color. Massive uppercase headings, serial numbers, and stamped labels establish scanning order before body copy or iconography. ### Density Medium-high density with tightly packed metadata, visible separators, and little ornamental breathing room. Space exists as structural gutters, not as airy luxury. ### Signature Patterns - Each major panel casts a hard offset black shadow and may be nudged with a tiny rotate or translate transform so modules feel misregistered like layered print sheets. - Section headers use thick top and bottom rules with uppercase condensed titles and monospace issue labels, creating a poster-strip motif across the interface. - Inputs, selects, and textareas are rendered as underlined or boxed mechanical controls with explicit 3px borders and harsh inverted focus states instead of soft fills. - Data rows and cards use repeated internal divider lines and boxed metadata tags so every container visibly declares its structure rather than hiding it. - Buttons invert from off-white to solid black on hover while shifting a few pixels, producing a blunt physical press effect rather than a smooth glossy transition. ## Layout ### Grid Desktop uses a four-column exposed grid with a narrow serial rail, a dominant central work area, and stacked support modules. Tablet collapses to two columns, and mobile becomes a single brutal vertical stack. ### Breakpoints Desktop 1440+, tablet 768-1023, mobile 375-767 with explicit reflow of headline bands, forms, and action groups. ### Whitespace Use tight but consistent gutters. Negative space should feel like production margin and crop marks, not soft luxury padding. ## Guidance ### Do - Lead with enormous uppercase typography before introducing supporting copy. - Keep borders, divider rules, and offset shadows visibly dominant in every module. - Use monochrome contrast and texture shifts to separate layers instead of colorful decoration. - Treat labels, timestamps, and status chips like stamped production metadata. - Let small positional misalignments add tension without breaking usability. ### Don't - Do not round corners, blur surfaces, or introduce soft glassmorphic gradients. - Do not rely on bright accent color to create hierarchy that typography and structure should handle. - Do not center everything in a balanced startup-dashboard composition. - Do not hide controls inside minimal ghost styling or invisible borders. - Do not make the roughness so chaotic that scanning and interaction become unclear.
DESIGN.md
---
version: "alpha"
name: "Anti-Design Brutalist Monochrome"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
primary: "#111111"
secondary: "#2b2b2b"
accent: "#6d6d6d"
background: "#f1eee8"
surface: "#f7f4ef"
text: "#111111"
muted: "#73706a"
border: "#171717"
error: "#2a2a2a"
success: "#4d4d4d"
warning: "#5a5a5a"
info: "#858585"
typography:
headline-lg:
fontFamily: "Archivo Black"
fontSize: "1.953rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "0.01em"
headline-md:
fontFamily: "Archivo Black"
fontSize: "1.563rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "0.01em"
body-md:
fontFamily: "Azeret Mono"
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: "0px"
lg: "0px"
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"
---
# Anti-Design Brutalist Monochrome
## Overview
A confrontational monochrome interface language that borrows from anti-design websites, editorial brutalism, photocopied protest posters, and raw developer-built interfaces. It rejects polish in favor of visible structure, typographic aggression, and a deliberately awkward but still usable hierarchy.
### Values
- Visible construction over seamless illusion
- Typography as the primary navigational device
- Utility, tension, and directness over comfort
### Anti-Values
- Soft consumer-app friendliness
- Decorative color-led delight without structural purpose
- Invisible boundaries and floating ambiguity
### Visual Character
- Every major container uses thick 3px to 4px soot-black borders, square corners, and slight rotational or positional offsets so the interface feels assembled from printed sheets pinned into a grid.
- Headlines are oversized, condensed, uppercase blocks that dominate the viewport, often breaking onto abrupt lines and colliding with nearby rules so typography behaves like signage instead of gentle content chrome.
- The background is a dirty off-white paper field with repeating grid lines, photocopy grain, and horizontal ruling marks that make the surface feel printed, handled, and slightly worn rather than digitally pristine.
- Controls are stark black-on-off-white or inverted off-white-on-black slabs with hard underlines, stamped labels, and no rounded softness, creating a raw industrial form vocabulary.
- Section metadata appears in compact monospace labels with aggressive letterspacing and boxed tags, giving the whole scene a marked-up production-sheet character.
## 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 | `#111111` |
| secondary | `#2b2b2b` |
| accent | `#6d6d6d` |
| background | `#f1eee8` |
| surface | `#f7f4ef` |
| text | `#111111` |
| muted | `#73706a` |
| border | `#171717` |
| error | `#2a2a2a` |
| success | `#4d4d4d` |
| warning | `#5a5a5a` |
| info | `#858585` |
## Typography
- **Headline-Lg**: Archivo Black, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Archivo Black, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Azeret Mono, 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 four-column exposed grid with a narrow serial rail, a dominant central work area, and stacked support modules. Tablet collapses to two columns, and mobile becomes a single brutal vertical stack.
### Breakpoints
Desktop 1440+, tablet 768-1023, mobile 375-767 with explicit reflow of headline bands, forms, and action groups.
### Whitespace
Use tight but consistent gutters. Negative space should feel like production margin and crop marks, not soft luxury padding.
## Elevation & Depth
### Shadows
- **Sm**: 4px 4px 0 rgba(0,0,0,0.7)
- **Md**: 8px 8px 0 rgba(0,0,0,0.82)
- **Lg**: 12px 12px 0 rgba(0,0,0,0.9)
## Shapes
### Rounded
- **None**: `0px`
- **Sm**: `0px`
- **Md**: `0px`
- **Lg**: `0px`
- **Full**: `9999px`
### Surfaces
- **Treatment**: paper
- **Card Style**: Dirty off-white paper panels with black ruling lines, visible grain overlay, and layered black offset shadows that feel like stacked printed boards.
- **Bg Pattern**: grid
### Borders
- **Default Width**: 3px
- **Accent Width**: 4px
- **Style**: solid
- **Character**: Hard mechanical borders that feel stamped and uncompromising, always visible and often paired with offset duplicates or collision lines.
## Components
### Composition
Use an exposed editorial grid with oversized headline bands, stacked paper-like modules, and abrupt asymmetry. Layouts should look intentionally overbuilt, as if posters, tables, and utility strips were assembled by hand inside a browser window.
### Hierarchy
Primary hierarchy comes from typographic weight and border mass, not color. Massive uppercase headings, serial numbers, and stamped labels establish scanning order before body copy or iconography.
### Density
Medium-high density with tightly packed metadata, visible separators, and little ornamental breathing room. Space exists as structural gutters, not as airy luxury.
### Signature Patterns
- Each major panel casts a hard offset black shadow and may be nudged with a tiny rotate or translate transform so modules feel misregistered like layered print sheets.
- Section headers use thick top and bottom rules with uppercase condensed titles and monospace issue labels, creating a poster-strip motif across the interface.
- Inputs, selects, and textareas are rendered as underlined or boxed mechanical controls with explicit 3px borders and harsh inverted focus states instead of soft fills.
- Data rows and cards use repeated internal divider lines and boxed metadata tags so every container visibly declares its structure rather than hiding it.
- Buttons invert from off-white to solid black on hover while shifting a few pixels, producing a blunt physical press effect rather than a smooth glossy transition.
## 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-019da32b-3350-7bf0-9114-0fb194d3d7e5/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 Lead with enormous uppercase typography before introducing supporting copy.
- Do Keep borders, divider rules, and offset shadows visibly dominant in every module.
- Do Use monochrome contrast and texture shifts to separate layers instead of colorful decoration.
- Do Treat labels, timestamps, and status chips like stamped production metadata.
- Do Let small positional misalignments add tension without breaking usability.
- Don't Do not round corners, blur surfaces, or introduce soft glassmorphic gradients.
- Don't Do not rely on bright accent color to create hierarchy that typography and structure should handle.
- Don't Do not center everything in a balanced startup-dashboard composition.
- Don't Do not hide controls inside minimal ghost styling or invisible borders.
- Don't Do not make the roughness so chaotic that scanning and interaction become unclear.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "anti-design-brutalist-monochrome",
"type": "registry:theme",
"title": "Anti-Design Brutalist Monochrome shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#f1eee8",
"foreground": "#111111",
"card": "#f7f4ef",
"card-foreground": "#111111",
"popover": "#f7f4ef",
"popover-foreground": "#111111",
"primary": "#111111",
"primary-foreground": "#ffffff",
"secondary": "#2b2b2b",
"secondary-foreground": "#ffffff",
"muted": "#73706a",
"muted-foreground": "#111111",
"accent": "#6d6d6d",
"accent-foreground": "#ffffff",
"destructive": "#2a2a2a",
"border": "#171717",
"input": "#171717",
"ring": "#6d6d6d",
"chart-1": "#111111",
"chart-2": "#2b2b2b",
"chart-3": "#6d6d6d",
"chart-4": "#4d4d4d",
"chart-5": "#5a5a5a",
"sidebar": "#f7f4ef",
"sidebar-foreground": "#111111",
"sidebar-primary": "#111111",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#858585",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#171717",
"sidebar-ring": "#6d6d6d",
"radius": "0"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#111111",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#6d6d6d",
"accent-foreground": "#ffffff",
"destructive": "#2a2a2a",
"border": "#303642",
"input": "#303642",
"ring": "#6d6d6d",
"chart-1": "#111111",
"chart-2": "#2b2b2b",
"chart-3": "#6d6d6d",
"chart-4": "#4d4d4d",
"chart-5": "#5a5a5a",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#111111",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#6d6d6d",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#6d6d6d",
"radius": "0"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019da32b-3350-7bf0-9114-0fb194d3d7e5",
"slug": "anti-design-brutalist-monochrome",
"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"
]
}
}
}
```embodiments
at a glance
Typography
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Components
Components rendered with this language’s tokens — colors, type, and rounded corners as specified.
Spacing
- base8px
- xs4px
- sm8px
- md12px
- lg16px
- xl24px
- 2xl32px
- 3xl48px
- 4xl64px
Shape
implementation kit
DESIGN.md with shadcn
Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.
advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #f1eee8;
--foreground: #111111;
--card: #f7f4ef;
--card-foreground: #111111;
--popover: #f7f4ef;
--popover-foreground: #111111;
--primary: #111111;
--primary-foreground: #ffffff;
--secondary: #2b2b2b;
--secondary-foreground: #ffffff;
--muted: #73706a;
--muted-foreground: #111111;
--accent: #6d6d6d;
--accent-foreground: #ffffff;
--destructive: #2a2a2a;
--border: #171717;
--input: #171717;
--ring: #6d6d6d;
--chart-1: #111111;
--chart-2: #2b2b2b;
--chart-3: #6d6d6d;
--chart-4: #4d4d4d;
--chart-5: #5a5a5a;
--sidebar: #f7f4ef;
--sidebar-foreground: #111111;
--sidebar-primary: #111111;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #858585;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #171717;
--sidebar-ring: #6d6d6d;
--radius: 0;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #111111;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #6d6d6d;
--accent-foreground: #ffffff;
--destructive: #2a2a2a;
--border: #303642;
--input: #303642;
--ring: #6d6d6d;
--chart-1: #111111;
--chart-2: #2b2b2b;
--chart-3: #6d6d6d;
--chart-4: #4d4d4d;
--chart-5: #5a5a5a;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #111111;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #6d6d6d;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #303642;
--sidebar-ring: #6d6d6d;
--radius: 0;
}
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 AntiDesignBrutalistMonochromeShadcnKit() {
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">Anti-Design Brutalist Monochrome</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "anti-design-brutalist-monochrome",
"type": "registry:theme",
"title": "Anti-Design Brutalist Monochrome shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#f1eee8",
"foreground": "#111111",
"card": "#f7f4ef",
"card-foreground": "#111111",
"popover": "#f7f4ef",
"popover-foreground": "#111111",
"primary": "#111111",
"primary-foreground": "#ffffff",
"secondary": "#2b2b2b",
"secondary-foreground": "#ffffff",
"muted": "#73706a",
"muted-foreground": "#111111",
"accent": "#6d6d6d",
"accent-foreground": "#ffffff",
"destructive": "#2a2a2a",
"border": "#171717",
"input": "#171717",
"ring": "#6d6d6d",
"chart-1": "#111111",
"chart-2": "#2b2b2b",
"chart-3": "#6d6d6d",
"chart-4": "#4d4d4d",
"chart-5": "#5a5a5a",
"sidebar": "#f7f4ef",
"sidebar-foreground": "#111111",
"sidebar-primary": "#111111",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#858585",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#171717",
"sidebar-ring": "#6d6d6d",
"radius": "0"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#111111",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#6d6d6d",
"accent-foreground": "#ffffff",
"destructive": "#2a2a2a",
"border": "#303642",
"input": "#303642",
"ring": "#6d6d6d",
"chart-1": "#111111",
"chart-2": "#2b2b2b",
"chart-3": "#6d6d6d",
"chart-4": "#4d4d4d",
"chart-5": "#5a5a5a",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#111111",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#6d6d6d",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#303642",
"sidebar-ring": "#6d6d6d",
"radius": "0"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019da32b-3350-7bf0-9114-0fb194d3d7e5",
"slug": "anti-design-brutalist-monochrome",
"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"
]
}
}
}
# Anti-Design Brutalist Monochrome shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019da32b-3350-7bf0-9114-0fb194d3d7e5`
Slug: `anti-design-brutalist-monochrome`
## Intent
A confrontational monochrome interface language that borrows from anti-design websites, editorial brutalism, photocopied protest posters, and raw developer-built interfaces. It rejects polish in favor of visible structure, typographic aggression, and a deliberately awkward but still usable hierarchy.
## 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": "#111111",
"secondary": "#2b2b2b",
"accent": "#6d6d6d",
"background": "#f1eee8",
"surface": "#f7f4ef",
"text": "#111111",
"muted": "#73706a",
"border": "#171717",
"error": "#2a2a2a",
"success": "#4d4d4d",
"warning": "#5a5a5a",
"info": "#858585"
}
Typography:
{
"heading_font": "Archivo Black",
"body_font": "Azeret Mono",
"mono_font": "IBM Plex Mono",
"base_size": "16px",
"scale_ratio": 1.25,
"line_height": 1.5,
"letter_spacing": "0.01em",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Archivo+Black&family=Azeret+Mono:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500;600;700&display=swap"
}
## Visual character to preserve
- Every major container uses thick 3px to 4px soot-black borders, square corners, and slight rotational or positional offsets so the interface feels assembled from printed sheets pinned into a grid.
- Headlines are oversized, condensed, uppercase blocks that dominate the viewport, often breaking onto abrupt lines and colliding with nearby rules so typography behaves like signage instead of gentle content chrome.
- The background is a dirty off-white paper field with repeating grid lines, photocopy grain, and horizontal ruling marks that make the surface feel printed, handled, and slightly worn rather than digitally pristine.
- Controls are stark black-on-off-white or inverted off-white-on-black slabs with hard underlines, stamped labels, and no rounded softness, creating a raw industrial form vocabulary.
- Section metadata appears in compact monospace labels with aggressive letterspacing and boxed tags, giving the whole scene a marked-up production-sheet character.
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": true,
"motion": "lift-rotate",
"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/anti-design-brutalist-monochrome/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: Lead with enormous uppercase typography before introducing supporting copy.; Keep borders, divider rules, and offset shadows visibly dominant in every module.; Use monochrome contrast and texture shifts to separate layers instead of colorful decoration.; Treat labels, timestamps, and status chips like stamped production metadata.; Let small positional misalignments add tension without breaking usability.
- Do not: Do not round corners, blur surfaces, or introduce soft glassmorphic gradients.; Do not rely on bright accent color to create hierarchy that typography and structure should handle.; Do not center everything in a balanced startup-dashboard composition.; Do not hide controls inside minimal ghost styling or invisible borders.; Do not make the roughness so chaotic that scanning and interaction become unclear.
## 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 AntiDesignBrutalistMonochromeShadcnKit() {
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">Anti-Design Brutalist Monochrome</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 four-column exposed grid with a narrow serial rail, a dominant central work area, and stacked support modules. Tablet collapses to two columns, and mobile becomes a single brutal vertical stack.",
"breakpoints": "Desktop 1440+, tablet 768-1023, mobile 375-767 with explicit reflow of headline bands, forms, and action groups.",
"whitespace": "Use tight but consistent gutters. Negative space should feel like production margin and crop marks, not soft luxury padding."
}
{
"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-019da32b-3350-7bf0-9114-0fb194d3d7e5",
"name": "Anti-Design Brutalist Monochrome",
"slug": "anti-design-brutalist-monochrome"
},
"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": [
"Every major container uses thick 3px to 4px soot-black borders, square corners, and slight rotational or positional offsets so the interface feels assembled from printed sheets pinned into a grid.",
"Headlines are oversized, condensed, uppercase blocks that dominate the viewport, often breaking onto abrupt lines and colliding with nearby rules so typography behaves like signage instead of gentle content chrome.",
"The background is a dirty off-white paper field with repeating grid lines, photocopy grain, and horizontal ruling marks that make the surface feel printed, handled, and slightly worn rather than digitally pristine.",
"Controls are stark black-on-off-white or inverted off-white-on-black slabs with hard underlines, stamped labels, and no rounded softness, creating a raw industrial form vocabulary.",
"Section metadata appears in compact monospace labels with aggressive letterspacing and boxed tags, giving the whole scene a marked-up production-sheet character."
],
"visualProfile": {
"family": "paper-collage",
"material": "paper",
"contour": "default",
"border": "solid",
"underlay": true,
"grain": true,
"stickerBadges": true,
"motion": "lift-rotate",
"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": "Anti-Design Brutalist Monochrome 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": [
"Lead with enormous uppercase typography before introducing supporting copy.",
"Keep borders, divider rules, and offset shadows visibly dominant in every module.",
"Use monochrome contrast and texture shifts to separate layers instead of colorful decoration.",
"Treat labels, timestamps, and status chips like stamped production metadata.",
"Let small positional misalignments add tension without breaking usability."
],
"dont": [
"Do not round corners, blur surfaces, or introduce soft glassmorphic gradients.",
"Do not rely on bright accent color to create hierarchy that typography and structure should handle.",
"Do not center everything in a balanced startup-dashboard composition.",
"Do not hide controls inside minimal ghost styling or invisible borders.",
"Do not make the roughness so chaotic that scanning and interaction become unclear."
]
}
}