Roblox — Run and Operate (house stack)

Overview

This skill maps every way code and assets leave your editor and land in Roblox on the firebit house stack: the local dev loop, Studio automation, GitHub CI/CD, and the two ID-minting CLIs (rblxsync, asphalt). The core principle: local builds and dry-runs are always safe; anything that touches origin main/production or runs a live sync publishes to a real Roblox universe (canonical rules in roblox-change-control).

All commands run from the current project's repo root unless stated otherwise. Every project on this stack shares the same skeleton (Rojo + Wally + npm scripts + boilerplate workflows), but names, IDs, and script lists vary per project — verify against the current repo before quoting them.

When to use / When NOT to use

Use when you need to run the game, build a place file, drive Roblox Studio, understand CI, or operate rblxsync/asphalt.

Do NOT use for:

• Bootstrap, npm script internals, sourcemap traps, wally → roblox-build-and-env
• Test/playtest/storybook mechanics and evidence standards → roblox-validation-and-qa (and plugin commands /roblox-testing:test, /roblox-testing:playtest)
• The four hard rules' canonical statement and change gates → roblox-change-control
• Adding a new config axis or flag → roblox-config-and-flags
• Runtime debugging in a running game → skill roblox-debugging
• General Rojo/rblxsync theory → global skills rojo-pro, rblxsync