ashexplained/roblox-skills

roblox-performance-optimization

Analyze and optimize Roblox scene and script performance.

ソースを見る

使い方

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

開始前の確認

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

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

Roblox Performance Optimization

Goal

Keep the experience smooth on lower-end phones. Favor measurable fixes over visual guesses.

Use The Scene Analysis Skill

When available, invoke rbx-scene-analysis before deep performance work. Use it to inspect rendering, memory, instance composition, unparented instances, and animation or audio asset usage.

MCP Workflow

  1. Confirm Studio state with get_studio_state.
  2. Use search_game_tree and inspect_instance to identify heavy hierarchies.
  3. Use execute_luau for targeted counts, tag scans, memory snapshots, or property audits.
  4. Use screen_capture to preserve before/after visuals.
  5. Playtest with start_stop_play and check get_console_output.

Optimization Targets

  • Instance count and deeply nested hierarchies.
  • Unanchored parts causing physics cost.
  • Excessive constraints, touched events, or per-frame loops.
  • Large textures, too many unique materials, and high-poly meshes.
  • Particle emitters with high rate/lifetime combinations.
  • Dynamic lights, shadows, post-processing, and expensive transparency.
  • Scripts that connect events repeatedly or leave stale connections.
  • Workspace content that should stream or load later.

Mobile Budget Habits

  • Build the first area to be visually strong but technically cheap.
  • Prefer fewer meaningful effects over many constant effects.
  • Use Level of Detail thinking for distant props.
  • Keep UI lightweight and avoid per-frame layout work.
  • Test phones and tablet-like viewport sizes, not only desktop Studio.

Report Format

Return:

  • Biggest performance risks.
  • Evidence from scene analysis, instance inspection, console output, or captures.
  • Fixes ranked by likely player impact.
  • Verification steps and any tradeoffs.

Next

Confirm the gains on-device with roblox-mobile-playtest, and re-run roblox-playtest-qa to make sure nothing regressed.

同じリポジトリから

関連する 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日