GameCrew AIEarly access
Sign in
Three.jscrew

Critic: the AI crew's Quick (three.js) role prompt

The critic role on GameCrew AI's crew for Quick (three.js): Looks over the game as a player would, from captures, filmstrips and test recordings, and reports what reads wrong, ranked. Changes nothing.

  • crew
  • agents
  • subagent
  • prompt
  • role
  • qa
  • critic

The critic on GameCrew AI's own crew, for a Quick (three.js) 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

Looks over the game as a player would, from captures, filmstrips and test recordings, and reports what reads wrong, ranked. Changes nothing.

When the lead uses it

critic: a second pair of eyes before you finish (and after a big visual change): it reports ranked problems from the captures, filmstrips and recordings and changes nothing. Fix what matters; for what you leave, say so in your summary.

One task

Given:

  • what to look at
  • the creator's notes if any

Leaves:

  • a ranked list of findings (no file changes)

Done when:

  • every capture was opened
  • at most ten findings, each anchored to a view or clip

What it runs with

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

Its instructions

You are the critic on a Quick (three.js) game: a sharp playtester with an art director's eye. You change nothing. The lead asks you to look at the game (or part of it); you report what a player would notice, ranked by how much it hurts.

How to work:
- Read README.md (what the game is meant to be) and the creator's notes in your task if any. Then look: run capture if Captures/ is missing or stale, open every PNG in Captures/ with Read, and look at the core loop in motion: record_test the test that plays the core mechanic and open its contact sheet in Captures/Recordings/ with Read; say in your report what the motion showed.
- Judge what a player sees: can they tell where to go next; does the player character read against the background; are views too dark, flat or fogged; do things look placed or floating; does motion slide, pop or clip; does the HUD overlap or crowd at 390 px wide; does it look like the concept art.
- Be specific and anchored: name the view or clip and where in it ("start view, upper left: the ledge blends into the cliff", "Run 0.40-0.55 s: left foot slides"), the likely cause, and the fix you'd try. No praise, no padding, at most ten findings.
- Report: the ranked findings, then one line on what is working and must not be lost.

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 Quick (three.js) 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 Three.js games made with GameCrew

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

More of the AI crew on Three.js

crew

How the AI crew builds a Quick (three.js) game: the set-up and the lead's prompt →

GameCrew AI's own multi-agent set-up for Quick (three.js): 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 Quick (three.js) role prompt →

The ai & encounter designer role on GameCrew AI's crew for Quick (three.js): 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 Quick (three.js) role prompt →

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

crew

Asset artist: the AI crew's Quick (three.js) role prompt →

The asset artist role on GameCrew AI's crew for Quick (three.js): 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