ashexplained/roblox-skills

roblox-luau-architecture

Design, inspect, and refactor Roblox Luau game architecture.

ソースを見る

使い方

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

開始前の確認

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

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

Roblox Luau Architecture

Goal

Keep Roblox game code modular, server-authoritative, and easy to extend. Use Roblox Studio MCP to inspect existing scripts before changing architecture.

MCP Workflow

  1. Start with list_roblox_studios, set_active_studio if needed, and get_studio_state.
  2. Locate code with script_search or script_grep.
  3. Read relevant scripts with script_read before editing.
  4. Apply edits with multi_edit.
  5. Playtest with start_stop_play.
  6. Check get_console_output for regressions.

Placement Rules

  • Put authoritative game logic in ServerScriptService or server-owned modules.
  • Put shared constants, type definitions, remotes, and pure shared helpers in ReplicatedStorage.
  • Put player input, camera, local-only UI, and visual prediction in client scripts.
  • Keep workspace scripts rare and intentional; prefer service-style scripts that manage tagged instances or configured folders.
  • Avoid scattering duplicated constants across client and server.

Remote Boundaries

  • Treat every client remote payload as untrusted.
  • Prefer narrow remotes with explicit action names and typed payload checks.
  • Rate-limit player-triggered remotes that can affect economy, inventory, combat, or placement.
  • Use RemoteFunctions sparingly; avoid long-yielding server calls from the client.
  • Never let the client decide currency, inventory, ownership, damage, quest completion, or purchase grants.

Module Pattern

Use modules for:

  • Services with Init and Start style lifecycle.
  • Data access wrappers.
  • Economy calculations.
  • Reward tables and balancing constants.
  • UI controllers on the client.
  • Shared utility functions that are deterministic and side-effect-light.

Keep modules small enough that another system can depend on them without importing unrelated behavior.

Prefer Deep Modules

Aim for deep modules: a lot of behavior behind a small, stable interface. A shallow module — where the interface is nearly as complex as its implementation — earns its keep only if it hides real complexity.

  • Interface = everything a caller must know: the function signature plus invariants, ordering, error modes, and which side (client/server) may call it. In Roblox, a remote's contract is part of its interface.
  • Deletion test: imagine deleting a module. If complexity vanishes, it was a pass-through — inline it. If the same complexity reappears across several call sites, it was earning its keep — keep it and deepen it.
  • Locality: put related behavior and its valuable-state rules in one module so a change, a bug, or the knowledge to reason about it lives in one place — not scattered across a LocalScript, a server Script, and three constants files.
  • One adapter satisfying an interface is a hypothetical seam; two is a real one. Don't build indirection for a single implementation.

Good seams get names from the game's own vocabulary (the "coin economy service", the "quest tracker"), not generic ones ("Handler", "Manager").

Refactor Output

When proposing or making architecture changes, include:

  • Current script locations and responsibilities.
  • Proposed module/service boundaries.
  • Remote contract changes.
  • Migration steps.
  • Playtest and console checks.

Next

Slice the architecture work with roblox-to-issues so it lands one safe change at a time, and verify each with roblox-playtest-qa. For valuable-state modules, review the trust boundary with roblox-security-economy; for cleanup of existing debt, use roblox-code-maintenance-refactor.

同じリポジトリから

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