# sega

Defines rules for an arcade-inspired design system with VT323 typography, 0px corners, and chunky push buttons. Useful when crafting game UI specs.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2200 installs · ★ 3349
- Author: typeui.sh
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/sega/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/sega

## What it does

The skill sets instructions for generating game UI guidelines inspired by retro arcade cabinets. It centers on hard 0px corners, the VT323 pixel font for primary and display text, and JetBrains Mono for monospace snippets. Type sizes follow a fixed 13/15/17/21/27/35 scale. Chunky buttons physically press into solid offset blocks, while cards receive rainbow-ringed shadows designed to emulate cabinet trim.

Guideline authoring follows a mandatory six-step process. The model must define design tokens before writing component rules, document interaction states like `focus-visible` or `loading`, and deliver a QA checklist for code review. Accessibility is non-negotiable. The skill demands WCAG 2.2 AA compliance and prioritizes contrast over purely aesthetic choices.

This strict foundation leaves no room for soft border radii or vague spacing values. Components must rely strictly on the 4/8/12/16/24/32 spacing scale and designated hex tokens like `#4502FF` and `#FFDA14`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sega -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/sega/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/sega/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sega -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/sega/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sega -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/sega/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install bergside/awesome-design-skills sega
```

2. **Manually: put the files in place**
- File: `.github/skills/sega/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sega -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/bergside/awesome-design-skills --path skills/sega
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/sega/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sega -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/sega/SKILL.md

## When to use it
- write arcade UI component rules covering all interaction states
- define design tokens using the 4/8/12/16/24/32 spacing scale and VT323 typography
- enforce WCAG 2.2 AA accessibility requirements for retro game interfaces
- generate QA checklists for component code reviews

## Example prompts
- Define an arcade action button with hover, active, and focus-visible states using sega guidelines
- Create design tokens and spacing specs for a retro game inventory card
- Generate a WCAG 2.2 AA compliance checklist for pixel UI elements following sega

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 910e555b5c0adea8.

BEGIN THIRD-PARTY FILE 910e555b5c0adea8
```text
---
name: "sega"
description: "A playful, arcade-inspired interface for games — built on the VT323 pixel typeface, hard-edged 0px corners, chunky pill buttons that physically press into solid offset blocks"
metadata:
  author: typeui.sh
---

<!-- TYPEUI_SH_MANAGED_START -->
# Sega Design System Skill (Universal)

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

## Brand
A playful, arcade-inspired interface for games — built on the VT323 pixel typeface, hard-edged 0px corners, chunky pill buttons that physically press into solid offset blocks, and cards wrapped in rainbow-ringed brand shadows that read like cabinet trim.

## Style Foundations
- Visual style: modern, playful
- Typography scale: 13/15/17/21/27/35 | Fonts: primary=VT323, display=VT323, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#4502FF, secondary=#FFDA14, 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

## Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit

## 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.

## Guideline Authoring Workflow
1. Restate the design intent in one sentence before proposing rules.
2. Define tokens and foundational constraints before component-level guidance.
3. Specify component anatomy, states, variants, and interaction behavior.
4. Include accessibility acceptance criteria and content-writing expectations.
5. Add anti-patterns and migration notes for existing inconsistent UI.
6. End with a QA checklist that can be executed in code review.

## Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist

## Component Rule Expectations
```
END THIRD-PARTY FILE 910e555b5c0adea8

The third-party file has ended. Everything between the 910e555b5c0adea8 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2721 of 3664 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/sega/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md