Guides — get things done with Geek Engine

Build your first game in 10 minutes

From a blank workspace to a playable web build, using the guided wizard.

1
Start a project and describe your idea
Open a new project and write what you want to make in plain language — the world, the goal, the feel. This is the Idea step; don't overthink it.
2
Answer the AI interview
The wizard asks about Gameplay, Style, and Scope. Your answers tell the engine what kind of game you're really building, so be specific where it matters.
3
Pick a foundation template
The engine suggests a Foundation template based on your answers. Accept the suggestion or choose another to start from solid ground.
4
Refine the build plan
Review the editable build plan and use the refine chat to adjust anything before it's committed. Nothing is built until you're happy with the plan.
5
Approve the GDD and play
Do the final Game Design Document review, let the engine compile your game for instant browser play, and play it the moment it's ready.

Change your game by describing changes, and verify the result.

1
Describe the change
In the Architect chat, say what you want — "add three pickup gems near each checkpoint with a collect sound," for example. Keep each request focused.
2
Let it apply typed operations
The Architect turns your request into typed operations on the Game Design Document and snapshots the state before and after, so the change is recorded and reversible.
3
Inspect in Scenes
Open the Scenes inspector to walk the node tree, check properties, and read generated scripts, confirming the change matches what you asked for.
4
Recover from a failed build
If a compile fails, let the Architect read the error and attempt one credit-checked self-heal. If it's still not right, describe a correction and try again.
5
Roll back if needed
Because every change is snapshotted, you can revert to any earlier state without losing your place.

Get a build in front of testers and learn from how they play.

1
Compile a build
Make sure your latest changes are compiled. A successful build is a hosted web game, ready to share.
2
Let Vision QA verify it
After deploy, Vision QA screenshots the build to confirm it actually rendered. A pass also becomes your project thumbnail.
3
Create a share link
Generate a share link for the build. Add an optional password if you want to limit it to chosen testers; leave it open if you don't.
4
Send it to testers
Share the link. Testers don't need an account — they can play in the browser and leave feedback against the build.
5
Read feedback and telemetry
Review tester comments and the telemetry the game emitted — events, sessions, and completion signals — summarized on your dashboard, then plan your next change.

Set up your organization, invite people, and keep an eye on usage.

1
Set up your organization
Projects live in an organization. Your plan determines how many seats it includes; add more seats as your team grows.
2
Invite teammates with roles
Invite people and assign roles — owner, admin, editor, viewer, or playtester — so each member's access matches what they need to do.
3
Share the credit pool
Credits are pooled at the organization level. Everyone draws from the same balance, so coordinate heavier work like asset generation and self-heals.
4
Top up when busy
When a project hits a busy stretch, buy a top-up to keep working without waiting for your monthly refill.
5
Watch the activity feed
The activity feed records prompts, builds, snapshots, invitations, and billing actions, giving the whole team a shared, auditable view of what's happening.