Borrowing it
Nothing to install: this file belongs to ukanwat/aaabench. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ukanwat/aaabench/main/.claude/skills/game-ui-ux/SKILL.mdgit clone --depth 1 https://github.com/ukanwat/aaabenchWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ukanwat/aaabench/game-ui-ux)<a href="https://agentmods.dev/skills/ukanwat/aaabench/game-ui-ux"><img src="https://agentmods.dev/badge/skills/ukanwat/aaabench/game-ui-ux/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ukanwat/aaabench/game-ui-ux"><img src="https://agentmods.dev/badge/skills/ukanwat/aaabench/game-ui-ux.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00123 | $0.02125 |
| Opus 5 | $0.00062 | $0.01063 |
| Sonnet 5 | $0.00025 | $0.00425 |
| Haiku 4.5 | $0.00012 | $0.00213 |
Grade A, and why
game-ui-ux scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
91% identical to game-ui-ux — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Game UI/UX
Build HUDs and menus that stay correct on a phone, an ultrawide monitor, and a TV across a gamepad and a mouse. This skill owns the engine-neutral UI architecture — responsive layout, scaling, focus navigation, screen flow, and how UI talks to game state — and defers the concrete widget API to the engine UI skill.
When to use
- Use when building a HUD (health/ammo/score), a menu (main/pause/settings), an inventory or shop screen, or any overlay, and you want it to scale and navigate correctly.
- Use to fix UI that breaks at other resolutions/aspect ratios, ignores notches/safe areas, can't be used with a controller, or is wired to game state by per-frame polling.
- Use to structure screen flow (title → game → pause → settings) as a stack, not flag soup.
When not to use: for the engine's concrete UI nodes/components and styling, use
godot-ui-control or Unity UI (UGUI/UI Toolkit). For visual punch (button pop, damage
numbers, shake) use game-feel. For branching conversation UI use dialogue-systems. For
translating UI strings, that is localization (see references/ and input-systems for
rebinding screens). For card/board layout specifics, the card-game genre composes this skill.
Core workflow
- Pick a layout model: anchors + containers, never absolute pixels. Anchor elements to
edges/corners/center and let containers (rows, columns, grids) flow children. Absolute
(x, y)positions break at the first new resolution. - Choose a scaling strategy for the whole UI: a reference resolution that scales to fit (most games), plus a policy for extra width/height on other aspect ratios (letterbox, expand, or anchor HUD corners outward).
- Respect the safe area. Inset critical UI from screen edges so notches, rounded corners, and TV overscan don't clip it.
- Make every screen keyboard/gamepad navigable. Set an initial focused control per screen, define focus order/neighbors, and show a clear focus highlight. Mouse and focus must coexist.
- Model screens as a stack. Push (pause over game), pop (resume), with input + visibility handed to the top screen. This makes overlays and "back" trivial.
- Drive the HUD from events, not polling. The HUD subscribes to
health_changed,score_changed, etc. and updates only when they fire — it does not read game state every frame. - Verify across screens and devices. Resize the window, switch aspect ratios, unplug the mouse and navigate by gamepad only, and confirm focus, scaling, and safe-area insets. Report what you actually observed at which resolutions.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 158 lines · 123 tokens per session scan A a950af7eb94c
game-ui-ux is a skill published in the GitHub repository ukanwat/aaabench (382 stars, last pushed 25d ago), licensed MIT. It adds 123 tokens to every session and 2,125 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to game-ui-ux, differing in 22 lines, and is treated as a copy.
Other skills, from other repositories
game-ui-ux
Design and build game UI/UX — HUDs, menus, and overlays — that survive every screen: anchor- based responsive layout, resolution/aspect scaling and safe areas, keyboard/gamepad focus navigation, a screen/menu state stack, and event-driven (not polled) HUD updates. Engine- neutral patterns that pair with the detected…
biome-creation
A workflow for placing rocks, trees, plants, and other reusable scene objects into a Unity biome, a themed area of a game world. It also covers regenerating the biome and checking the result with screenshots.
use-widget-asset
Use when consuming a widget slice (panel, button, slider, progress bar, or toggle pair) from a create-asset-sheet pack in a Summer Engine scene. The pack's metadata.sliceMeta carries 9-slice margins, fill rects, and on/off pair links per slice. This skill explains how to wire those into NinePatchRect…
before-after-audit
A before-and-after screenshot workflow for checking visual changes in a Unity scene. It keeps the Scene view camera fixed, compares the two images, and sends the difference for an external review.
ui-basics
Use when building Summer Engine UI: HUDs, main menus, pause menus, health bars, progress bars, dialogue boxes, or any Control-node tree. Covers anchors, containers (VBox/HBox/Margin), responsive layout, and theme versus inline styling. Trigger on "UI", "HUD", "menu", "health bar", "Control", "anchors"…
game-ui-workflow
Orchestrates an end-to-end game UI workflow from game design (GDD), PRD, and UI interaction logic through design specification, screen-system extension, page image generation, component breakdown, sprite-sheet splitting, PNG ZIP packaging, atlas packing, engine JSON handoff, asset registration, and validation. Use…