How do I install the Latitude UI And Hud Lifecycle skill?

Run npx skillmds@latest add tomevault-io/latitude-ui-and-hud-lifecycle in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Latitude UI And Hud Lifecycle safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Latitude UI And Hud Lifecycle?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Latitude UI And Hud Lifecycle free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Latitude UI And Hud Lifecycle?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Latitude UI And Hud Lifecycle by tomevault-io

Name: Latitude UI And Hud Lifecycle
Author: tomevault-io

Latitude UI And Hud Lifecycle

Rules for when Latitude UI screens and HUD overlays may render or open. Prevents screens auto-opening in-world, enforces debug gating, and codifies “world creation only” flows. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Latitude — UI & HUD Lifecycle (Authoritative)

This skill prevents UI regressions such as:

spawn/band picker screens opening automatically after joining a world
debug screens appearing without explicit user action
HUD overlays rendering over menus/inventories unintentionally

Screen-opening rules (absolute)

No Latitude config screen may auto-open in-world after joining/spawning.
Screens that configure worldgen (spawn band picker, presets, etc.) are World Creation only.
The only allowed in-world screen opens are:
- explicit keybind action by the player, or
- explicit debug flag enabled (dev-only), or
- explicit command-driven open (if the mod provides commands).

Default must be OFF for any auto-open behavior.

Approved gates for dev-only auto-open

If a developer convenience auto-open exists, it must be gated by a JVM property:

-Dlatitude.debugOpenSpawnPicker=true (default false)

Rules:

Must never be enabled by default.
Must be clearly labeled “debug” in code comments.

HUD overlay rendering rules

HUD overlays must not render when a GUI screen is open unless explicitly intended.
Default: if MinecraftClient.currentScreen != null, skip overlay rendering.
Exceptions must be explicit (e.g., a dedicated “HUD Studio” preview screen).

Event lifecycle rules (client)

Do not open screens from:

join world callbacks
first tick hooks
network handler init
world load events

If a screen must be shown on world creation, it must be launched from:

world creation UI integration points only

Required assistant behavior

When asked to add a screen or overlay, the assistant must:

state the allowed opening triggers
specify the exact gate (keybind / debug property / world creation)
confirm “default OFF” for any auto-open
include a rollback plan

Forbidden behaviors

“Open this screen on join for convenience” unless gated behind a debug flag
Rendering overlays over inventory/menus by default
Shipping releases with debug auto-open enabled

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: latitude-ui-and-hud-lifecycledescription: Rules for when Latitude UI screens and HUD overlays may render or open. Prevents screens auto-opening in-world, enforces debug gating, and codifies “world creation only” flows. Use when this capability is needed.---# Latitude — UI & HUD Lifecycle (Authoritative)This skill prevents UI regressions such as:- spawn/band picker screens opening automatically after joining a world- debug screens appearing without explicit user action- HUD overlays rendering over menus/inventories unintentionally---## Screen-opening rules (absolute)1) **No Latitude config screen may auto-open in-world** after joining/spawning.2) Screens that configure worldgen (spawn band picker, presets, etc.) are **World Creation only**.3) The only allowed in-world screen opens are: - explicit keybind action by the player, or - explicit debug flag enabled (dev-only), or - explicit command-driven open (if the mod provides commands).Default must be **OFF** for any auto-open behavior.---## Approved gates for dev-only auto-openIf a developer convenience auto-open exists, it must be gated by a JVM property:- `-Dlatitude.debugOpenSpawnPicker=true` (default false)Rules:- Must never be enabled by default.- Must be clearly labeled “debug” in code comments.---## HUD overlay rendering rules1) HUD overlays must not render when a GUI screen is open unless explicitly intended.2) Default: if `MinecraftClient.currentScreen != null`, skip overlay rendering.3) Exceptions must be explicit (e.g., a dedicated “HUD Studio” preview screen).---## Event lifecycle rules (client)Do not open screens from:- join world callbacks- first tick hooks- network handler init- world load eventsIf a screen must be shown on world creation, it must be launched from:- world creation UI integration points only---## Required assistant behaviorWhen asked to add a screen or overlay, the assistant must:1) state the allowed opening triggers2) specify the exact gate (keybind / debug property / world creation)3) confirm “default OFF” for any auto-open4) include a rollback plan---## Forbidden behaviors- “Open this screen on join for convenience” unless gated behind a debug flag- Rendering overlays over inventory/menus by default- Shipping releases with debug auto-open enabled---> Converted and distributed by [TomeVault](https://tomevault.io/claim/joolbits) — claim your Tome and manage your conversions.

Frequently asked questions