neobrutalism

Convert Neobrutalism visual branding into token-based design-system implementation rules.

1|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/PiercingXX/xx-stack --skill neobrutalism-piercingxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neobrutalism
Source: https://github.com/PiercingXX/xx-stack/tree/main/packs/design/design-skills/neobrutalism
Command: npx skills add https://github.com/PiercingXX/xx-stack --skill neobrutalism-piercingxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns Neobrutalism’s visual foundations into clear, implementation-ready design-system rules so teams can build consistent, high-contrast interfaces without guessing.

Core Features & Use Cases

  • Style foundations into enforceable tokens: Codifies typography, spacing, and color palette into concrete constraints (Inter, JetBrains Mono, defined scales).
  • Component-level guidance with states: Provides rules that cover anatomy, variants, and interaction states (default, hover, focus-visible, active, disabled, loading, error as relevant).
  • Accessibility-first acceptance criteria: Anchors requirements to testable accessibility expectations (WCAG 2.2 AA, visible focus states, keyboard-first interactions).
  • Implementation-focused workflow: Guides authors to produce opinionated, concise rules with do/don’t examples, anti-patterns, and a QA checklist.

Quick Start

Ask the design-system authoring assistant to produce Neobrutalism component guidelines for a specific UI element using the provided token palette, typography and spacing scales, and explicit accessibility acceptance criteria.

Frequently Asked Questions about neobrutalism

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create consistent Neobrutalism UI guidelines for a design system?

Yes, Neobrutalism design systems can meet WCAG 2.2 AA accessibility standards. The guidelines generate testable acceptance criteria, ensuring keyboard-first interactions and visible focus states are explicitly defined alongside high-contrast color palettes and token constraints.

Can I standardize component states like hover and focus-visible using design tokens?

You can standardize component states using design tokens by codifying typography, spacing, and color into concrete constraints. The generated rules cover default, hover, focus-visible, active, disabled, loading, and error states to ensure consistent UI behavior across product interfaces.

What is the best way to structure design-to-engineering handoff for high-contrast interfaces?

You need defined typography and spacing scales, such as Inter and JetBrains Mono, to generate Neobrutalism component guidelines. These foundational design tokens act as concrete constraints, allowing the assistant to produce standardized rules for bold borders and warm surface styling.

When should I not use a Neobrutalism style for my product UI?

You should not use a Neobrutalism style for product UIs requiring soft visual hierarchies or low-contrast aesthetics. The style enforces bold borders and high-contrast styling on warm surfaces, which may conflict with minimalist branding or strict visual constraints outside its token palette.