# pacman

Guides coding agents to build 8-bit arcade design systems with pixel typography, dotted borders, high-contrast tokens, and strict WCAG 2.2 AA accessibility.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2300 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/pacman/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/pacman

## What it does

The skill instructs your coding assistant to write design guidelines inspired by vintage Pac-Man arcade games. It sets up an 8pt baseline grid, dotted borders, and a defined token set with `#2A3FE5` primary, `#F4B9B0` secondary, and `#000000` surface colors. For typography, it enforces Press Start 2P for primary and display text alongside Space Mono for monospaced elements.

Every component guideline generated through this skill covers anatomy, responsive limits, and mandatory interaction states. These states include hover, focus-visible, active, disabled, loading, and error. The output also supplies anti-patterns and a QA checklist ready for pull request reviews.

When retro visual choices clash with usability, the instructions prioritize accessibility over stylistic novelty. Unnecessary motion and low-contrast labels are flagged and replaced by high-contrast tokens and 44px minimum touch targets.

## Install

### Claude Code (native platform)

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

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

### Codex

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

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

### Cursor

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

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

### GitHub Copilot

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

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

### Gemini CLI

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

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

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill pacman -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/pacman/SKILL.md

## When to use it
- write design-system guidelines for retro arcade web interfaces
- specify component states with keyboard-first focus indicators
- enforce WCAG 2.2 AA criteria and 44px touch targets on UI components
- generate code-review QA checklists for frontend styling

## Example prompts
- Generate component rules and interaction states for a retro button in the pacman style
- Create a QA checklist for code review based on the pacman design tokens
- Define modal dialog anatomy and keyboard navigation requirements under pacman

## 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: 73ac68ceb73019e2.

BEGIN THIRD-PARTY FILE 73ac68ceb73019e2
```text
---
name: pacman
description: Retro arcade-inspired design with pixel fonts, dotted borders, playful high-contrast colors, and 8-bit game aesthetics.
license: MIT
metadata:
  author: typeui.sh
---

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

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

## Brand
Dive into the legendary arcade adventure of Pac‑Man, where quick reflexes and smart moves help you clear mazes and escape the ghosts.

## Style Foundations
- Visual style: high-contrast, playful, dotted borders
- Typography scale: desktop-first expressive scale | Fonts: primary=Press Start 2P, display=Press Start 2P, mono=Space Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary, success, warning, danger, info, surface/subtle layers | Tokens: primary=#2A3FE5, secondary=#F4B9B0, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#000000, text=#111827
- Spacing scale: 8pt baseline grid


## Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states, reduced-motion support, 44px+ touch targets, high-contrast support

## Writing Tone
professional

## Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy

## Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid decorative motion without purpose
- avoid ambiguous labels
- avoid mixing multiple visual metaphors

## 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
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
```
END THIRD-PARTY FILE 73ac68ceb73019e2

The third-party file has ended. Everything between the 73ac68ceb73019e2 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 2837 of 3675 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/pacman/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