
industrial-brutalist-ui
Classic style skill, opt-in: it runs only when called by name. A hard mechanical look with Swiss type, rigid grids, extreme scale contrast and utilitarian colour.
- Installs
- 317
- Last 24h
- +36
- Trending rank
- #4069
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/leonxlnx/taste-skill-classics --skill industrial-brutalist-ui- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads industrial-brutalist-ui automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
SKILL: Industrial Brutalism & Tactical Telemetry UI
1. 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.
2. 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.
2.1 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.
2.2 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).
3. Typographic Architecture
Typography is the primary structural and decorative infrastructure. Imagery is secondary. The system demands extreme variance in scale, weight, and spacing.
3.1 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.03emto-0.06em), forcing glyphs to form solid architectural blocks. - Leading (Line-height): Highly compressed (
0.85to0.95). - Casing: Exclusively uppercase for structural impact.
- Scale: Deployed at massive scales using fluid typography (e.g.,
3.2 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 (
10pxto14px/0.7remto0.875rem). - Tracking: Generous (
0.05emto0.1em) to simulate mechanical typewriter spacing or terminal matrices. - Leading: Standard to tight (
1.2to1.4). - Casing: Exclusively uppercase. Used for all metadata, navigation, unit IDs, and coordinates.
- Scale: Fixed and small (
3.3 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.
4. 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:
#F4F4F0or#EAE8E3(Matte, unbleached documentation paper). - Foreground:
#050505to#111111(Carbon Ink). - Accent:
#E61919or#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:
#0A0A0Aor#121212(Deactivated CRT. Avoid pure#000000). - Foreground:
#EAEAEA(White phosphor). This is the primary text color. - Accent:
#E61919or#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.
5. 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 (
1pxor2px 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.
6. 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:
>>>,///,\\\\
- Framing:
- 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.
7. 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: multiplyoverlays combined with SVG radial dot patterns. - CRT Scanlines: For terminal interfaces, applying a
repeating-linear-gradientto 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.
8. Web Engineering Directives
- 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. - Semantic Rigidity: Construct the DOM using precise semantic tags (
<data>,<samp>,<kbd>,<output>,<dl>) to accurately reflect the technical nature of the telemetry. - Typography Clamping: Implement CSS
clamp()functions exclusively for macro-typography to ensure massive text scales aggressively while maintaining structural integrity across viewports.
FAQ
What does the industrial-brutalist-ui skill do?
Classic style skill, opt-in: it runs only when called by name. A hard mechanical look with Swiss type, rigid grids, extreme scale contrast and utilitarian colour.
How do I install industrial-brutalist-ui?
Run npx skills add https://github.com/leonxlnx/taste-skill-classics --skill industrial-brutalist-ui in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/industrial-brutalist-ui/ (personal) or .claude/skills/industrial-brutalist-ui/ (project).
Which AI agents can use industrial-brutalist-ui?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is industrial-brutalist-ui safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains industrial-brutalist-ui?
It is published by leonxlnx in leonxlnx/taste-skill-classics. It has 317 recorded installs.
More from leonxlnx/taste-skill-classics
high-end-visual-design
leonxlnx/taste-skill-classics
Classic style skill, opt-in: it runs only when called by name. A calm, polished look with soft contrast, generous whitespace and spring motion.
minimalist-ui
leonxlnx/taste-skill-classics
Classic style skill, opt-in: it runs only when called by name. Editorial product UI with a warm monochrome palette, typographic contrast and flat bento grids.
gpt-taste
leonxlnx/taste-skill-classics
Classic skill for GPT and Codex, opt-in: it runs only when called by name. Layout variance, a strict AIDA page structure and GSAP scroll motion.
stitch-design-taste
leonxlnx/taste-skill-classics
Open the skill to read its SKILL.md instructions.
design-taste-frontend-v1
leonxlnx/taste-skill-classics
Open the skill to read its SKILL.md instructions.
design-taste-frontend-v2-experimental
leonxlnx/taste-skill-classics
Open the skill to read its SKILL.md instructions.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.