back to gallery
design language·bauhaus-functional-geometry

Bauhaus Functional Geometry

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 design language that translates Bauhaus workshop logic into interface structure: primary geometry, visible construction lines, disciplined asymmetry, and typography treated as architecture rather than decoration. It feels educational, industrial, and optimistic, using color blocks as navigational anchors and black rules as the skeleton that keeps expressive geometry functional.
values
Function stated through formGeometric clarity before ornamentTypography as structural framingAsymmetry balanced by grid discipline
anti-values
×Soft decorative luxury styling×Glassy atmospheric gradients×Invisible containers and vague hierarchy
tokens
colors12 items
primary
#C63A2F
secondary
#2E5FA5
accent
#D4A62A
background
#F3EBD9
surface
#FFF9EE
text
#1E1B18
muted
#6E655A
border
#1F1A17
error
#B23A32
success
#3C7A4B
warning
#BA7A16
info
#355F8C
typography8 items
heading font
League Spartan
body font
Archivo
mono font
Space 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:wght@400;500;600;700&family=League+Spartan:wght@500;700;800&family=Space+Mono:wght@400;700&display=swap
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
radii5 items
none
0
sm
6px
md
14px
lg
24px
full
9999px
shadows3 items
sm
4px 4px 0 #1F1A17
md
8px 8px 0 #1F1A17
lg
14px 14px 0 #1F1A17
surfaces3 items
treatment
paper
card style
Warm ivory paper panels with flat color insets, exposed divider lines, and occasional circular overlays that read like printed geometric studies.
bg pattern
grid
borders4 items
default width
2px
accent width
4px
style
solid
character
Borders are assertive drafting rules: dark, straight, and always visible enough to separate modules with poster-like authority.
motion3 items
duration
180ms
easing
cubic-bezier(0.2, 0.8, 0.2, 1)
philosophy
snappy
rules
composition
Compose each screen like a Bauhaus poster translated into product UI: dominant geometric hero block, secondary stacked utilities, and strong line divisions that make every zone legible at a glance.
hierarchy
Hierarchy comes from scale, weight, and color fields rather than subtle shadow alone; headlines claim area, metrics sit inside framed units, and labels are compressed into disciplined caption strips.
density

Moderate density with clear segmentation: enough information to feel operational, but every cluster gets its own ruled container and negative space buffer.

signature patterns
Use black horizontal and vertical rules that visibly intersect panels, so cards often look like sections cut from a larger technical poster rather than isolated floating tiles.Pair rectangular content blocks with one oversized absolute-positioned circle or semicircle in a primary color, partially cropped by the container edge to create geometric tension.Build buttons, tabs, and stat chips with flat fills plus offset shadow slabs, making interaction states feel like printed labels mounted above the page surface.Create asymmetric split layouts where one column is substantially wider, and punctuate the narrower side with stacked color-bar headers and numbered mono annotations.Apply uppercase heading locks and compressed label strips in contrasting color bands, using typography as a modular block that participates in the geometry of the layout.
layout
grid
A 12-column desktop grid with one dominant 7-column narrative area and a 5-column utility rail; tablet collapses to 8 columns and mobile to a single stacked flow.
breakpoints

Desktop default, tablet at 980px, mobile at 680px with all compositions reflowing into stacked panels and full-width actions.

whitespace
Use deliberate negative space around geometric anchors; padding is generous inside panels, but outer gaps stay tight enough to preserve the poster-like composition.
guidance
do
  • Let one geometric element dominate each composition.
  • Keep borders, divider lines, and label bands visibly structural.
  • Use primary colors sparingly but boldly on large shapes and control groups.
  • Make typography blocky, uppercase, and clearly staged by scale.
avoid
  • Do not soften the system with frosted transparency or blurred gradients.
  • Do not hide structure behind borderless floating cards.
  • Do not use pastel ambiguity or too many accent colors.
  • Do not center everything; asymmetry is part of the identity.
katagami spec
# Bauhaus Functional Geometry

## Philosophy

A design language that translates Bauhaus workshop logic into interface structure: primary geometry, visible construction lines, disciplined asymmetry, and typography treated as architecture rather than decoration. It feels educational, industrial, and optimistic, using color blocks as navigational anchors and black rules as the skeleton that keeps expressive geometry functional.

### Values

- Function stated through form
- Geometric clarity before ornament
- Typography as structural framing
- Asymmetry balanced by grid discipline

### Anti-Values

- Soft decorative luxury styling
- Glassy atmospheric gradients
- Invisible containers and vague hierarchy

### Visual Character

- Large flat rectangles and circles in primary red, cobalt blue, and mustard are pinned against warm ivory fields, acting as spatial anchors rather than small accent flourishes.
- Every major panel is defined by crisp charcoal borders between 2px and 4px, with visible divider rules that make the composition feel drafted and constructed like a workshop poster.
- Headings use oversized uppercase geometric sans typography with tight line height, while labels and metrics sit in disciplined mono or compact sans blocks that resemble instructional signage.
- Layouts are intentionally asymmetric: one oversized hero column is counterweighted by stacked utility panels, with generous negative space preserving order around bold geometric forms.
- Interactive elements use flat fills, square or slightly rounded corners, and offset color bars or circular markers so controls feel fabricated, not soft or skeuomorphic.

## Tokens

### Colors

| Name | Value |
|------|-------|
| primary | `#C63A2F` |
| secondary | `#2E5FA5` |
| accent | `#D4A62A` |
| background | `#F3EBD9` |
| surface | `#FFF9EE` |
| text | `#1E1B18` |
| muted | `#6E655A` |
| border | `#1F1A17` |
| error | `#B23A32` |
| success | `#3C7A4B` |
| warning | `#BA7A16` |
| info | `#355F8C` |

### Typography

- **Heading Font**: League Spartan
- **Body Font**: Archivo
- **Mono Font**: Space 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:wght@400;500;600;700&family=League+Spartan:wght@500;700;800&family=Space+Mono:wght@400;700&display=swap

### Spacing

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

### Radii

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

### Shadows

- **Sm**: 4px 4px 0 #1F1A17
- **Md**: 8px 8px 0 #1F1A17
- **Lg**: 14px 14px 0 #1F1A17

### Surfaces

- **Treatment**: paper
- **Card Style**: Warm ivory paper panels with flat color insets, exposed divider lines, and occasional circular overlays that read like printed geometric studies.
- **Bg Pattern**: grid

### Borders

- **Default Width**: 2px
- **Accent Width**: 4px
- **Style**: solid
- **Character**: Borders are assertive drafting rules: dark, straight, and always visible enough to separate modules with poster-like authority.

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1)
- **Philosophy**: snappy

## Rules

### Composition

Compose each screen like a Bauhaus poster translated into product UI: dominant geometric hero block, secondary stacked utilities, and strong line divisions that make every zone legible at a glance.

### Hierarchy

Hierarchy comes from scale, weight, and color fields rather than subtle shadow alone; headlines claim area, metrics sit inside framed units, and labels are compressed into disciplined caption strips.

### Density

Moderate density with clear segmentation: enough information to feel operational, but every cluster gets its own ruled container and negative space buffer.

### Signature Patterns

- Use black horizontal and vertical rules that visibly intersect panels, so cards often look like sections cut from a larger technical poster rather than isolated floating tiles.
- Pair rectangular content blocks with one oversized absolute-positioned circle or semicircle in a primary color, partially cropped by the container edge to create geometric tension.
- Build buttons, tabs, and stat chips with flat fills plus offset shadow slabs, making interaction states feel like printed labels mounted above the page surface.
- Create asymmetric split layouts where one column is substantially wider, and punctuate the narrower side with stacked color-bar headers and numbered mono annotations.
- Apply uppercase heading locks and compressed label strips in contrasting color bands, using typography as a modular block that participates in the geometry of the layout.

## Layout

### Grid

A 12-column desktop grid with one dominant 7-column narrative area and a 5-column utility rail; tablet collapses to 8 columns and mobile to a single stacked flow.

### Breakpoints

Desktop default, tablet at 980px, mobile at 680px with all compositions reflowing into stacked panels and full-width actions.

### Whitespace

Use deliberate negative space around geometric anchors; padding is generous inside panels, but outer gaps stay tight enough to preserve the poster-like composition.

## Guidance

### Do

- Let one geometric element dominate each composition.
- Keep borders, divider lines, and label bands visibly structural.
- Use primary colors sparingly but boldly on large shapes and control groups.
- Make typography blocky, uppercase, and clearly staged by scale.

### Don't

- Do not soften the system with frosted transparency or blurred gradients.
- Do not hide structure behind borderless floating cards.
- Do not use pastel ambiguity or too many accent colors.
- Do not center everything; asymmetry is part of the identity.
DESIGN.md
---
version: "alpha"
name: "Bauhaus Functional Geometry"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  primary: "#C63A2F"
  secondary: "#2E5FA5"
  accent: "#D4A62A"
  background: "#F3EBD9"
  surface: "#FFF9EE"
  text: "#1E1B18"
  muted: "#6E655A"
  border: "#1F1A17"
  error: "#B23A32"
  success: "#3C7A4B"
  warning: "#BA7A16"
  info: "#355F8C"
typography:
  headline-lg:
    fontFamily: "League Spartan"
    fontSize: "1.953rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "0.01em"
  headline-md:
    fontFamily: "League Spartan"
    fontSize: "1.563rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "0.01em"
  body-md:
    fontFamily: "Archivo"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "0.01em"
  label-md:
    fontFamily: "Space Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  none: "0px"
  sm: "6px"
  md: "14px"
  lg: "24px"
  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"
---

# Bauhaus Functional Geometry

## Overview

A design language that translates Bauhaus workshop logic into interface structure: primary geometry, visible construction lines, disciplined asymmetry, and typography treated as architecture rather than decoration. It feels educational, industrial, and optimistic, using color blocks as navigational anchors and black rules as the skeleton that keeps expressive geometry functional.

### Values

- Function stated through form
- Geometric clarity before ornament
- Typography as structural framing
- Asymmetry balanced by grid discipline

### Anti-Values

- Soft decorative luxury styling
- Glassy atmospheric gradients
- Invisible containers and vague hierarchy

### Visual Character

- Large flat rectangles and circles in primary red, cobalt blue, and mustard are pinned against warm ivory fields, acting as spatial anchors rather than small accent flourishes.
- Every major panel is defined by crisp charcoal borders between 2px and 4px, with visible divider rules that make the composition feel drafted and constructed like a workshop poster.
- Headings use oversized uppercase geometric sans typography with tight line height, while labels and metrics sit in disciplined mono or compact sans blocks that resemble instructional signage.
- Layouts are intentionally asymmetric: one oversized hero column is counterweighted by stacked utility panels, with generous negative space preserving order around bold geometric forms.
- Interactive elements use flat fills, square or slightly rounded corners, and offset color bars or circular markers so controls feel fabricated, not soft or skeuomorphic.

## 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 | `#C63A2F` |
| secondary | `#2E5FA5` |
| accent | `#D4A62A` |
| background | `#F3EBD9` |
| surface | `#FFF9EE` |
| text | `#1E1B18` |
| muted | `#6E655A` |
| border | `#1F1A17` |
| error | `#B23A32` |
| success | `#3C7A4B` |
| warning | `#BA7A16` |
| info | `#355F8C` |

## Typography

- **Headline-Lg**: League Spartan, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: League Spartan, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Archivo, 16px, weight 400, line-height 1.5.
- **Label-Md**: Space 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

A 12-column desktop grid with one dominant 7-column narrative area and a 5-column utility rail; tablet collapses to 8 columns and mobile to a single stacked flow.

### Breakpoints

Desktop default, tablet at 980px, mobile at 680px with all compositions reflowing into stacked panels and full-width actions.

### Whitespace

Use deliberate negative space around geometric anchors; padding is generous inside panels, but outer gaps stay tight enough to preserve the poster-like composition.

## Elevation & Depth

### Shadows

- **Sm**: 4px 4px 0 #1F1A17
- **Md**: 8px 8px 0 #1F1A17
- **Lg**: 14px 14px 0 #1F1A17

## Shapes

### Rounded

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

### Surfaces

- **Treatment**: paper
- **Card Style**: Warm ivory paper panels with flat color insets, exposed divider lines, and occasional circular overlays that read like printed geometric studies.
- **Bg Pattern**: grid

### Borders

- **Default Width**: 2px
- **Accent Width**: 4px
- **Style**: solid
- **Character**: Borders are assertive drafting rules: dark, straight, and always visible enough to separate modules with poster-like authority.

## Components

### Composition

Compose each screen like a Bauhaus poster translated into product UI: dominant geometric hero block, secondary stacked utilities, and strong line divisions that make every zone legible at a glance.

### Hierarchy

Hierarchy comes from scale, weight, and color fields rather than subtle shadow alone; headlines claim area, metrics sit inside framed units, and labels are compressed into disciplined caption strips.

### Density

Moderate density with clear segmentation: enough information to feel operational, but every cluster gets its own ruled container and negative space buffer.

### Signature Patterns

- Use black horizontal and vertical rules that visibly intersect panels, so cards often look like sections cut from a larger technical poster rather than isolated floating tiles.
- Pair rectangular content blocks with one oversized absolute-positioned circle or semicircle in a primary color, partially cropped by the container edge to create geometric tension.
- Build buttons, tabs, and stat chips with flat fills plus offset shadow slabs, making interaction states feel like printed labels mounted above the page surface.
- Create asymmetric split layouts where one column is substantially wider, and punctuate the narrower side with stacked color-bar headers and numbered mono annotations.
- Apply uppercase heading locks and compressed label strips in contrasting color bands, using typography as a modular block that participates in the geometry of the layout.

## 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-019da2ca-82fd-7261-94a9-d9278375958e/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 Let one geometric element dominate each composition.
- Do Keep borders, divider lines, and label bands visibly structural.
- Do Use primary colors sparingly but boldly on large shapes and control groups.
- Do Make typography blocky, uppercase, and clearly staged by scale.
- Don't Do not soften the system with frosted transparency or blurred gradients.
- Don't Do not hide structure behind borderless floating cards.
- Don't Do not use pastel ambiguity or too many accent colors.
- Don't Do not center everything; asymmetry is part of the identity.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "bauhaus-functional-geometry",
  "type": "registry:theme",
  "title": "Bauhaus Functional Geometry shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F3EBD9",
      "foreground": "#1E1B18",
      "card": "#FFF9EE",
      "card-foreground": "#1E1B18",
      "popover": "#FFF9EE",
      "popover-foreground": "#1E1B18",
      "primary": "#C63A2F",
      "primary-foreground": "#ffffff",
      "secondary": "#2E5FA5",
      "secondary-foreground": "#ffffff",
      "muted": "#6E655A",
      "muted-foreground": "#1E1B18",
      "accent": "#D4A62A",
      "accent-foreground": "#ffffff",
      "destructive": "#B23A32",
      "border": "#1F1A17",
      "input": "#1F1A17",
      "ring": "#D4A62A",
      "chart-1": "#C63A2F",
      "chart-2": "#2E5FA5",
      "chart-3": "#D4A62A",
      "chart-4": "#3C7A4B",
      "chart-5": "#BA7A16",
      "sidebar": "#FFF9EE",
      "sidebar-foreground": "#1E1B18",
      "sidebar-primary": "#C63A2F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#355F8C",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#1F1A17",
      "sidebar-ring": "#D4A62A",
      "radius": "14px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#C63A2F",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#D4A62A",
      "accent-foreground": "#ffffff",
      "destructive": "#B23A32",
      "border": "#303642",
      "input": "#303642",
      "ring": "#D4A62A",
      "chart-1": "#C63A2F",
      "chart-2": "#2E5FA5",
      "chart-3": "#D4A62A",
      "chart-4": "#3C7A4B",
      "chart-5": "#BA7A16",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#C63A2F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#D4A62A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#D4A62A",
      "radius": "14px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019da2ca-82fd-7261-94a9-d9278375958e",
    "slug": "bauhaus-functional-geometry",
    "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 · bauhaus-functional-geometry
DESIGN.md

at a glance

Palette

Typography

headline-lgLeague Spartan · 31px · 700

The quick brown fox jumps

headline-mdLeague Spartan · 25px · 600

The quick brown fox jumps

body-mdArchivo · 16px · 400

The quick brown fox jumps

label-mdSpace 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
sm6px
md14px
lg24px
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: #F3EBD9;
  --foreground: #1E1B18;
  --card: #FFF9EE;
  --card-foreground: #1E1B18;
  --popover: #FFF9EE;
  --popover-foreground: #1E1B18;
  --primary: #C63A2F;
  --primary-foreground: #ffffff;
  --secondary: #2E5FA5;
  --secondary-foreground: #ffffff;
  --muted: #6E655A;
  --muted-foreground: #1E1B18;
  --accent: #D4A62A;
  --accent-foreground: #ffffff;
  --destructive: #B23A32;
  --border: #1F1A17;
  --input: #1F1A17;
  --ring: #D4A62A;
  --chart-1: #C63A2F;
  --chart-2: #2E5FA5;
  --chart-3: #D4A62A;
  --chart-4: #3C7A4B;
  --chart-5: #BA7A16;
  --sidebar: #FFF9EE;
  --sidebar-foreground: #1E1B18;
  --sidebar-primary: #C63A2F;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #355F8C;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #1F1A17;
  --sidebar-ring: #D4A62A;
  --radius: 14px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #C63A2F;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #D4A62A;
  --accent-foreground: #ffffff;
  --destructive: #B23A32;
  --border: #303642;
  --input: #303642;
  --ring: #D4A62A;
  --chart-1: #C63A2F;
  --chart-2: #2E5FA5;
  --chart-3: #D4A62A;
  --chart-4: #3C7A4B;
  --chart-5: #BA7A16;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #C63A2F;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #D4A62A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #D4A62A;
  --radius: 14px;
}
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 BauhausFunctionalGeometryShadcnKit() {
  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">Bauhaus Functional Geometry</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": "bauhaus-functional-geometry",
  "type": "registry:theme",
  "title": "Bauhaus Functional Geometry shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F3EBD9",
      "foreground": "#1E1B18",
      "card": "#FFF9EE",
      "card-foreground": "#1E1B18",
      "popover": "#FFF9EE",
      "popover-foreground": "#1E1B18",
      "primary": "#C63A2F",
      "primary-foreground": "#ffffff",
      "secondary": "#2E5FA5",
      "secondary-foreground": "#ffffff",
      "muted": "#6E655A",
      "muted-foreground": "#1E1B18",
      "accent": "#D4A62A",
      "accent-foreground": "#ffffff",
      "destructive": "#B23A32",
      "border": "#1F1A17",
      "input": "#1F1A17",
      "ring": "#D4A62A",
      "chart-1": "#C63A2F",
      "chart-2": "#2E5FA5",
      "chart-3": "#D4A62A",
      "chart-4": "#3C7A4B",
      "chart-5": "#BA7A16",
      "sidebar": "#FFF9EE",
      "sidebar-foreground": "#1E1B18",
      "sidebar-primary": "#C63A2F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#355F8C",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#1F1A17",
      "sidebar-ring": "#D4A62A",
      "radius": "14px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#C63A2F",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#D4A62A",
      "accent-foreground": "#ffffff",
      "destructive": "#B23A32",
      "border": "#303642",
      "input": "#303642",
      "ring": "#D4A62A",
      "chart-1": "#C63A2F",
      "chart-2": "#2E5FA5",
      "chart-3": "#D4A62A",
      "chart-4": "#3C7A4B",
      "chart-5": "#BA7A16",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#C63A2F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#D4A62A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#D4A62A",
      "radius": "14px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019da2ca-82fd-7261-94a9-d9278375958e",
    "slug": "bauhaus-functional-geometry",
    "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
# Bauhaus Functional Geometry shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019da2ca-82fd-7261-94a9-d9278375958e`
Slug: `bauhaus-functional-geometry`

## Intent

A design language that translates Bauhaus workshop logic into interface structure: primary geometry, visible construction lines, disciplined asymmetry, and typography treated as architecture rather than decoration. It feels educational, industrial, and optimistic, using color blocks as navigational anchors and black rules as the skeleton that keeps expressive geometry functional.

## 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": "#C63A2F",
  "secondary": "#2E5FA5",
  "accent": "#D4A62A",
  "background": "#F3EBD9",
  "surface": "#FFF9EE",
  "text": "#1E1B18",
  "muted": "#6E655A",
  "border": "#1F1A17",
  "error": "#B23A32",
  "success": "#3C7A4B",
  "warning": "#BA7A16",
  "info": "#355F8C"
}

Typography:

{
  "heading_font": "League Spartan",
  "body_font": "Archivo",
  "mono_font": "Space 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:wght@400;500;600;700&family=League+Spartan:wght@500;700;800&family=Space+Mono:wght@400;700&display=swap"
}

## Visual character to preserve

- Large flat rectangles and circles in primary red, cobalt blue, and mustard are pinned against warm ivory fields, acting as spatial anchors rather than small accent flourishes.
- Every major panel is defined by crisp charcoal borders between 2px and 4px, with visible divider rules that make the composition feel drafted and constructed like a workshop poster.
- Headings use oversized uppercase geometric sans typography with tight line height, while labels and metrics sit in disciplined mono or compact sans blocks that resemble instructional signage.
- Layouts are intentionally asymmetric: one oversized hero column is counterweighted by stacked utility panels, with generous negative space preserving order around bold geometric forms.
- Interactive elements use flat fills, square or slightly rounded corners, and offset color bars or circular markers so controls feel fabricated, not soft or skeuomorphic.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "stickerBadges": false,
  "motion": "lift",
  "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/bauhaus-functional-geometry/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: Let one geometric element dominate each composition.; Keep borders, divider lines, and label bands visibly structural.; Use primary colors sparingly but boldly on large shapes and control groups.; Make typography blocky, uppercase, and clearly staged by scale.
- Do not: Do not soften the system with frosted transparency or blurred gradients.; Do not hide structure behind borderless floating cards.; Do not use pastel ambiguity or too many accent colors.; Do not center everything; asymmetry is part of the identity.

## 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 BauhausFunctionalGeometryShadcnKit() {
  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">Bauhaus Functional Geometry</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": "A 12-column desktop grid with one dominant 7-column narrative area and a 5-column utility rail; tablet collapses to 8 columns and mobile to a single stacked flow.",
  "breakpoints": "Desktop default, tablet at 980px, mobile at 680px with all compositions reflowing into stacked panels and full-width actions.",
  "whitespace": "Use deliberate negative space around geometric anchors; padding is generous inside panels, but outer gaps stay tight enough to preserve the poster-like composition."
}
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-019da2ca-82fd-7261-94a9-d9278375958e",
    "name": "Bauhaus Functional Geometry",
    "slug": "bauhaus-functional-geometry"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "Large flat rectangles and circles in primary red, cobalt blue, and mustard are pinned against warm ivory fields, acting as spatial anchors rather than small accent flourishes.",
    "Every major panel is defined by crisp charcoal borders between 2px and 4px, with visible divider rules that make the composition feel drafted and constructed like a workshop poster.",
    "Headings use oversized uppercase geometric sans typography with tight line height, while labels and metrics sit in disciplined mono or compact sans blocks that resemble instructional signage.",
    "Layouts are intentionally asymmetric: one oversized hero column is counterweighted by stacked utility panels, with generous negative space preserving order around bold geometric forms.",
    "Interactive elements use flat fills, square or slightly rounded corners, and offset color bars or circular markers so controls feel fabricated, not soft or skeuomorphic."
  ],
  "visualProfile": {
    "family": "system",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": false,
    "stickerBadges": false,
    "motion": "lift",
    "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": "Bauhaus Functional Geometry 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": [
      "Let one geometric element dominate each composition.",
      "Keep borders, divider lines, and label bands visibly structural.",
      "Use primary colors sparingly but boldly on large shapes and control groups.",
      "Make typography blocky, uppercase, and clearly staged by scale."
    ],
    "dont": [
      "Do not soften the system with frosted transparency or blurred gradients.",
      "Do not hide structure behind borderless floating cards.",
      "Do not use pastel ambiguity or too many accent colors.",
      "Do not center everything; asymmetry is part of the identity."
    ]
  }
}
related

More like this