tetris

Generate WCAG 2.2 AA design-system guidelines with Tetris-inspired tokens and interaction states.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides consistent design-system guidance for building bold, compact, high-contrast interfaces inspired by the classic Tetris aesthetic.

Core Features & Use Cases

  • Token-driven foundations: Establishes a defined color palette, typography (Bangers + JetBrains Mono), rounding, and a compact spacing rhythm.
  • Engineering-ready component rules: Guides implementation toward explicit interaction states (default/hover/focus-visible/active/disabled/loading/error) and consistent component behavior.
  • Accessibility and quality gates: Requires WCAG 2.2 AA, keyboard-first interaction patterns, and testable acceptance criteria to prevent regressions.

Quick Start

Use the tetris skill to generate accessible UI guidelines and component implementations that follow its typography, color tokens, spacing rhythm, and explicit interaction-state rules.

Frequently Asked Questions about tetris

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

FAQPage Schema
How do I build an accessible design system with bold typography and high contrast?

To build an accessible design system with bold typography, establish token-driven foundations using fonts like Bangers and JetBrains Mono, then apply WCAG 2.2 AA keyboard-first rules and explicit interaction states to ensure consistent component behavior.

What are semantic design tokens and how do they standardize UI component states?

Semantic design tokens standardize UI component states by mapping raw styling values—like compact spacing rhythms and defined color palettes—to explicit interaction states including default, hover, focus-visible, active, disabled, loading, and error for consistent implementation.

Can I use a playful UI design system for strict accessibility and keyboard-first interactions?

Yes, you can use a playful UI design system for strict accessibility by applying testable QA checklists and WCAG 2.2 AA keyboard-first interaction patterns, ensuring high-contrast interfaces maintain explicit focus-visible states without regressions.

How do I implement focus-visible and other explicit interaction states in UI components?

Implement focus-visible and other explicit interaction states by following engineering-ready component rules that define default, hover, active, disabled, loading, and error behaviors, paired with testable acceptance criteria to prevent visual regressions.

Does a compact spacing rhythm work for high-contrast accessibility guidelines?

A compact spacing rhythm works for high-contrast accessibility guidelines when combined with semantic token usage and explicit component state design, ensuring that bold, compact interfaces meet WCAG 2.2 AA standards for keyboard-first products.