Making games with Claude

Claude works inside the editor you have open. It reads the open scene the way you see it in the Hierarchy and the Inspector, changes it, writes Rengy Script, presses Play and looks at the result. Every change appears in your window as it is made.

Ask in your own words. In the opened scene, where the flames are, add a light that glows like fire. Claude finds the flame nodes, looks up what each field of a LightComponent does, adds a warm light under each flame, and takes a picture of the viewport to check. With the request finished, one Ctrl+Z removes every light it added.

It reaches all of Rengy: every component and every field the Inspector shows, artifacts and their overrides, scripts, the game’s controls, sprite clips, state machines, property clips, cutscenes, tile maps, sorting layers, translations and .data files.

Connect Claude does four things, and the window says how each went:

• It registers Rengy with Claude Code once, for every project, by running claude mcp add --scope user rengy. If claude is not installed, the window shows that line with a Copy button, to run once Claude Code is installed.
• It adds Rengy to the Claude app’s settings, if the app is installed. The app’s old settings are kept beside the new ones as a backup.
• It writes rules into the project’s .claude/settings.json. Claude may use Rengy’s tools without asking each time. Claude Code’s own file tools may not change scenes, scripts or Rengy’s other files behind the editor’s back.
• It adds a short section to the instructions Claude Code reads in the project’s folder, telling Claude how to work here. Run it again and that section is replaced; the rest of the file is yours.

Nothing else is installed. The editor itself answers Claude, and it listens only on your own computer, never on the network. While Claude is connected, the status bar says Claude connected.

Claude works from what is open. Name things the way you see them, or select them first and say these. Click an empty spot in the viewport and say here: Claude can read where you last clicked.

• Give every crate a box collider the size of its sprite.
• Place three copies of the torch artifact along the corridor, 64 apart.
• Make the knight jump when I press Space, then play it and check that it jumps.
• Add a run state to the hero’s state machine that plays the run clip while speed is above 10.
• Paint a floor of tile 4 from x 0 to 30 on the ground layer.
• Add a French translation for every string in the menu.

Claude looks before it changes anything. It reads the scene, and it reads what a component’s fields mean before setting them. When it gets a name wrong, Rengy answers with the names that exist, and Claude corrects itself. A value outside a field’s range is refused, not quietly clamped.

For a script, Claude reads the Rengy Script reference, writes the file, reads what the checker says and fixes it. Then it attaches the script, presses Play, holds keys down and reads the running scene and the Console to see whether it worked. While the game plays, Claude can look but not change the scene; it stops the game first.

Each request is one step in the editor’s history, named in it as Claude: …. One Ctrl+Z takes back the whole request: the nodes and fields, and every script or asset file it wrote. A script or asset it created is removed again. Ctrl+Y puts it all back.

• Claude never saves the scene. When you like what you see, press Ctrl+S.
• A script or asset file is written as soon as Claude changes it, because the game runs from the files. It is still part of the request’s undo step.
• Claude does not write over your unsaved work. When a script or an asset is open in a panel with changes you have not saved, Claude asks you to save or discard them first.
• If you change a file after Claude did, undoing Claude’s step leaves your version as it is, and the status line says so.

• It deletes no files, and it reaches nothing outside the project’s folder. Bring a new picture or sound into the project yourself, by dragging it into Assets.
• It does not change the project’s settings, its levels, a picture’s pixels, a texture’s import settings or a sprite sheet’s regions yet. Do those in their panels.
• Claude Code’s own terminal can still run any command. The rules Connect Claude writes stop its file tools from editing Rengy’s files, and its instructions tell it to work through Rengy, but a rule cannot stop a shell command. Keep the project in version control, as you would anyway.