best-practiceslisted

# Roblox Game Development Best Practices Framework-agnostic standards for writing clean, efficient, lightweight, and resource-frugal Luau code. These rules fit any architecture — they govern *how each script is written*, not how the project is structured. **Goals, in priority order:** correct → secure (server-authoritative) → efficient (CPU/memory/network) → readable → consistent. ## Session Invariants (must survive compaction) A summary that drops these rules silently downgrades every file written afterwards. Two standing obligations: 1. **Carry it forward verbatim** in any summary, handoff, plan, or task note. It is active instruction, never compressed into "follow the Roblox skill". 2. **Re-read this file before acting** whenever the card's full text is not visible in your context. Never reconstruct these rules from memory — a half-remembered layout rule looks deliberate and is worse than none. ```text ROBLOX LUAU SKILL - INVARIANT CARD 1 Three sections, this order: -- // VARIABLES // -- Services > Modules > Objects > Configuration > State Management -- // FUNCTIONS // -- definitions only (ModuleScript: Private before Public) -- // INITIALIZATION // -- everything that runs 2 Documentation Comments (Luau Comments) - default style, adapts to the project. Default block: --[[ ]] above the function, desc > @param > @return. Moonwave --[=[ ]=] or --- is equally correct when that is the project's style. - Desc <= 3 lines and <= 250 chars, contract