cmoriarty/trog
1
0
Fork 0
Code Issues 11 Pull requests Projects 1 Releases Packages Wiki Activity Actions

12 · Studio: new-game wizard — guided design questionnaire + proper kickoff #25

New issue
Open
opened 2026-07-25 21:45:06 -04:00 by cmoriarty · 0 comments
cmoriarty commented 2026-07-25 21:45:06 -04:00
Owner
Copy link

From studio review (2026-07-25): trog needs a hand-holding on-ramp — a new-game wizard in the studio that asks design questions and guarantees a well-formed start to development.

Sketch:

  • Design questionnaire: art direction (retro pixel vs HD/modern — pairs with #24's art-direction modes), genre/archetype (platformer, top-down, puzzle…), 2D/3D (maps to the framework table: Phaser / Three+Rapier / Pixi), scope (jam toy vs full production), vibe references
  • Output: a structured brief + GDD scaffold the ideation phase consumes — the wizard's answers become constraints the graph respects, not suggestions it forgets
  • Kickoff: wizard ends by creating the game repo (trog-games org) and starting the production run, properly configured — the user never hand-writes a brief or touches curl
  • Guardrails: sane defaults every step, so "just make me something cozy" is three clicks

Studio-side this is a pane/modal flow riding the same Aegra client; graph-side it may want a dedicated intake node or run-input schema.

Filed from #7 review; sequencing after the walking skeleton (#11) makes sense.

From studio review (2026-07-25): trog needs a hand-holding on-ramp — a **new-game wizard** in the studio that asks design questions and guarantees a well-formed start to development. Sketch: - **Design questionnaire:** art direction (retro pixel vs HD/modern — pairs with #24's art-direction modes), genre/archetype (platformer, top-down, puzzle…), 2D/3D (maps to the framework table: Phaser / Three+Rapier / Pixi), scope (jam toy vs full production), vibe references - **Output:** a structured brief + GDD scaffold the ideation phase consumes — the wizard's answers become constraints the graph respects, not suggestions it forgets - **Kickoff:** wizard ends by creating the game repo (trog-games org) and starting the production run, properly configured — the user never hand-writes a brief or touches curl - Guardrails: sane defaults every step, so "just make me something cozy" is three clicks Studio-side this is a pane/modal flow riding the same Aegra client; graph-side it may want a dedicated intake node or run-input schema. Filed from #7 review; sequencing after the walking skeleton (#11) makes sense.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feat/11-walking-skeleton
No results found.
Labels
Clear labels   
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
wontfix
This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cmoriarty/trog#25
No description provided.