NEXPACE-Limited

balance-tuning

Reviews and tunes game balance across difficulty and progression curves, session pacing, option or strategy trade-offs, and reward economies. Use when players report that a game is too hard, easy, short, long, or grindy; a weapon, upgrade, or strategy dominates; damage, health, spawn, drop, price, or progression values need tuning; or a requested pre-release balance pass has not been validated. Establishes the target experience, measures the relevant model, and reports or applies specific number changes with before-and-after evidence.

cross-device-check

Audits a game's UI and interaction across supported viewports, aspect ratios, pixel densities, orientations, and input capabilities. Use when mobile, tablet, desktop, controller, keyboard, pointer, or touch support is being checked; UI clips, overlaps, blurs, or overflows; controls are unreachable or hard to use; resizing or orientation changes break layout; or an explicit pre-release device-coverage pass is requested. Reproduces each issue on the relevant target and reports severity, evidence, exact trigger conditions, and fixes while distinguishing observed from source-inferred findings.

debug-visualization

Use when creating any game or interactive toy, when adding gameplay/UI features to one, when the builder asks for value tweaks in any language (too fast/slow, too big/small, a bit more/less, move it left/right/up/down, can't hit it, my tap doesn't register, hitbox, feels floaty/heavy/off, easier/harder, change X from N to M, 'don't rebuild — just fix this'; 너무 빨라요/느려요, 버튼이 안 눌려요, 판정이 이상해요, 히트박스, 이것만 고쳐줘), or when a message contains a [TUNING] or [ERRORS] block. Once loaded, stays in force for every subsequent message in the session without being re-mentioned. Ships a live in-game tuning panel with every game so builders adjust values themselves instead of burning chat round-trips.

determinism-audit

Audits nondeterministic game behavior and flaky execution. Use when the same initial state and inputs produce different outcomes, a test fails intermittently or only under load, behavior differs by frame rate or machine, a replay diverges, or lockstep peers desynchronize. Establishes the required determinism boundary, reproduces and measures variance, isolates randomness, timing, async or thread ordering, state leakage, unordered iteration, and numeric drift, then reports verified causes and implements and stress-tests fixes only when requested.

game-tutorial

Audits, adds, or reworks a game's first-time-player tutorial. Use when players cannot identify the controls, goal, failure conditions, or a non-obvious rule; new players quit before completing the core loop; onboarding presents too much at once; or an explicit tutorial or first-run improvement is requested. Separates first-action essentials from later guidance, prefers in-flow or staged first-run teaching, provides a skippable fallback and reusable help, and verifies behavior from clean, completed, and skipped states.

i18n-setup

Sets up or repairs localization for a game: player-facing string extraction, locale catalogs, draft target-locale translations, fallback and locale selection, runtime switching, plural and parameter formatting, glyph coverage, and translation-safe layouts. Use when the user requests another locale or localization-ready architecture; existing translations, fallback, pluralization, locale detection, or switching are broken; or translated text overflows or renders missing glyphs. Follows the project's engine and existing localization system and marks generated translations for human review.

maple-make

Use when working with MapleStory assets — how to look up, compose, and render characters, mobs, maps, skills, items, or sprites via maple-lookup MCP.