roblox-project-conventionslisted

# Roblox Project Conventions ## Purpose A Roblox game is not a program with a `main`. It is a live object tree — the DataModel — in which the *container* an instance sits in determines who can see it, who can run it, and whether an exploiter can read it. Getting placement wrong is not a style issue: putting a script in `ReplicatedStorage` ships its source to every client, and putting a `LocalScript` in `Workspace` means it never runs at all. This skill establishes the two facts that gate every other Roblox task: the shape of the DataModel this project uses, and whether the project is edited as files on disk (Rojo) or only inside Studio. The second question decides whether file edits are even usable output. ## When to use - First contact with a repository that contains `.luau`, `.rbxlx`, `.rbxl` or `default.project.json`. - Deciding which container a new script, module or asset belongs in. - The task says "add a system" and you need to know where its server half, client half and shared half go. - Adding or auditing a dependency (`wally.toml`, `Packages/`). - Before invoking any other `roblox-*` skill — this one and `roblox-security` are the entry points. ## When NOT to use - Auditing trust boundaries or validating remote traffic — use `roblox-security`. - Writing typed Luau, classes or module internals — use `roblox-luau-patterns`. - Designing the remote surface between client and server — use `roblox-client-server-architecture`. - Setting up linting, tests or CI — use