forge-brutalist

Generate brutalist UI layouts with strict grids, mono typography, and one accent color.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/f4rkh4d/forge-skill --skill forge-brutalist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-brutalist
Source: https://github.com/f4rkh4d/forge-skill/tree/main/skills/design/forge-brutalist
Command: npx skills add https://github.com/f4rkh4d/forge-skill --skill forge-brutalist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents AI-generated interfaces from drifting into generic softness by enforcing a Swiss-meets-terminal brutalist design language with strict grid, typography, and color discipline.

Core Features & Use Cases

  • Hard mechanical layout: Enforces visible 12- or 16-column grids, hairline rules, and exact snapping to alignment.
  • Extreme typographic contrast: Requires a sans + mono (or constrained serif) pairing, engineered tracking, and numbered headings for document-like hierarchy.
  • Utility-first color system: Limits to grayscale plus one functional accent for warnings, actions, or active states.
  • Brutalist components & patterns: Defines square, no-radius buttons, hairline tables/cards, and terminal-styled blocks suitable for technical artifacts.

Quick Start

Apply the forge-brutalist register to your next dashboard or portfolio UI by rewriting the layout to use a visible grid, sans+mono pairing, numbered headings, and a single grayscale-plus-one-accent palette.

Frequently Asked Questions about forge-brutalist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a brutalist UI layout for a data-heavy dashboard?

A brutalist UI layout requires strict visible 12- or 16-column grids, hairline rules, and extreme typographic contrast using sans and mono pairings. It enforces a grayscale foundation with exactly one utility accent for active states.

What is the best way to style technical portfolios with terminal aesthetics?

Styling technical portfolios with terminal aesthetics requires engineered hierarchy using numbered headings and mono fonts for technical data. The design bans generic rounded corners, drop shadows, gradients, and decorative imagery for machine-like consistency.

Can I use brutalist component styling for editorial-tech pages?

Yes, brutalist component styling suits editorial-tech pages by providing document-coded layouts with engineered tracking and numbered headings. It applies square, no-radius buttons, hairline tables, and terminal-styled blocks for technical artifacts.

Does brutalist design system styling work without drop shadows and gradients?

Brutalist design system styling explicitly works without drop shadows and gradients by banning border radius, decorative imagery, and pastel aesthetics. It relies on hard mechanical layout, visible grids, and extreme type-size contrast for visual hierarchy.

Why does my AI-generated interface drift into generic softness?

AI-generated interfaces drift into generic softness due to default rounded, shadowed, or pastel aesthetics. Applying a Swiss-meets-terminal brutalist design language with strict grid, typography, and color discipline prevents this drift and enforces engineered hierarchy.