Build a Scary First-Person Horror Game

PROJECT CONTEXT:
Create a playable first-person horror game prototype focused on tension, exploration, interaction, and survival. The game should include a controllable player, a dark explorable environment, interactive objectives, horror events, and a hostile threat that creates pressure.

GOAL:
Build a genuinely functional scary first-person game prototype that can be played from start to finish, with working controls, interactions, game logic, enemy behavior, audio/visual horror cues, win state, and lose state.

REQUIREMENTS:
- Implement first-person movement with mouse look and collision
- Create at least one explorable indoor horror environment with lighting and navigable layout
- Add interactive objects such as doors, keys, notes, switches, or pickups
- Include at least one clear objective chain the player must complete
- Add a hostile entity or threat that can detect, chase, or punish the player
- Implement health, death, or capture fail state with restart flow
- Use lighting, sound, and environmental triggers to create fear and tension
- Show objective or interaction feedback through UI or on-screen prompts
- Ensure progression logic actually gates access using inventory or event conditions
- Make the full loop playable from game start to win or loss

CONSTRAINTS:
- Prioritize a working prototype over polished art assets
- Use placeholder assets if needed, but all gameplay systems must function
- Keep the scope to one short level or vertical slice
- Do not rely on fake scripted demos that break during free play

DEFINITION OF DONE:
- Player can launch the game and freely move through the level in first-person
- At least one objective chain requires real interactions and unlocks progression
- Enemy or threat behavior works during actual gameplay, not just in a cutscene
- Game includes at least one loss condition and one successful completion condition
- Audio, lighting, and event triggers noticeably increase tension during play
- All core interactions display feedback and respond correctly to player input
- A full playthrough can be completed without developer intervention or editor tweaks

COMMON FAILURES TO AVOID:
- 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
- Doors, keys, and triggers exist visually but are not wired together
- Game has no real win state, lose state, or restart flow