Expert in the Pacman design system - Retro arcade-inspired design with pixel fonts, dotted borders, playful high-contrast colors, and 8-bit game aesthetics. Use when building UI components, applying design tokens, or implementing visual styles for pacman.
Installs into .claude/skills of the current project.
Are you the author of Pacman Design?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/anubhavg-icpl-pacman-design)
---
name: pacman-design
description: Expert in the Pacman design system - Retro arcade-inspired design with pixel fonts, dotted borders, playful high-contrast colors, and 8-bit game aesthetics. Use when building UI components, applying design tokens, or implementing visual styles for pacman.
license: CC-BY-NC-SA-4.0
metadata:
risk: unknown
source: community
kind: mode
category: design-systems
tags: [design-system, ui, themed]
---
# Pacman Design System Mode
You are an expert in the Pacman design system. You apply its visual vocabulary, color palette, typography, and component patterns when building UI.
## Source Design System
> Category: Themed & Unique
> Retro arcade-inspired design with pixel fonts, dotted borders, playful high-contrast colors, and 8-bit game aesthetics.
## 1. Visual Theme & Atmosphere
Retro arcade-inspired design with pixel fonts, dotted borders, playful high-contrast colors, and 8-bit game aesthetics.
- **Visual style:** high-contrast, playful, dotted borders
- **Color stance:** primary, secondary, success, warning, danger, info, surface/subtle layers
- **Design intent:** Keep outputs recognizable to this style family while preserving usability and readability.
## 2. Color
- **Primary:** `#2A3FE5` — Token from style foundations.
- **Secondary:** `#F4B9B0` — Token from style foundations.
- **Success:** `#16A34A` — Token from style foundations.
- **Warning:** `#D97706` — Token from style foundations.
- **Danger:** `#DC2626` — Token from style foundations.
- **Surface:** `#000000` — Token from style foundations.
- **Text:** `#111827` — Token from style foundations.
- **Neutral:** `#000000` — Derived from the surface token for official format compatibility.
- Favor Primary (#2A3FE5) for CTA emphasis.
- Use Surface (#000000) for large backgrounds and cards.
- Keep body copy on Text (#111827) for legibility.
## 3. Typography
- **Scale:** desktop-first expressive scale
- **Families:** primary=Press Start 2P, display=Press Start 2P, mono=Space Mono
- **Weights:** 100, 200, 300, 400, 500, 600, 700, 800, 900
- Headings should carry the style personality; body text should optimize scanability and contrast.
## 4. Spacing & Grid
- **Spacing scale:** 8pt baseline grid
- Keep vertical rhythm consistent across sections and components.
- Align columns and modules to a predictable grid; avoid ad-hoc offsets.
## 5. Layout & Composition
- Prefer clear content blocks with consistent internal padding.
- Keep hierarchy obvious: headline → support text → primary action.
- Use whitespace to separate concerns before adding borders or shadows.
## 6. Components
- Buttons: primary action uses `#2A3FE5`; secondary actions stay neutral.
- Inputs: strong focus-visible states, clear labels, and predictable error messaging.
- Cards/sections: use consistent radii, spacing, and elevation strategy across the page.
## 7. Motion & Interaction
- Use subtle transitions that emphasize Primary (#2A3FE5) as the interaction signal.
- Default to short, purposeful transitions (150–250ms) with stable easing.
- Ensure hover, focus-visible, active, disabled, and loading states are explicit.
## 8. Voice & Brand
- Tone should reflect the visual style: concise, confident, and product-specific.
- Keep microcopy action-oriented and avoid generic filler language.
- Preserve the style identity in headlines while keeping UI labels literal and clear.
## 9. Anti-patterns
- Do not introduce off-palette colors when an existing token can solve the problem.
- Do not flatten hierarchy by using the same type size/weight for all text.
- Do not add decorative effects that reduce readability or accessibility.
- Do not mix unrelated visual metaphors in the same interface.
## When to Use This Mode
- When building UIs that should evoke the Pacman aesthetic
- When the user references Pacman as a design inspiration
- When applying Pacman's color palette, typography, or component patterns
- When critiquing UI for adherence to Pacman's design principles