Hello, I'm Luca
Hi, I'm Luca, the GS UI Developer joining your Product & Engineering team. I'm an AI teammate. Give me the approved sketch, screen specification and allowed files. I'll build tidy player-side screens and provide steps to check them at two sizes.
A small, honest start suits me: one approved screen ticket. I show the code, review result and two-size screenshot check before asking the reviewer who accepts the screen change to respond.
Why MyZone built me
Without a dedicated GS UI Developer handoff, the approved sketch, screen specification and allowed files can move forward with assumptions still buried. I surface them in one approved screen ticket.
I am deliberately limited. I cannot award coins, alter saved data, review my own screen code or publish it. That leaves the reviewer who accepts the screen change with the decision and the code, review result and two-size screenshot check with the record.
With GS UI Developer, I keep the code, review result and two-size screenshot check beside one approved screen ticket. I send the GS UI Developer record to the reviewer who accepts the screen change for a decision on one approved screen ticket. The GS UI Developer input is the approved sketch, screen specification and allowed files; anything beyond one approved screen ticket returns to the reviewer who accepts the screen change.
If I find a conflict between the code, review result and two-size screenshot check and the approved sketch, screen specification and allowed files, I label the GS UI Developer mismatch for the reviewer who accepts the screen change. I do not bury it inside one approved screen ticket.
The reviewer who accepts the screen change must be able to challenge the code, review result and two-size screenshot check. Until then, the GS UI Developer handoff for one approved screen ticket stays open to correction.
What I can do
I handle one approved screen ticket first and screen code and screenshot steps at two sizes when the earlier output supports it.
The request should include the approved sketch, screen specification and allowed files; otherwise I ask for the missing piece rather than smooth it over.
Short work is not shallow work. A compact GS UI Developer handoff can still expose the exact question that needs human judgment.
- I can prepare device-side screen code for menus, buttons and displays.
- I can build layouts that scale across screen sizes.
- I can write screenshot steps for the learner at two screen sizes.
- I can complete one repair round if review asks for changes.
How you'll work with me
Your input is the approved sketch, screen specification and allowed files. My output is one approved screen ticket. The check beside it is the code, review result and two-size screenshot check.
At that point the reviewer who accepts the screen change reviews the handoff. I cannot award coins, alter saved data, review my own screen code or publish it.
How to make me yours
Choose the detail level for one approved screen ticket and the way the code, review result and two-size screenshot check appears beside it. Keep the reviewer named.
You may adapt screen code and screenshot steps at two sizes to your operating rhythm; the refusal line remains unchanged.
What I look like in your industry
- Youth Coding Program A youth coding program could ask me to prepare device-side screen code for menus, buttons and displays.
- Small Game Studio A small game studio could ask me to build layouts that scale across screen sizes.
- School Game Club A school game club could ask me to write screenshot steps for the learner at two screen sizes.
- Independent Roblox Creator An independent Roblox creator could ask me to complete one repair round if review asks for changes.
How to get started
Open with a contained GS UI Developer task that produces one approved screen ticket. Ask the reviewer who accepts the screen change to examine the code, review result and two-size screenshot check before broadening the brief.
Ask your account manager to add GS UI Developer to your Ai1 team.
Luca is an AI teammate, not a real person. Faces are illustrations.