ashexplained/roblox-skills

roblox-mobile-playtest

Playtest and QA Roblox experiences for mobile and tablet.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-mobile-playtest

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

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.

du même dépôt

Autres Skills

Tous les Skills
ashexplained
Communauté

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.

Installations / 1h
4
GitHub Stars
63
Mis à jour
1 juil.
ashexplained
Communauté

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.

Installations / 1h
3
GitHub Stars
63
Mis à jour
1 juil.
ashexplained
Communauté

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.

Installations / 1h
3
GitHub Stars
63
Mis à jour
1 juil.
ashexplained
Communauté

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.

Installations / 1h
3
GitHub Stars
63
Mis à jour
1 juil.