Files
open-design/design-systems/neobrutalism/DESIGN.md
T
Zakaria a46764fb1b
ci / Validate workspace (push) Has been cancelled
landing-page-ci / Validate landing page (push) Has been cancelled
landing-page-deploy / Deploy landing page (push) Has been cancelled
github-metrics / Generate repository metrics SVG (push) Has been cancelled
refresh-contributors-wall / Refresh contributors wall cache bust (push) Waiting to run
first-commit
2026-05-04 14:58:14 -04:00

3.0 KiB
Raw Blame History

Design System Inspired by Neobrutalism

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

1. Visual Theme & Atmosphere

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

  • Visual style: modern, clean, high-contrast
  • Color stance: primary, neutral, success, warning, danger
  • Design intent: Keep outputs recognizable to this style family while preserving usability and readability.

2. Color

  • Primary: #FDC800 — Token from style foundations.

  • Secondary: #432DD7 — Token from style foundations.

  • Success: #16A34A — Token from style foundations.

  • Warning: #D97706 — Token from style foundations.

  • Danger: #DC2626 — Token from style foundations.

  • Surface: #FBFBF9 — Token from style foundations.

  • Text: #1C293C — Token from style foundations.

  • Neutral: #FBFBF9 — Derived from the surface token for official format compatibility.

  • Favor Primary (#FDC800) for CTA emphasis.

  • Use Surface (#FBFBF9) for large backgrounds and cards.

  • Keep body copy on Text (#1C293C) for legibility.

3. Typography

  • Scale: 13/15/17/21/27/35
  • Families: primary=Inter, display=Inter, mono=JetBrains Mono
  • Weights: 100, 200, 300, 400, 500, 600, 700, 800, 900
  • Headings should carry the style personality; body text should optimize scanability and contrast.

4. Spacing & Grid

  • Spacing scale: 4/8/12/16/24/32
  • Keep vertical rhythm consistent across sections and components.
  • Align columns and modules to a predictable grid; avoid ad-hoc offsets.

5. Layout & Composition

  • Prefer clear content blocks with consistent internal padding.
  • Keep hierarchy obvious: headline → support text → primary action.
  • Use whitespace to separate concerns before adding borders or shadows.

6. Components

  • Buttons: primary action uses #FDC800; secondary actions stay neutral.
  • Inputs: strong focus-visible states, clear labels, and predictable error messaging.
  • Cards/sections: use consistent radii, spacing, and elevation strategy across the page.

7. Motion & Interaction

  • Use subtle transitions that emphasize Primary (#FDC800) as the interaction signal.
  • Default to short, purposeful transitions (150250ms) with stable easing.
  • Ensure hover, focus-visible, active, disabled, and loading states are explicit.

8. Voice & Brand

  • Tone should reflect the visual style: concise, confident, and product-specific.
  • Keep microcopy action-oriented and avoid generic filler language.
  • Preserve the style identity in headlines while keeping UI labels literal and clear.

9. Anti-patterns

  • Do not introduce off-palette colors when an existing token can solve the problem.
  • Do not flatten hierarchy by using the same type size/weight for all text.
  • Do not add decorative effects that reduce readability or accessibility.
  • Do not mix unrelated visual metaphors in the same interface.