Create a game with AI

Chat works with your current project. Give it a clear, verifiable task, then follow this loop: Describe the goal → Provide file context → Let Chat make changes → Review the diff → Run the game → Report the actual result.

Chat shares project context but still needs a clear task boundary

Suitable tasks for Chat

Pink Demo's interface is stored in assets/main.scene. ClickGame.ts handles clicks, scoring, movement, and reset. The ClickGame component on GameController connects to scene objects through its Score Label, Target, and Reset Button Inspector references. Specify whether a task changes the scene interface or gameplay behavior.

• Explain the scoring and reset call paths in ClickGame.ts.
• Change scene text or colors while preserving node names, references, and behavior.
• Propose a minimal fix based on the first error in the Problems panel.
• Locate the scene's Sprite reference to pink-target.png and the target node bound to the script.
• Add a checklist for the fixed acceptance behavior.

A request to finish gameplay, assets, refactoring, builds, and publishing together makes it harder to identify which change solved the problem.

Example request

Goal: change the restart label to "Play Again".
Read assets/main.scene and assets/scripts/ClickGame.ts.
Edit only the Label text at Canvas/ResetButton/Label in the scene.
Preserve scripts, node names, Inspector references, scoring, TARGET_POSITIONS, and dependencies.
Acceptance: clicking scores 1 point; restarting resets to 0.
Explain your plan before editing.

This prompt defines the goal, the boundaries, and the way to verify the result.

Permissions and tool calls

Chat may request permission to run commands, edit multiple files, or access external resources. Check the goal, affected scope, and recovery method before approving. Pay particular attention to deletion, overwriting, dependency installation, uploads, and publishing.

Continue with Provide useful context.