con un clic
help
Guide on using Roblox Creator Skills
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Guide on using Roblox Creator Skills
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Compatibility visual-delivery runtime for Roblox creator UI, HUD, and plugin work; the canonical completion owner is now Forge.
Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs grounded cross-file explanation before any changes are proposed.
Persistent Roblox Studio execution loop that carries an approved creator plan to verified completion
Run an anti-slop cleanup/refactor/deslop workflow
Ask Claude via local CLI and capture a reusable artifact
Ask Gemini via local CLI and capture a reusable artifact
| name | help |
| description | Guide on using Roblox Creator Skills |
| surface-class | operator |
| domain | creator-runtime |
| audience | operator |
| artifact-type | skill |
RCS uses creator-facing workflow triggers as the primary public surface:
$brief for request, audience, and goal clarification$blueprint for structured design and planning artifacts$forge for concrete creator-facing deliverables and specs$crew for coordinated multi-role creator workflows$autoforge for end-to-end creator workflow execution$brief:audience$brief:motivation$blueprint:psych$blueprint:loop$blueprint:retention$blueprint:social$forge:reward-loop$forge:daily-loop$forge:event-loop$forge:progression$forge:status$forge:fomo$forge:mastery$forge:community$brief "farming simulator for mobile-first Roblox sessions"
$brief:audience "who is this for and why do they return?"
$brief:motivation "rank progression, status, FOMO, mastery, and community"
$blueprint:psych "design the game from player desire backward"
$blueprint:loop "define session, daily, weekly, and comeback loops"
$forge:progression "write the progression ladder"
$forge:community "write the social stickiness systems"
These are advanced lower-level runtime surfaces, not the primary public creator workflow:
rcs setup installs prompts, skills, hooks, and runtime wiringrcs doctor checks install healthrcs team runs the lower-level durable tmux-backed team runtimercs forge runs the lower-level persistent completion looprcs explore and rcs sparkshell cover read-only repo lookup and bounded shell inspectionBefore any Roblox game setup, system design, code generation, UI work, monetization design, plugin work, or refactor:
Use:
docs/reference/roblox-pre-action-protocol.mdtemplates/roblox/pre-action-plan.mddocs/reference/player-psychology-framework.mddocs/reference/player-psychology-command-surfaces.mddocs/reference/roblox-pre-action-protocol.mdtemplates/psychology/templates/roblox/