Industrial Brutalist UI Skill
Equip AI agents with brutalist and tactical telemetry UI rules to produce raw, mechanical, data-dense frontends.
The skill is purely a front-end UI design guide with no code execution, network calls, or data access, so no malicious behavior or over-permission risk is evident. However, it lacks explicit user confirmation mechanisms or data-flow transparency; the publisher is unverified by FollowSkills' curated enterprise registry, so identity is unknown. Deductions: unclear security boundaries, confirmation processes, and data transparency.
The skill is a self-contained text-only design guide; instructions are consistent and do not depend on external scripts or services, making the core usage path plausible. However, no tests, examples, or failure-handling for abnormal input are provided; failure feedback is thin. As this is a static review, execution cannot be verified. Deductions: lack of test coverage and error handling.
The skill clearly defines two visual paradigms (Swiss Industrial Print and Tactical Telemetry) and lists applicable scenarios (data-heavy dashboards, portfolios, editorial sites), but does not explicitly declare non-fit boundaries or unsupported styles like lightweight, soft UIs. Trigger conditions are described clearly, but fit for Chinese users and mainland network reachability is not addressed; no overseas services are required. Deductions: incomplete boundary and trigger documentation.
The skill follows a standard SKILL.md structure with metadata, name, and description; README provides installation instructions, changelog link, FAQ, and license, with clear maintenance responsibility. However, no version or changelog information is present, and known limitations are not explicitly disclosed; examples and technical specifications are sparse. Deductions: missing version info and limitation disclosure.
The skill provides detailed design guidance that can direct users to create industrial brutalist UI, but it offers no directly usable code templates or sample outputs; users must implement from scratch, limiting marginal value. Deductions: lack of directly usable output or verification evidence.
Only the skill file and README are present; no tests, examples, or third-party execution evidence exist, making independent verification impossible. The example images in README lack details and no actual demo is provided. Deductions: insufficient evidence and no independent verification.
- Publisher identity is unverified by the FollowSkills curated enterprise registry; trust level is limited.
- The skill lacks explicit versioning and disclosure of known limitations; use with caution.
- No tests or examples are provided; users should verify actual effectiveness independently.
- The skill does not depend on overseas services, but compatibility for Chinese users and mainland networks is not explicitly addressed.
What does this skill do, and when should you use it?
This skill provides AI agents with a strict visual and engineering specification for building industrial-brutalist user interfaces. It merges Swiss typographic print, military terminal aesthetics, and simulated analog degradation (halftones, CRT scanlines). The skill defines two distinct visual archetypes (Swiss Industrial Print and Tactical Telemetry) with detailed rules for typography hierarchy, color systems, grid layout, UI components, and post-processing effects. It aims to produce designs with high data density and a raw, functional feel, breaking away from common consumer UI patterns. The skill outputs design guidance, not executable code.
Reads a design brief (typically from a user prompt) and outputs a complete design specification, including: choosing one visual archetype (Swiss Industrial Print or Tactical Telemetry); specifying font choices and typographic parameters (e.g., clamp() for macro type, monospaced for micro); setting strict color systems (e.g., #F4F4F0 background and aviation red accent for Swiss style); defining grid layout, borders, and compartmentalization; suggesting UI components (ASCII decorations, industrial markers) and CSS techniques for simulating analog degradation. It also provides engineering directives, such as using CSS grid for 1px dividers and semantic HTML tags, and rejecting border-radius.
- A developer wanting to create a data dashboard with a raw, mechanical feel instead of typical SaaS aesthetics.
- A frontend engineer building a portfolio or editorial site with a dense, terminal-like design language.
- An AI coding agent working on a prototype for an aerospace or military-style concept, needing a cohesive visual language.
- A UI designer who admires Swiss design and brutalism and wants consistent rules applied in AI-assisted projects.
- A team redesigning a legacy web app into a dark, high-tech telemetry aesthetic.
What are this skill's strengths and limitations?
- Detailed typographic and grid specifications for consistent output
- Two distinct and well-defined visual styles
- Includes concrete CSS techniques for analog degradation effects
- Framework-agnostic, applicable to various frontend projects
- Emphasizes anti-generic design, aligning with anti-slop goals
- The skill only provides guidance, not actual code implementation, requiring the agent or developer to implement rules themselves
- The strict rules may be overly prescriptive and not suitable for all project types
- Visual style is very specific and may not suit all brands or client needs
- No test suite or verification method is provided; quality depends on the agent's adherence
- Accessibility considerations like color contrast or readability are not addressed in the skill description
How do you install this skill?
To install the whole collection, run: npx skills add https://github.com/Leonxlnx/taste-skill. To install only this skill, run: npx skills add https://github.com/Leonxlnx/taste-skill --skill "industrial-brutalist-ui". Alternatively, manually copy the file skills/brutalist-skill/SKILL.md into your project or paste it into a conversation.
How do you use this skill?
Ask the agent to follow the skill, e.g., 'Design this dashboard in an industrial brutalist style.' The skill will provide design directions. It does not generate code, only design guidance. For actual implementation, use a coding agent (like Codex or Claude Code) that can write code based on the design rules.
How does this skill compare with similar options?
In the same repository, other skills offer alternative aesthetics: soft-skill provides a softer, more elegant style, while minimalist-skill offers an editorial, Notion-inspired design. If the brutalist style is not suitable, consider these options.