Hire an AI Roblox systems programmer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A list of what the server owns and what the client only shows
• A map of every RemoteEvent, with the checks the server must make
• A save plan with retries and a save on shutdown
• A script layout with ModuleScripts
• A security review of each server handler, and a test list

How it does the job well

• Do not invent API names. If unsure that a Roblox call exists, say "confirm in the Roblox docs".
• Start from the user's task and the content, then the layout. Decoration comes last.
• Design every state: empty, loading, error, long text and mobile.
• Keep one visual system. Reuse spacing, type and colour tokens instead of one-off values.
• Check text contrast (at least 4.5:1 for body text) and keyboard focus as you go.

Mistakes it avoids

• Designing only the happy path at desktop width.
• Copying a reference's logo, text or claims instead of learning from its structure.
• Handing over a picture without the sizes, tokens and behaviour a developer needs.

What a good result looks like

An example, not your task: You are building a shop, combat, inventory, round or points system and want the structure right before you write it.

• Authority split. What the server owns and what the client only shows.
• Remote map. Each RemoteEvent with its direction, its payload and the checks the server must make.
• DataStore plan. Keys, default data, retry rule, and when data saves, including on shutdown.
• Module layout. Folders and ModuleScripts, each with one job, and a start-up script that only wires them.
• Starter Luau. Short code for the main module, marked untested. Only if you ask for it.
• Security review. For each server handler, what a cheater could send and how to stop it.

How the work is checked

• Every screen has its states, breakpoints and interactions written down.
• Colour pairs and type sizes pass the stated contrast checks.
• The handoff names components, tokens and open questions.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Linus Torvalds would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Split the work. It decides what the server owns, such as health, coins and items, and what the client only displays.
• Map the messages. It lists each RemoteEvent, who fires it, what it carries and what the server checks before acting.
• Plan the saving. It plans keys, default data, retries, a save when a player leaves and a save when the server shuts down.
• Lay out the scripts. It puts game logic in ModuleScripts and keeps the plain Scripts to a short start-up file.
• Review for cheats. For each handler it asks what happens if the client sends garbage, and notes the fix.
• Plan the tests. It lists tests for fake input, fast joins and leaves, and server shutdown.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id roblox-systems-scripter only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/roblox-systems-scripter/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• What the system should do, in a few plain sentences
• Your scripts or folder list, if the game already exists (optional)
• What must be saved for each player, such as coins, level or items
• Any problem you have seen, such as lost data or players cheating (optional)

Helpful context (optional)

• Your full script folder, pasted in or uploaded.
• The error messages from Studio's output window.

Tools and access

• Claude, ChatGPT or Gemini: Any of them can read your scripts and review each handler. One that can browse can check current Roblox limits.

Functions and deliverables

• Roblox systems programmer: Plan a Roblox game system in Luau with a server and client split, safe RemoteEvents and DataStore saves that do not lose player data.
  • A list of what the server owns and what the client only shows
  • A map of every RemoteEvent, with the checks the server must make
  • A save plan with retries and a save on shutdown
  • A script layout with ModuleScripts
  • A security review of each server handler, and a test list
  Source: Michael Sitarzewski and Agency Agents contributors.
• Data system design reviewer: Describe your app’s data and access patterns. Get storage choices, trade-offs and a score out of 10.
  • Recommended storage and replication
  • Splitting and consistency choices
  • Score out of 10 with failed checks
  • Fix list to improve
  Source: Wondel.ai.
• Agent feedback review system planner: Plan how Slack reactions teach your AI agents. Get a four-way feedback log and lessons drafted for a person to review. Draft code only.
  • A list of gaps in the starter, each with a fix
  • Four feedback kinds, each with its emoji and what it teaches
  • A feedback record layout that keeps client scope
  • Lesson rules with the settings you choose, and a lesson draft format
  • A rule for telling a policy change from a data fix
  • Test cases for each kind and for edge cases
• System model estimator: Fit a system model from your input and output data. Get a MATLAB model, fit scores on held-out data, and a side-by-side check of model types.
  • A fitted dynamic model
  • Fit percentages on validation data
  • A comparison of candidate models
  • Residual checks and warnings about weak data
  Source: MathWorks.
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• Linus Torvalds: Review a code change using Linus Torvalds’s recorded approach. Ask what works, what breaks for existing users and who owns the fix.
  • Your problem worked on the way Linus Torvalds would: their questions, their method, their push-back
  • The answer or the work, in Linus Torvalds's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You are building a shop, combat, inventory, round or points system and want the structure right before you write it.
• Players lose coins or items when they leave, and you suspect your saving.
• You think a client could cheat by firing your RemoteEvents with fake values.
• Your scripts have grown messy and you want them split into ModuleScripts.

Limits to check before starting

• You want to design the game itself, such as goals, rewards and levels. Use the Roblox Experience Designer agent.
• You are making avatar items, such as hats and clothes. Use the Roblox avatar designer.
• You need a bug fixed in a live game right now. Test any fix in Studio first.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack and add it to your AI as a skill. If you cannot, paste SKILL.md and then references/source-agent.md into a new chat.
• Describe the system. If you have scripts, paste them. Say what must be saved.
• Say "Plan this first. Give me starter Luau only if I ask." Your AI asks once for anything missing.
• Read the RemoteEvent map first. For each row, ask what a cheater could send. Fix any row where the answer is "anything".
• Build in Roblox Studio. Run the tests from the list, including a player leaving mid-save.
• Paste your results or errors back and ask for a re-check.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/roblox-systems-scripter for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.