The Roblox Game Skill is a self-contained Claude Code skill that brings full-lifecycle Roblox game development into your AI-assisted workflow. Whether you’re a first-time creator who wants to ship a pet simulator over a weekend or a studio engineer hardening a live game against exploits, the skill meets you where you are — with deep Luau expertise, production-ready genre templates, autonomous MCP Studio integration, and step-by-step guided workflows covering everything from initial scaffold to pre-launch checklist.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/brockmartin/roblox-game-skill/llms.txt
Use this file to discover all available pages before exploring further.
Architecture
The skill is built on a Router + Reference Library pattern. A lightweight 121-lineSKILL.md dispatcher sits at the top level and handles every incoming request. When you describe your intent, the router matches it against 19 routing paths and lazily loads only the reference files, templates, and workflows that are actually relevant — keeping responses focused and context lean.
The Three Pillars
References
16 deep-dive files covering Luau mastery, architecture patterns, security hardening, DataStore persistence, performance optimization, monetization systems, multiplayer networking, and more.
Templates
7 genre templates — Simulator, Tycoon, Obby, RPG, Horror, and Battle Royale — each containing complete, production-ready Luau code for every core system in that genre.
Workflows
7 guided workflows that walk you through building a game from scratch, debugging iteratively, auditing performance or security, reviewing monetization, and preparing for launch.
MCP Studio Integration
MCP Overview
Connect Roblox Studio directly to Claude Code via the community MCP server (39 tools) or the official Roblox MCP server (6 tools) for live code execution, file-tree browsing, and autonomous building — or run fully offline with copy-paste-ready scripts.
Routing Table
When you send a message, the skill scans your intent and loads only what is needed. Here are the 19 routing paths with example prompts:| User Intent | Example Prompt | Files Loaded |
|---|---|---|
| Build a game | ”Build me a pet simulator with 3 zones” | workflows/new-game.md + templates/genre-simulator.md + templates/game-scaffold.md |
| Fix a bug | ”Why is my leaderboard not updating?” | workflows/debug-loop.md + references/mcp-orchestration.md |
| Save/load data | ”How do I save player inventory?” | references/datastore-persistence.md |
| Combat system | ”Add a sword combat system” | references/combat-systems.md + references/security-hardening.md |
| Shop / monetization | ”Add a GamePass shop” | references/monetization-systems.md + references/gui-systems.md |
| Optimize performance | ”My game drops to 20 FPS with 30 players” | workflows/performance-audit.md + references/performance-optimization.md |
| Security review | ”Review my RemoteEvents for exploits” | workflows/security-audit.md + references/security-hardening.md |
| General Luau question | ”How do metatables work in Luau?” | references/luau-mastery.md |
| Ready to publish | ”Is my game ready to launch?” | workflows/publish-checklist.md |
| Review monetization | ”How can I improve my game’s revenue?” | workflows/monetization-audit.md |
| Multiplayer / networking | ”How do I sync state across clients?” | references/multiplayer-networking.md |
| Animation / VFX | ”Add particle effects to my ability” | references/animation-vfx.md |
| Testing | ”How do I write unit tests for my modules?” | references/testing-patterns.md |
| Inventory / items | ”Build a drag-and-drop inventory” | references/inventory-systems.md |
| GUI / UI | ”Create an animated shop screen” | references/gui-systems.md |
| Game design | ”How do I design a good progression system?” | references/game-design-roblox.md |
| Tooling / Rojo | ”Set up Rojo with VSCode” | references/tooling-ecosystem.md |
| Sharp edges | ”What are the most common Roblox gotchas?” | references/sharp-edges.md |
| Review code quality | ”Grade my codebase” | workflows/code-review.md |
Service Hierarchy
Every Roblox game is organized around a set of core services. Understanding what belongs where is fundamental to building a correct, secure architecture:| Service | Purpose |
|---|---|
| ServerScriptService | Server-only logic — game state, data management, anti-cheat. Never accessible to the client. |
| ReplicatedStorage | Shared ModuleScripts, RemoteEvents, and assets that both the server and client need. |
| StarterPlayerScripts | Client-side controllers — input handling, camera, UI logic. Cloned into each player on join. |
| StarterGui | UI ScreenGuis. Cloned into PlayerGui on spawn; drives all in-game interfaces. |
| ServerStorage | Server-only assets — maps, tools, and models to clone on demand. Invisible to clients. |
| Workspace | The live 3D world. Keep it lean; avoid storing data or logic here. |
Script Types
Roblox has three script types, and using the wrong one in the wrong place is one of the most common sources of bugs and security holes:| Type | Runs On | Use For |
|---|---|---|
Script | Server | Game logic, authoritative data, physics authority |
LocalScript | Client | Input handling, camera control, UI, local visual effects |
ModuleScript | Either (requires caller’s context) | Shared code, config tables, utility functions |
A
ModuleScript required from a Script runs on the server; required from a LocalScript it runs on the client. The same module file can behave differently depending on who requires it — use this intentionally and document it clearly.