chocoliticekreem
@chocoliticekreem
Public Skills
mubit-tester
by chocoliticekreem
Use when checking that a Roblox game change actually works in play, reproducing a gameplay bug, testing multiplayer, co-op or squad behaviour (lobby, pads, countdown, parallel mission instances, friendly fire, revive, hose tether), or running playtests/scenarios against Roblox Studio with the mubit-tester MCP tools.
forge
by chocoliticekreem
Use when driving the forge MCP tools (build_game, improve_game, done, correct, tester_report, versions, rollback, jobs) on Forge-made Roblox games, or checking how Forge's self-improving loop (auditor, fixer, verifier, Mubit training) is doing.
building-games-with-forge
by chocoliticekreem
Use when the user wants a new Roblox game made from an idea ("make me a co-op lava escape", "build a tycoon with Forge"), especially when they will be away while it builds.
improving-games-until-done
by chocoliticekreem
Use when an existing Forge game (runs/<slug>) should keep improving until it is ready ("keep improving until forge done is green", "the tycoon is scuffed, fix it", "make it good"), or when deciding whether a Forge game is finished.
forge-autopilot
by chocoliticekreem
Use when the user wants Forge to take a game from an idea to ready on its own, to keep improving a game driven by its logs and playtest evidence, to find anomalies (error spikes, counters that never move, regressions, stuck testers, features nobody uses), to get a read-only improvement report on the human-built main game, or to correct an autopilot decision. Drives forge autopilot (or the forge MCP tool autopilot).
forge-orchestrate
by chocoliticekreem
Use when the user wants Forge to make an existing game much better on its own (for example "make the tycoon 10x better"), to find what a game is missing or what is broken, to queue several Forge jobs that share Studio windows, or to correct the gap list Forge produced. Drives forge orchestrate, forge gaps and forge queue (or the forge MCP tools orchestrate, gaps and orchestrator).
testing-roblox-features
by chocoliticekreem
Use when asked to check, verify or prove that a Roblox gameplay change or feature works in Studio ("does the hydrant refill work now?", "check my change", "test X before the demo"), or before saying a game change is done.
swarm-testing
by chocoliticekreem
Use when many testers should hit a Roblox game at once ("throw 10 testers at it", "stress the lobby", "parallel AI testers", load or concurrency bugs in squads, pads, countdowns or mission instances).
triaging-tester-reports
by chocoliticekreem
Use when a playtester, teammate or AI tester report describes bugs in a Roblox game in loose words ("hose sometimes doesn't spray", "my buddy got blamed", "horn too quiet") and has to become fixes, or when a test_feature/playtest/swarm report lists several bugs.
training-mubit-from-corrections
by chocoliticekreem
Use when an AI playtester, Forge role (fixer, auditor, critic, triage) or AI player made a wrong call and the user wants Mubit to learn from it ("make it learn", "correct the AI", "this should be a training example"), or when preparing the demo's correction → model update moment.
roblox-studio-dev
by chocoliticekreem
Use when writing, changing, debugging or playtesting Luau game code in this repo (game/ or runs/<slug>/game), when Roblox Studio or mcp__Roblox_Studio__* tools are involved, or when a change has to be checked inside a running Roblox game.