agentleFS
Sign inStart free
MRCalderon3DMRCalderon3D/everything-game-dev-code/skills/engineering-common/ui-hud-patterns/SKILL.md

ui-hud-patterns

Skill105 starsChanged 8 months agoMITView on GitHub

Structure HUD and menu implementation so UI remains understandable, maintainable, and aligned with UX goals.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    verify focus, persistence, and feedback loops

    line 29
  2. Distinctive:

    Keep this skill aligned with the relevant rules layer and current project documentation.

    line 63
  3. Distinctive:

    If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

UI Hud Patterns

Purpose

Structure HUD and menu implementation so UI remains understandable, maintainable, and aligned with UX goals.

Use When

  • HUD complexity is growing
  • UI logic is leaking into gameplay code
  • navigation and state are hard to maintain

Inputs

  • flow maps
  • screen inventory
  • input model
  • localization and accessibility needs

Process

  1. separate state, navigation, and presentation
  2. define UI ownership and update triggers
  3. minimize coupling between gameplay systems and widget hierarchies
  4. support localization, scaling, and platform variation
  5. verify focus, persistence, and feedback loops

Outputs

  • UI architecture notes
  • HUD ownership map
  • navigation model
  • integration constraints

Quality Bar

  • UI reads game state through a defined binding layer, never by reaching into gameplay internals
  • HUD elements update from events or observed state changes, not per-frame polling of unrelated systems
  • screen flow (stack, transitions, modality) is owned by one navigation system
  • UI is testable with mocked game state

Common Failure Modes

  • gameplay code directly manipulating UI widgets
  • HUD logic duplicated per screen instead of shared binding patterns
  • navigation state spread across individual screens, causing stuck or double-open menus
  • layouts that break at non-default resolutions or aspect ratios

Related Agents

  • ui-programmer
  • ui-ux-designer
  • accessibility-reviewer

Related Commands

  • ui-flow-review
  • tech-design
  • verify

Related Skills

  • ui-animation-pipeline

Notes

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
  • Boundary: this skill owns runtime HUD architecture and data binding; ui-animation-pipeline owns UI motion authoring and tuning conventions.

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.

Check your setup, free