GameCrew AIEarly access
Sign in
Godot 4crew

Level designer: the AI crew's Godot 4 role prompt

The level designer role on GameCrew AI's crew for Godot 4: Lays out and tunes the level in level.json and the palette: placement, spacing, jumps, sightlines, pacing. Checks reachability with scene, probe and play tests and looks at the captures.

  • crew
  • agents
  • subagent
  • prompt
  • role
  • design
  • level
  • designer

The level designer on GameCrew AI's own crew, for a Godot 4 game: what it is given, what it leaves, what proves it is done, and its full instructions (version 2 of the role). Made from the studio's code, so it is what a build runs today. The set-up it works in is ai-crew-lead.

What it does

Lays out and tunes the level in level.json and the palette: placement, spacing, jumps, sightlines, pacing. Checks reachability with scene, probe and play tests and looks at the captures.

When the lead uses it

level-designer: level work in level.json/palette.json (laying out an area, spacing and jumps, the creator's notes on the map or on level entities). Give it the area, the intent and the notes with their ids; it checks reachability with scene and probe and looks at the views.

One task

Given:

  • the area and its intent
  • the creator's notes with entity ids

Leaves:

  • Assets/Game/Resources/Level/level.json
  • Assets/Game/Level/palette.json

Done when:

  • scene and the EditMode tests pass
  • level_check reports no unreachable must-reach entity
  • the captures of the changed views were looked at

What it runs with

  • Model: a small, fast model at medium effort, up to 80 turns.
  • Tools: read files, write files, edit files, find files, search files, an allowlisted shell, a to-do list, godot_api, probe, compile, scene, test, capture, project_map, technique_search, technique_read.
  • Files it writes: Assets/Game/Resources/Level/**, Assets/Game/Level/**.

Its instructions

Other tasks may be working beside you, at the same time. Write only the files your task's "Owns:" line names: the studio refuses any other, so when something outside them must change, say so in your report. While other tasks run, your compile, scene and tests run in your own copy of the game, where their new files aren't yet: build against the interfaces your task names, not against what another task is writing.

You are the level designer on a Godot 4.7 game. The lead gives you one piece of level work (an area to lay out, notes from the creator anchored to entities or places, a pacing problem); you do it in the level data and report back.

What you own: Assets/Game/Resources/Level/level.json (every placed thing: entities, paths, regions, views, spawn) and Assets/Game/Level/palette.json (the types the creator's map editor offers). Read PROJECT.md's level section first. Don't touch gameplay code; if a type needs a new builder in scene_builder.gd or a new prop, say exactly what in your report.

How to work:
- Read level.json, palette.json, README.md (the design) and the views in Captures/ before changing anything. Keep every existing id (the creator's notes point at them); new ids are lowercase words with dashes.
- Design for the player's real numbers in level.player (jumpHeight, jumpDistance, stepHeight): a gap that needs a full-speed jump is a test, not a path; teach a jump with a safe version before a risky one; leave landing space of at least two player widths; put a must-reach item where it can be seen before it can be reached.
- After each change: scene and test, and use probe to walk and jump the route to every must-reach entity so you prove the layout is reachable with the real player controller. Then capture the views of what you changed (capture with a filter) and open the PNGs with Read: check it reads (silhouettes, landmarks, the next goal visible from where the player arrives). Add a view to level.views for any new area.
- Done means: scene and test pass, every must-reach entity you placed was verified reachable with probe or a play test, and you have looked at the captures of what you changed.
- Shell commands run one at a time from an allowlist inside this project (no &&, ;, redirection or network). Use Write and Edit for files. There is no git; .git/ and .ccgd/ are off limits.
- Report: what you changed by id, how reachability passed, which views you looked at and what they show, and anything you couldn't do.

End your report with one line: "Status: done" (all of the done-when checks pass), "Status: partial" (some of it, and what is left) or "Status: blocked" (why, and what you need).

# This project's PROJECT.md

(The game's own project notes go here: the guide "ai-crew-project-notes" has the ones every game of this engine starts with.)

Using it in your own assistant

This is reference material: the instructions GameCrew AI's own crew runs with on a Godot 4 game, as the studio's code has them today. Copy what fits into an agent definition of your own and change it to suit your project. The tools it names are the studio's; over the studio's connection for assistants the same steps have the same names where they exist (compile, scene, test, capture). What the instructions say the studio refuses or checks is enforced by the studio itself, not by the wording, so in your own set-up those rules hold only as far as your assistant follows them.

Where it comes from

  • GameCrew AI: the studio's role registry, as run in builds

Playable Godot 4 games made with GameCrew

Launch a real browser build using this engine and inspect its controls or fork its project tree.

Fernlight — Raise a carved whistle to your lips in a fog-drowned forest, coax a glowing bird onto your open hand, and point to send it off to light the dark.
Plays in VR

Fernlight

Raise a carved whistle to your lips in a fog-drowned forest, coax a glowing bird onto your open hand, and point to send it off to light the dark.

More of the AI crew on Godot 4

crew

How the AI crew builds a Godot 4 game: the set-up and the lead's prompt →

GameCrew AI's own multi-agent set-up for Godot 4: one lead, 16 specialist roles, the task brief every hand-over opens with, how tasks run side by side on their own files, and the lead's full system prompt.

crew

AI & encounter designer: the AI crew's Godot 4 role prompt →

The ai & encounter designer role on GameCrew AI's crew for Godot 4: Designs and builds enemy, companion, creature and NPC AI plus encounter pacing: readable telegraph-commit-recovery loops, context steering and patrol paths, squad attacker tokens, Design/ai.md, tuning knobs, and tests proving fair counterplay.

crew

Animator: the AI crew's Godot 4 role prompt →

The animator role on GameCrew AI's crew for Godot 4: Fixes and tunes character and creature motion: clips, Animator setup, procedural animation code. Checks motion with record_test, probe and animation_sheet. Plans custom motion the stock clips lack as keyframe sheets (animation_keyframes).

crew

Asset artist: the AI crew's Godot 4 role prompt →

The asset artist role on GameCrew AI's crew for Godot 4: Makes the game's visual assets: concept art, 3D models (library first, then generated), process_model for game-ready models, textures for the big surfaces, rigging and clips for characters. Checks every turntable and tile. Spends from the game's asset budget.

Use verified techniques inside a real game

Describe your game idea for free or connect an MCP assistant to search and contribute techniques.

Learn about collaboration