Use the G-L-W-C-P-I-S frame

Build a prompt from seven practical parts:

  1. Goal: what the player is trying to achieve.
  2. Loop: the action the player repeats.
  3. World: the setting and important objects.
  4. Controls: how the player moves or interacts.
  5. Progression: how challenge, score or upgrades change.
  6. Interface: what information must stay visible.
  7. Style: the visual mood without copying a protected character or brand.

The initials are a Build Creator writing aid, not a Roblox feature or guarantee.

Original starting examples

Collect-and-score

Create a small moon greenhouse. The player collects glowing spores and deposits them in three planters. Each deposit adds to a visible score. New spores appear farther from the base after every ten points. Use simple cyan paths and violet plants.

Arcade survival

Create a top-down arena where the player avoids slow moving energy waves for sixty seconds. Show a large timer and three shield points. Increase wave speed every fifteen seconds. End with a clear survive or retry screen.

Clicker progression

Create a workshop clicker where tapping the core produces parts. Show parts per tap and total parts. Allow three upgrades that improve output, with each next cost visible before purchase.

These examples make output testable; they do not promise a specific generated result.

Prompt one change at a time

After the first playtest, describe the current behavior, the desired behavior and what must stay unchanged:

When a player deposits spores, update the score immediately. Keep the current movement, map size and planter positions unchanged.

That structure makes the requested difference easier to verify.

Respect content boundaries

Roblox Support says Build requests must follow the Restricted Content Policy and Community Standards. Requests involving disallowed age-inappropriate material or third-party characters and brands may be rejected.

Use original settings, characters and visual direction. Do not disguise a request to reproduce someone else’s protected property.

Common prompt problems

  • Too many systems at once: start with one loop, then add progression.
  • Abstract direction: replace “make it fun” with an observable goal, timer, score or rule.
  • Conflicting instructions: state which current behavior must remain.
  • Untested revisions: playtest after each meaningful change.
  • Generation stops: type please continue when usage is available.