erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
acdream/AGENTS.md
Erik 9444a328fa feat(studio): #156 #157 mockup desktop and font resolver 
Create AGENTS.md as a thin bridge to CLAUDE.md, fix isolated dat-layout previews by normalizing panel roots to the studio canvas, add a --mockup mode that mounts production-backed UI windows into one UiHost, and thread the per-element dat-font resolver through GameWindow's live imports.

Verified with dotnet test and headless studio screenshots for inventory and the mockup desktop.
2026-06-26 12:56:05 +02:00

1.6 KiB
Raw Blame History

Agent Instructions

CLAUDE.md is the source of truth for this repository.

Before doing project work, read CLAUDE.md and follow it. If anything in this file appears to conflict with CLAUDE.md, treat CLAUDE.md as authoritative and update this file rather than carrying a second version of the rules.

Codex Notes

  • Keep this file as a thin bridge for agent tooling that discovers AGENTS.md. Do not duplicate the full project state, roadmap, memory protocol, launch workflow, or domain reference tables here.
  • The project goal is acdream: a modern open-source C#/.NET 10 Asheron's Call client whose behavior faithfully tracks the retail client while using a modern architecture.
  • Align all code and planning work with the architecture document named in CLAUDE.md, the current milestones/roadmap docs, and the relevant memory digests before touching a subsystem.
  • Treat GameWindow.cs as runtime wiring. New substantial behavior belongs in dedicated controllers, sinks, orchestrators, or Core/UI abstractions according to the layer rules in CLAUDE.md.
  • For AC-specific algorithms, wire formats, constants, coordinates, rendering, physics, movement, UI, audio, chat, plugin behavior, or dat handling, read the references named in CLAUDE.md before implementing. Do not guess.
  • Fix root causes. Do not ship workaround guards, retry loops, grace periods, suppressions, or symptom masks without explicit approval.
  • Continue autonomously through implementation, build/test verification, docs, memory updates, and commits when appropriate. The main reason to stop is when visual confirmation from the user is the actual acceptance test.