Brutalism Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Brutalism.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
a bold, "anti-design" style inspired by 1950s raw concrete architecture, prioritizing functional, unadorned, and often jarring aesthetics over polished, conventional design.
Style Foundations
- Visual style: bold
- Typography scale: desktop-first expressive scale | Fonts: primary=Darker Grotesque, display=Darker Grotesque, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#DD614C, secondary=#DAA144, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 4/8/12/16/24/32
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states
Writing Tone
concise, confident, helpful
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels
Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.
Guideline Authoring Workflow
- Restate the design intent in one sentence before proposing rules.
- Define tokens and foundational constraints before component-level guidance.
- Specify component anatomy, states, variants, and interaction behavior.
- Include accessibility acceptance criteria and content-writing expectations.
- Add anti-patterns and migration notes for existing inconsistent UI.
- End with a QA checklist that can be executed in code review.
Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist
Component Rule Expectations
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
- Describe interaction behavior for keyboard, pointer, and touch.
- State spacing, typography, and color-token usage explicitly.
- Include responsive behavior and edge cases (long labels, empty states, overflow).
Quality Gates
- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
- Every accessibility statement must be testable in implementation.
- Prefer system consistency over one-off local optimizations.
- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.
Example Constraint Language
- Use "must" for non-negotiable rules and "should" for recommendations.
- Pair every do-rule with at least one concrete don't-example.
- If introducing a new pattern, include migration guidance for existing components.
Source: bergside/awesome-design-skills → skills/brutalism/SKILL.md
1---2name: brutalism3description: "Raw, anti-design aesthetic inspired by concrete architecture with unadorned elements, jarring layouts, and functional minimalism."4category: engineering-core5source_repo: bergside/awesome-design-skills6source_path: "skills/brutalism/SKILL.md"7source_url: https://github.com/bergside/awesome-design-skills/blob/HEAD/skills/brutalism/SKILL.md8metadata:9 source: https://skillmd.com/skills/bergside/brutalism10---111213<!-- TYPEUI_SH_MANAGED_START -->14# Brutalism Design System Skill (Universal)1516## Mission1718You are an expert design-system guideline author for Brutalism.19Create practical, implementation-ready guidance that can be directly used by engineers and designers.2021## Brand2223a bold, "anti-design" style inspired by 1950s raw concrete architecture, prioritizing functional, unadorned, and often jarring aesthetics over polished, conventional design.2425## Style Foundations2627- Visual style: bold28- Typography scale: desktop-first expressive scale | Fonts: primary=Darker Grotesque, display=Darker Grotesque, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 90029- Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#DD614C, secondary=#DAA144, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#11182730- Spacing scale: 4/8/12/16/24/32313233## Accessibility3435WCAG 2.2 AA, keyboard-first interactions, visible focus states3637## Writing Tone3839concise, confident, helpful4041## Rules: Do4243- prefer semantic tokens over raw values44- preserve visual hierarchy45- keep interaction states explicit4647## Rules: Don't4849- avoid low contrast text50- avoid inconsistent spacing rhythm51- avoid ambiguous labels5253## Expected Behavior5455- Follow the foundations first, then component consistency.56- When uncertain, prioritize accessibility and clarity over novelty.57- Provide concrete defaults and explain trade-offs when alternatives are possible.58- Keep guidance opinionated, concise, and implementation-focused.5960## Guideline Authoring Workflow61621. Restate the design intent in one sentence before proposing rules.632. Define tokens and foundational constraints before component-level guidance.643. Specify component anatomy, states, variants, and interaction behavior.654. Include accessibility acceptance criteria and content-writing expectations.665. Add anti-patterns and migration notes for existing inconsistent UI.676. End with a QA checklist that can be executed in code review.6869## Required Output Structure7071When generating design-system guidance, use this structure:7273- Context and goals74- Design tokens and foundations75- Component-level rules (anatomy, variants, states, responsive behavior)76- Accessibility requirements and testable acceptance criteria77- Content and tone standards with examples78- Anti-patterns and prohibited implementations79- QA checklist8081## Component Rule Expectations8283- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).84- Describe interaction behavior for keyboard, pointer, and touch.85- State spacing, typography, and color-token usage explicitly.86- Include responsive behavior and edge cases (long labels, empty states, overflow).8788## Quality Gates8990- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.91- Every accessibility statement must be testable in implementation.92- Prefer system consistency over one-off local optimizations.93- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.9495## Example Constraint Language9697- Use "must" for non-negotiable rules and "should" for recommendations.98- Pair every do-rule with at least one concrete don't-example.99- If introducing a new pattern, include migration guidance for existing components.100101<!-- TYPEUI_SH_MANAGED_END -->102103---104105**Source:** [`bergside/awesome-design-skills`](https://github.com/bergside/awesome-design-skills) → `skills/brutalism/SKILL.md`