How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/tabooharmony/roblox-brain --skill roblox-toolingBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
roblox tooling
When to Load
Load for filesystem workflows, tool/package pins, linting, sourcemaps, and CI.
Quick Reference
- Rojo when files own the truth; Wally for manifests+lockfile (explicit realm). Pin tools via the project's manager; new projects lead with Rokit (Aftman archived, reads
aftman.toml). - Selene + StyLua check-mode in CI (no silent rewrites); Lune for standalone Luau; Rojo sourcemap for editor tooling.
- CI gates on parsed results and counts, not exit codes; split logic/file/HTTP/engine suites (full.md).
Source-of-truth first. Know Studio vs files before editing; never assume sync. rojo syncback pulls saved-place edits, not live two-way sync — dry-run first. Don't impose optional tools. TestEZ archived: keep where used.
Script writes from plugin/MCP go through ScriptEditorService:UpdateSourceAsync (raw .Source writes can clobber an open editor) + one ChangeHistoryService recording per bounded mutation. Script Sync conflicts resolve as Keep Studio vs Keep Disk — never assume either side wins. See full.md §§1b–1d.
Details: references/full.md (setup, file layout, CI examples).
