Documentation

How to Structure Phaser Scenes and Levels

How to Structure Phaser Scenes and Levels

A practical step-by-step guide to structure phaser scenes and levels, with prompts, review checks, and links to related GenStory.cc guidance.

A practical step-by-step guide to structure phaser scenes and levels, with prompts, review checks, and links to related GenStory.cc guidance.

What you will create

You will finish with an editable, reviewable project artifact rather than an unstructured one-shot output. Start with the smallest useful version, verify it, and expand only after the workflow is reliable.

Step-by-step workflow

1. Reduce the idea to one playable core loop

Define the input, expected result, and acceptance check for this step. Record confirmed decisions, unresolved questions, and any change that could affect connected content before moving on.

2. Plan scenes, state ownership, controls, and assets

Define the input, expected result, and acceptance check for this step. Record confirmed decisions, unresolved questions, and any change that could affect connected content before moving on.

3. Implement input and win/lose conditions with placeholders

Define the input, expected result, and acceptance check for this step. Record confirmed decisions, unresolved questions, and any change that could affect connected content before moving on.

4. Add levels, UI, and final assets incrementally

Define the input, expected result, and acceptance check for this step. Record confirmed decisions, unresolved questions, and any change that could affect connected content before moving on.

5. Debug from reproducible steps, console output, and network failures

Define the input, expected result, and acceptance check for this step. Record confirmed decisions, unresolved questions, and any change that could affect connected content before moving on.

6. Build, preview on a static server, and deploy

Define the input, expected result, and acceptance check for this step. Record confirmed decisions, unresolved questions, and any change that could affect connected content before moving on.

Example prompt

Replace bracketed text with project-specific information.

Help me with this task: How to Structure Phaser Scenes and Levels.

Project type: [type]
Audience: [audience]
Existing material: [paste only relevant context]
Fixed constraints: [facts that must not change]
Desired output: [outline/table/checklist/draft/code]

Ask up to three clarifying questions first. Then return a structured result, label assumptions, and do not overwrite confirmed facts.

Review the output for fixed constraints, scope, omissions, unverifiable claims, and continuity with adjacent content. Regenerate only the affected part.

Common mistakes

Asking for a complete finished work before confirming its structure and constraints.
Changing content, style, format, and assets at the same time.
Writing AI output directly into the project without review or a recoverable copy.
Checking one page or scene in isolation instead of reviewing continuity.
Treating a publishing export as the only editable backup.

Quality checklist

Audience, final format, scope, and success criteria are explicit.
Fixed facts are separated from details that may change.
Every step produces an observable result.
Connected pages, scenes, or states do not contradict one another.
External generation output has been reviewed by a person.
The editable source project and key assets have an independent backup.

Next step

Open the relevant creation-type page and build the smallest section that can be read, previewed, or run. Expand it using the review results above.