AgentSkillsCN

modify-game

当您对 Wave Assault 游戏进行任何代码修改时，此技能可精准定位并指引您前往所需修改的文件。在编辑游戏代码之前，请务必先使用此技能。

SKILL.md
--- frontmatter
name: modify-game
description: Use when making any code change to the Wave Assault game. Routes you to the exact files needed for any modification type. Use this before editing game code.
allowed-tools: Read, Edit, Write, Grep, Glob, Bash
argument-hint: "<what-to-change>"

Modify Wave Assault

You are modifying a browser-based wave shooter. Follow this workflow strictly to minimize token usage.

Step 1: Classify the change

Read $ARGUMENTS and classify into one of these categories:

CategoryFiles to readFiles to edit
Balance/tuning (speeds, health, damage, spawn rates)js/config.jsjs/config.js, maybe js/game.js
New enemy typejs/config.js, js/entities.js, js/game.js:spawnWave, js/render.js:drawSpaceEnemy+drawWolfAll four
New powerup typejs/entities.js, js/game.js:update (bullet-powerup section), js/render.jsAll three + js/config.js
Player movementjs/game.js:update (player movement section)js/game.js
Shooting mechanicsjs/game.js:update (auto-fire section), js/entities.js:createBulletBoth
Visual/sprite changesjs/render.jsjs/render.js
HUD/UI changesjs/ui.js, index.htmlBoth, maybe styles.css
Camera/pose behaviorjs/webcam.jsjs/webcam.js
Game flow (start, end, restart)js/main.jsjs/main.js, maybe js/ui.js
New themejs/render.js:render, js/ui.js:selectThemeBoth, plus styles.css and index.html
Styling onlystyles.cssstyles.css
Super weapon / nukejs/game.js (activateSuperWeapon + checkSuperWeaponThreshold), js/state.js, js/render.js (flash effect), js/ui.js (HUD progress)All four + js/config.js for tuning
Audio/musicjs/audio.jsjs/audio.js
New game mechanicjs/state.js (add state), js/game.js (add logic), js/render.js (add visuals)All three + js/main.js (reset in startGame)

Step 2: Read ONLY the files from the table above

Do NOT read the full codebase. Read the minimum files needed.

Step 3: Make the change

Key rules:

  • •All files share globals — no imports/exports needed
  • •Script load order: config → state → entities → input → webcam → audio → game → render → ui → main
  • •gameState.players[] is the source of truth for player data
  • •After modifying player 0's .crowdSize, also set gameState.crowdSize (legacy compat)
  • •New CONFIG entries go in js/config.js
  • •New state fields go in js/state.js AND must be reset in js/main.js:startGame()
  • •New entity factories go in js/entities.js
  • •Drawing code always goes in js/render.js, game logic in js/game.js
  • •Per-player arrays use index 0 for P1, index 1 for P2
  • •Kill attribution: bullet kills → bullet.owner, shield/collision → player index i, enemies passing bottom → no player (skip nuke credit)
  • •Super weapon charges are per-player: gameState.playerKills[i], superWeaponCharges[i], superWeaponNextThreshold[i]
  • •Both themes must be considered: check gameTheme === 'unicorn' for theme-specific rendering
  • •HUD: single-player elements in #singlePlayerHud (right side), multi-player in #multiPlayerHud with #p1Hud/#p2Hud

Step 4: Test considerations

  • •Open index.html in a browser (no build step needed)
  • •Check both themes (space + unicorn) if you changed rendering
  • •Check both control modes (keyboard + camera) if you changed input/movement
  • •Check both 1P and 2P if you changed per-player logic
  • •Nuke progress is shown on the right-side HUD (single: #nukeProgress, multi: #p1Nuke/#p2Nuke)