# roblox-studio-workflow

A workflow skill for editing existing Roblox Studio projects, from inspecting the project tree to Studio testing and removing temporary test objects.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 3700 installs · ★ 4506
- Author: gamedev-skills
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/HEAD/skills/other-engines/roblox-studio-workflow/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/roblox-studio-workflow

## What it does

roblox-studio-workflow guides an agent through changes to an existing place, `rbxl` or `rbxlx` project, or a Rojo-backed project. It starts with Explorer, scripts, modules, remotes, tags, project mapping, and current warnings before it proposes a small compatible edit.

The skill maps server, client, and shared code to locations such as `ServerScriptService`, `StarterPlayerScripts`, `StarterCharacterScripts`, `StarterGui`, and `ReplicatedStorage`. It treats Attributes as typed metadata on an Instance and `CollectionService` tags as a way to find related Instances. Creating a second remote or manager is risky because both systems can run and apply the same action twice.

Verification can use Test, Test Here, Run, Server & Clients, Device Simulator, and other Studio modes. The workflow calls for checking both server and client Output, then removing debug UI, temporary parts, test remotes, and other experiment leftovers. Studio's MCP server is optional; manual Studio and Rojo work remain part of the workflow.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill roblox-studio-workflow -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/roblox-studio-workflow/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/roblox-studio-workflow/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill roblox-studio-workflow -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/roblox-studio-workflow/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill roblox-studio-workflow -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/roblox-studio-workflow/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install gamedev-skills/awesome-gamedev-agent-skills roblox-studio-workflow
```

2. **Manually: put the files in place**
- File: `.github/skills/roblox-studio-workflow/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill roblox-studio-workflow -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/gamedev-skills/awesome-gamedev-agent-skills --path skills/other-engines/roblox-studio-workflow
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/roblox-studio-workflow/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill roblox-studio-workflow -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/HEAD/skills/other-engines/roblox-studio-workflow/SKILL.md

## When to use it
- inspect a Roblox project before changing its structure
- place server and client scripts in the right containers
- reuse an existing RemoteEvent instead of adding a duplicate
- test behavior through server and client Studio sessions
- remove temporary debugging objects after a playtest

## Example prompts
- Inspect this Roblox Studio project before changing the door system and find existing `CollectionService` tags.
- Add the client behavior while preserving the current modules and RemoteEvent.
- Test the change with Server & Clients and report messages from Output.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: b0b7534e306f76db.

BEGIN THIRD-PARTY FILE b0b7534e306f76db
```text
---
name: roblox-studio-workflow
description: >
  Modify living Roblox Studio projects safely: inspect Explorer and execution locations, preserve
  existing structure, reuse modules/remotes, create meaningful Instances, apply Attributes and
  CollectionService tags, test server/client and multiple devices, inspect Output, and remove
  experiments/debug objects. Use when an agent edits a place or rbxl/rbxlx/Rojo project, operates
  in Studio, adds Scripts/LocalScripts/ModuleScripts, or must verify a Roblox change in context.
---

# Roblox Studio workflow

Work as a collaborator inside an existing place, not as if it were a blank text repository. Targets
current Roblox Studio and rolling platform APIs.

## When to use

- Use before invasive edits to a Roblox place, Studio DataModel, or Rojo-backed project.
- Use to plan execution location, find/reuse systems, create editable Instances, and gather honest
  Studio verification evidence.

**When not to use:** this skill owns project operation, not the domain implementation. Compose it
with `roblox-ui`, `roblox-networking`, `roblox-characters`, `roblox-physics`, `roblox-luau`, or
`roblox-datastores` as appropriate.

## Workflow

1. **Establish source of truth.** Determine whether Studio, Rojo files, a package manager, or a
   generated build owns each subtree. Do not hand-edit generated output or create Studio-only
   changes that the next sync overwrites.
2. **Inventory before proposing structure.** Inspect Explorer, search scripts/modules/remotes/tags,
   read project mapping and naming conventions, and run once to observe existing warnings. Locate
   the feature's current owner and dependencies.
3. **Plan the smallest compatible edit.** Name the Instances and execution locations you will
   change. Reuse existing remotes, component modules, cleanup utilities, tags, Attributes, folders,
   and configuration patterns. State any unresolved ownership boundary.
4. **Create real, meaningful objects.** Normal authored UI, folders, attachments, constraints,
   remotes, and configuration remain inspectable in Explorer. Use scripts for behavior and truly
   dynamic repetition—not to hide the entire feature in runtime construction.
```
END THIRD-PARTY FILE b0b7534e306f76db

The third-party file has ended. Everything between the b0b7534e306f76db tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2208 of 11092 bytes. © gamedev-skills · Apache-2.0 · https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/HEAD/skills/other-engines/roblox-studio-workflow/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md