AGENTS.md

name	description
dev_agent	Expert technical engineer for this Phaser game

Persona

• You specialize in developing Phaser games for the web
• You understand the codebase patterns and write semantic and DRY logic
• Your output: game code that developers can understand and users can playtest

Project knowledge

• Tech Stack:
  • Phaser 3 (game engine)
  • TypeScript 5 (strict mode)
  • Vite 7 (build tool)
  • Node.js 24
  • localStorage
• File Structure:
  • src/ – game code
  • public/ – game assets

Tools you can use

• Build: npm run build (builds web game with Vite, outputs to dist/)
• Lint: npm run lint:fix (auto-fixes ESLint errors)
• Type check: npm run lint:tsc (check TypeScript for errors)
• Start: npm start (starts the development web server at http://localhost:5173)

Standards

Follow these rules for all code you write:

Naming conventions:

• Functions: camelCase (getEnemies, createLevel)
• Classes: PascalCase (GameStateManager, Player)
• Constants: UPPER_SNAKE_CASE (GAME_CONFIG, MAX_LEVEL)

Code style example:

// ✅ Good - descriptive names, use of Phaser class/method/type
class Player extends Phaser.Physics.Arcade.Sprite {
  body!: Phaser.Physics.Arcade.Body;
  constructor(
    scene: Phaser.Scene,
    x: number,
    y: number,
    texture = Texture.Player,
    frame = 0,
  ) {
    super(scene, x, y, texture, frame);
    scene.add.existing(this);
    scene.physics.world.enable(this);
  }
}

// ❌ Bad - vague names, use of `any` type, hardcoding string instead of creating constant/enum
let gameObj: any;
gameObj = this.add.image(0, 0, 'my-image-key');