magicciv/tooling/claude/dot-claude/instructions/task-runner.md
Natalie 93f94ac78f feat(@projects/@magic-civilization): implement claude agent workflows
Co-Authored-By: Lilith Autocommit <noreply@atlilith.com>
2026-04-17 03:43:00 -07:00

1.5 KiB

Task Runner & Screenshot / Env Config

Load when: using ./run, capturing screenshots, setting up proof scenes, or configuring .env.* files.

Task Runner (./run)

Central entry point for dev, export, deploy commands.

./run play                         # Launch the game locally
./run editor                       # Open Godot editor
./run lint                         # gdlint src/game/engine/src/
./run verify                       # lint + typecheck + cargo check + tests
./run test                         # GUT tests + Rust tests + vitest
./run screenshot [name] [scene]    # Capture + SCP to EDIT host ($SCREENSHOT_HOST)
./run export [version]             # All platforms in parallel

Screenshot & Visual Verification

./tools/screenshot.sh [name] [scene] [delay]

Screenshots are captured in the RUN host's Flatpak user data and SCP'd back to $SCREENSHOT_HOST:~/Desktop/magic_civ_<name>.png (typically the EDIT host). Set $SCREENSHOT_HOST to match your workstation for review access.

Proof Scenes (src/game/engine/scenes/tests/)

Self-capturing test scenes. Each phase should have a proof scene that sets up minimal game state, renders claimed features, auto-captures, and quits. See phase-gate-protocol.md for the approval ritual.

Environment Config (.env.*)

EnvConfig autoload reads .env (base) then .env.development (overrides) at startup:

  • .env.productionFORCE_DISABLE_FOGOFWAR=false
  • .env.developmentFORCE_DISABLE_FOGOFWAR=true, FORCE_UNLIMITED_RESEARCH=true