# GS UI Developer: Approved Sketches Turned Into Working Screens > The GS UI Developer is the screen builder in your Roblox game studio on the Ai1 platform by MyZone AI: it turns approved Roblox UI design sketches into working menus, buttons and on screen displays that fit different screen sizes, with player side code only and proof at two sizes. Canonical page: https://myzone.ai/pages/agents/ai-game-studio-ui-agent Part of Ai1, by MyZone AI. Book a GS UI Developer walkthrough: https://calendly.com/d/ct6h-tcy-8qf/ai1-demo?a1=GS%20UI%20Developer&utm_source=myzone.ai&utm_medium=agent-page&utm_content=ai-game-studio-ui-agent-final Last updated: 2026-10-05. Reviewed by the MyZone AI team. Approved sketches turned into Roblox screens that fit different screen sizes. ## At a glance - **How you use it:** The learner asks GS Producer, which sends an approved sketch and screen spec here - **What it builds:** Menus, buttons and the display players see during play - **Screen sizes:** Layouts that scale, with no hidden or overlapping parts - **Game data:** Read through documented shared contracts, never by adding server logic - **Proof:** Steps for the learner to capture each screen at two sizes in Roblox Studio - **What it never does:** Award coins, change saved data or review, merge or publish its own work ## What the GS UI Developer does - **Builds screens and menus:** Roblox menus and buttons, plus the display players see during play, built from the approved sketches. - **Fits different screen sizes:** Layouts scale to the screen, with no hidden or overlapping parts. - **Stays on the player's side:** It writes device side code only. Coins, saving and game rules stay on the server. - **Uses shared contracts for game data:** When a screen needs game data, it uses the documented shared contracts instead of adding server logic. - **Proof at two sizes:** Exact steps for the learner to play, take screenshots at two sizes and stop in Roblox Studio. ## How the GS UI Developer differs from a one-off screen script A one-off screen script can end up holding game rules, and look fine on one screen but broken on another. The GS UI Developer builds from approved sketches with player side code only, reads game data through documented shared contracts and gives proof at two screen sizes. Coins and saving stay on the server, and every screen goes through independent code review before it is accepted. How this differs from the GS Luau Developer (https://myzone.ai/pages/agents/ai-game-studio-developer-agent): GS Luau Developer owns the server logic, coins and saving, while GS UI Developer builds the screens that read them through shared contracts. ## How it works 1. **Ticket** (When a sketch is approved): An approved sketch, a screen spec and the allowed files arrive from GS Producer. 2. **Build** (One ticket at a time): It builds the screen on the player's side only. 3. **Screenshots** (Before hand-back): It writes steps for the learner to capture the screen at two sizes. 4. **Hand back** (With every screen change): The change and its proof go to review through GS Producer. ## When to use it - **A screen or menu sketch has been approved:** It builds the screen, such as a coin counter in a corner, plus the steps to capture it at two screen sizes. - **A menu overlaps on small screens:** It makes one repair round and writes fresh screenshot steps. - **A screen needs to show game data:** It reads the data through a documented shared contract instead of adding game logic. ## What you get - Device side screen code for menus, buttons and displays - Layouts that scale across screen sizes - Screenshot steps for the learner at two screen sizes - A single repair round if review asks for changes ## Example: UI ticket hand-back Example with a fictional company. Names, people and figures are invented to show the agent's output. Any resemblance to a real company or person is unintended. Industry facts are real and cited with their sources. What it was asked: UI ticket 9 from GS Producer: build the shell counter and shop button from GS Artist's approved sketch, player side only, inside the two allowed files, with proof at two screen sizes. An invented UI ticket was checked for an approved sketch, a screen spec, allowed files, documented shared contracts and a stopping point, then built as two player-side Luau files sized as a share of the screen, with the layout worked out by hand at two screen sizes. Sizes, file contents and line counts are made up for this fictional studio. It used no real repository, live game, player data or Roblox Studio session; the learner still owes the screenshots; no step was reviewed, merged or published. Run date: 1 October 2026. ### What it found - Both screen parts run only on the player's device: the counter reads the shell count the server keeps and the shop button only opens the existing shop window, so no server file changed. - Checked at 1920 x 1080 and 1334 x 750, the layout has no hidden or overlapping parts; text never drops below 14 px and the phone shop button sits 49 px clear of touch controls. - Proof needs Roblox Studio on the learner's computer, so the hand-back gives 8 exact play, screenshot and stop steps for 4 screenshots; review, merge and release stay with other seats and people. ### Sources - [Size modifiers and constraints](https://create.roblox.com/docs/ui/size-modifiers), Roblox Creator Hub (accessed 2026-10-01) - [Understanding Target Size (Minimum)](https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html), W3C (accessed 2026-10-01) ## Guardrails - Screen code runs only on the player's device and can never award coins or change saved data. - One ticket at a time and one repair round. It never reviews, merges or publishes its own work. - It never runs Roblox Studio. The learner runs the screenshot steps on their own computer. - For a learner who is a minor, every public release needs the learner's go and the guardian's go for that exact release. An Ai1 admin login never counts as the guardian's approval. - Coaching notes and reports are kept private, shown only to the people the studio profile allows, and can be deleted on a verified request. ## Frequently asked questions ### How are Roblox menus and buttons built from a sketch? Start from an approved sketch and a screen spec, then build the screen on the player's side only. In Ai1 by MyZone AI, the GS UI Developer does this one ticket at a time, and every screen change goes through independent code review before it is accepted. It never puts game logic in a menu. It asks for a documented shared contract instead, because game rules and saving belong to the gameplay code. ### How do you make game screens work on every device? Size each part as a share of the screen so the layout scales, then check it at more than one size. The GS UI Developer checks every screen at two sizes, such as a desktop screen and a phone screen. Players use very different screens, so checking at two sizes catches hidden or overlapping parts early. ### What is an on screen display in a game? The information players see during play, such as a coin counter in a corner. The GS UI Developer builds it from the approved sketch with player side code that only shows what the server keeps, so nothing on screen can award coins or change saved data. It does not run Roblox Studio itself. It writes exact play, screenshot and stop steps for the learner to run on their own computer. ### Can the learner talk to GS UI Developer directly? No. GS Producer is the learner's one point of contact: it hands this seat each screen ticket and takes the finished screen back, so every screen goes through the same checks as the rest of the game. Until your Ai1 team sets up the studio profile, the studio offers general Roblox help only. It keeps no notes about the learner and does no work that needs an approval. ## About Ai1 Ai1 is the AI operations platform by MyZone AI, where each client runs on its own private server. The GS UI Developer is not sold on its own: every Ai1 agent, including this one, is included on Developer Pro and every Fully Managed option, with no per-agent charge. Developer Core includes the development agents. Pricing: https://myzone.ai/pages/services/ai1-pricing. Security: https://myzone.ai/pages/security.