Brutalist UI Skill: Industrial & Tactical Interface Design
A design language that forces Claude to build raw, mechanical interfaces — Swiss industrial print or CRT terminal telemetry, with rigid grids and zero rounded corners
Ask an AI agent for a 'bold' UI and you get rounded cards, a blue gradient, and Inter. This playbook replaces that default with two committed visual archetypes: Swiss industrial print or tactical CRT telemetry, enforced down to the hex code and border-radius.
Who it's for: frontend developers, indie hackers building dev tools or dashboards, portfolio site owners, designers prototyping with Claude Code, teams shipping data-dense admin panels
Example
"Build a landing page for my monitoring dashboard" → A dark CRT-terminal interface with monospace telemetry data, ASCII bracket framing, scanline texture, and a single hazard-red accent, instead of a generic SaaS template
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Industrial Brutalism & Tactical Telemetry UI
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
## Skill Meta
**Name:** Industrial Brutalism & Tactical Telemetry Interface Engineering
**Description:** Advanced proficiency in architecting web interfaces that synthesize mid-century Swiss Typographic design, industrial manufacturing manuals, and retro-futuristic aerospace/military terminal interfaces. This discipline requires absolute mastery over rigid modular grids, extreme typographic scale contrast, purely utilitarian color palettes, and the programmatic simulation of analog degradation (halftones, CRT scanlines, bitmap dithering). The objective is to construct digital environments that project raw functionality, mechanical precision, and high data density, deliberately discarding conventional consumer UI patterns.
## Visual Archetypes
The design system operates by merging two distinct but highly compatible visual paradigms. Pick ONE per project and commit to it. Do not alternate or mix both modes within the same interface.
### Swiss Industrial Print
Derived from 1960s corporate identity systems and heavy machinery blueprints.
- **Characteristics:** High-contrast light modes (newsprint/off-white substrates). Reliance on monolithic, heavy sans-serif typography. Unforgiving structural grids outlined by visible dividing lines. Aggressive, asymmetric use of negative space punctuated by oversized, viewport-bleeding numerals or letterforms. Heavy use of primary red as an alert/accent color.
### Tactical Telemetry & CRT Terminal
Derived from classified military databases, legacy mainframes, and aerospace Heads-Up Displays (HUDs).
- **Characteristics:** Dark mode exclusivity. High-density tabular data presentation. Absolute dominance of monospaced typography. Integration of technical framing devices (ASCII brackets, crosshairs). Application of simulated hardware limitations (phosphor glow, scanlines, low bit-depth rendering).
## Typographic Architecture
Typography is the primary structural and decorative infrastructure. Imagery is secondary. The system demands extreme variance in scale, weight, and spacing.
### Macro-Typography (Structural Headers)
- **Classification:** Neo-Grotesque / Heavy Sans-Serif.
- **Optimal Web Fonts:** Neue Haas Grotesk (Black), Inter (Extra Bold/Black), Archivo Black, Roboto Flex (Heavy), Monument Extended.
- **Implementation Parameters:**
- **Scale:** Deployed at massive scales using fluid typography (e.g., `clamp(4rem, 10vw, 15rem)`).
- **Tracking (Letter-spacing):** Extremely tight, often negative (`-0.03em` to `-0.06em`), forcing glyphs to form solid architectural blocks.
- **Leading (Line-height):** Highly compressed (`0.85` to `0.95`).
- **Casing:** Exclusively uppercase for structural impact.
### Micro-Typography (Data & Telemetry)
- **Classification:** Monospace / Technical Sans.
- **Optimal Web Fonts:** JetBrains Mono, IBM Plex Mono, Space Mono, VT323, Courier Prime.
- **Implementation Parameters:**
- **Scale:** Fixed and small (`10px` to `14px` / `0.7rem` to `0.875rem`).
- **Tracking:** Generous (`0.05em` to `0.1em`) to simulate mechanical typewriter spacing or terminal matrices.
- **Leading:** Standard to tight (`1.2` to `1.4`).
- **Casing:** Exclusively uppercase. Used for all metadata, navigation, unit IDs, and coordinates.
### Textural Contrast (Artistic Disruption)
- **Classification:** High-Contrast Serif.
- **Optimal Web Fonts:** Playfair Display, EB Garamond, Times New Roman.
- **Implementation Parameters:** Used exceedingly sparingly. Must be subjected to heavy post-processing (halftone filters, 1-bit dithering) to degrade vector perfection and create textural juxtaposition against the clean sans-serifs.
## Color System
The color architecture is uncompromising. Gradients, soft drop shadows, and modern translucency are strictly prohibited. Colors simulate physical media or primitive emissive displays.
CRITICAL: Choose ONE substrate palette per project and use it consistently. Never mix light and dark substrates within the same interface.
### If Swiss Industrial Print (Light)
- **Background:** `#F4F4F0` or `#EAE8E3` (Matte, unbleached documentation paper).
- **Foreground:** `#050505` to `#111111` (Carbon Ink).
- **Accent:** `#E61919` or `#FF2A2A` (Aviation/Hazard Red). This is the ONLY accent color. Used for strike-throughs, thick structural dividing lines, or vital data highlights.
### If Tactical Telemetry (Dark)
- **Background:** `#0A0A0A` or `#121212` (Deactivated CRT. Avoid pure `#000000`).
- **Foreground:** `#EAEAEA` (White phosphor). This is the primary text color.
- **Accent:** `#E61919` or `#FF2A2A` (Aviation/Hazard Red). Same red, same rules.
- **Terminal Green (`#4AF626`):** Optional. Use ONLY for a single specific UI element (e.g., one status indicator or one data readout) — never as a general text color. If it doesn't serve a clear purpose, omit it entirely.
## Layout and Spatial Engineering
The layout must appear mathematically engineered. It rejects conventional web padding in favor of visible compartmentalization.
- **The Blueprint Grid:** Strict adherence to CSS Grid architectures. Elements do not float; they are anchored precisely to grid tracks and intersections.
- **Visible Compartmentalization:** Extensive utilization of solid borders (`1px` or `2px solid`) to delineate distinct zones of information. Horizontal rules (`<hr>`) frequently span the entire container width to segregate operational units.
- **Bimodal Density:** Layouts oscillate between extreme data density (tightly packed monospace metadata clustered together) and vast expanses of calculated negative space framing macro-typography.
- **Geometry:** Absolute rejection of `border-radius`. All corners must be exactly 90 degrees to enforce mechanical rigidity.
## UI Components and Symbology
Standard web UI conventions are replaced with utilitarian, industrial graphic elements.
- **Syntax Decoration:** Utilization of ASCII characters to frame data points.
- *Framing:* `[ DELIVERY SYSTEMS ]`, `< RE-IND >`
- *Directional:* `>>>`, `///`, `\\\\`
- **Industrial Markers:** Prominent integration of registration (`®`), copyright (`©`), and trademark (`™`) symbols functioning as structural geometric elements rather than legal text.
- **Technical Assets:** Integration of crosshairs (`+`) at grid intersections, repeating vertical lines (barcodes), thick horizontal warning stripes, and randomized string data (e.g., `REV 2.6`, `UNIT / D-01`) to simulate active mechanical processes.
## Textural and Post-Processing Effects
To prevent the design from appearing purely digital, simulated analog degradation is engineered into the frontend via CSS and SVG filters.
- **Halftone and 1-Bit Dithering:** Transforming continuous-tone images or large serif typography into dot-matrix patterns. Achieved via pre-processing or CSS `mix-blend-mode: multiply` overlays combined with SVG radial dot patterns.
- **CRT Scanlines:** For terminal interfaces, applying a `repeating-linear-gradient` to the background to simulate horizontal electron beam sweeps (e.g., `repeating-linear-gradient(0deg, transparent, transparent 2px, rgba(0,0,0,0.1) 2px, rgba(0,0,0,0.1) 4px)`).
- **Mechanical Noise:** A global, low-opacity SVG static/noise filter applied to the DOM root to introduce a unified physical grain across both dark and light modes.
## Web Engineering Directives
1. **Grid Determinism:** Utilize `display: grid; gap: 1px;` with contrasting parent/child background colors to generate mathematically perfect, razor-thin dividing lines without complex border declarations.
2. **Semantic Rigidity:** Construct the DOM using precise semantic tags (`<data>`, `<samp>`, `<kbd>`, `<output>`, `<dl>`) to accurately reflect the technical nature of the telemetry.
3. **Typography Clamping:** Implement CSS `clamp()` functions exclusively for macro-typography to ensure massive text scales aggressively while maintaining structural integrity across viewports.
What This Does
Gives Claude a strict design system for raw, mechanical interfaces instead of generic rounded-corner SaaS defaults. It defines two committed visual archetypes — Swiss Industrial Print (light, newsprint background, oversized black type, hazard red accent) and Tactical Telemetry (dark CRT terminal, monospace data, scanlines, phosphor glow) — and requires picking one and holding it for the whole interface.
The system controls typography scale contrast (massive headers at clamp(4rem, 10vw, 15rem) next to 10px monospace metadata), a locked-down color palette, zero border-radius, and analog degradation effects like halftone dithering and CRT scanlines. It comes from Leonxlnx's "taste-skill" project, a set of anti-slop frontend design skills for AI coding agents.
Quick Start
Step 1: Create a Project Folder
mkdir -p ~/Documents/BrutalistUI
Step 2: Download the Template
Click Download above, then:
mv ~/Downloads/CLAUDE.md ~/Documents/BrutalistUI/
Step 3: Start Working
cd ~/Documents/BrutalistUI
claude
Describe the interface you want. Claude picks one archetype (Swiss print or tactical terminal) and applies the full typographic, color, and layout system to it.
The Two Visual Archetypes
Pick one per project. Never mix them in the same interface.
- Swiss Industrial Print — light mode, matte off-white background (
#F4F4F0), carbon-ink text, monolithic heavy sans-serif headers, hazard red (#E61919) as the only accent. Modeled on 1960s corporate identity systems and machinery blueprints. - Tactical Telemetry & CRT Terminal — dark mode only, near-black background (
#0A0A0A, never pure black), white phosphor text, monospace-dominant, ASCII bracket framing, scanline and dithering overlays. Modeled on military databases and aerospace HUDs.
Typography Rules
- Macro headers: Neo-grotesque black weights (Neue Haas Grotesk, Archivo Black, Monument Extended) at fluid scales up to
15rem, negative tracking down to-0.06em, compressed leading (0.85–0.95), uppercase only. - Micro/data text: Monospace (JetBrains Mono, IBM Plex Mono, Space Mono) fixed at 10–14px, generous tracking (
0.05em–0.1em), uppercase, used for all metadata, nav, and coordinates. - Textural disruption: A high-contrast serif (Playfair Display, EB Garamond) used sparingly and only after halftone or 1-bit dithering processing — never rendered clean.
Layout Rules
- Strict CSS Grid. Elements anchor to grid tracks, never float freely.
- Solid 1–2px borders delineate every zone. Full-width horizontal rules separate operational units.
- Density oscillates between tightly packed monospace data clusters and large stretches of negative space around macro type — no in-between.
- Zero border-radius anywhere. All corners are exactly 90 degrees.
Symbology & Texture
- ASCII framing around data points:
[ DELIVERY SYSTEMS ],< RE-IND >, directional markers like>>>and///. - Registration/copyright/trademark symbols (
®©™) used as geometric elements, not legal text. - Simulated analog degradation: CRT scanlines via
repeating-linear-gradient, halftone/1-bit dithering on images and serif type, a global low-opacity noise filter for physical grain.
Tips
- Commit to one archetype before writing any code. Mixing light Swiss print with dark terminal styling in the same interface breaks the system.
- Use
display: grid; gap: 1px;with contrasting parent/child backgrounds to get perfect hairline dividers without managing individual borders. - Reach for semantic tags (
<data>,<samp>,<kbd>,<output>,<dl>) — they reinforce the technical, telemetry feel structurally, not just visually. - Reserve terminal green (
#4AF626) for exactly one status indicator. It has no role as a general text color.
Limitations
- This is a maximalist, opinionated aesthetic. It is wrong for consumer apps, marketing sites aiming for warmth, or anything needing broad accessibility-friendly softness.
- Zero border-radius and heavy monospace use can hurt readability on long-form body text. Reserve the system for dashboards, portfolios, and data-dense tools, not blog content.
- The scanline/noise/dithering effects add visual weight. Test performance on lower-end devices before shipping them at full opacity.