mono

Define a monospace-driven design system with WCAG 2.2 AA accessibility tokens.

Updated May 13, 2026
One-click install
npx skills add https://github.com/superpollo02/awesome-design-skill --skill mono-superpollo02
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mono
Source: https://github.com/superpollo02/awesome-design-skill/tree/main/skills/mono
Command: npx skills add https://github.com/superpollo02/awesome-design-skill --skill mono-superpollo02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mono turns a vague “hacker/matrix” aesthetic into a consistent, implementation-ready design system with clear tokens, accessibility rules, and do/don’t guidance.

Core Features & Use Cases

  • High-contrast hacker-chic foundations: Space Mono and JetBrains Mono typography, compact density spacing, and a vibrant token palette (primary/secondary/success/warning/danger/surface/text).
  • Accessible interaction behavior: WCAG 2.2 AA, keyboard-first interaction, semantic HTML before ARIA, and visible focus states.
  • Quality-gated component guidance: Opinionated, testable rules that specify required states (default/hover/focus-visible/active/disabled/loading/error where relevant) and enforce hierarchy, spacing rhythm, and accessible hit areas.
  • Use case: Use Mono to design buttons, inputs, cards, and navigation that look “matrix-like” while remaining predictable and screen-reader friendly.

Quick Start

Ask an AI agent to generate the design-system rules and component guidance for a new Mono-styled interface, using the provided tokens and accessibility acceptance criteria.

Frequently Asked Questions about mono

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

FAQPage Schema
How do I build a hacker-chic UI design system with consistent tokens?

A monospace design system uses concrete tokens for typography, spacing, and color to build matrix-inspired UI components. It enforces predictable visual hierarchy and rhythm across buttons, inputs, and cards using named design tokens.

Can I generate accessible matrix-style UI components that meet WCAG 2.2 AA?

Yes, generating matrix-style UI components can meet WCAG 2.2 AA by enforcing keyboard-first interaction and visible focus-visible styling. The design system requires semantic HTML before ARIA to ensure screen-reader friendly interactions.

What interaction states should I include when designing monospace UI components?

When designing monospace UI components, include default, hover, focus-visible, active, disabled, loading, and error states. Testable do/don't quality gates enforce these specific interaction states to maintain accessible and predictable behavior.

How do I apply design tokens to agentic UI generation workflows?

Apply design tokens to agentic UI generation workflows by instructing an AI agent to use the provided spacing, typography, and color tokens as constraints. The agent generates component guidance and accessibility acceptance criteria based on these defined rules.

Does a monospace UI design system require specific dependencies or frameworks?

No, a monospace UI design system does not require specific dependencies or frameworks. It provides implementation-ready rules and concrete tokens that can be applied directly within any agentic UI generation workflow or standard HTML environment.

When should I avoid using a matrix-inspired design system for my interface?

You should avoid using a matrix-inspired design system when your interface requires non-monospace typography or expanded spacing density. The strict token constraints and compact density rules are specialized for hacker-chic aesthetics rather than generalized visual layouts.