Loading...
Loading...
Found 15 Skills
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.
This skill should be used when the user asks to "execute Lua code in Roblox Studio", "run code in Studio", "test Lua script", "connect to Studio Hub", "manage Studio instances", "check Studio status", "install Studio Hub", "setup Studio Hub service", or mentions Roblox Studio remote execution, Studio Hub API, or Lua code testing.
Official Roblox Studio MCP server tools reference. What each tool does, how to use it, reliability patterns, and workflows for script editing, building, playtesting, and debugging. Use when the AI has an MCP connection to Roblox Studio.
Drive Roblox Studio from an AI agent via the built-in Studio MCP server - connecting Claude Code, Codex, Cursor, OpenCode, Gemini CLI; tools to explore the DataModel, read/edit scripts, run Luau in edit/server/client, playtest, read output, capture screenshots, simulate input, insert assets. Use when an agent should inspect, modify, or playtest an open Studio place, or to set up the connection.
Use Roblox Studio MCP safely and productively from Claude. Use when connecting to Studio, inspecting a Roblox place, editing scripts or instances, inserting assets, generating models/materials, or playtesting through MCP tools.
Build, inspect, repair, validate, and playtest Roblox Studio maps and Luau through the local bridge. Use for SceneSpecs, terrain, Studio edits, gameplay objects, visual checks, and Rojo output.
Use for foundational Roblox experience development: deciding what runs on the client or server, where scripts and modules belong, how to structure reusable code, and how to handle everyday services, attributes, bindables, workspace objects, input, camera, raycasts, collisions, and CFrame-based gameplay scripting in Studio.
World-class Roblox game development - Lua scripting, Roblox Studio, game systems, monetization, and building experiences that millions play. Use when "roblox, roblox studio, lua scripting, roblox game, obby, simulator game, roblox experience, robux, devex, " mentioned.
Build maps, areas, zones, and large-scale environments in Roblox Studio via MCP. Use when: user asks to create a map, battle arena, lobby, hub, town, village, open area, game world, level design, or any environment that spans multiple zones or regions. Triggers on: "マップを作って", "エリアを作って", "フィールドを作りたい", "build a map", "create an arena", "make a lobby", "design a level", "make a hub world", "create a town", or any request involving spatial layout, zone planning, or multi-area environments. Scope boundary: applies to multi-zone layouts. For a single object, prop, or room interior → use building-3d-objects instead.
Build 3D objects, props, and room-scale structures in Roblox Studio via MCP. Use when: user asks to create, build, or place a single physical object — furniture, animals, vehicles, gates, towers, decorations, street props, room interiors, or any individual tangible structure. Triggers on: "○○を作って", "○○を置いて", "build me a ___", "create a ___", "make a ___" in the context of Roblox Studio. Also use when user mentions CSG, Union, Subtract, Part placement, or 3D modeling in Roblox. If the user is in a Roblox project and asks to "make" or "build" something physical, this skill should trigger even without explicit mention of "3D" or "Roblox". Scope boundary: applies if the result can be grouped into a single `Model`. For full maps, arenas, lobbies, hubs, or multi-zone environments → use building-maps instead. Dispatch rule: When the user requests multiple related/variant objects (e.g., "5 types of swords", "3 chair styles"), dispatch ALL variants to a SINGLE agent. Do NOT spawn parallel agents. Consistency requires sequential building by one agent.
Use when making or fixing Roblox visual effects or game audio: ParticleEmitter, Beam, Trail, flipbook sprite sheets, slash, hit, impact, explosion, fireball, aura or projectile VFX; effects only one player sees, effects that lag or pile up, particles invisible, popping or too bright; the Audio API (AudioPlayer, Wire, AudioEmitter, AudioListener, AudioDeviceOutput, effects), "no sound", "3D sound not working", music, ducking, footsteps, SoundGroup volumes; or importing Scenario-generated sound effects, music, voice or VFX sheets into a Roblox game.
Set up the free Roblox game-creation skills on THIS machine - check which tools are installed (Python, Rojo, Wally, Lune, Selene, StyLua, Blender, the Roblox Studio MCP), walk the user through anything missing, then write each skill's personal LOCAL.md (folders, tool paths, rig file, VFX library location, env var names for keys) by asking the user and auto-detecting what it can, and finish with a smoke test. Use this the first time after installing the skills, whenever a skill says "LOCAL.md not found", when the user moves folders or installs a new tool, or when they ask "how do I set these skills up", "what do I need installed", or "why can't the skill find Blender/Rojo/my library".