back to gallery
design language·braun-functional-minimalism

Braun Functional Minimalism

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

Download DESIGN.md

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

the spec

specification

philosophy
summary
A restrained interface language derived from Dieter Rams and Braun industrial design: neutral surfaces, precise alignment, and controls that communicate function before personality. The interface should feel engineered, durable, and quietly confident rather than expressive or decorative.
values
usefulness before noveltyclarity through reductiondetail discipline and consistencyhonest hierarchy with no false emphasis
anti-values
×decorative flourish without purpose×trendy gradients or glass effects×ambiguous controls that hide function
tokens
colors12 items
primary
#2E3133
secondary
#6E7377
accent
#D96A32
background
#ECE7DE
surface
#F7F3EC
text
#17191A
muted
#8C877F
border
#B8B0A4
error
#B7442A
success
#4E6B50
warning
#B9832F
info
#5C7688
typography8 items
heading font
Archivo
body font
Archivo
mono font
IBM Plex Mono
base size
16px
scale ratio
1.2
line height
1.5
letter spacing
0.01em
google fonts url
https://fonts.googleapis.com/css2?family=Archivo:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500&display=swap
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
radii5 items
none
0
sm
8px
md
14px
lg
22px
full
9999px
shadows3 items
sm
0 1px 0 rgba(23,25,26,0.06)
md
0 10px 24px rgba(23,25,26,0.08)
lg
0 22px 44px rgba(23,25,26,0.10)
surfaces3 items
treatment
paper
card style
Matte warm surfaces with subtle inset highlight and no glossy effects; panels feel like powder-coated product casings or printed manuals.
bg pattern
none
borders4 items
default width
1px
accent width
2px
style
solid
character
Borders are quiet engineering lines: thin, crisp, evenly applied, and more important than shadow in defining component edges.
motion3 items
duration
180ms
easing
cubic-bezier(0.2, 0, 0.2, 1)
philosophy
deliberate
rules
composition

Compose screens as functional instrument panels: a calm summary zone, clearly segmented modules, and aligned controls with strong shared baselines.

hierarchy

Use scale sparingly; hierarchy comes from spacing, alignment, keyline separators, and label/value pairing rather than oversized display treatments.

density

Medium density with disciplined breathing room; panels contain many controls, but every control has a defined slot and measured padding.

signature patterns
Every major section begins with an uppercase mono overline and a thin divider rule, creating manual-like segmentation instead of decorative headers.Interactive controls use inset tracks, dial-like circular indicators, or segmented buttons with 1px borders so the UI echoes physical appliance hardware.Numeric readouts and metadata use tabular monospace figures aligned in narrow columns, reinforcing product-instrument precision across the whole layout.Selected states are indicated by a restrained burnt-orange signal line, dot, or fill inside a control, never by flooding the entire panel with accent color.
layout
grid
A 12-column desktop grid collapses to 8 columns on tablet and a single measured column on mobile, with modules spanning whole columns rather than arbitrary card widths.
breakpoints

desktop 1440, tablet 768, mobile 375 with stacked panels and full-width controls on small screens.

whitespace

Whitespace is deliberate and even, favoring consistent gutters and module padding over dramatic empty voids; every gap should feel engineered.

guidance
do
  • Use keylines, measured spacing, and neutral surfaces to separate content before reaching for color.
  • Make controls self-explanatory with labels, values, and visible mechanical states.
  • Reserve accent color for active state, warning, or live signal feedback.
avoid
  • Do not introduce ornamental illustrations, soft blobs, or expressive gradients.
  • Do not rely on oversized hero text when alignment and labeling can do the work.
  • Do not hide important actions inside visually ambiguous minimalist treatments.
katagami spec
# Braun Functional Minimalism

## Philosophy

A restrained interface language derived from Dieter Rams and Braun industrial design: neutral surfaces, precise alignment, and controls that communicate function before personality. The interface should feel engineered, durable, and quietly confident rather than expressive or decorative.

### Values

- usefulness before novelty
- clarity through reduction
- detail discipline and consistency
- honest hierarchy with no false emphasis

### Anti-Values

- decorative flourish without purpose
- trendy gradients or glass effects
- ambiguous controls that hide function

### Visual Character

- Large fields of warm off-white and graphite are interrupted by thin keyline dividers, so sections are separated with hairline rules instead of heavy cards or colorful panels.
- Controls sit inside precise rounded-rectangle tracks with measured 1px borders, restrained shadows, and monochrome iconography that makes each element feel like a physical Braun appliance interface.
- Typography uses disciplined sans-serif stacks with uppercase micro-labels, tabular numerals, and generous line spacing, creating a neutral instruction-manual tone instead of editorial drama.
- Accent color is used sparingly as a functional signal on toggles, level meters, focus rings, and status dots, never as background fill for large surfaces or decorative illustration.

## Tokens

### Colors

| Name | Value |
|------|-------|
| primary | `#2E3133` |
| secondary | `#6E7377` |
| accent | `#D96A32` |
| background | `#ECE7DE` |
| surface | `#F7F3EC` |
| text | `#17191A` |
| muted | `#8C877F` |
| border | `#B8B0A4` |
| error | `#B7442A` |
| success | `#4E6B50` |
| warning | `#B9832F` |
| info | `#5C7688` |

### Typography

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

### Spacing

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

### Radii

- **None**: 0
- **Sm**: 8px
- **Md**: 14px
- **Lg**: 22px
- **Full**: 9999px

### Shadows

- **Sm**: 0 1px 0 rgba(23,25,26,0.06)
- **Md**: 0 10px 24px rgba(23,25,26,0.08)
- **Lg**: 0 22px 44px rgba(23,25,26,0.10)

### Surfaces

- **Treatment**: paper
- **Card Style**: Matte warm surfaces with subtle inset highlight and no glossy effects; panels feel like powder-coated product casings or printed manuals.
- **Bg Pattern**: none

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Borders are quiet engineering lines: thin, crisp, evenly applied, and more important than shadow in defining component edges.

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.2, 0, 0.2, 1)
- **Philosophy**: deliberate

## Rules

### Composition

Compose screens as functional instrument panels: a calm summary zone, clearly segmented modules, and aligned controls with strong shared baselines.

### Hierarchy

Use scale sparingly; hierarchy comes from spacing, alignment, keyline separators, and label/value pairing rather than oversized display treatments.

### Density

Medium density with disciplined breathing room; panels contain many controls, but every control has a defined slot and measured padding.

### Signature Patterns

- Every major section begins with an uppercase mono overline and a thin divider rule, creating manual-like segmentation instead of decorative headers.
- Interactive controls use inset tracks, dial-like circular indicators, or segmented buttons with 1px borders so the UI echoes physical appliance hardware.
- Numeric readouts and metadata use tabular monospace figures aligned in narrow columns, reinforcing product-instrument precision across the whole layout.
- Selected states are indicated by a restrained burnt-orange signal line, dot, or fill inside a control, never by flooding the entire panel with accent color.

## Layout

### Grid

A 12-column desktop grid collapses to 8 columns on tablet and a single measured column on mobile, with modules spanning whole columns rather than arbitrary card widths.

### Breakpoints

desktop 1440, tablet 768, mobile 375 with stacked panels and full-width controls on small screens.

### Whitespace

Whitespace is deliberate and even, favoring consistent gutters and module padding over dramatic empty voids; every gap should feel engineered.

## Guidance

### Do

- Use keylines, measured spacing, and neutral surfaces to separate content before reaching for color.
- Make controls self-explanatory with labels, values, and visible mechanical states.
- Reserve accent color for active state, warning, or live signal feedback.

### Don't

- Do not introduce ornamental illustrations, soft blobs, or expressive gradients.
- Do not rely on oversized hero text when alignment and labeling can do the work.
- Do not hide important actions inside visually ambiguous minimalist treatments.
DESIGN.md
---
version: "alpha"
name: "Braun Functional Minimalism"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  primary: "#2E3133"
  secondary: "#6E7377"
  accent: "#D96A32"
  background: "#ECE7DE"
  surface: "#F7F3EC"
  text: "#17191A"
  muted: "#8C877F"
  border: "#B8B0A4"
  error: "#B7442A"
  success: "#4E6B50"
  warning: "#B9832F"
  info: "#5C7688"
typography:
  headline-lg:
    fontFamily: "Archivo"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "0.01em"
  headline-md:
    fontFamily: "Archivo"
    fontSize: "1.44rem"
    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: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  none: "0px"
  sm: "8px"
  md: "14px"
  lg: "22px"
  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"
---

# Braun Functional Minimalism

## Overview

A restrained interface language derived from Dieter Rams and Braun industrial design: neutral surfaces, precise alignment, and controls that communicate function before personality. The interface should feel engineered, durable, and quietly confident rather than expressive or decorative.

### Values

- usefulness before novelty
- clarity through reduction
- detail discipline and consistency
- honest hierarchy with no false emphasis

### Anti-Values

- decorative flourish without purpose
- trendy gradients or glass effects
- ambiguous controls that hide function

### Visual Character

- Large fields of warm off-white and graphite are interrupted by thin keyline dividers, so sections are separated with hairline rules instead of heavy cards or colorful panels.
- Controls sit inside precise rounded-rectangle tracks with measured 1px borders, restrained shadows, and monochrome iconography that makes each element feel like a physical Braun appliance interface.
- Typography uses disciplined sans-serif stacks with uppercase micro-labels, tabular numerals, and generous line spacing, creating a neutral instruction-manual tone instead of editorial drama.
- Accent color is used sparingly as a functional signal on toggles, level meters, focus rings, and status dots, never as background fill for large surfaces or decorative illustration.

## 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 | `#2E3133` |
| secondary | `#6E7377` |
| accent | `#D96A32` |
| background | `#ECE7DE` |
| surface | `#F7F3EC` |
| text | `#17191A` |
| muted | `#8C877F` |
| border | `#B8B0A4` |
| error | `#B7442A` |
| success | `#4E6B50` |
| warning | `#B9832F` |
| info | `#5C7688` |

## Typography

- **Headline-Lg**: Archivo, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Archivo, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: Archivo, 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

A 12-column desktop grid collapses to 8 columns on tablet and a single measured column on mobile, with modules spanning whole columns rather than arbitrary card widths.

### Breakpoints

desktop 1440, tablet 768, mobile 375 with stacked panels and full-width controls on small screens.

### Whitespace

Whitespace is deliberate and even, favoring consistent gutters and module padding over dramatic empty voids; every gap should feel engineered.

## Elevation & Depth

### Shadows

- **Sm**: 0 1px 0 rgba(23,25,26,0.06)
- **Md**: 0 10px 24px rgba(23,25,26,0.08)
- **Lg**: 0 22px 44px rgba(23,25,26,0.10)

## Shapes

### Rounded

- **None**: `0px`
- **Sm**: `8px`
- **Md**: `14px`
- **Lg**: `22px`
- **Full**: `9999px`

### Surfaces

- **Treatment**: paper
- **Card Style**: Matte warm surfaces with subtle inset highlight and no glossy effects; panels feel like powder-coated product casings or printed manuals.
- **Bg Pattern**: none

### Borders

- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Borders are quiet engineering lines: thin, crisp, evenly applied, and more important than shadow in defining component edges.

## Components

### Composition

Compose screens as functional instrument panels: a calm summary zone, clearly segmented modules, and aligned controls with strong shared baselines.

### Hierarchy

Use scale sparingly; hierarchy comes from spacing, alignment, keyline separators, and label/value pairing rather than oversized display treatments.

### Density

Medium density with disciplined breathing room; panels contain many controls, but every control has a defined slot and measured padding.

### Signature Patterns

- Every major section begins with an uppercase mono overline and a thin divider rule, creating manual-like segmentation instead of decorative headers.
- Interactive controls use inset tracks, dial-like circular indicators, or segmented buttons with 1px borders so the UI echoes physical appliance hardware.
- Numeric readouts and metadata use tabular monospace figures aligned in narrow columns, reinforcing product-instrument precision across the whole layout.
- Selected states are indicated by a restrained burnt-orange signal line, dot, or fill inside a control, never by flooding the entire panel with accent color.

## 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-019da134-4ac8-7631-b242-bde2d56cc6f2/DESIGN.with-shadcn.md`.

The shadcn page also exposes optional machine-readable files for automation, but the human-facing handoff is DESIGN.md with shadcn.

Install recommended primitives with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

Use these primitives in shadcn apps:
- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Implementation rule for agents: import shadcn primitives from `@/components/ui/*`, apply the generated CSS variables first, then compose the language-specific recipes from the companion MD. Katagami remains the source of truth; shadcn names are the implementation surface.

## Do's and Don'ts

- Do Use keylines, measured spacing, and neutral surfaces to separate content before reaching for color.
- Do Make controls self-explanatory with labels, values, and visible mechanical states.
- Do Reserve accent color for active state, warning, or live signal feedback.
- Don't Do not introduce ornamental illustrations, soft blobs, or expressive gradients.
- Don't Do not rely on oversized hero text when alignment and labeling can do the work.
- Don't Do not hide important actions inside visually ambiguous minimalist treatments.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "braun-functional-minimalism",
  "type": "registry:theme",
  "title": "Braun Functional Minimalism shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#ECE7DE",
      "foreground": "#17191A",
      "card": "#F7F3EC",
      "card-foreground": "#17191A",
      "popover": "#F7F3EC",
      "popover-foreground": "#17191A",
      "primary": "#2E3133",
      "primary-foreground": "#ffffff",
      "secondary": "#6E7377",
      "secondary-foreground": "#ffffff",
      "muted": "#8C877F",
      "muted-foreground": "#17191A",
      "accent": "#D96A32",
      "accent-foreground": "#ffffff",
      "destructive": "#B7442A",
      "border": "#B8B0A4",
      "input": "#B8B0A4",
      "ring": "#D96A32",
      "chart-1": "#2E3133",
      "chart-2": "#6E7377",
      "chart-3": "#D96A32",
      "chart-4": "#4E6B50",
      "chart-5": "#B9832F",
      "sidebar": "#F7F3EC",
      "sidebar-foreground": "#17191A",
      "sidebar-primary": "#2E3133",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5C7688",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#B8B0A4",
      "sidebar-ring": "#D96A32",
      "radius": "14px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2E3133",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#D96A32",
      "accent-foreground": "#ffffff",
      "destructive": "#B7442A",
      "border": "#303642",
      "input": "#303642",
      "ring": "#D96A32",
      "chart-1": "#2E3133",
      "chart-2": "#6E7377",
      "chart-3": "#D96A32",
      "chart-4": "#4E6B50",
      "chart-5": "#B9832F",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2E3133",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#D96A32",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#D96A32",
      "radius": "14px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019da134-4ac8-7631-b242-bde2d56cc6f2",
    "slug": "braun-functional-minimalism",
    "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 · braun-functional-minimalism
DESIGN.md

at a glance

Palette

Typography

headline-lgArchivo · 28px · 700

The quick brown fox jumps

headline-mdArchivo · 23px · 600

The quick brown fox jumps

body-mdArchivo · 16px · 400

The quick brown fox jumps

label-mdIBM Plex Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

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

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl48px
  • 4xl64px

Shape

none0px
sm8px
md14px
lg22px
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: #ECE7DE;
  --foreground: #17191A;
  --card: #F7F3EC;
  --card-foreground: #17191A;
  --popover: #F7F3EC;
  --popover-foreground: #17191A;
  --primary: #2E3133;
  --primary-foreground: #ffffff;
  --secondary: #6E7377;
  --secondary-foreground: #ffffff;
  --muted: #8C877F;
  --muted-foreground: #17191A;
  --accent: #D96A32;
  --accent-foreground: #ffffff;
  --destructive: #B7442A;
  --border: #B8B0A4;
  --input: #B8B0A4;
  --ring: #D96A32;
  --chart-1: #2E3133;
  --chart-2: #6E7377;
  --chart-3: #D96A32;
  --chart-4: #4E6B50;
  --chart-5: #B9832F;
  --sidebar: #F7F3EC;
  --sidebar-foreground: #17191A;
  --sidebar-primary: #2E3133;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #5C7688;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #B8B0A4;
  --sidebar-ring: #D96A32;
  --radius: 14px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #2E3133;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #D96A32;
  --accent-foreground: #ffffff;
  --destructive: #B7442A;
  --border: #303642;
  --input: #303642;
  --ring: #D96A32;
  --chart-1: #2E3133;
  --chart-2: #6E7377;
  --chart-3: #D96A32;
  --chart-4: #4E6B50;
  --chart-5: #B9832F;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #2E3133;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #D96A32;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #D96A32;
  --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 BraunFunctionalMinimalismShadcnKit() {
  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">Braun Functional Minimalism</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": "braun-functional-minimalism",
  "type": "registry:theme",
  "title": "Braun Functional Minimalism shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#ECE7DE",
      "foreground": "#17191A",
      "card": "#F7F3EC",
      "card-foreground": "#17191A",
      "popover": "#F7F3EC",
      "popover-foreground": "#17191A",
      "primary": "#2E3133",
      "primary-foreground": "#ffffff",
      "secondary": "#6E7377",
      "secondary-foreground": "#ffffff",
      "muted": "#8C877F",
      "muted-foreground": "#17191A",
      "accent": "#D96A32",
      "accent-foreground": "#ffffff",
      "destructive": "#B7442A",
      "border": "#B8B0A4",
      "input": "#B8B0A4",
      "ring": "#D96A32",
      "chart-1": "#2E3133",
      "chart-2": "#6E7377",
      "chart-3": "#D96A32",
      "chart-4": "#4E6B50",
      "chart-5": "#B9832F",
      "sidebar": "#F7F3EC",
      "sidebar-foreground": "#17191A",
      "sidebar-primary": "#2E3133",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#5C7688",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#B8B0A4",
      "sidebar-ring": "#D96A32",
      "radius": "14px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2E3133",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#D96A32",
      "accent-foreground": "#ffffff",
      "destructive": "#B7442A",
      "border": "#303642",
      "input": "#303642",
      "ring": "#D96A32",
      "chart-1": "#2E3133",
      "chart-2": "#6E7377",
      "chart-3": "#D96A32",
      "chart-4": "#4E6B50",
      "chart-5": "#B9832F",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2E3133",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#D96A32",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#D96A32",
      "radius": "14px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019da134-4ac8-7631-b242-bde2d56cc6f2",
    "slug": "braun-functional-minimalism",
    "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
# Braun Functional Minimalism shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019da134-4ac8-7631-b242-bde2d56cc6f2`
Slug: `braun-functional-minimalism`

## Intent

A restrained interface language derived from Dieter Rams and Braun industrial design: neutral surfaces, precise alignment, and controls that communicate function before personality. The interface should feel engineered, durable, and quietly confident rather than expressive or decorative.

## 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": "#2E3133",
  "secondary": "#6E7377",
  "accent": "#D96A32",
  "background": "#ECE7DE",
  "surface": "#F7F3EC",
  "text": "#17191A",
  "muted": "#8C877F",
  "border": "#B8B0A4",
  "error": "#B7442A",
  "success": "#4E6B50",
  "warning": "#B9832F",
  "info": "#5C7688"
}

Typography:

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

## Visual character to preserve

- Large fields of warm off-white and graphite are interrupted by thin keyline dividers, so sections are separated with hairline rules instead of heavy cards or colorful panels.
- Controls sit inside precise rounded-rectangle tracks with measured 1px borders, restrained shadows, and monochrome iconography that makes each element feel like a physical Braun appliance interface.
- Typography uses disciplined sans-serif stacks with uppercase micro-labels, tabular numerals, and generous line spacing, creating a neutral instruction-manual tone instead of editorial drama.
- Accent color is used sparingly as a functional signal on toggles, level meters, focus rings, and status dots, never as background fill for large surfaces or decorative illustration.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": false,
  "grain": true,
  "stickerBadges": false,
  "motion": "still",
  "density": "balanced",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

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

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

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

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

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

## Preview shots

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

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/braun-functional-minimalism/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Use keylines, measured spacing, and neutral surfaces to separate content before reaching for color.; Make controls self-explanatory with labels, values, and visible mechanical states.; Reserve accent color for active state, warning, or live signal feedback.
- Do not: Do not introduce ornamental illustrations, soft blobs, or expressive gradients.; Do not rely on oversized hero text when alignment and labeling can do the work.; Do not hide important actions inside visually ambiguous minimalist treatments.

## 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 BraunFunctionalMinimalismShadcnKit() {
  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">Braun Functional Minimalism</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 collapses to 8 columns on tablet and a single measured column on mobile, with modules spanning whole columns rather than arbitrary card widths.",
  "breakpoints": "desktop 1440, tablet 768, mobile 375 with stacked panels and full-width controls on small screens.",
  "whitespace": "Whitespace is deliberate and even, favoring consistent gutters and module padding over dramatic empty voids; every gap should feel engineered."
}
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-019da134-4ac8-7631-b242-bde2d56cc6f2",
    "name": "Braun Functional Minimalism",
    "slug": "braun-functional-minimalism"
  },
  "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 fields of warm off-white and graphite are interrupted by thin keyline dividers, so sections are separated with hairline rules instead of heavy cards or colorful panels.",
    "Controls sit inside precise rounded-rectangle tracks with measured 1px borders, restrained shadows, and monochrome iconography that makes each element feel like a physical Braun appliance interface.",
    "Typography uses disciplined sans-serif stacks with uppercase micro-labels, tabular numerals, and generous line spacing, creating a neutral instruction-manual tone instead of editorial drama.",
    "Accent color is used sparingly as a functional signal on toggles, level meters, focus rings, and status dots, never as background fill for large surfaces or decorative illustration."
  ],
  "visualProfile": {
    "family": "editorial",
    "material": "flat",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": false,
    "stickerBadges": false,
    "motion": "still",
    "density": "balanced",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Braun Functional Minimalism launch room",
        "description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
        "primaryAction": "Apply theme",
        "secondaryAction": "Review states",
        "stats": [
          {
            "label": "components",
            "value": "16",
            "tone": "accent"
          },
          {
            "label": "states",
            "value": "ready"
          },
          {
            "label": "density",
            "value": "balanced",
            "tone": "warning"
          }
        ],
        "rows": [
          {
            "label": "Primary flow",
            "value": "mapped",
            "status": "active"
          },
          {
            "label": "Token coverage",
            "value": "semantic",
            "status": "synced"
          },
          {
            "label": "Responsive proof",
            "value": "queued",
            "status": "review"
          }
        ],
        "statuses": [
          "Active",
          "Synced",
          "Draft"
        ]
      }
    },
    {
      "id": "detail-editor",
      "title": "Detail editor",
      "viewport": "tablet",
      "primitives": [
        "button",
        "card",
        "input",
        "textarea",
        "select",
        "checkbox",
        "switch",
        "slider",
        "dialog",
        "sheet"
      ],
      "composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
      "mustShow": [
        "focus ring",
        "error or destructive state",
        "dialog or sheet treatment",
        "written guidance content"
      ],
      "avoid": [
        "unstyled browser controls",
        "floating cards inside cards",
        "missing labels"
      ],
      "scene": {
        "eyebrow": "editing flow",
        "headline": "Language recipe editor",
        "description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
        "primaryAction": "Save recipe",
        "secondaryAction": "Open sheet",
        "fields": [
          {
            "label": "Component family",
            "value": "Narrative cards"
          },
          {
            "label": "State treatment",
            "value": "Visible focus + validation"
          },
          {
            "label": "Motion",
            "value": "Small lift, no opacity-only fade"
          }
        ],
        "statuses": [
          "Focus",
          "Invalid",
          "Confirmed"
        ]
      }
    },
    {
      "id": "data-operations",
      "title": "Data operations",
      "viewport": "mobile",
      "primitives": [
        "button",
        "tabs",
        "badge",
        "dropdown-menu",
        "table",
        "tooltip",
        "separator"
      ],
      "composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
      "mustShow": [
        "responsive reflow",
        "dense row styling",
        "menu affordance",
        "status badge system"
      ],
      "avoid": [
        "desktop-only tables",
        "text overflow",
        "default shadcn spacing without Katagami character"
      ],
      "scene": {
        "eyebrow": "operations",
        "headline": "Compact review queue",
        "description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
        "primaryAction": "Resolve",
        "secondaryAction": "Filter",
        "rows": [
          {
            "label": "Button hierarchy",
            "value": "approved",
            "status": "ok"
          },
          {
            "label": "Table rhythm",
            "value": "needs pass",
            "status": "watch"
          },
          {
            "label": "Empty state",
            "value": "designed",
            "status": "done"
          }
        ],
        "statuses": [
          "Queued",
          "Blocked",
          "Done"
        ]
      }
    }
  ],
  "componentRecipes": [
    {
      "primitive": "button",
      "intent": "Prove action hierarchy, focus, disabled, and destructive states."
    },
    {
      "primitive": "card",
      "intent": "Carry the language surface, border, elevation, and density rules."
    },
    {
      "primitive": "input",
      "intent": "Show labels, focus rings, validation, and spacing rhythm."
    },
    {
      "primitive": "textarea",
      "intent": "Show longer guidance, validation copy, and writing density."
    },
    {
      "primitive": "select",
      "intent": "Show filtering, selection contrast, and menu trigger styling."
    },
    {
      "primitive": "dialog",
      "intent": "Show centered decision states and overlay treatment."
    },
    {
      "primitive": "sheet",
      "intent": "Show contextual side panels and responsive editing."
    },
    {
      "primitive": "tabs",
      "intent": "Show navigational structure and active/inactive contrast."
    },
    {
      "primitive": "badge",
      "intent": "Show compact status vocabulary and semantic colors."
    },
    {
      "primitive": "separator",
      "intent": "Show section rhythm without generic gray dividers."
    },
    {
      "primitive": "checkbox",
      "intent": "Show binary selection with visible focus and checked states."
    },
    {
      "primitive": "switch",
      "intent": "Show settings toggles and on/off contrast."
    },
    {
      "primitive": "slider",
      "intent": "Show numeric adjustment with track/thumb styling."
    },
    {
      "primitive": "tooltip",
      "intent": "Show concise explanation styling above compact controls."
    },
    {
      "primitive": "dropdown-menu",
      "intent": "Show action menus, destructive items, and grouped choices."
    },
    {
      "primitive": "table",
      "intent": "Show dense operational data, separators, row states, and responsive behavior."
    }
  ],
  "qualityRules": {
    "do": [
      "Use keylines, measured spacing, and neutral surfaces to separate content before reaching for color.",
      "Make controls self-explanatory with labels, values, and visible mechanical states.",
      "Reserve accent color for active state, warning, or live signal feedback."
    ],
    "dont": [
      "Do not introduce ornamental illustrations, soft blobs, or expressive gradients.",
      "Do not rely on oversized hero text when alignment and labeling can do the work.",
      "Do not hide important actions inside visually ambiguous minimalist treatments."
    ]
  }
}