game-ui-ux
Skill2 starsChanged 31 days agoMITView on GitHub
Engine-agnostic game UI/UX design guidance, adapted for Roblox ScreenGuis. Covers responsive scale-based layout, safe areas, gamepad focus navigation, a panel/screen stack, event-driven HUD updates, accessibility and localization. Use when building or fixing a Roblox HUD, menu, shop, modal window or overlay; when UI breaks on phones, tablets or consoles, collides with the top bar, thumbstick or jump button, or can't be used with a gamepad; when a HUD polls state every frame; or when structuring panel flow so only one window is open at a time.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- ForgeyClap/Forge-Coretheir own version, first seen Nov 16, 2026
- felixarvid2/claude-skillstheir own version, first seen Nov 16, 2026
- gamedev-skills/awesome-gamedev-agent-skillstheir own version, first seen Nov 11, 2026
- openaigames/OpenAIGamesDesignertheir own version, first seen Oct 15, 2026
- ukanwat/aaabenchtheir own version, first seen Aug 15, 2026
- ukanwat/overtimetheir own version, first seen Aug 15, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- gamedev-skills/awesome-gamedev-agent-skills★ 9ksame name
- ukanwat/aaabench★ 399same name
- ukanwat/overtime★ 399same name
- ukanwat/selfstarter★ 399same name
- openaigames/OpenAIGamesDesigner★ 24same name
- ForgeyClap/Forge-Core★ 2same name
- felixarvid2/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- template/CLAUDE.mdCLAUDE.md
- roblox-lessonsSkill
- audio-designSkill
- game-feelSkill
- level-designSkill
- roblox-creator-store-security-auditSkill
- roblox-dataSkill
- roblox-debugging-bugfixSkill
- roblox-devSkill
- roblox-monetizationSkill
- roblox-networkingSkill
- roblox-publish-checklistSkill
- roblox-release-operationsSkill
- roblox-security-economySkill
- roblox-securitySkill
- roblox-studio-mcpSkill
- roblox-to-issuesSkill
- roblox-toolingSkill
- save-systemsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Layout: use Scale sizes with AnchorPoint, UIAspectRatioConstraint, and UIListLayout/UIGridLayout/UIPadding.
- Very specific: line 16
Panel stack: use a UIManager-style client module.
- Very specific: line 22
Event-driven: update on RemoteEvent pushes or GetAttributeChangedSignal, never by polling in RenderStepped.
- Very specific: line 23
Localization: use LocalizationTable and AutoLocalize, and let text containers grow with AutomaticSize.
- Distinctive: line 33
Verify at real sizes: a phone in landscape (about 749×367 usable), a tablet, 1080p, and gamepad-only.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Game UI/UX
Where this conflicts with the roblox-lessons skill, roblox-lessons wins. Read roblox-lessons references/ui.md before building UI. It holds the TextScaled, inset, canvas-size and aspect-constraint traps.
Build HUDs and menus that stay correct on a phone in landscape, a desktop monitor and a TV with a gamepad.
On Roblox
- Layout: use Scale sizes with
AnchorPoint,UIAspectRatioConstraint, andUIListLayout/UIGridLayout/UIPadding. Never use offset-only pixel layouts. Size windows from the screen with a maximum cap. - Layering: give each layer its own ScreenGui with a fixed
DisplayOrder(ladder: HUD 2–4, windows 5, notices 6, reveals 7, tutorial 9, effects 20, loading 100). SetResetOnSpawn = falseon persistent UI. - Panel stack: use a
UIManager-style client module. Panels register by name, opening one closes the others, Escape or gamepad B closes the top one, and a changed signal lets HUD tiles hide under an open window. - Safe areas:
- The top bar:
GuiService:GetGuiInset()andIgnoreGuiInset. - Notches:
ScreenGui.ScreenInsets. - On phones, the thumbstick (bottom-left), the jump button (bottom-right) and the chat button (top-left). Read
TouchGuipositions at runtime.
- The top bar:
- Gamepad and console: set the initial focus with
GuiService.SelectedObject, set explicit neighbours withNextSelectionUp/Down/Left/Right, and mark controlsSelectable. Style focus withSelectionImageObject. Track the input device withUserInputService.LastInputTypeChanged. - Event-driven: update on RemoteEvent pushes or
GetAttributeChangedSignal, never by polling inRenderStepped. Build list rows once and update them in place. - Localization: use
LocalizationTableandAutoLocalize, and let text containers grow withAutomaticSize.
Workflow
- Lay out with anchors, scale and layouts, never absolute pixel positions.
- Pick one scaling policy for the whole UI (size from screen height with caps), and decide where extra width goes.
- Inset critical UI from the top bar, notches and touch controls. Decorative art can bleed to the edges.
- Make every screen reachable by gamepad: give it an initial focus, neighbours and a visible focus style.
- Model screens as a stack (push an overlay, pop on back) instead of boolean flags.
- Drive the HUD from events.
- Verify at real sizes: a phone in landscape (about 749×367 usable), a tablet, 1080p, and gamepad-only. Report what you observed at each size.
Pitfalls
- Offset sizes designed on one monitor overflow phones.
TextScaledturned off by settingTextWrappedafterwards (roblox-lessons ui.md).- HUD under the top bar, a notch or the thumbstick.
- Nothing focused when a window opens, so the gamepad does nothing.
- Polling player state every frame instead of reacting to pushes.
- Rebuilding lists on every push, which restarts every progress bar.
- Tiny fixed text; text with no size cap that balloons on big screens.
- Menu flow as flags (
isShopOpen,inSettings, ...). Use a stack. - English baked into fixed-width buttons, so translations overflow.
- A refusal toast drawn under the window that triggered it.
References
references/layout-and-flow.md: scaling, safe-area math, focus navigation, a panel-stack sketch, world-space UI (BillboardGui, SurfaceGui, ProximityPrompt), accessibility, and localization-ready layout.
Related: game-feel (pops and transitions on top of this layout), roblox-lessons.
Adapted from awesome-gamedev-agent-skills (Apache-2.0). Modified; see SOURCE.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

