Imported from Lookies09/unity-mobile-horde-lab (AGENTS.md). Install upstream with npx skills add Lookies09/unity-mobile-horde-lab. Copyright stays with the author.

Repository Guidelines

Project Structure & Module Organization

This is a Unity 6000.5.9f1 URP project. Runtime C# code belongs in Assets/Scripts/, with each class in a same-named file. Scenes are in Assets/Scenes/; Benchmark.unity is the controlled performance scene. Reusable meshes and prefabs belong in Assets/Prefabs/, pipeline assets in Assets/Settings/, and documentation in Docs/. Keep every Unity .meta file beside its asset.

Build, Test, and Development Commands

• Unity.exe -projectPath . opens the project in the configured Unity Editor.
• In Unity, use File > Build Profiles to select Android and build a player; no repository build script is defined.
• In Unity, open Window > General > Test Runner and run EditMode or PlayMode tests.
• Headless EditMode example: Unity.exe -batchmode -quit -projectPath . -runTests -testPlatform EditMode -testResults TestResults/editmode.xml.

Open Benchmark for controlled profiling. Validate meaningful performance changes on Galaxy A9 and Galaxy S22, not only in the Editor.

Coding Style & Naming Conventions

Use four spaces in C# files and small, focused MonoBehaviours. Use PascalCase for types, methods, and public members; camelCase for locals and serialized fields; use descriptive PascalCase names for assets and scenes. No formatter or linter is configured, so match nearby code manually.

Testing Guidelines

The Unity Test Framework is installed. Lightweight EditMode tests live in Assets/Tests/Editor/ and cover spawning, target initialization, and clearing; there is no coverage threshold. Name new test files *Tests.cs, and keep EditMode logic separate from PlayMode scene behavior. Record enemy count, FPS/frame time, CPU/GPU timings, and device for benchmark runs.

Commit & Pull Request Guidelines

Only an initial commit exists, so no established message convention is visible. Use short, imperative commit subjects. PRs should explain the problem, measurement, hypothesis, implementation, result, and conclusion; include linked issues when applicable, plus test/build results, device details, and profiler screenshots for performance changes. Include scene, asset, and .meta changes together.

Repository Hygiene

Do not commit generated Unity folders such as Library/, Temp/, Logs/, obj/, or local UserSettings/; the root .gitignore covers them. Do not store credentials or device-specific signing keys in project settings.