webui-tester

Test Majsoul WebUI interactions via JavaScript execution and visual debugging.

6|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/Sunalamye/Naki --skill webui-tester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webui-tester
Source: https://github.com/Sunalamye/Naki/tree/main/skills-naki/skills/webui-tester
Command: npx skills add https://github.com/Sunalamye/Naki --skill webui-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp__naki__execute_js, mcp__naki__bot_status, mcp__naki__game_state, mcp__naki__game_hand, and includes references (resource) components.

What problem does it solve?

This Skill helps test, debug, and modify Majsoul WebUI (Laya engine) running inside the Naki app. It guides you to clarify whether you mean Naki's SwiftUI app UI or Majsoul's WebUI, and provides a structured approach to WebUI JavaScript execution, tile manipulation, and visual debugging.

Core Features & Use Cases

  • Unified WebUI testing: Run JavaScript against Majsoul WebUI and inspect results via Naki's MCP tooling.
  • Tile manipulation & debugging visuals: Inspect hand tiles, highlight AI recommendations, and simulate actions.
  • NakiCoordinator guidance: Prefer the built-in NakiCoordinator for safe interactions, reducing risk of UI breakage.
  • Use Case: QA wants to verify a UI flow by executing a JS snippet to fetch game state and highlight a tile, then capture logs.

Quick Start

Run a simple check to get the current state: mcp__naki__execute_js({ code: "return naki.state.getFullState()" })

Frequently Asked Questions about webui-tester

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

FAQPage Schema
How do I test and debug Majsoul WebUI JavaScript execution inside Naki?

Testing Majsoul WebUI in Naki involves running JavaScript against the WebUI via MCP tools and inspecting results. Use mcp__naki__execute_js to execute code snippets that return state data, then verify output through Naki's bot status and game state tools to confirm UI interactions work correctly.

What's the difference between Naki App UI and Majsoul WebUI when debugging?

Naki App UI is SwiftUI—the native application interface. Majsoul WebUI is the Laya engine running inside Naki. Distinguishing between them is critical: WebUI debugging targets JavaScript execution and tile manipulation within the game engine, while app-level issues affect Naki's navigation and controls.

How do I manipulate and highlight tiles in Majsoul WebUI for testing?

Tile manipulation and debugging in Majsoul WebUI requires inspecting hand tiles via mcp__naki__game_hand, then executing JavaScript to highlight AI recommendations or simulate player actions. Verify results through visual inspection and game state queries using NakiCoordinator for safe, coordinated interactions.

Can I use NakiCoordinator to safely execute WebUI interactions without breaking the UI?

Yes, NakiCoordinator is the preferred method for safe WebUI interactions. It reduces UI breakage risk by coordinating JavaScript execution with game state checks and MCP tool results, ensuring operations complete successfully before proceeding to dependent tasks.

What MCP tools do I need for WebUI testing in Naki?

WebUI testing requires four core MCP tools: mcp__naki__execute_js for running JavaScript, mcp__naki__bot_status for bot state verification, mcp__naki__game_state for full game context, and mcp__naki__game_hand for tile inspection. All must return valid results before confirming UI changes.

Why do I need to verify return statements when executing JavaScript in WebUI?

Return statements are mandatory for safe JavaScript execution in WebUI. They ensure executed code produces verifiable output that Naki's MCP tools can capture and validate, preventing silent failures and confirming that UI state changes actually occurred as intended.