ashexplained/roblox-skills

roblox-mobile-playtest

Playtest and QA Roblox experiences for mobile and tablet.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-mobile-playtest

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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.

同じリポジトリから

関連する Skills

すべての Skills
ashexplained
コミュニティ

roblox-playtest-qa

Playtest Roblox experiences through Studio MCP with attention to first-session fun, mobile UX, console errors, progression, social hooks, performance, and exploit-sensitive flows.

1時間の導入数
4
GitHub Stars
63
更新日
7月1日
ashexplained
コミュニティ

roblox-animation-audio-feedback

Improve Roblox feel through animation, audio, VFX, haptics-like feedback, reward juice, movement feel, combat feedback, UI transitions, emotes, and satisfying loop feedback without hurting mobile performance.

1時間の導入数
3
GitHub Stars
63
更新日
7月1日
ashexplained
コミュニティ

roblox-combat-systems

Design, implement, and review Roblox combat systems. Use for melee, ranged, abilities, cooldowns, hit detection, damage validation, status effects, enemy AI hooks, combat UI, balance knobs, VFX/SFX, and exploit-resistant remotes.

1時間の導入数
3
GitHub Stars
63
更新日
7月1日
ashexplained
コミュニティ

roblox-creator-store-security-audit

Audit Roblox Creator Store, Toolbox, inventory, group, universe, package, model, UI, gameplay, plugin-like, and other third-party imported assets for malicious or risky scripts. Use whenever Claude imports, inserts, reviews, or trusts Creator Store assets, especially assets with Scripts, LocalScripts, ModuleScripts, hidden descendants, require calls, HTTP, DataStore, remote creation, obfuscated code, or suspicious names.

1時間の導入数
3
GitHub Stars
63
更新日
7月1日