ashexplained/roblox-skills

roblox-ui-implementation

Implement Roblox UI in Studio.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-ui-implementation

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Roblox UI Implementation

Goal

Build Roblox UI that is readable, responsive, touch-friendly, and connected to real game state without trusting the client for valuable decisions.

Design Gate (read before building)

Do not improvise UI. Before building a non-trivial surface, read its approved design brief:

  • design/DESIGN.md — global palette, type scale, spacing, and patterns.
  • design/features/<feature-slug>/design.md — this surface's layout, states, and mobile/tablet/desktop behavior. It must say Status: approved.

If the brief is missing or still draft, stop and run roblox-game-ux to produce and approve it first (or get an explicit user override). Build every state the brief specifies — default, empty, loading, error, and permission/locked — not just the happy path, and match the mobile/tablet/desktop behavior it describes.

Architecture

  • Keep UI construction and state updates in client-side controllers.
  • Keep reward, purchase, inventory, and currency decisions on the server.
  • Put shared UI constants or formatting helpers in ReplicatedStorage.
  • Use remotes to request actions, not to grant value directly.
  • Separate HUD state, menu state, notification state, and input handling when the UI grows.

Layout Rules

  • Design phone-first.
  • Use UIScale, constraints, and anchors deliberately.
  • Keep important buttons away from corners and system gesture zones.
  • Use large tap targets and clear pressed/disabled/loading states.
  • Avoid text that can overflow in small buttons or compact panels.
  • Keep core HUD visible without blocking the playfield.

Common Surfaces

  • HUD: objective, currency, health/energy, progress, next reward.
  • Upgrade panel: current value, next value, cost, affordability.
  • Shop: optional offers, clear benefit, no first-session pressure.
  • Rewards: short celebration, visible delta, next goal.
  • Settings: audio, graphics/performance, input preferences.

MCP Build Workflow

  1. Locate UI scripts and GUI instances with script_search, script_grep, and search_game_tree.
  2. Read scripts with script_read and inspect GUI instances with inspect_instance.
  3. Use multi_edit for code changes or execute_luau for targeted GUI construction.
  4. Use start_stop_play, user_mouse_input, user_keyboard_input, and screen_capture to verify.
  5. Check get_console_output.

Verification

Confirm:

  • Text fits on mobile-sized screens.
  • Buttons have obvious affordances and state.
  • UI does not block first action.
  • Valuable actions are server-validated.
  • The built surface matches the approved design brief across mobile, tablet, and desktop, including empty/loading/error states.
  • No new console errors.

Next

Verify the surface with roblox-mobile-playtest and roblox-playtest-qa. If the UI drove new server actions, review the trust boundary with roblox-security-economy. Return to roblox-to-issues / roblox-game-development-lifecycle for the next slice.

from this repository

More skills

All skills
ashexplained
Community

roblox-playtest-qa

Playtest Roblox experiences through Studio MCP with attention to first-session fun, mobile UX, console errors, progression, social hooks, performance, and exploit-sensitive flows.

1h installs
4
GitHub stars
63
Updated
Jul 1
ashexplained
Community

roblox-animation-audio-feedback

Improve Roblox feel through animation, audio, VFX, haptics-like feedback, reward juice, movement feel, combat feedback, UI transitions, emotes, and satisfying loop feedback without hurting mobile performance.

1h installs
3
GitHub stars
63
Updated
Jul 1
ashexplained
Community

roblox-combat-systems

Design, implement, and review Roblox combat systems. Use for melee, ranged, abilities, cooldowns, hit detection, damage validation, status effects, enemy AI hooks, combat UI, balance knobs, VFX/SFX, and exploit-resistant remotes.

1h installs
3
GitHub stars
63
Updated
Jul 1
ashexplained
Community

roblox-creator-store-security-audit

Audit Roblox Creator Store, Toolbox, inventory, group, universe, package, model, UI, gameplay, plugin-like, and other third-party imported assets for malicious or risky scripts. Use whenever Claude imports, inserts, reviews, or trusts Creator Store assets, especially assets with Scripts, LocalScripts, ModuleScripts, hidden descendants, require calls, HTTP, DataStore, remote creation, obfuscated code, or suspicious names.

1h installs
3
GitHub stars
63
Updated
Jul 1