Define the game loop and systems before building

Force the builder to design a complete horror gameplay loop with concrete systems, not just a spooky scene.

Keep the scope to one short but complete level with a beginning, escalation, and ending.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Plan a playable first-person horror prototype with one short level. Specify: player movement, camera, interaction system, inventory or key items, door/lock logic, objective chain, threat or enemy behavior, audio scare triggers, lighting/event triggers, UI prompts, death/capture state, and end condition. Return a build plan with concrete systems, scene objects, scripts/components needed, and the order to implement them so the game is playable end to end.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A concrete game specification describing the level flow, mechanics, and required systems.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

The plan includes a start, midgame escalation, and end stateThere is at least one objective chain with dependenciesA threat or enemy has clear gameplay behaviorWin and lose conditions are explicitly definedThe scope fits a single prototype level

Do not continue if…

! AI builds a level that looks scary but has no real gameplay loop
! Interactions appear in UI but objects do not actually change state
! Enemy is decorative, scripted once, or does not truly chase the player
! Objectives are described in text but are not connected to progression logic

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

Your plan is too vague and cinematic. Rewrite it as a build specification with exact systems, object interactions, state changes, and a full playable loop from spawn to victory or death.