game-menu-system

Manage non-blocking in-game menus through a MENUS data structure.

2|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/TimelessP/idlegames --skill game-menu-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: game-menu-system
Source: https://github.com/TimelessP/idlegames/tree/main/.github/skills/game-menu-system
Command: npx skills add https://github.com/TimelessP/idlegames --skill game-menu-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables developers to build non-blocking, data-driven in-game menus that run alongside gameplay and simulation without forcing pauses.

Core Features & Use Cases

  • Data-driven menus: menus are defined as pure data; handlers are separate.
  • Attribute-driven behavior: actions control navigation and updates without DOM re-creation.
  • Concurrent UI: menus open and update while the game state continues to run.
  • Stack-based navigation: supports root vs. submenu flows with back/close behavior.
  • Extensible architecture: optionally utilize scripts, references, and assets for advanced interactions.

Quick Start

Define a MENUS object with a root entry and render the initial panel using renderUnifiedMenu.

Frequently Asked Questions about game-menu-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create non-blocking in-game menus that run concurrently with gameplay?

Non-blocking in-game menus are created by driving menu structure as pure data, separating handlers from rendering, and using attribute-driven behavior to update navigation without pausing the simulation.

What is a data-driven menu system for live games?

A data-driven menu system defines menus as pure data objects rather than UI code, allowing dynamic lists and in-place updates to refresh values without re-creating the DOM or halting game state.

How do I manage stack-based navigation between root and submenus?

Stack-based navigation manages root and submenu flows by treating menu transitions as data states, supporting back and close behaviors while maintaining concurrent UI updates alongside the simulation.

Can I update dynamic game menu lists in-place without re-rendering?

Yes, in-place menu updates are handled through routines like refreshUnifiedMenuValues and rebuildUnifiedMenuInPlace, which modify dynamic lists and attribute values without full UI re-creation.

Do I need external dependencies to build concurrent game UI menus?

No external dependencies are required; the system relies on a MENUS data structure, a behavior system, and rendering routines, with optional scripts, references, and assets for extended functionality.

When should I avoid using a data-driven approach for game menus?

Avoid data-driven menus if your game requires simple, static UI screens that pause gameplay, as this system is specifically designed for concurrent, non-blocking interfaces within live simulations.