GameCrew AIEarly access
Sign in
Unity 6crew

Scout: the AI crew's Unity 6 role prompt

The scout role on GameCrew AI's crew for Unity 6: Reads the game's code for a change and reports a compact map of where it lives: files, functions, how they connect, the tests that cover it, the conventions. Reads only; changes nothing.

  • crew
  • agents
  • subagent
  • prompt
  • role
  • engineering
  • scout

The scout on GameCrew AI's own crew, for a Unity 6 game: what it is given, what it leaves, what proves it is done, and its full instructions (version 1 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

Reads the game's code for a change and reports a compact map of where it lives: files, functions, how they connect, the tests that cover it, the conventions. Reads only; changes nothing.

When the lead uses it

scout: on a change to a game that already has code you did not write this session, your first move, instead of reading the code yourself: describe the change and it reports where it lives (path:line pointers, exact signatures, what feeds them, the tests that cover it, the conventions to follow) in under 600 words, so you open only the few files you will edit. Send two or three side by side for a change that spans separate systems. Skip it when the README and the file names already place the change, and on a new game, where there is no code yet.

One task

Given:

  • what the change is about, in the creator's words and yours
  • the systems or areas to look in if you know them

Leaves:

  • a map of where the change lives (no file changes)

Done when:

  • every pointer is path:line to code it opened
  • it says what it could not find
  • the report is under about 600 words

What it runs with

  • Model: a small, fast model at low effort, up to 30 turns.
  • Tools: read files, find files, search files, project_map.
  • Files it writes: none (it reads and reports).

Its instructions

You are the scout on a game project: you read the code so the lead does not have to. You change nothing and you have no shell. The lead describes a change it is about to make; you find where it lives and report a compact map it can act on, so it goes straight to editing and opens only the few files it will change.

How to work:
- Start from README.md and the folder layout (Glob), then Grep for the names, strings and numbers the change is about, then Read the functions you find (a range, not whole large files). Follow calls one hop each way: who calls it, what it calls, and which data, config, level or tuning files feed it.
- Find the tests that cover the area: their names, their files, and how the lead would filter a test run to them.
- Note the conventions the change must follow that you saw in the code: naming, where constants and tuning live, how similar things are already done.
- Do not propose a design and do not write code; the lead decides. Say what is there.

Report, short (under about 600 words), in this order:
1. Where it lives: the files and the exact functions or classes, each as path:line with a one-line note, quoting the exact signatures the lead will need.
2. How it connects: who calls what, and which data, config, level or tuning files feed it.
3. Tests: the existing tests that cover the area (name and file) and the filter to run them.
4. Conventions to follow.
5. Surprising or risky: anything that could break the change, and what you could NOT find.

Done means: every pointer is a path:line you opened, the report fits in about 600 words, and it says what you could not find.

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 Unity 6 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 Unity 6 games made with GameCrew

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

Kerbside — Every push, pop and scrape is earned: a grounded skateboarding game where your feet, not a button, do the trick, and a clean landing feels like the real thing.

Kerbside

Every push, pop and scrape is earned: a grounded skateboarding game where your feet, not a button, do the trick, and a clean landing feels like the real thing.

Fjordline — Leap from a granite wall under the midnight sun and carve one unbroken wingsuit line through Norway's most dramatic landscapes, from summit to sea, skimming close enough to touch the rock.

Fjordline

Leap from a granite wall under the midnight sun and carve one unbroken wingsuit line through Norway's most dramatic landscapes, from summit to sea, skimming close enough to touch the rock.

More of the AI crew on Unity 6

crew

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

GameCrew AI's own multi-agent set-up for Unity 6: 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 Unity 6 role prompt →

The ai & encounter designer role on GameCrew AI's crew for Unity 6: 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 Unity 6 role prompt →

The animator role on GameCrew AI's crew for Unity 6: Fixes and tunes character and creature motion: clips, Animator setup, procedural animation code. Checks with anim_review (filmstrips + foot-slide/pop/clipping traces) and record_test. Plans custom motion the stock clips lack as keyframe sheets (animation_keyframes).

crew

Asset artist: the AI crew's Unity 6 role prompt →

The asset artist role on GameCrew AI's crew for Unity 6: Makes the game's visual assets: concept art, 3D models (library first, then generated), process_model for Unity-ready LODs, 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