Vibe code an HTML5 browser game
The developer of Xenodochium built the game with Gemini, hit repeated errors, and worked around them by starting a fresh chat. Task: The developer guided Gemini through game goals and existing code, narrowing scope via prompts before requesting output. When chats stalled with generic errors, they manually restarted sessions and re-supplied all related scripts to continue iteration. This workflow relied on human context management to bypass tool instability.; tools: Gemini. Human role: The developer guided Gemini through goals and existing code, narrowed scope via prompts, and manually managed context by starting fresh chats to resolve errors.; limitations: Gemini chats are prone to stalling with generic errors, requiring manual session resets and full context re-supply. The tool may leak internal markup or introduce regressions when fixing bugs. Success depends on the user's patience and ability to modularize prompts, as single-chat workflows proved unstable for this task..
Tools
Published on Agent Work Atlas:
Overview
The developer of Xenodochium built the game with Gemini, hit repeated errors, and worked around them by starting a fresh chat.
Workflow
The developer guided Gemini through game goals and existing code, narrowing scope via prompts before requesting output. When chats stalled with generic errors, they manually restarted sessions and re-supplied all related scripts to continue iteration. This workflow relied on human context management to bypass tool instability.
Reported result
The process yielded a working inventory manager for basic resources with placeholders for complex items. However, Gemini's fixes frequently introduced new errors and leaked internal markup into the code. The developer reported significant frustration due to repeated 'Something went wrong' failures and incorrect initial fixes.
Human role
The developer guided Gemini through goals and existing code, narrowed scope via prompts, and manually managed context by starting fresh chats to resolve errors.
Limitations
Gemini chats are prone to stalling with generic errors, requiring manual session resets and full context re-supply. The tool may leak internal markup or introduce regressions when fixing bugs. Success depends on the user's patience and ability to modularize prompts, as single-chat workflows proved unstable for this task.
Try it
Act as a game developer using Gemini to build an HTML5 inventory system. Input: [Game Goal], [Existing Code Snippets], [Error Logs]. Step 1: Describe goals and scope to Gemini. Step 2: Request code updates. Step 3: If 'Something went wrong' occurs, start a new chat and paste all related scripts plus the error. Step 4: Iterate until a working script is returned. Deliverable: A functional JavaScript inventory manager. Quality Check: Verify no internal markup leaks and confirm basic resource handling works. Metric: Time to achieve a stable prototype without context stalls. Note: This is a suggested pilot; human verification of code functionality is required before integration.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.