design-docs
01Agent
This game is designed in an Obsidian vault outside the repo. Treat these two notes as primary context — for design/doc work, and for knowing what to build next.
Agent
This game is designed in an Obsidian vault outside the repo. Treat these two notes as primary context — for design/doc work, and for knowing what to build next.
Agent
Issues live in this repo's GitHub Issues; use the gh CLI. The repo is public — every issue body and comment is world-readable.
Agent
This repo is backed by a persistent, file-based agent memory — durable facts, decisions, and the why/how behind tracker issues. It lives outside the repo, in the primary session's memory directory.
Agent
Review law for scripts/. Read it before changing a script's outputs or calling one from another script. Provenance: doc/FeaturePlans/ScriptSeamHardening.md.
Agent
explicit outDir/-OutDir).
Agent
Repo-side companion to the machine-generated unity-cli skill (/.claude/skills/unity-cli/, rendered from the binary by unity skill refresh — never edit it; repo deltas live here). The editor-side surface is experimental (com.unity.pipeline) on a beta CLI: re-verify the bugs below after any version bump. Coordination…
Agent
Camera.main never run in Start/OnEnable/Initialize/update loops or any runtime path. Cache in Awake; Initialize(...) only assigns injected references (see AGENTS.md → dependency wiring).
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: