roblox-ui-design
Skill1 starsChanged 4 months agoMITView on GitHub
Roblox UI design with simulator default and existing-style inheritance. Use with `roblox-gui`.
In this repository32 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- roblox-analyticsSkill
- roblox-animated-modelsSkill
- roblox-animation-vfxSkill
- roblox-architectureSkill
- roblox-assetsSkill
- roblox-audioSkill
- roblox-buildingSkill
- roblox-cameraSkill
- roblox-cloudSkill
- roblox-code-reviewSkill
- roblox-dataSkill
- roblox-debugSkill
- roblox-guiSkill
- roblox-inputSkill
- roblox-lightingSkill
- roblox-localizationSkill
- roblox-luau-coreSkill
- roblox-luau-patternsSkill
- roblox-luau-typesSkill
- roblox-monetizationSkill
- roblox-networkingSkill
- roblox-npc-aiSkill
- roblox-oauthSkill
- roblox-performanceSkill
- roblox-physicsSkill
- roblox-publish-checklistSkill
- roblox-securitySkill
- roblox-server-dataSkill
- roblox-sharp-edgesSkill
- roblox-studio-mcpSkill
- roblox-toolingSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Alignment: use shared layouts, fixed icon slots, and matching anchors.
- Distinctive: line 39
Default: bold, layered, toy-like UI over 3D gameplay.
- Distinctive: line 44
Use one neutral outline per surface.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Roblox UI Visual Design
When to Load
Load for Roblox UI design/review. No style source: use the simulator default. Existing UI/reference: preserve its style while applying these rules. Load roblox-gui for mechanics.
Quick Reference
Style
Existing UI/reference > explicit art direction > default.
For existing style, inspect surfaces, fonts, borders, depth, icons, spacing, and action colors. Reuse those tokens. Borrow style, not broken geometry. Do not import conflicting simulator conventions.
Core Principles
- Topology: choose composition from the job: single-focus, collection, compare, HUD, list, or another justified shape. Do not force every task into one modal.
- Hierarchy: one focal object, state, or action gets the strongest contrast and scale. Quiet secondary content.
- Flow: each repeated flow has one owner:
UIListLayout,UIGridLayout, or shared-column math. Do not mix layout objects with guessed offsets. - Density: size the complete panel around useful content. Do not stretch shells or add metadata to fill space.
- Bounds: sum widths, gaps, padding, borders, and minimums. Keep content, strokes, and backings inside parents.
- Alignment: use shared layouts, fixed icon slots, and matching anchors. Do not independently offset paired icons and labels.
- State: active, available, locked, completed, and disabled states need structural/textual differences. Color is not the only signal.
- Verification: inspect the target viewport for clipping, overflow, dead space, type, and hierarchy. A valid tree is not proof of good composition.
Default
Default: bold, layered, toy-like UI over 3D gameplay.
- Base: charcoal/warm brown. Green = claim/buy; red = danger/close; yellow = premium; blue = navigation/currency; purple = rare.
- Display:
FredokaOne(cute) orOswald(action); body:BuilderSans. - Display type covers titles, section labels, item names, and key stats. Secondary values stay clean and smaller. Outline title and primary CTA only.
- Use one neutral outline per surface. Backings share the radius or stay inset. Put color in fills, active insets, or small cues, not every perimeter.
- Content cards need a centered focal icon/art placeholder. Do not leave item grids blank.
Anti-Patterns
Oversized shells, wide panels around narrow stacks, fixed offsets in auto-sized flows, drifting actions, colored outlines on every card, blank item boxes, independent icon/label offsets, or simulator styling pasted over an existing identity.
Full specs and QA checklist: references/full.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

