← ClaudeAtlas

studio-opslisted

Operating a Roblox project's tooling safely: Studio MCP connections, filesystem sync with Rojo, Argon, Script Sync, or Azul, and proving a change actually works in the running engine. Use when the user asks why their edits are being overwritten, how to set up or diagnose a sync toolchain, what a Studio MCP tool will do before it runs, how to playtest or verify a fix, or how to test replication and multi-client behaviour. Governs how the agent drives its tools, not how Luau is written. Not for authoring Luau — that is the best-practices skill; not for judging code that already exists — that is the code-review skill; not for working out why a reported symptom happens — that is the diagnose skill, which calls on this one to run the probe.
andrian-syh/roblox-optimum · ★ 1 · AI & Automation · score 77
Install: claude install-skill andrian-syh/roblox-optimum
# Roblox Studio Operations Driving the tooling around a Roblox project without destroying the user's work. Nothing here writes game code or judges it; this is about which side owns the file, what a tool call will actually do, and how a change is proven to work. **Goal, in priority order:** do not destroy work → know before acting → prove it → spend few tokens. ## Session Invariants (must survive compaction) ```text ROBLOX STUDIO OPS - INVARIANT CARD 1 Detect the environment before touching anything: Studio-native, or a filesystem project synced by Rojo, Argon, Script Sync, or Azul. 2 WHICH SIDE IS THE SOURCE OF TRUTH DIFFERS PER TOOL. Assuming wrong overwrites the user's work and there is no undo. Confirm, never infer. 3 Never start, stop, or reconfigure a sync session unasked. 4 On an MCP connection, run the preflight before ANY write, and name an irreversible operation as irreversible before performing it. 5 A change is not verified by reading it. Drive the affected flow in a running session and observe the result. 6 Replication, remotes, and StreamingEnabled need multiple clients. A single-Play session hides every networking bug. 7 Leave no residue: test scripts, tags, and instances created to verify are removed when done. 8 User authority outranks this skill. ``` Everything below expands these; nothing below overrides them. ## Which situation is this | The request is about | Read | |---|---| | Edits overwritten, sync setup, which side wi