Skills

Matrix

A cyber-slick, dark-only Matrix-inspired interface defined by minimalist fashion...

Install

npx skills add bergside/awesome-design-skills --skill matrix -g -a claude-code -y
Category
Engineering
Updated
4mo ago
License
MIT
Context cost
Lightabout 912 tokens
Runs scripts
No, instructions only

What it does

A cyber-slick, dark-only Matrix-inspired interface defined by minimalist fashion, high-tech digital elements

<!-- TYPEUI_SH_MANAGED_START -->

Matrix Design System Skill (Universal)

Mission

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

Brand

A cyber-slick, dark-only Matrix-inspired interface defined by minimalist fashion, high-tech digital elements, monospaced typography, and a single deep monochromatic surface. The aesthetic borrows from order-book exchanges and terminal interfaces: ultra-dense layouts, mono numerics, hairline borders, near-square 2px corners, a single brand-green accent that drives every interaction, and a flat dark surface across every section.

Style Foundations

  • Visual style: high-contrast
  • Typography scale: 12/14/16/20/24/32 | Fonts: primary=Space Mono, display=Space Mono, mono=Space Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
  • Color palette: primary, neutral, success, warning, danger | Tokens: primary=#2DB58A, secondary=#0B0C14, 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, clear, friendly

Rules: Do

  • prefer semantic tokens over raw values
  • preserve visual hierarchy
  • keep interaction states explicit
  • design for empty/loading/error states

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.
Read the whole SKILL.md on GitHub

More in Engineering