Guides
How-to guides
Step-by-step guidance for getting the best results from WandGx, from prompt writing to publish readiness.
Prompts
How to write effective prompts
Learn the structure of a good WandGx prompt. Include the right level of detail — enough for accurate generation, not so much that you constrain the output unnecessarily.
- 1Start with the core purpose: what the app does in one sentence
- 2Describe your target user: who will use it and in what context
- 3List key features: the 3–7 things the app must do
- 4Specify data requirements: what gets stored, read, or processed
- 5Note integrations: APIs, databases, or external services needed
Web Apps
Building web apps with WandGx
Web app builds use a modern app structure. Understand what to include in your prompt for the best web app output.
- 1Describe the page structure: what pages exist and their purpose
- 2Include auth requirements: who can access what
- 3Specify the data structure: what entities exist and their relationships
- 4Note styling preferences: any design system or brand requirements
- 5List third-party integrations: payment, analytics, email, etc.
Mobile Apps
Building mobile apps with WandGx
Mobile builds use a cross-platform app structure. Include platform-specific details in your prompt for the right output.
- 1List the screens: home, detail, settings, onboarding, etc.
- 2Specify device APIs needed: camera, location, push notifications
- 3Describe navigation: tab bar, nested screens, drawer, or hybrid
- 4Include auth requirements: social login, email, biometrics
- 5Note offline requirements: what should work without network
Validation
Reading and resolving validation reports
Builds that run validation include a report. Learn how to read it and resolve issues.
- 1Check the severity level: critical blocks delivery, warnings and info do not
- 2Find the affected file and line number in each issue
- 3Read the plain-language description and suggested fix
- 4For critical issues: resubmit with a prompt that addresses the root cause
- 5For warnings: evaluate if the issue affects your use case before ignoring
Games
Building games and interactive experiences
Game builds focus public delivery on browser-first output, while source/export remains a beta lane. Choose the right path for your use case.
- 1Pick the path: browser-first for public preview, source/export for beta editor workflows
- 2Describe gameplay: core loop, objectives, controls, and win/lose conditions
- 3List visual requirements: art style, perspective (2D/3D), color palette
- 4Specify audio: background music, sound effects, silence
- 5Note difficulty and progression: levels, unlocks, scoring