authentic-ui-rebuild

Stars14

Forks4

UpdatedMay 26, 2026 at 07:30

Use when the user wants a placeholder/custom UI overlay replaced with the authentic v95 client version sourced from the WZ assets + IDA database — phrases like "not the custom overlay", "not the placeholder", "we have a custom overlay right now, but it's not authentic", "authentic v95", "authentic [stat/inventory/equip/chat/skill/quest/family/system menu/NPC dialog/channel select/character profile/key config/buddy/party/guild/alliance/blacklist] window", "rebuild [UI] 1:1 from the IDB", "look up CUI[X] and rebuild it 1:1", "fix [UI screen] to match the IDB", "look into the proper IDB implementation", "use the natural UI and proper icons", "should reuse the [UIWindow*.img/...]", "look into the IDB for the proper [UI]". Walks the WZ subtree identification → `CUI*` class decompile via `ida-lookup` → coordinate extraction → C# rebuild loop. For full-screen rebuilds it escalates to the `v95-ui-rebuilder` agent; for origin extraction to the `ui-origin-finder` agent. Triggers ONLY for UI that exists in the original

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

MujyKun

MujyKun/MapleClaude

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

More from this repository

same repository

autonomous-phase

MujyKun/MapleClaude

Use when the user explicitly hands off the phase queue and wants Claude to pick the next item from `docs/roadmap.md` and run it to completion, then loop — phrases like "continue with the next phase", "do the next phase", "do the next phase from the readme", "continue with the phases", "continue with the phases to be implemented from the readme", "auto-implement the rest of the phases", "on auto mode dont ask me about anything", "im going to bed", "keep going on the roadmap", "keep going", "auto-run the roadmap". Reads `docs/roadmap.md` for the next un-shipped phase, plans, implements (delegating to `authentic-ui-rebuild`, `ingame-feature`, `wz-audio-bind`, `wz-subsystem-research`, packet skills as needed), tests, and ships via `ship-pr` — which still asks for per-commit approval per CLAUDE.md (no blanket auto-commit). Loops to the next phase until interrupted, roadmap exhausted, or three consecutive failures. Triggers NOT for a single mid-flight task (just keep working) and NOT for short replies like "continu

2026-05-2614

ida-lookup

MujyKun/MapleClaude

Use when the user wants a single v95 client class, function, struct, or constant looked up — phrases like "look into the IDB", "look into the IDB for X", "reference the IDB", "look up CXxx", "look in the idb", "check the IDB for", "investigate it with the idb", "look into how the v95 client does X", "look into the proper IDB implementation", "find the function that does Y", "decompile CUI[X]", "the IDB for the proper [Y]", or anywhere the user implies "go ask the IDA database what the real client does here". Drives the live `ida-pro/idalib` MCP via `idb-bind`, runs the standard lookup_funcs → decompile → xrefs recipe, and surfaces a paraphrased answer with translated constants / coordinates / formulas — never the .i64 path, never raw decompiled C++ blocks pasted into committed files. Triggers ONLY for single-symbol queries; NOT for full WZ subsystem sweeps (use `wz-subsystem-research`) and NOT for full UI screen rebuilds (use `authentic-ui-rebuild`, which itself calls into this skill).

2026-05-2614

ingame-feature

MujyKun/MapleClaude

Use when the user wants a player or world feature implemented end-to-end (packets + animation + WZ assets + state) — phrases like "implement [combat / death / drop / pickup / NPC click / emotion / facial expression / damage / attack / knockback / tombstone / revive / collision / aggro / mob movement / loot / level up]", "research how a player dies", "ensure when the player's HP reaches 0 he dies", "we need to be able to hit mobs", "mobs should X when Y", "player should X when Y", "when [event] happens, [response]", "mob death animation", "drop to the ground", "pick it up should fly into the character", "play the mob's sounds when hit", "introduce facial expressions", "we want emotions when F1-F7 is pressed", or similar full-feature requests that cut across the packet layer + the IDB animation logic + the WZ assets + the runtime state. Coordinates calls into `client-packet-author`, `server-packet-mirror`, `ida-lookup`, `wz-audio-bind`, and `wz-subsystem-research`. Triggers NOT for UI windows alone (`authentic-

2026-05-2614

layering

MujyKun/MapleClaude

Use when the user reports — or wants to enforce — that an NPC, mob, character, or drop is rendering on the wrong z-layer relative to a map's tiles/objs/trees — phrases like "layering", "z-index", "z-order", "z order", "render order", "the player goes behind/in front of [the tree/the object/the platform]", "draw order is wrong", "entity is in the wrong layer", "obj covers the player", "tree is behind the mob", "foothold layer", "make NPCs/mobs/characters layer-aware", "honor the v95 layer model", "draw on the correct layer", "behind the [obj/wall/decoration]". Owns the 8-layer + per-layer-z draw model documented in `docs/map-wz.md`, the foothold→entity-layer mapping, and the canonical per-layer entity draw order used by `GameStage.DrawEntitiesAtLayer`. Triggers NOT for parallax-back sort order (that's the `back/front` flag inside `FieldScene.DrawBacks`) and NOT for shader depth-buffer questions (we are 2D — no real depth buffer).

2026-05-2614

layout-tune

MujyKun/MapleClaude

Use when the user wants to nudge an already-rendered UI element by a small amount — phrases like "move it [N]px [direction]", "move it 3px down", "lower it like 3px", "move it 2 pixels to the right, 4 down", "icon too high", "icon too low", "the [element] is wrong [direction]", "needs to be a bit higher", "needs to be a bit lower", "nudge [element]", "position is wrong", "the position is off", "needs to be [N]px [direction]". Redirects the user to the live debug overlay (`watch.ps1` + `MAPLECLAUDE_DEBUG=1`) for tuning without rebuild, and only when overlay tuning isn't possible, makes the smallest constant-edit in the right Stage/UI file. Triggers ONLY for nudging an existing element; NOT for adding new UI (use `authentic-ui-rebuild`) and NOT for reading WZ origins from scratch (use `ida-lookup` or the `ui-origin-finder` agent).

2026-05-2614

wz-audio-bind

MujyKun/MapleClaude

Use when the user wants a sound or music clip from `Sound.wz` wired to a runtime event — phrases like "play [X] sound", "play the BGM", "play the BGM from Sound.wz", "BGM from Sound.wz of maps", "mob sounds when it gets hit", "play the mob's sounds", "audio for [Wizet/Nexon/Title/login]", "Bgm for [Wizet/Nexon]", "play the map's BGM", "Sound.wz/[node]", or any reference to binding a Sound.wz node to a play trigger (map BGM swap on `SetField`, mob hit/die SFX, UI clicks, login map BGM, drop/pickup SFX). Locates the right Sound.wz subtree, identifies the trigger site, wires through the project's MonoGame audio service in `src/MapleClaude/Audio/` (XAudio2 — NOT BASS). Triggers NOT for WZ binary decode work (that's `wz-reader`) and NOT for inventing new sound effects with no Sound.wz source.

2026-05-2614

name

authentic-ui-rebuild

description

authentic-ui-rebuild

The MapleClaude codebase has converted many UI screens from custom placeholders to WZ-textured + IDB-coordinate-authentic versions: stat window, system menu, key config, channel/world/char select, skill window, quest log, NPC dialog, social/community window, item tooltip, chat window, minimap, etc. The pattern is well-established. This skill owns the recipe for the next conversion.

When this fires vs adjacent skills

Pattern	Skill
"Not the custom overlay, the authentic v95 X"	THIS skill
"Look up CXxx in the IDB" (single symbol)	`ida-lookup`
"Move it 3px down" (already authentic)	`layout-tune`
"Build a typed model for all of Mob.wz" (data, not UI)	`wz-subsystem-research`
"Implement the player death flow" (gameplay)	`ingame-feature` (which may call into this)

Procedure

1. Identify the WZ subtree

The window's name maps to a UIWindow.img/<X> or UIWindow2.img/<X> subtree. Common ones:

Window	WZ path	IDB class
Stat	`UIWindow2.img/Stat`	`CUIStat`, `CUIStatDetail`
Inventory	`UIWindow.img/Item`	`CUIItemInven`, `CUIInvenDlg`
Equipment	`UIWindow.img/EquipSlot`	`CUIEquip`, `CUIEquipSlot`
Character profile	`UIWindow2.img/UserInfo/character`	`CUIUserInfo`
Skill	`UIWindow.img/Skill`	`CUISkill`
Quest log	`UIWindow2.img/QuestInfo`	`CUIQuestInfo`
NPC dialog	`UIWindow2.img/UtilDlgEx`	`CUtilDlgEx`, `CUtilNpcChat`
System menu (ESC)	`UIWindow.img/GameMenu`	`CUIGameMenu`
System options	`UIWindow.img/SysOpt` (NOT `OptionMenu`)	`CUISysOpt`
Channel shift	`UIWindow2.img/ChannelShift`	`CUIChannelShift`
Channel select	UI.wz (login)	`CUIChannelSelect`
World select	UI.wz (login)	`CUIWorldSelect`
Character select	UI.wz (login)	`CUICharSelect`
Character creation	UI.wz (login)	`CUICharCreate`, `CUIRaceSelect`
Key config	`UIWindow2.img/KeyConfig` (NOT UIWindow)	`CFuncKeyManager`, `CUIKeyConfig`
Quick slot	`StatusBar2.img/quickSlot` (NOT `quickSlot` popout in HD)	`CUIQuickSlot`
Status bar HUD	`StatusBar2.img/...` (HD) / `StatusBar.img` (legacy)	`CUIStatusBar`
Minimap	`UIWindow.img/MiniMap` (frame) + `Map.wz/MapHelper.img/minimap` (icons)	`CUIMiniMap`
Tooltip (item/equip)	`UIWindow2.img/ToolTip/Equip` (NOT custom)	`CUIToolTip`, `CUIItemTip`
Chat / chatbox	`UIWindow2.img/ChatBalloon` + status bar chat	`CUIChat`, `CUIChatBox`
Buddy / Party / Guild / Alliance / Blacklist	`UIWindow2.img/UserList/Main` (6-tab)	`CUIUserList`
Family	`UIWindow2.img/Family`	`CUIFamily`
Storage / Trunk	`UIWindow.img/Trunk`	`CUITrunk`
Messenger	`UIWindow.img/Messenger`	`CUIMessenger`
Cash shop	`UIWindow.img/CashShop`	`CUICashShop`
Revive / Tombstone	`UIWindow2.img/Revive` + tombstone canvas	`CUIRevive`, `CUITombstone`

When the mapping isn't obvious, run lookup_funcs CUI and grep the results for the window the user named. Search the existing memory entries first — many windows are already mapped (see [[ingame-ui-windows]]).

2. Identify the matching `CUI*` class

Delegate to ida-lookup:

Look up CUIStat::OnCreate, CUIStat::Init, CUIStat::Draw, CUIStat::PaintRect, CUIStat::UpdateRect. Decompile each and report the WZ canvas frame ids, exact (x, y) offsets per element, origin frame / coordinate space, and mouse-hit rectangles.

For full-screen rebuilds where the IDB walk is complex (lots of sub-classes, lots of state), escalate to the v95-ui-rebuilder agent — same handoff pattern as wz-subsystem-research uses for its sweep agent:

Agent({
  description: "Authentic <X> UI rebuild",
  subagent_type: "v95-ui-rebuilder",
  prompt: "Rebuild the v95 <X> window 1:1 from the WZ assets + IDB. WZ path: <…>. IDB
           class: CUI<X>. Produce a working stage/widget in src/MapleClaude/UI/Game/ that
           matches the original positions, mouse-hit rects, and tab/button behavior.
           Match the depth of the CUIStat conversion — see memory [[stat-window-cuistat]]."
})

For origin extraction (a known sticking point), the ui-origin-finder agent specializes:

Agent({
  description: "<X> UI origin table",
  subagent_type: "ui-origin-finder",
  prompt: "Extract the authentic on-screen position / origin / layout of the v95 <X>
           window. Return a table of element → (x, y) + origin + WZ asset + coordinate
           space, ready to drop into the C# stage."
})

3. Extract the layout from the IDB output

From the decompile, you should leave with:

WZ canvas frame ids the element uses (backgrnd, Bt*, icon, etc.).
Per-element (x, y) offsets — usually relative to the window's origin frame, not screen.
The origin frame itself (the WZ canvas's origin node, often (0, 0) but not always).
Mouse-hit rectangles (PtInRect calls; their bounds = the click region).
StringPool ids for any labels — resolve via mcp__plugin_ida-pro_idalib__get_string or search_text of the numeric id.
Font / color picks (often WzComparerR-style: font face id, font size, color RGBA).
Tab navigation: which sub-classes get pushed/popped on tab clicks.

4. Implement in C#

Place files where the rest of the converted windows live:

File	Purpose
`src/MapleClaude/UI/Game/<X>Window.cs` (or `Stages/<X>Stage.cs` for a full-screen one)	Top-level widget
`src/MapleClaude/UI/Game/<X>Tab.cs` (per tab)	Sub-widgets
`src/MapleClaude/UI/Components/...`	Reusable buttons / scrolls if needed
`src/MapleClaude/Net/Handlers/<X>Handlers.cs`	Any new packet decoders
`src/MapleClaude/Net/Senders/<X>Sender.cs`	Any new packet encoders

Use the existing WzCanvas + SpriteAtlas + Renderer plumbing — don't reinvent canvas loading. The canonical worked example is CUIStat (see [[stat-window-cuistat]]); copy its style.

5. Hard rules — what authentic means

No custom-drawn rectangles when a Bt* (button) or backgrnd canvas already exists.
No hand-picked font / color when the WZ node carries them.
No hand-eyeballed coordinates when the IDB has them — that's just a delayed bug.
No OptionMenu — the v95 system options window is SysOpt (common mistake).
No UIWindow icons for the v95 key config — it's UIWindow2.img/KeyConfig (don't pull MonsterBook etc.; v95 doesn't have it).
Tabs hidden when not applicable. E.g. skill window tab for job advance 2 hidden if the character hasn't reached 2nd-job yet.

6. Verify

dotnet build passes.
dotnet test passes.
Launch via watch.ps1 (with MAPLECLAUDE_DEBUG=1 if any position needs final tuning).
Visually compare against a reference screenshot or the IDB-derived layout table.
Confirm no privacy-token leak in committed files (pr-privacy-guard.local).

7. Memory

After a non-trivial conversion, save a memory entry summarizing what the IDB analysis revealed — what WZ paths drive what, integer constants discovered, off-by-one quirks. See existing entries for the format: [[stat-window-cuistat]], [[ingame-system-menu]], [[npc-quest-dialog]], [[skill-window-system]], [[social-community-ui]].

Privacy

Same rules as ida-lookup — no .i64 paths, no private project names, no raw decompile blocks in committed files. Translated coordinates / constants / canvas paths are fine.
pr-privacy-guard.local will fire on the eventual PR — keep its forbidden-token list in mind while writing commit messages.

Related skills / agents

ida-lookup — single-class decompile lookup; this skill calls it per CUI*.
v95-ui-rebuilder (agent) — full-screen rebuild; this skill escalates to it.
ui-origin-finder (agent) — origin extraction; this skill escalates to it.
layout-tune — for the inevitable pixel-level nudge after the rebuild lands.
wz-reader — for WZ canvas decode questions.
client-packet-author / server-packet-mirror — for any packets the window needs.

Linked memories

[[ingame-ui-windows]], [[stat-window-cuistat]], [[ingame-system-menu]], [[social-community-ui]], [[skill-window-system]], [[quest-system]], [[npc-quest-dialog]], [[ui-origin-tooling]], [[keyconfig-1to1]], [[minimap-system]], [[drops-portals-rendering]].

authentic-ui-rebuild

More from this repository

authentic-ui-rebuild

When this fires vs adjacent skills

Procedure

1. Identify the WZ subtree

2. Identify the matching CUI* class

3. Extract the layout from the IDB output

4. Implement in C#

5. Hard rules — what authentic means

6. Verify

7. Memory

Privacy

Related skills / agents

Linked memories

authentic-ui-rebuild

When this fires vs adjacent skills

Procedure

1. Identify the WZ subtree

2. Identify the matching CUI* class

3. Extract the layout from the IDB output

4. Implement in C#

5. Hard rules — what authentic means

6. Verify

7. Memory

Privacy

Related skills / agents

Linked memories

More from this repository

2. Identify the matching `CUI*` class

2. Identify the matching `CUI*` class