This skill helps an agent build Roblox user interfaces as real, named Instances in Explorer with small behavior modules. It inspects the game’s existing fonts, colors and spacing first, decides whether each ScreenGui survives respawn, and builds responsive structure with UDim2, layouts and size constraints.
It includes patterns for a layout that reflows at a breakpoint, gamepad entry focus based on PreferredInput, and an interruptible fade that honors reduced motion, plus quality gates and a symptom table. A small Rojo fixture gives an inventory screen to review layouts against.
What You Get
- An eight-step workflow from inspecting existing UI to building, polishing and checking it
- A production hierarchy for a screen with a template, components and theme layout
- Three Luau patterns: a reflowing layout, explicit gamepad entry focus and a cancelable fade
- Two references on responsive layout and input navigation, a viewport test matrix and a Rojo fixture for an inventory screen
Common Use Cases
- Fixing a menu that clips on phones or sits under the topbar
- Making a shop or inventory usable with a controller, including modals that trap focus
- Stopping a HUD from resetting or duplicating after respawn
- Adding open and close motion that respects reduced motion
What Makes It Unique
The skill extends the game’s own visual language and keeps screens inspectable in Explorer. It picks input-dependent UI from PreferredInput, which follows the player’s main device, and names design traps such as card-on-card shells, neon outlines and a single global UIScale used as the whole responsive system.
Under The Hood
The agent loads the SKILL.md and, when needed, references on responsive layout and input navigation. It reads and edits Luau and UI files, and builds a Rojo project or the bundled fixture with the rojo command line to check that it compiles. With a connected Roblox Studio MCP server it starts play, runs Luau on the client to print focus and sizes, and captures screenshots; Studio’s device simulator skill switches device presets. Without that server it asks you to check the viewport matrix in Studio and report back. Documentation URLs are listed for re-checking APIs, and nothing is fetched during normal use.