roblox tooling
When to Load
Load for filesystem workflows, tool/package pins, linting, sourcemaps, and CI.
Quick Reference
- Use Rojo when the source of truth should live in files and sync or build into Studio.
- Use Wally only when the project wants package manifests and a lockfile; keep package scope and server/client placement explicit.
- Pin tools with the project's existing manager; for a new project lead with Rokit (Aftman is archived, but Rokit reads existing
aftman.tomlprojects). - Run Selene and StyLua in check mode in CI. Do not let a formatter rewrite a contributor's branch silently.
- Use Lune for standalone Luau scripts or test helpers when its standard libraries fit the task.
- Generate a Rojo sourcemap for editor tooling when the project needs Roblox-aware navigation.
- CI must check test results and expected counts, not merely exit codes. Separate logic, file/HTTP, and engine suites; see full.md.
Source-of-truth first. Identify Studio vs files before editing; never assume they match. rojo syncback pulls saved-place edits, not live two-way sync; preview with dry-run/list. Follow existing tooling; do not impose optional tools. TestEZ is archived: keep where used, not as a new default. See full.md §§1b–1c.
Need the details? Load references/full.md for setup, file layout, and CI examples.
