Atomic Design
Tokens first development.
Neubrutalism design system and Next.js UI kit with reusable components, design tokens, live docs, and SEO-safe markup for fast product shipping.
Version: v0.3.0 · Last updated:
This isn’t a “gallery of random components”. It’s the small set of primitives and patterns that power MetalHatsCats pages, kept consistent as datasets and programmatic routes scale.
The kit is designed to be metadata-safe and JSON-LD friendly: predictable headings, clean markup, and multi-domain-safe URL building.
A live preview of the complete MetalHatsCats Design Kit inventory. Every component here is exactly what you get.
The base container with hard shadow and border.
NBOffsetPanel: Playful tilted box.
The bold top-level header for articles.
"Neubrutalism is the rejection of the polished, the glossy, and the safe."
const theme = "neubrutalism";
console.log(`Shipping ${theme}...`);Quick answer
A summary block designed for SEO snippets and immediate TLDR answers.
| Design Token | Value |
|---|---|
| --mhc-border | 4px |
| --mhc-radius | 14px |
| Plan | Basic | ProBest | Ultra |
|---|---|---|---|
| Borders | ✓ | ✓ | ✓ |
| Shadows | Small | Massive | Custom |
| Support | 24/7 | Dedicated |
Set your design tokens.
Build layouts with cards.
Refine patterns.
Tokens first development.
Built mapping to JSON-LD.
Perfectly balanced contrast.
When to use: Comparing two distinct options or showing a high-level feature overview.
Every component is built with perfectly balanced contrast for both light and dark themes.
Access all components and future updates.
Architect
Creating the neubrutalist web one pixel at a time.
Bold headers improve user retention by 15%.
Because the web deserves a bit of fun. Flat design is everywhere. We want our UI to feel tactile.
Built by developers for developers.
Automatically scans headings on the page.
Not yet. Right now it’s a living kit inside MetalHatsCats: we build real pages first, then harden patterns into reusable components. A sellable “exportable kit” (license + versioning + docs) is planned.
See /design-kit for the token list and component docs.
Yes: canonical/OG and JSON-LD URLs should be derived from an env-based base URL (via getSiteUrl()) rather than hardcoding domains.