AGENT SKILL

industrial-brutalist-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.

License 许可
MIT
最近更新
2026-11-01
Stars
★ 1
Forks
0

01 前言 Front Matter

name
industrial-brutalist-ui
description
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.

02 资源文件 2

03 SKILL.md 正文

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.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.

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 (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.

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: #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.

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 (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.

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: >>>, ///, \\\\
  • 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: 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.

8. 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.

04 同仓库更多 Skills

EmperorKaido99
EmperorKaido99/kai-vault

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

★ 1
EmperorKaido99
EmperorKaido99/kai-vault

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

★ 1
EmperorKaido99
EmperorKaido99/kai-vault

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

★ 1
EmperorKaido99
EmperorKaido99/kai-vault

playwright-skill

Complete browser automation with Playwright. Auto-detects dev servers, writes reusable test scripts, and supports screenshots, responsive checks, UX validation, login flows, link checks, and arbitrary browser automation. Use when the user wants to test a website, automate browser interactions, validate web functionality, or perform browser-based testing.

★ 1
EmperorKaido99
EmperorKaido99/kai-vault

theme-factory

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

★ 1
EmperorKaido99
EmperorKaido99/kai-vault

slack-gif-creator

Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."

★ 1