# Arcade Skill Design

Arcade Skill is an agent-era waiting-room arcade. The visual language should
feel like a tiny cabinet beside a terminal: useful enough for developers,
playful enough to invite one run, and honest enough to avoid growth-hack gloss.

## Product Shape

- **Audience:** developers waiting on Codex, Claude Code, installs, tests, CI,
  lint, or diff generation.
- **Core feeling:** retro cabinet, terminal sidecar, short break, back to work.
- **Do not feel like:** a generic browser-game portal, a crypto casino, a mobile
  revive economy, or a SaaS landing page wearing game copy.

## Visual System

- Background: warm paper, not flat white.
- Primary surface: dark cabinet/screen panels.
- Accent colors: phosphor green, coin yellow, spike red, muted teal.
- Radius: 8px or less.
- Typography: system sans for pages, monospace for terminal/game signals.
- Imagery: actual game state, terminal/cabinet compositions, score meters.
- Layout: first viewport should reveal the product premise and at least one real
  arcade/game signal.

## UX Rules

- Language links and scenario links stay readable; do not crowd languages into
  body copy.
- Stripe support is allowed, but never framed as buying power.
- Ranked language must repeat: no paid health, no paid revive, no leaderboard
  advantage.
- Local skill sessions stay ad-free. AdSense belongs only to hosted web pages.

## Awesome Design MD Collaboration Angle

Proposed category: **Retro Web / Developer Tool / Agent UX**.

Pitch: Arcade Skill turns AI-agent waiting time into a tiny retro arcade cabinet.
The design combines terminal status, manifest hot-update architecture, and
Flash-era mini-game energy without becoming a generic games portal.

Contribution posture:

1. Open an issue first, because `VoltAgent/awesome-design-md` asks contributors
   to discuss new entries before PRs.
2. Link the live page: `https://arcade.fxpeek.com/scenarios/`.
3. Link this design file and screenshots.
4. Keep the ask as a design-pattern contribution, not product advertising.