CLAUDE.md for Phaser

# CLAUDE.md

Project memory for Claude Code in this Phaser repository. Read it before editing. Other agents can follow the same rules.

## Stack

This repository is a Phaser game. Scenes own lifecycle, systems run in update only when they must, and assets are preloaded in the scene that needs them.

## Layout

- Scenes live one file per scene unless the project already groups them.
- Reusable systems sit beside scenes, not inside the boot scene.
- Asset keys are constants. Do not sprinkle string keys through update.

## Commands

- Dev: `npm run dev`
- Tests: `npm test`
- Build: `npm run build`

Use the script the repo already defines when it differs from the command above.

## Conventions

- Preload assets in `preload`. Create objects in `create`.
- Do not allocate textures, text objects, or closures every frame inside `update`.
- Use the physics system the scene already has. Do not mix Arcade and Matter on one sprite.
- Remove listeners and timers in `shutdown`.
- Keep game config in one place. Do not fork a second Phaser.Game.
- Match the language, TypeScript or JavaScript, of the neighboring scene.

## Testing

Add or update tests when behavior changes.

Test pure game rules outside Phaser. Boot a scene only when lifecycle is the bug.

## Style

- Optimize for the next reader over the shortest diff.
- Comment only when the why is non-obvious.
- Name things the way neighboring files already do.
- Do not reformat code you did not change.

## Errors

- Fail at the boundary. Do not swallow errors.
- Log a missing asset once and skip the spawn. Do not throw inside the game loop.

## Scope

- Do the requested task. Do not refactor unrelated code.
- Match the rigor already in the repo. Fix what you touch.
- Ask one clarifying question only when the task cannot be finished without it. Otherwise state the assumption and continue.

## Avoid

- Do not load assets from update.
- Do not leave a physics body alive after the sprite is destroyed.
- Do not use browser `alert` for game errors.
- Do not depend on frame time being 16ms. Scale by delta.

## Done when

- The requested behavior works.
- The scene boots in dev and the update path you touched does not allocate per frame.
- The diff stays inside the task.
- You list anything you could not run.