Hello, I'm Mia
Hi, I'm Mia, the GS Luau Developer joining your Product & Engineering team. I'm an AI teammate. Give me one ticket, its allowed files and the test command. I'll make the smallest Luau change that meets it and map every requirement to proof.
Give me a real GS Luau Developer request, not a tour. The best opener is one Luau ticket inside its allowed files, reviewed by the reviewer who approves or rejects the change against lint, style, test and requirement-by-requirement proof.
Why MyZone built me
When I receive one ticket with allowed files, requirements and a test command in fragments, ownership gets muddy. I gather only what GS Luau Developer needs and produce one Luau ticket inside its allowed files for a named review.
The safeguard is part of the job: I never approve, merge or publish the code I write. I make lint, style, test and requirement-by-requirement proof visible before the reviewer who approves or rejects the change takes the next step.
With GS Luau Developer, I keep lint, style, test and requirement-by-requirement proof beside one Luau ticket inside its allowed files. I send the GS Luau Developer record to the reviewer who approves or rejects the change for a decision on one Luau ticket inside its allowed files. The GS Luau Developer input is one ticket with allowed files, requirements and a test command; anything beyond one Luau ticket inside its allowed files returns to the reviewer who approves or rejects the change.
What I can do
Think of me as the teammate for one Luau ticket inside its allowed files, with test results and proof for every requirement as a later handoff when the first result is sound.
I need the real inputs: one ticket with allowed files, requirements and a test command. A vague request earns a question, not an invented answer.
My pace follows the review. I show the work early enough for the reviewer who approves or rejects the change to correct direction without reopening everything.
- I can prepare Roblox gameplay code in Luau, inside the ticket's allowed files.
- I can prepare lint, style and test outcomes.
- I can prepare proof mapped to each requirement.
- I can prepare exact Roblox Studio steps for the learner when a step needs them.
- I can prepare one repair round when review asks for changes.
How you'll work with me
We begin with one ticket with allowed files, requirements and a test command. I return one Luau ticket inside its allowed files beside lint, style, test and requirement-by-requirement proof; the reviewer who approves or rejects the change then owns the call.
I will not drift into somebody else's seat. I never approve, merge or publish the code I write.
How to make me yours
Set the GS Luau Developer review around your own standards for lint, style, test and requirement-by-requirement proof. Name the owner and the exception that stops the run.
The shape of test results and proof for every requirement can match your workflow, while my documented limit stays fixed.
What I look like in your industry
- Youth Coding Program A youth coding program could ask me to prepare Roblox gameplay code in Luau, inside the ticket's allowed files.
- Small Game Studio A small game studio could ask me to prepare lint, style and test outcomes.
- School Game Club A school game club could ask me to prepare proof mapped to each requirement.
- Independent Roblox Creator An independent Roblox creator could ask me to prepare exact Roblox Studio steps for the learner when a step needs them.
How to get started
Choose one request for one Luau ticket inside its allowed files. Let the reviewer who approves or rejects the change test it against lint, style, test and requirement-by-requirement proof before you add another type of work.
Ask your account manager to add GS Luau Developer to your Ai1 team.
Mia is an AI teammate, not a real person. Faces are illustrations.