What problem does it solve? Teams building interfaces in a Brutalist aesthetic often lack consistent, codified rules, leading to inconsistent spacing, low-contrast text, and ambiguous component states. This Skill turns the Brutalism style foundations into concrete, testable design-system guidance that engineers and designers can apply directly. ## Core Features & Use Cases - Token-anchored guidance: Defines color tokens (primary #DD614C, secondary #DAA144, semantic states), typography (Darker Grotesque, JetBrains Mono), and a 4/8/12/16/24/32 spacing scale as the basis for every rule. - Component-level rules: Specifies anatomy, variants, and states (default, hover, focus-visible, active, disabled, loading, error) with keyboard, pointer, and touch interaction behavior. - Accessibility enforcement: Anchors guidance to WCAG 2.2 AA with testable acceptance criteria, visible focus states, and explicit do/don't rules. - Use Case: A designer asks for a design-system spec for a new landing page; the Skill outputs tokens, component rules, anti-patterns, migration notes, and a QA checklist usable in code review. ## Quick Start Ask the assistant to generate Brutalism design-system guidelines for your component library, including tokens, component states, accessibility criteria, and a QA checklist.
