scadavide55

Roblox Studio Claude Skill — Development skill for Claude Code

Development community

Claude Code skill for operating a live Roblox Studio session via the Studio MCP server.

How to install Roblox Studio Claude Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open scadavide55/roblox-studio-claude-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Roblox Studio Claude Skill does

Claude Code skill for operating a live Roblox Studio session via the Studio MCP server. Claude inspects before editing, verifies after, asks before destructive changes, and playtests what it builds. Includes Luau standards, system recipes, a debugging checklist, and test cases. Unofficial, MIT licensed.

Alternatives in Development

Rb Refresh — Rebuild the repobrain project knowledge base after significant changes 1.3k ★
Ag Refresh — Rebuild the antigravity project knowledge base after significant changes 1.2k ★
Compiletex — Compile LaTeX and report errors/warnings 446 ★

README

roblox-studio-claude-skill

A [Claude Code](https://claude.com/claude-code) skill that makes Claude a careful operator of a **live Roblox Studio** session through Roblox's built-in Studio MCP server. You describe what you want in plain language ("add four collectable coins around the spawn with a counter in the top left"), and Claude builds, scripts, debugs, and playtests it in your place.

Invoke it with `/roblox-studio`, or just ask for Roblox work and let Claude pick it up.

Unofficial. Not affiliated with or endorsed by Roblox Corporation or Anthropic.

What it does

The skill is a single `SKILL.md` that teaches Claude a disciplined workflow for editing a real place:

Bootstrap. Finds the open Studio instance (list_roblox_studios), checks whether a playtest is running, and detects whether your scripts are synced from disk with Rojo or Roblox's Script Sync, in which case it edits the files instead of overwriting them from Studio.
Inspect, change, verify. Reads before editing, makes the smallest change, then reads it back, runs a state check, and checks the console. It does not call something done because it wrote it.
Edit vs. playtest. Knows that changes made during a playtest are discarded, and that new scripts should be created with the right class first, because multi_edit creates a script from a mistyped path.
Undoable changes. Tries to record each change in Studio's undo history so you can Ctrl+Z it as one step, and says so when it can't.
Ask first. Pauses before deleting things, touching DataStore data, changing monetization or publish settings, large restructures, or inserting third-party assets with scripts. Everything else it just does and tells you what it chose.
Luau standards. Server-authoritative design, where each script type belongs, remote validation, safe DataStore handling, task library, --!strict, and the platform gotchas that cause most "it does nothing" bugs.
Recipes. Tested-sha