agentleFS
Oliyflemishspeaking560Oliyflemishspeaking560/threejs-game-skills/skills/threejs-game-ui-designer/SKILL.md

threejs-game-ui-designer

Skill0 starsChanged 5 months agoMITView on GitHub

Design premium Three.js game UI. Use for HUDs, menus, overlays, pause/win/lose screens, settings, icon controls, touch UI, typography, responsive layout, safe areas, text fit, and UI/world cohesion.

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use stable dimensions, safe-area padding, text-fit constraints, hover/pressed/focus/disabled states.

    line 26
  2. Distinctive:

    Verify text fit, overlap, safe areas, touch targets, responsive screenshots, and real state changes.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 3 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Three.js Game UI Designer

Purpose

Make game UI intentional, readable, responsive, and genre-specific.

Workflow

Load references/ui-patterns.md as the first action when designing HUDs, menus, overlays, pause/win/lose screens, settings, touch controls, typography, responsive layout, safe areas, text fit, icons, or UI/world cohesion. Track it in a reference ledger with yes/no, path, and failure reason. Do not mark the UI phase complete while this reference is skipped for interface work.

Load references/checklists/game-ui-quality.md, references/checklists/hud-readability.md, and references/checklists/responsive-ui-fit.md before claiming UI/HUD/menu work is complete. Load references/checklists/mobile-input.md when touch controls or mobile safe areas are in scope.

Load references/prompt-templates.md only when the user asks for reusable prompts, a UI pass prompt, or a task template.

Load threejs-image-generator when logos, icons, GUI art, faction marks, menu backgrounds, decals, or 2D HUD assets would improve quality. Use threejs-3d-generator only for 3D menu/showcase objects or diegetic 3D UI props, not normal flat HUD elements.

  1. Capture/inspect desktop and mobile screenshots.
  2. Inventory UI states: gameplay, pause, settings, fail/retry, win/milestone, loading, touch controls.
  3. Define hierarchy: survival/status, objective, feedback, flavor.
  4. Replace utility stat cards with authored clusters, meters, badges, icons, alerts, and modal states.
  5. Use stable dimensions, safe-area padding, text-fit constraints, hover/pressed/focus/disabled states.
  6. Wire UI to game state, not duplicated rules.
  7. Verify text fit, overlap, safe areas, touch targets, responsive screenshots, and real state changes.

Common Failure Modes

  • Generic dashboard/stat-card HUD.
  • UI covers player/threats.
  • Text shifts/clips on mobile.
  • Decorative panels reduce readability.
  • Touch controls look right but do not emit intents.

Final Response

Report the reference ledger, UI state checklist, UI intent, states covered, files changed, screenshots, text-fit/overlap checks, safe-area/touch-target evidence, controls, and remaining risks.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.