agent split overview

Guide for agent split overview

Agent Split Strategy

Objective: Split pending work into 3 distinct, non-overlapping agents to accelerate development and ensure migration compatibility.

👥 The 3 Agents

1. Agent 1: Web, Account & Backend (The "Bridge")

Focus: loh-website and loh-backend (Workers). Primary Goal: Implement the Cloudflare Worker Account API using Rust-compatible schemas and polish the Website Store. Domains:
  • loh-website/*
  • loh-cf-workers/account-api
  • loh-cf-workers/reservation-api

2. Agent 2: Engine Stability & UI Core (The "Foundation")

Focus: loh-game Core Systems and UI Framework. Primary Goal: Resolve heavy bug fixing, eliminate panics, and complete the Bevy 0.17 event migration to ensure a stable runtime. Domains:
  • src/systems/ui/* (General UI)
  • src/systems/network (Event Migration)
  • src/systems/world (Core Resources)

3. Agent 3: Gameplay, Economy & Content (The "Builder")

Focus: loh-game Gameplay Mechanics. Primary Goal: Fix the Economy system compilation, implement the Tutorial area (AI + Spawning), and finish Magic VFX. Domains:
  • src/systems/economy
  • src/systems/combat
  • src/systems/tutorial
  • src/systems/ai
  • src/systems/magic

🔄 Shared Constraints

  1. Agent 1 must define TypeScript interfaces that strictly match the JSON serialization of Rust structs in logic-core.
  2. Agent 2 owns mod.rs and global resource registration to prevent conflicts.
  3. Agent 3 must not touch base UI systems (like ui/mod.rs), only their specific domain UIs (e.g., economy/ui.rs).