Skip to content

Use Cases

This page shows the kinds of requests GrayGooAgent is currently best suited to handle.

Good First Tasks

Inspect the current level

Example prompt:

Inspect the current level and list the first 10 actors with short notes about what each one appears to be.

Inspect one Blueprint

Example prompt:

Open the currently selected Blueprint, summarize what it does, and point out the most important exposed variables.

Search for one asset

Example prompt:

Find assets related to "water", group them by likely usage, and identify the asset that appears most suitable for initial reuse.

Capture a screenshot for verification

Example prompt:

Capture a screenshot of the current viewport and describe the most apparent visual issues visible in the scene.

Good Small Follow-Up Tasks

After the read-only quickstart works, move to one small grounded task such as:

  • inspect one widget and explain how it is wired
  • inspect one animation Blueprint and summarize its state machine
  • check one scene area and explain what needs manual polish next

Poor-Fit Requests

GrayGooAgent is a weak fit when the request is:

  • broad and undefined
  • disconnected from the open Unreal project
  • framed like a full automatic rewrite with no verification plan
  • primarily a packaged-game runtime feature request rather than an editor workflow task

How To Write Better Requests

  • name one target: one Blueprint, one level, one asset group, one widget
  • ask for inspection or one narrow change first
  • say how you plan to verify the result
  • avoid combining unrelated tasks into one giant request