sega

Generate arcade-style game UI component guidance with tokenized styling and WCAG 2.2 AA interaction states.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams consistently create game-like, arcade-inspired interfaces that look sharp and feel tactile while staying accessible and implementation-ready.

Core Features & Use Cases

  • Arcade visual system: Pixel-typography foundations (VT323 + JetBrains Mono) with hard 0px corners and chunky, pressable control shapes.
  • Tokenized styling rules: Reusable color, spacing, and rounding scales to keep UI cohesive across components.
  • Accessible interaction guidance: Keyboard-first behavior and visible focus states aligned to WCAG 2.2 AA expectations.

Quick Start

Use the sega skill to generate UI component guidance for an arcade-style game dashboard, including typography, colors, spacing, and accessibility-safe interaction states.

Frequently Asked Questions about sega

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

FAQPage Schema
What is an arcade-inspired design system and when do I need one for my UI?

An arcade-inspired design system provides tokenized styling and component rules for pixel-forward game UIs. You need one when building cohesive game menus or dashboards that require pixel typography, chunky pressable controls, and consistent interaction states.

How do I build accessible arcade UI components with proper interaction states?

Build accessible arcade UI components by defining explicit default, hover, focus-visible, active, disabled, loading, and error states. Align keyboard-first behavior with WCAG 2.2 AA expectations to ensure pixel-style controls remain navigable and tactile.

Can I use pixel typography like VT323 and JetBrains Mono in a token-driven design system?

Yes, pixel typography like VT323 and JetBrains Mono works in a token-driven design system. These fonts establish an arcade visual foundation that pairs with reusable color and spacing scales to maintain cohesive styling across hard-cornered UI components.

What's the best way to standardize component states for pixel-style game menus?

Standardize component states for pixel-style game menus by authoring rules that require token-driven styling for every interaction. Define explicit visual changes for default, hover, active, and focus-visible states to keep arcade UIs accessible and implementation-ready.

Does an arcade UI design system support WCAG 2.2 AA keyboard-first navigation patterns?

An arcade UI design system supports WCAG 2.2 AA keyboard-first patterns by enforcing visible focus states and tactile interaction guidance. This ensures pixel-forward interfaces like game dashboards remain accessible without sacrificing their chunky, pressable aesthetic.

Why do my game dashboard components look inconsistent across different screens?

Game dashboard components look inconsistent when they lack a tokenized styling system. Applying reusable color, spacing, and rounding scales with explicit component state rules ensures your arcade UI maintains visual cohesion across all interactive controls and screens.