gui-config

Edits Excel config source tables and mirrors changes into *_data.lua files.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/AvatarGanymede/dev-gui-plugin --skill gui-config-avatarganymede
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gui-config
Source: https://github.com/AvatarGanymede/dev-gui-plugin/tree/main/skills/gui-config
Command: npx skills add https://github.com/AvatarGanymede/dev-gui-plugin --skill gui-config-avatarganymede

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game GUI features often depend on configuration data, and manually keeping Excel source tables in sync with their exported *_data.lua mirrors is error-prone. This Skill automates Phase 4 of the Atom Game GUI pipeline by editing design/tables Excel sources and propagating identical changes to the corresponding *_data.lua files without human interruption. ## Core Features & Use Cases - Excel source table editing: Modifies the authoritative Excel config tables under design/tables as the single source of truth. - Tool-first export with manual fallback: Prefers formal export tools (GDE CLI, excel-config, excel-mcp) to regenerate *_data.lua; falls back to hand-mirroring with a TODO(simulated export) marker when tools are unavailable. - Structured subagent reporting: Returns edited/skipped/blocked status plus changed files and degradation notes to the orchestrator, which records run state centrally. - Use Case: While building a new Bag panel batch-sell button, a subagent adds the new item config rows to the Excel table and mirrors them into bag_data.lua so the runtime and later pipeline phases immediately see the new configuration. ## Quick Start Ask the agent to run the gui-config phase for a panel whose feature requires new configuration data, providing the panel ID and the config fields to add.

Frequently Asked Questions about gui-config

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

FAQPage Schema
How do I sync Excel config tables with Lua data files in a game pipeline?▼

Edit the Excel source table under design/tables first, then export the *_data.lua using a formal tool like GDE CLI or excel-config. If no export tool is available, manually mirror the same fields and values into the *_data.lua file and mark it with a TODO(simulated export) comment.

When should the gui-config phase be skipped?▼

Skip it when the feature does not involve any configuration data. The subagent returns a skipped status and the orchestrator records gui-config as skipped in the run state, letting the pipeline proceed directly to review.

What happens if the Excel export tool is unavailable?▼

The phase degrades gracefully: changes are hand-mirrored into *_data.lua following the GDE export format, a TODO(simulated export) marker is added, and a note to formally re-export is recorded in HUMAN_REVIEW.md without stopping the pipeline.

Does gui-config modify ViewModel files directly?▼

It distinguishes generated file types: *_data.lua config exports may be hand-mirrored on export failure, while *_viewmodel.lua and *ViewModel.cs follow the same tool-first rule defined in the mvvm-contract. Both prefer formal tool export over manual edits.

Why does gui-config not write run state itself?▼

Run state is session-scoped and owned by the orchestrator main agent, which lacks session environment inside subagents. The subagent only returns structured results, and the orchestrator records gui-config status via gui_run_state.py.