mcpField
R
roblox-mobile-playtest

roblox-mobile-playtest

github.com/ashexplainedTesting & quality38118 installsUpdated 17w ago
Repository

About roblox-mobile-playtest

A skill for checking whether Roblox experiences are usable on phones and tablets. It guides a playtest through controls, HUD, readability, performance, and a structured launch-fix report.

Key features

  1. 01Studio state and play-mode checks
  2. 02Phone and tablet simulation
  3. 03Control and character movement tests
  4. 04Screen capture and console review
  5. 05Mobile usability checklist
  6. 06Structured issue report

Use cases

  1. 01Checking touch targets and thumb reach
  2. 02Finding HUD overlap on small screens
  3. 03Testing orientation and text readability
  4. 04Prioritizing fixes before launch

MCP support

The skill describes an MCP workflow using tools to inspect Studio state, start play mode, simulate devices, exercise input, capture screens, and inspect console output.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-mobile-playtest

After installing, type/roblox-mobile-playtestin Claude Code to confirm it loaded.

Details

From the project README

Roblox Mobile Playtest

Goal

Verify that the Roblox experience works and feels good for phone-first players.

Use Device Simulator

When available, invoke rbx-device-simulator-lua before device-specific UI checks. Use it to test phone and tablet form factors, orientation, and layout behavior.

MCP Workflow

  1. Confirm Studio state with get_studio_state.
  2. Start play mode with start_stop_play.
  3. Use device simulation when relevant.
  4. Exercise controls with user_mouse_input, user_keyboard_input, and direct character movement through character_navigation.
  5. Capture evidence with screen_capture.
  6. Check get_console_output.

Mobile Checks

  • First core action is reachable in 10-30 seconds.
  • Tap targets are large and spaced apart.
  • Important buttons avoid thumb conflict and system gesture zones.
  • HUD does not block movement, combat, collection, or objectives.
  • Text is readable on phone and tablet sizes.
  • Objective markers and reward feedback are visible without opening menus.
  • No keyboard-only requirement exists for core play.
  • Menus scroll cleanly and do not hide primary actions.
  • Performance remains smooth in the first playable area.

Report Format

Return:

  • Devices or simulated form factors checked.
  • First-action time.
  • Control and HUD issues.
  • Readability issues.
  • Console or performance risks.
  • Highest-impact fixes before launch.

Next

Run the full first-session pass with roblox-playtest-qa, and send any defect to roblox-debugging-bugfix.

Comments

Markdown supported