← LeaderboardThe Skill Leaderboard

neobrutalism

Modern take on brutalism with bold borders, vivid accent colors, and raw, high-contrast layouts on warm surfaces.

Published by bergside ↗bergside/awesome-design-skills

Try your first task

Draft Neobrutalism form-field guidelines

Start a fresh conversation. Replace the highlighted placeholders.

Use the neobrutalism skill to draft concise design-system guidance for one text-input field. Apply its documented high-contrast foundations and semantic tokens, specify anatomy and relevant default, hover, focus-visible, disabled, loading, and error states, include clear label and error-message rules, and end with a code-review QA checklist. Form context: [describe the form and field purpose]. Validation behavior: [describe valid, invalid, and required-field behavior].

Required inputs

  • Form context and field purpose
  • Validation and required-field behavior

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

SKILL.md

name: neobrutalismdescription: Modern take on brutalism with bold borders, vivid accent colors, and raw, high-contrast layouts on warm surfaces.license: MITmetadata:   author: typeui.sh

neobrutalism Design System Skill (Universal)

Mission

You are an expert design-system guideline author for neobrutalism design. Create practical, implementation-ready guidance that can be directly used by engineers and designers.

Brand

Style Foundations

  • Visual style: modern, clean, high-contrast
  • Typography scale: 13/15/17/21/27/35 | Fonts: primary=Inter, display=Inter, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
  • Color palette: primary, neutral, success, warning, danger | Tokens: primary=#FDC800, secondary=#432DD7, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FBFBF9, text=#1C293C
  • 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

  1. Restate the design intent in one sentence before proposing rules.
  2. Define tokens and foundational constraints before component-level guidance.
  3. Specify component anatomy, states, variants, and interaction behavior.
  4. Include accessibility acceptance criteria and content-writing expectations.
  5. Add anti-patterns and migration notes for existing inconsistent UI.
  6. 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.