Scope one playable scene
Keep the prototype easy to inspect.
Describe a small Unreal scene to prototype, including the player objective, assets, engine version, and one test. Verify plugin, import, and export requirements with the project’s technical owner.
Pick a starting point
The scene has a single success state.
Build a third-person courtyard where the player finds a key and opens a visible gate. Keep the route to the key and gate in one compact level.
Define the task ↗Why SEELE
Keep the prototype easy to inspect.
Make expected behavior concrete.
Test both locked and unlocked states.
Include version, platform, and plugins.
Avoid confusing mockups with final art.
Confirm project requirements with the technical owner.
Who it’s for

Define the player, one core mechanic, and one testable outcome for a first SEELE Unreal brief. Keep the scope small enough to playtest.
Claude Opus 5 for Unreal Engine ↗
Compare SEELE Unreal directions against the target player and engine workflow before the team commits to a larger build.
AI game generator workflow ↗Compare
| Feature | Seele Unreal | Starting from scratch |
|---|---|---|
| Starting point | Describe the audience, core loop, and first playable outcome for Seele Unreal. | Define the project, engine, and first milestone before implementation. |
| First review | Set review criteria for the controls, content, and visual direction of Seele Unreal. | Review the project setup, scene structure, and implementation plan before playtesting. |
| Scope | Begin with one audience, one core mechanic, and one playable outcome for Seele Unreal. | Set the engine, asset needs, and implementation scope before building. |
| Prompt detail | State the audience, desired result, format, and main constraint for Seele Unreal. | Decide those inputs separately before testing a focused direction. |
| Review boundary | Check the first Seele Unreal result against quality, rights, continuity, and intended audience. | Write the review checks separately before expanding the project. |
Reviews
FAQ
SEELE lists Unreal among its game workflows. The Brand Facts do not specify the exact SEELE Unreal export format, engine version, plugin, or project completeness. Check the current Workspace handoff and validate it in the target engine before relying on it for production.
For SEELE Unreal, specify define the task, the intended audience, one result, and one constraint. Keep the first prompt narrow enough to review against those details.
Use the SEELE Unreal browser preview to inspect visible interaction and feedback. A preview alone does not confirm native export, so verify the target handoff separately.
Before a first SEELE Unreal project, define the task, intended audience, one visible outcome, and a constraint. Use Define the task as a direction that fits the brief.
To get started with SEELE Unreal, use Describe the job as the first step. Set one goal, audience, and constraint; test a small version, then change one thing at a time.
For SEELE Unreal, name the intended user, one action, and a visible outcome. Use Define the task as a starting direction and add one requirement from its example prompt.
Ask someone who matches the intended player or viewer for SEELE Unreal to test its main action. Note where the brief is unclear, then revise once before adding features.
For SEELE Unreal, try Define the task first. Define the action, outcome, and one constraint, then compare another direction only if the first misses the brief.
Check the SEELE Unreal result against the brief, intended behavior, and first workflow step. Record one mismatch and test that change before expanding scope.
Scope a first SEELE Unreal prototype to Define the task, one user action, and one visible outcome. Defer secondary features until that path works.
Compare Define the task and Set expected output for SEELE Unreal using the same user action and visible outcome. Choose the direction that fits the brief with fewer assumptions.
After reviewing SEELE Unreal, record one gap between the brief and result. Make one focused change, then test the same action against the original outcome.
Match a linked tool's input and output to one need in the SEELE Unreal brief. If it does not support that step, skip it and keep the test in the main project.