← Products

Design
⚙ Needs: a frontend project — the skill is a design system th…

Pacman arcade design system — retro tokens, sprites and UX specs

Build arcade-style interfaces in the Pacman universe: design tokens, SVG sprites, color palette, typography, component patterns, and accessibility guidance

At a glance
What
Build arcade-style interfaces in the Pacman universe: design tokens, SVG sprites, color palette, typography, component patterns, and accessibility guidance
Cost
Free
Needs
a frontend project — the skill is a design system the agent applies, not software
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @bergside
⌁

Install

Prerequisites: a frontend project — the skill is a design system the agent applies, not software Install "Pacman arcade design system — retro tokens, sprites and UX specs" for me. It gives my agent @bergside's complete Pacman-arcade design system: design tokens (colors, typography, spacing, radius, effects), full color palette, SVG sprites (Pacman, ghosts, game elements), component patterns (arcade buttons, score displays, cards, panels), page templates, UX specs, and accessibility guidance (reduced motion, high contrast, keyboard nav). NOTE: character designs reference the copyrighted Pac-Man IP — keep use to fan/tribute works, not commercial Pac-Man-branded products. The sprite assets live in the repo's assets directory. MIT-licensed. Repository: https://github.com/bergside/awesome-design-skills/blob/main/skills/pacman/SKILL.md 1. Fetch the SKILL.md file (and its assets directory) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "pacman". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the interface or project to restyle; nothing else — it's a design system). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.