You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>Use this center region for the primary tool canvas, editor, preview, or guided workflow.</p>
60
+
<p>Game Builder turns the design document into a build plan. The workflow reads the GDD, identifies the required game pieces, and assembles them into a manifest.</p>
61
+
<detailsclass="vertical-accordion" open>
62
+
<summary>GDD -> Manifest Workflow</summary>
63
+
<divclass="accordion-body">
64
+
<p>The builder interprets <code>game.gdd.json</code>, maps design intent to concrete screens, assets, objects, behaviors, and transitions, then produces the runtime assembly contract.</p>
65
+
<p>The output is the implementation manifest: <code>game.manifest.json</code>.</p>
66
+
</div>
67
+
</details>
68
+
<detailsclass="vertical-accordion">
69
+
<summary>Construction Crew</summary>
70
+
<divclass="accordion-body">
71
+
<p>Game Builder is the construction crew. It follows the blueprint from Game Design Studio and decides what pieces are needed, where they go, and how they connect.</p>
<p>Use this center region for the primary tool canvas, editor, preview, or guided workflow.</p>
70
+
<p>Game Design Studio turns an idea into a design blueprint. The workflow starts with AI-assisted discovery, then organizes the answers into a Game Design Document.</p>
71
+
<detailsclass="vertical-accordion" open>
72
+
<summary>AI -> GDD Workflow</summary>
73
+
<divclass="accordion-body">
74
+
<p>The AI interview asks what kind of game you want to build, clarifies the audience and rules, then produces a structured design plan for the next tool.</p>
75
+
<p>The output is the design contract: <code>game.gdd.json</code>.</p>
76
+
</div>
77
+
</details>
78
+
<detailsclass="vertical-accordion">
79
+
<summary>Architect / Blueprint</summary>
80
+
<divclass="accordion-body">
81
+
<p>Game Design Studio is the architect. It does not build the house. It decides what the house is, who it serves, how it should feel, and what must be true before construction begins.</p>
82
+
</div>
83
+
</details>
41
84
</section>
42
85
<asideclass="tool-column">
43
86
<divclass="tool-column-header forge-gold">
44
87
<h2>Inspector</h2>
45
88
</div>
46
89
<divclass="accordion-stack">
47
90
<detailsclass="vertical-accordion" open>
48
-
<summary>Inspector Accordion 5</summary>
49
-
<divclass="accordion-body">Game Design Studio inspector panel 5.</div>
91
+
<summary>Output</summary>
92
+
<divclass="accordion-body">
93
+
<p><strong>game.gdd.json</strong></p>
94
+
<pre><code>{
95
+
"genre": "",
96
+
"players": "",
97
+
"objectives": [],
98
+
"winConditions": [],
99
+
"loseConditions": [],
100
+
"assetRequirements": [],
101
+
"soundRequirements": []
102
+
}</code></pre>
103
+
</div>
104
+
</details>
105
+
<detailsclass="vertical-accordion">
106
+
<summary>Next Step</summary>
107
+
<divclass="accordion-body">
108
+
<p>Send <code>game.gdd.json</code> to Game Builder so the design can become a manifest.</p>
<p>Use this center region for the primary tool canvas, editor, preview, or guided workflow.</p>
68
+
<p>Publish Studio turns a game manifest into a release. It packages the playable game, prepares marketplace information, and defines the published record.</p>
69
+
<detailsclass="vertical-accordion" open>
70
+
<summary>Manifest -> Publish Workflow</summary>
71
+
<divclass="accordion-body">
72
+
<p>The publish workflow starts with <code>game.manifest.json</code>, verifies release metadata, prepares assets for listing, and creates release-ready outputs.</p>
<p>Publish Studio is the real estate agent and product launch desk. The game already exists; this page prepares how it is presented, priced, described, packaged, and released.</p>
0 commit comments