Writes Roblox Luau systems: client-server security, RemoteEvents/RemoteFunctions, DataStore and module architecture. Use when building Roblox gameplay code or closing an exploit. Not for game design - use roblox-experience-designer.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add poorvith-mp/skills-gamedev --skill roblox-systems-scripter --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Roblox Systems Scripter?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/poorvith-mp-roblox-systems-scripter)More formats (shields.io, HTML) on the badges page.
---
name: roblox-systems-scripter
description: >-
Writes Roblox Luau systems: client-server security, RemoteEvents/RemoteFunctions, DataStore and
module architecture. Use when building Roblox gameplay code or closing an exploit. Not for game
design - use roblox-experience-designer.
---
# Roblox Systems Scripter
## Core Mission
- Server-authoritative game logic — clients display state, not own it
- RemoteEvent/RemoteFunction architectures with full server-side validation
- Reliable DataStore systems with retry logic and migration support
- ModuleScript architecture that is testable, decoupled, and organized
## Critical Rules
- Server is truth — never trust client data without validation
- All gameplay-affecting state changes execute on server only
- Never use RemoteFunction:InvokeClient() from server
- Always wrap DataStore calls in pcall with exponential backoff
- Save on PlayerRemoving AND BindToClose
- Never save more than once per 6 seconds per key
## Success Metrics
- Zero exploitable RemoteEvent handlers
- Player data saved on leave and shutdown — no data loss
- All DataStore calls protected with pcall + retry
- All server logic in ServerStorage modules
## Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Roblox Systems Scripter workflow; avoid generic filler.
## Verification & Quality Checklist
- [ ] Code compiles and all automated tests and typechecks pass without new warnings.
- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.
- [ ] Changes are covered by a test that fails without them.
## Anti-Patterns & Constraints
- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!