Project notes for a Pulse game: layout, conventions and checks the AI crew works to
The notes every Pulse game on GameCrew AI starts with and every crew member reads: where code, levels, tuning and assets live, the conventions to keep, and the checks a change must pass.
- crew
- agents
- prompt
- project
- notes
- layout
- conventions
- template
The notes file every Pulse game on GameCrew AI starts with. The lead and every specialist get it after their own instructions, so the role prompts (ai-crew-lead and the others) refer to it as PROJECT.md. A game's own copy changes as the game does.
A Pulse game
Pulse is a deterministic engine made for this: the game's rules are TypeScript systems run in a sandbox, everything placed in the world is JSONC data, and a scenario replays the game to prove a thing can be done. .pulse/ is the engine's (its cache and types/pulse.d.ts, every signature you can call), spec/scenarios/ccgd/ is the studio's: read them, never change them.
### Layout
game.json:mode(3d),entry(the first area),hz,gravity_y,seed. Leaveengine,title,namespaceandbuiltin_audio(false: every sound is a generated file; a cue without one is silent) alone.contracts/<domain>.decl.jsonc+ the generatedcontracts/<domain>.ts: the game's components, events and tuning. Never edit either by hand: add withpulse_declare("component Health { hp: int(0..99)=5 } persist","event Damaged { target: entity, amount: int(1..) }","tuning combat { iframes_s: 0.4 }"; field typesint(lo..hi),num,bool,sym,entity,oneOf(a,b),flags(a,b),list(T, cap);persistkeeps it across areas and saves,cosmetickeeps it out of the simulation's state).systems/*.ts: the rules. Eachsystem(name, { after: "physics" }, (dt) => { ... })is exported (default or named).lib/*.tsfor shared helpers.world/<area>.area.jsonc: one area each:environment(below),entities(one per line, sorted by id),views(the camera shots captures take),reach(what the search bot must be able to get to), optionalterrain,water,foliage.prefabs/<name>.prefab.jsonc: reusable entities ("prefab": "orb"in an area; an area's components override the prefab's).tuning/<ns>.jsonc: the numbers. Read them in systems where used (movement.run_speed), never at module load.spec/scenarios/<area>/<name>.jsonc: the tests.- Assets:
Assets/Game/Resources/Models/<slug>.glb,Audio/<cue>.wav,Fonts/,textures/(made and imported for you; see the asset notes). Reuse this game's assets first, then the library; make only what nothing fits (reason), never duplicating unless asked.
### Systems (import { ... } from "pulse")
query(A, B)live entities with both;find("id");near(e, radius_m, Comp); a component's fields ase.camelName.field(p.score.orbs);e.pos(read-only),e.vel(writable),e.yaw,e.grounded,e.has(C),e.add(C, init),e.remove(C).emit(Ev, payload)/events(Ev);spawn({ id, pos, tags, components }),despawn(e),teleport(e, pos),travel(area, spawnId).input():left right up down jump dash interact attack aim crouch,axisX axisY lookX lookY,hotkey. Keys: WASD/arrows, Space, Shift, E, J/Enter/left mouse (attack), Q/right mouse (aim), C, V, 1-9; gamepads too.sfx(cue),sfxAt(cue, pos),music(cue),ambience(cue);vfx("burst" | "spark" | "ring" | "shockwave", { pos, color, count }),shake(amount);raycast,lookAt,setYaw;playAnim,blendAnim1D/2D;navMoveTo,navPatrol;rand()(seeded).- UI is immediate-mode, called every tick:
uiPanel,uiRow/uiColumn,uiText,uiButton(id, label)(true on the tick it's clicked),uiCard,uiChoice,uiDialogue,uiToast(text),setScreen("title" | "play" | "pause" | "victory" | "gameover", { title, subtitle }). HUD as components:HudBar { label, value, max, x, y, w, h, r, g, b },HudPrompt { text, offset_y }. Colours and fonts come fromAssets/Game/Resources/ui-theme.json(fonts inResources/Fonts/): use them, not hand-picked ones. - Saves:
saveSet(key, value),saveGet(key). - Determinism (the compile refuses otherwise): no module-level
let/var/arrays/objects (state lives in components), noMath.random,Date,asyncorPromise. Systems are pure functions of the world and the input.
### An area's environment Flat keys only (any other key is ignored; the compile warns): colours as "#rrggbb".
- Sky and sun:
sky_zenith,sky_horizon,sky_ground(what shows below the horizon: keep it darker than the sky),bg_color,physical_sky(bool),volumetric_clouds(0..1),skybox;sun_dir: [x, y, z](the way the light travels:[-0.4, -1, -0.3]is high, a small y is low and long),sun_color,sun_intensity,sun_shadows,sun_disc_size;ambient_color,ambient_intensity,ibl_intensity. - Air:
fog_density(0.002 a light haze; 0.01 already washes out an area 50 m across; there is no fog colour key),volumetric_fog_density,volumetric_fog_rgba. - Post:
tonemap("aces","agx"),exposure,bloom_intensity,bloom_threshold,contrast,saturation,color_temp,vignette; andtaa,contact_shadows,ssr_intensity,rt_gi_intensity,rt_reflections,dof_focus_dist,dof_focus_range,dof_blur. - A mood is mostly the three sky colours, the sun's direction and colour, and the fog: change those first, then check a capture.
### World components (used in areas and prefabs)
Transform: [x, y, z]or{ x, y, z, yaw }; Y up, -Z north, yaw 0 faces north; metres.Mesh { primitive: box|sphere|capsule|cylinder|wedge|arch|stairs|crystal, w, h, d, color, emissive, roughness, metallic, texture, normal_texture, cast_shadow, clearcoat, subsurface, shader }or{ asset: "Models/x.glb", scale }.Body { kind: static|dynamic|kinematic|sensor, shape: box|sphere|capsule|convex_mesh, w, h, d, radius, mesh }.- The player:
Player {},CharacterMotor3D {}(tuned intuning/movement.jsonc),CameraRig { mode: orbit_follow|first_person|top_down_aim|fixed, target, distance, height, fov_deg, pointer_lock },Animator { clip, loop, blend_s },IkRig { foot_ik: true }. - Light and life:
Light { kind: point|spot, r, g, b, intensity, range, cast_shadows },ParticleEmitter { shape, rate, life_s, speed, size, r, g, b, emissive },AudioSource { clip, loop, volume, spatial, ref_dist, max_dist, playing },Decal,LodGroup,ProceduralMotion(bob, breathe, lean),ProceduralGait(legged creatures),ProceduralChain(tails, tentacles),NavAgent,Joint,Vehicle. - Place with
pulse_editwhen position matters:place orb orb-4 at 3 1 -6,snap pier-2@south to pier-1@north,connect ramp-1 ramp from ledge-a@top to 0,0,-8 width=2,jump_path a -> b(checks a jump is makeable),move,set id.Comp.field=json,tune movement.jump_impulse=12,terrain create|sculpt|flatten|ramp,view play preset=player. Editing the JSONC directly is fine too: one entity per line.
Scenarios: how the game is proved
{ "area": "area-1", "bot": "reach", "target": "orb-1", "inputs": ["move", "jump"], "for_s": 4.0,
"until": "event(OrbCollected)", "expect": ["event(OrbCollected) by 3.5s", "player.Score.orbs >= 1"] }
bot:reach(a search bot that finds the inputs to get totarget),idle,patrol; or atapeof timed input ({ "tick": 0, "hold_ticks": 30, "buttons": ["north", "jump"] },{ "click_ui": "start" }).startsets{ area, at: spawnId, screen, give: { Comp: {...} }, save }.- Predicates:
reached(id),event(Name, field=v),played(cue),ui_visible("id"),player.Comp.field >= n,alive(id),count(tag) == n,died,t >= 2s; inexpectalsoby Ns,at Ns,always,never, androbust >= 3/4(still works with ±2 ticks of timing). - A scenario passes only when witnessed: replayed in full, every expectation held. A gate the player must not pass yet:
bot: reachwith"expect": ["never reached(door-2)"](it counts beside a witnessed scenario).pulse_runany scenario orreach <id>to see the run tick by tick, thenpulse_keepthe ref to save it as a scenario.
Using it in your own assistant
This is reference material: the instructions GameCrew AI's own crew runs with on a Pulse 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 project template each game starts from
More of the AI crew on Pulse
How the AI crew builds a Pulse game: the set-up and the lead's prompt →
GameCrew AI's own multi-agent set-up for Pulse: 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.
AI & encounter designer: the AI crew's Pulse role prompt →
The ai & encounter designer role on GameCrew AI's crew for Pulse: 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.
Animator: the AI crew's Pulse role prompt →
The animator role on GameCrew AI's crew for Pulse: Fixes and tunes character and creature motion: clips, Animator setup, procedural animation code. Checks motion with pulse_look and animation_sheet. Plans custom motion the stock clips lack as keyframe sheets (animation_keyframes).
Asset artist: the AI crew's Pulse role prompt →
The asset artist role on GameCrew AI's crew for Pulse: 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.