10-step workflowhorror first-person game atmosphere enemy-ai unity prototype guided-flow App Builder

Build a Scary First-Person Horror Game

A step-by-step flow to create a real playable first-person horror game with movement, interactions, enemy behavior, atmosphere, objectives, fail states, and testing.

Run this as a guided flow on Flows — verify gates and recovery prompts included →

Flows@flows12d ago

0 runs0 forks0

Chain

Inputs

Step 1

flow-build-scary-first-person-horror-game-1-define-the-game-loop-and-systems-bef

Step 2

flow-build-scary-first-person-horror-game-2-build-the-first-person-controller-an

Step 3

flow-build-scary-first-person-horror-game-3-add-interaction-doors-pickups-and-pr

Step 4

flow-build-scary-first-person-horror-game-4-create-the-horror-event-system-and-a

Step 5

flow-build-scary-first-person-horror-game-5-implement-the-enemy-or-threat-behavi

Step 6

flow-build-scary-first-person-horror-game-6-add-ui-feedback-objectives-and-fail-

Step 7

flow-build-scary-first-person-horror-game-7-tune-pacing-fear-escalation-and-play

Step 8

flow-build-scary-first-person-horror-game-8-run-gameplay-qa-and-identify-broken-

Step 9

flow-build-scary-first-person-horror-game-9-fix-critical-issues-and-harden-the-p

Step 10

flow-build-scary-first-person-horror-game-10-do-a-final-playable-vertical-slice-

Final output

Workflow inputs

No inputs required — hit Run to stream each step in order.

Each step streams from its model and feeds the next. BYOK — you pay your provider directly. Add a key in Settings if a step needs one.

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

flow-build-scary-first-person-horror-game-1-define-the-game-loop-and-systems-bef

Claude Sonnet 4.6→ {{step_1}}

Awaiting upstream steps…

Step 2 · Create the core locomotion and scene structure required for all later horror mechanics.

flow-build-scary-first-person-horror-game-2-build-the-first-person-controller-an

Claude Sonnet 4.6→ {{step_2}}

Awaiting upstream steps…

Step 3 · Create the real gameplay structure that makes exploration meaningful.

flow-build-scary-first-person-horror-game-3-add-interaction-doors-pickups-and-pr

Claude Sonnet 4.6→ {{step_3}}

Awaiting upstream steps…

Step 4 · Add controllable scares and environmental tension that react to player progress.

flow-build-scary-first-person-horror-game-4-create-the-horror-event-system-and-a

Claude Sonnet 4.6→ {{step_4}}

Awaiting upstream steps…

Step 5 · Introduce real danger so the game has pressure, stealth, chase, or survival stakes.

flow-build-scary-first-person-horror-game-5-implement-the-enemy-or-threat-behavi

Claude Sonnet 4.6→ {{step_5}}

Awaiting upstream steps…

Step 6 · Make the game understandable and complete for a player without developer guidance.

flow-build-scary-first-person-horror-game-6-add-ui-feedback-objectives-and-fail-

Claude Sonnet 4.6→ {{step_6}}

Awaiting upstream steps…

Step 7 · Turn the prototype from a collection of systems into a coherent horror experience.

flow-build-scary-first-person-horror-game-7-tune-pacing-fear-escalation-and-play

Claude Sonnet 4.6→ {{step_7}}

Awaiting upstream steps…

Step 8 · Systematically test the prototype for the failures AI-built games commonly hide.

flow-build-scary-first-person-horror-game-8-run-gameplay-qa-and-identify-broken-

Claude Sonnet 4.6→ {{step_8}}

Awaiting upstream steps…

Step 9 · Resolve the most common hidden implementation problems so the game is reliably playable.

flow-build-scary-first-person-horror-game-9-fix-critical-issues-and-harden-the-p

Claude Sonnet 4.6→ {{step_9}}

Awaiting upstream steps…

Step 10 · Confirm the game works as a short but complete horror experience ready to share or iterate on.

flow-build-scary-first-person-horror-game-10-do-a-final-playable-vertical-slice-

Claude Sonnet 4.6→ {{step_10}}

Awaiting upstream steps…

About this workflow

A step-by-step flow to create a real playable first-person horror game with movement, interactions, enemy behavior, atmosphere, objectives, fail states, and testing.

What happens when you run it

1
Force the builder to design a complete horror gameplay loop with concrete systems, not just a spooky scene.
Runs flow-build-scary-first-person-horror-game-1-define-the-game-loop-and-systems-bef on Claude Sonnet 4.6
2
Create the core locomotion and scene structure required for all later horror mechanics.
Runs flow-build-scary-first-person-horror-game-2-build-the-first-person-controller-an on Claude Sonnet 4.6
3
Create the real gameplay structure that makes exploration meaningful.
Runs flow-build-scary-first-person-horror-game-3-add-interaction-doors-pickups-and-pr on Claude Sonnet 4.6
4
Add controllable scares and environmental tension that react to player progress.
Runs flow-build-scary-first-person-horror-game-4-create-the-horror-event-system-and-a on Claude Sonnet 4.6
5
Introduce real danger so the game has pressure, stealth, chase, or survival stakes.
Runs flow-build-scary-first-person-horror-game-5-implement-the-enemy-or-threat-behavi on Claude Sonnet 4.6
6
Make the game understandable and complete for a player without developer guidance.
Runs flow-build-scary-first-person-horror-game-6-add-ui-feedback-objectives-and-fail- on Claude Sonnet 4.6
7
Turn the prototype from a collection of systems into a coherent horror experience.
Runs flow-build-scary-first-person-horror-game-7-tune-pacing-fear-escalation-and-play on Claude Sonnet 4.6
8
Systematically test the prototype for the failures AI-built games commonly hide.
Runs flow-build-scary-first-person-horror-game-8-run-gameplay-qa-and-identify-broken- on Claude Sonnet 4.6
9
Resolve the most common hidden implementation problems so the game is reliably playable.
Runs flow-build-scary-first-person-horror-game-9-fix-critical-issues-and-harden-the-p on Claude Sonnet 4.6
10
Confirm the game works as a short but complete horror experience ready to share or iterate on.
Runs flow-build-scary-first-person-horror-game-10-do-a-final-playable-vertical-slice- on Claude Sonnet 4.6

Best for

•Recurring tasks you currently copy-paste between tools.
•When a single prompt isn't enough — you need a chain where output(n) feeds prompt(n+1).
•Fork and adapt if your inputs differ materially from the author's use case.

Models used

Claude Sonnet 4.6