Make a clear game screen

Give important information a clear hierarchy on every device.

Your game details

Make this yours. Change the examples below to match your game. Every detail goes into your prompt.

Which game is this for?

Pick a saved game, or change the example to fit your idea.

Game nameA working name is fine.What is your game about?What do players do? Write one or two sentences.What will players use?Pick the devices your game should work on.Who plays together?For example: play alone, 8 friends, or two teams.What should it look like?For example: low-poly, colorful, spooky, or anime-inspired.Anything the AI should keep in mind?Your skill level, time, and things you want to keep.What have you already built?Paste your AI’s reply, relevant scripts, or what you already built. Tell the AI what to keep. Leave out passwords and keys.

Manage my games

Your next step

Ask for one thing to build, change, or fix. Pick a starting point, then edit it below.

What do you want to make?Be specific. You can change the example below.

Copy your prompt

Copy the full prompt, then paste it into your AI tool.

Name in Saved promptsOnly used if you save this prompt for later.

Use with a coding AI. Copy, paste, then test in Studio.

Full Prompt

You are helping a beginner-to-intermediate Roblox creator. Use plain language and original ideas.

PROJECT CONTEXT
Project: Lantern Harbor
Concept: Explore a coastal town, complete delivery jobs, and customize a tiny apartment.
Devices: Desktop and mobile-first; test on a modest phone.
Players: Co-op and social, up to 8 players.
Visual direction: Low-poly, warm matte surfaces, readable chunky silhouettes.
Scope: Solo beginner creator; one small playable slice; original assets; no paid random rewards.
Existing context: New prototype. No existing scripts. Request missing technical details before choosing APIs.
Task: A racing HUD needs lap progress, position, speed, and a pause control without covering the track.

SPECIFIC BRIEF
Audit the current HUD for essential, contextual, and optional information. Propose a responsive ScreenGui hierarchy, constraints, safe areas, readable text, and accessible state changes. Separate data binding from presentation. Explain keyboard focus, controller selection, touch target spacing, and non-color status indicators. Preserve existing event contracts.

WORKING RULES
Inspect relevant scripts and Explorer paths first. Preserve working systems and public interfaces. Ask only for missing context that blocks a safe change. Use current Luau and Roblox APIs verified against official documentation; state uncertainty. Separate Script, LocalScript, and ModuleScript locations. Keep rewards, ownership, damage, and progression server-authoritative. Validate remote payloads, permissions, finite values, and rate limits. Never overwrite working code without explaining the smallest required patch.

OUTPUT FORMAT
1. Short assumptions and missing context.
2. Explorer tree and step-by-step implementation with complete relevant Luau patches.
3. Integration instructions in numbered steps for a beginner.
4. Validation checklist covering: Test the smallest supported viewport, long localized text, keyboard focus order, controller selection, and no-audio gameplay.
5. Known limits and a small next iteration.

Never claim you ran Roblox Studio or a model test unless you actually did. Mark generated implementation as untested until playtested. No copied maps, characters, branded assets, UI, or endorsement claims.

Help, fixes & prompt info

Paste into your own AI tool. It cannot see your Studio project unless you provide the relevant context. External tools may have separate costs.

Need a change or got an error?

Make the first slice smaller

Using the a hud players understand instantly result above, identify the smallest playable or reviewable slice. Keep its defining constraint and remove optional systems. List exactly what to build first, what can wait, and one success test. Do not rewrite unrelated project systems.

Troubleshoot the result

Help me debug the a hud players understand instantly result. Ask for my actual output, relevant code or asset settings, exact error, expected behavior, and reproduction steps. Compare evidence against the stated constraints. Rank likely causes, then propose the smallest fix and a regression check. Do not claim successful Studio testing without evidence.

Review for the target device

Review the result for Desktop and mobile-first; test on a modest phone. in Lantern Harbor. Check input, readability, asset weight, transparent effects, network ownership, and bounded work where relevant. Separate findings from hypotheses. Give a short measurement plan and preserve working behavior.

Setup & testing help

Relevant scripts with Explorer paths, current behavior, desired behavior, and a minimal reproduction. Remove secrets and unrelated code.

Before you start

A Roblox Studio project or a clearly scoped original concept.
Relevant code, asset settings, or an original reference brief; no passwords or API keys.

Expected output

Assumptions, Explorer tree, complete focused Luau patches, setup steps, and manual tests.

Build steps

Apply in a duplicate test place or source-controlled branch; preserve working systems.
Keep sensitive authority on the server; use two-client Studio testing for multiplayer behavior.
Record actual evidence before changing the validation status to tested.

What to test

Test the smallest supported viewport, long localized text, keyboard focus order, controller selection, and no-audio gameplay.
Verify every API and import setting against the linked current official documentation.
Record Studio version, device, reproduction steps, observed outcome, and remaining issues.

Example, sources & reuse

Status: draft. Version 1. Source review: 2026-10-19. Generated code and assets need Studio testing.

You are helping a beginner-to-intermediate Roblox creator. Use plain language and original ideas.

Original Overlocked template. Reuse and customize in your own projects. Do not redistribute or resell the prompt library. External tool outputs and third-party assets have separate terms; confirm rights before publishing.

Schema and website behavior tested separately. This prompt has not been executed in Roblox Studio or evaluated across AI models.

All credits & sources ↗

How saved games and prompts work

Your full prompt

Loading your workspace…

You are helping a beginner-to-intermediate Roblox creator. Use plain language and original ideas. PROJECT CONTEXT Project: Lantern Harbor Concept: Explore a coastal town, complete delivery jobs, and customize a tiny apartment. Devices: Desktop and mobile-first; test on a modest phone. Players: Co-op and social, up to 8 players. Visual direction: Low-poly, warm matte surfaces, readable chunky silhouettes. Scope: Solo beginner creator; one small playable slice; original assets; no paid random rewards. Existing context: New prototype. No existing scripts. Request missing technical details before choosing APIs. Task: A racing HUD needs lap progress, position, speed, and a pause control without covering the track. SPECIFIC BRIEF Audit the current HUD for essential, contextual, and optional information. Propose a responsive ScreenGui hierarchy, constraints, safe areas, readable text, and accessible state changes. Separate data binding from presentation. Explain keyboard focus, controller selection, touch target spacing, and non-color status indicators. Preserve existing event contracts. WORKING RULES Inspect relevant scripts and Explorer paths first. Preserve working systems and public interfaces. Ask only for missing context that blocks a safe change. Use current Luau and Roblox APIs verified against official documentation; state uncertainty. Separate Script, LocalScript, and ModuleScript locations. Keep rewards, ownership, damage, and progression server-authoritative. Validate remote payloads, permissions, finite values, and rate limits. Never overwrite working code without explaining the smallest required patch. OUTPUT FORMAT 1. Short assumptions and missing context. 2. Explorer tree and step-by-step implementation with complete relevant Luau patches. 3. Integration instructions in numbered steps for a beginner. 4. Validation checklist covering: Test the smallest supported viewport, long localized text, keyboard focus order, controller selection, and no-audio gameplay. 5. Known limits and a small next iteration. Never claim you ran Roblox Studio or a model test unless you actually did. Mark generated implementation as untested until playtested. No copied maps, characters, branded assets, UI, or endorsement claims.