About roblox-tooling
roblox-tooling is a development skill for Roblox filesystem workflows, tool versioning, linting, sourcemaps, and CI. It emphasizes identifying whether Studio or files are the source of truth before making changes.
Key features
- 01Rojo and Wally project workflows
- 02Tool version pinning guidance
- 03Selene and StyLua CI checks
- 04Lune and Rojo sourcemaps
- 05CI result parsing and suite separation
- 06Safe script source updates
Use cases
- 01Setting up Roblox project files and dependencies
- 02Adding lint and test gates to CI
- 03Resolving Studio and disk sync conflicts
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/roblox-toolingin Claude Code to confirm it loaded.
Bundled filesreferences/full.md
Details
From the project READMEroblox 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).