brutalism
Skill1 starsChanged 6 months agoMITView on GitHub
Raw, anti-design aesthetic inspired by concrete architecture with unadorned elements, jarring layouts, and functional minimalism.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- hemal08ce094/DesignSkillsSwiftUItheir own version, first seen Nov 8, 2026
- Marvellbrazil/my-agentic-skillstheir own version, first seen Oct 17, 2026
- lachinovedhem/standards-mcpword for word, first seen Oct 11, 2026
- SkotAlexsander/skillsword for word, first seen Sep 16, 2026
- shekhsahebali/ux-ux-skillstheir own version, first seen Aug 10, 2026
- bergside/awesome-design-skillsword for word, first seen Apr 24, 2026
Other versions6 projects use a version of this.
Word for word · 3
- bergside/awesome-design-skills★ 2.9k100% same
- SkotAlexsander/skills★ 1100% same
- lachinovedhem/standards-mcp★ 0100% same
Edited · 0
None found.
Wrote their own version · 3
- Marvellbrazil/my-agentic-skills★ 4same name
- hemal08ce094/DesignSkillsSwiftUI★ 0same name
- shekhsahebali/ux-ux-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- futuristicSkill
- minimalSkill
- ui-ux-pro-maxSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 15 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
15
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
- Distinctive: line 39
prefer semantic tokens over raw values
- Distinctive: line 41
keep interaction states explicit
- Distinctive: line 45
avoid low contrast text
- Distinctive: line 46
avoid inconsistent spacing rhythm
- Distinctive: line 51
Follow the foundations first, then component consistency.
- Distinctive: line 52
When uncertain, prioritize accessibility and clarity over novelty.
- Distinctive: line 54
Keep guidance opinionated, concise, and implementation-focused.
- Distinctive: line 62
Add anti-patterns and migration notes for existing inconsistent UI.
- Distinctive: line 67
When generating design-system guidance, use this structure:
- Distinctive: line 86
No rule should depend on ambiguous adjectives alone.
- Distinctive: line 87
Every accessibility statement must be testable in implementation.
- Distinctive: line 88
Prefer system consistency over one-off local optimizations.
- Distinctive: line 93
Use "must" for non-negotiable rules and "should" for recommendations.
- Distinctive: line 95
If introducing a new pattern, include migration guidance for existing components.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- TYPEUI_SH_MANAGED_START -->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.
<!-- TYPEUI_SH_MANAGED_END -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

