sega

Generate Sega-inspired UI design guidance with VT323 typography and WCAG 2.2 AA accessibility.

2.3k|211|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/bergside/awesome-design-skills --skill sega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sega
Source: https://github.com/bergside/awesome-design-skills/tree/main/skills/sega
Command: npx skills add https://github.com/bergside/awesome-design-skills --skill sega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams build consistent, arcade-inspired game interfaces without losing accessibility or implementation clarity.

Core Features & Use Cases

  • Token-driven Sega foundations: Establishes Sega’s VT323 pixel typography, JetBrains Mono labels, and the primary/secondary/success/warning/danger palette with a strict spacing and rounding system.
  • Component-ready behavioral rules: Specifies interaction states (default/hover/focus-visible/active/disabled/error/loading as relevant) and interaction patterns that work for keyboard-first and touch/pointer inputs.
  • Quality gates and anti-pattern prevention: Enforces testable accessibility constraints (WCAG 2.2 AA) plus do/don’t guidance so generated UI remains readable, rhythm-consistent, and label-safe.
  • Use case: Ship a cohesive UI kit for a game settings screen, HUD, or menu system that looks authentically Sega while remaining maintainable and reviewable.

Quick Start

Use the sega skill to generate a Sega-styled, keyboard-accessible component set for a game UI, following the provided tokens, state rules, and QA checklist.

Frequently Asked Questions about sega

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

FAQPage Schema
How do I build an arcade-style game UI that stays accessible and consistent?

An arcade-style game UI requires tokenized styling foundations, explicit interaction states, and WCAG 2.2 AA keyboard-first focus behavior to remain accessible. Applying VT323 pixel typography with hard-edged rounding and strict spacing rules ensures visual consistency across game menus and HUD controls.

What typography and color tokens do I need for a Sega-inspired design system?

A Sega-inspired design system needs VT323 pixel typography for display text, JetBrains Mono for labels, and a primary/secondary/success/warning/danger color palette. Strict spacing and hard-edged rounding systems must also be tokenized to maintain rhythm across interactive component families.

How do I define interaction states for game menu components?

Game menu components require explicit default, hover, focus-visible, active, disabled, error, and loading interaction states. These states must support keyboard-first and touch/pointer inputs while adhering to WCAG 2.2 AA accessibility constraints and testable do/don't quality gates.

Can I use pixel typography in a game HUD without failing accessibility checks?

Pixel typography in a game HUD passes accessibility checks when paired with keyboard-first focus behavior and WCAG 2.2 AA compliance. Enforcing testable quality gates, label-safe rules, and consistent spacing rhythm ensures the UI remains readable and reviewable.

What's the best way to prevent anti-patterns in arcade UI component libraries?

Preventing anti-patterns in arcade UI component libraries requires enforcing testable do/don't rules, component anatomy specifications, and QA criteria. Token-driven foundations with explicit interaction states and accessibility constraints keep generated game interfaces maintainable and rhythm-consistent.

Does a Sega-inspired UI design system work for both game settings screens and HUD overlays?

A Sega-inspired UI design system works for game settings screens, HUD overlays, and menu systems by applying consistent tokenized styling across all component families. Shared behavioral rules for interaction states and spacing rhythm ensure cohesive implementation regardless of the specific game interface.