| # Unity Agent Knowledge Base |
|
|
| This directory contains markdown knowledge entries the agent consults when |
| generating Unity projects. Each file is a short, focused reference on one |
| area of Unity development. |
|
|
| ## Entries |
|
|
| | File | Topic | |
| |----------------------------|------------------------------------------------------------| |
| | `unity_fundamentals.md` | MonoBehaviour lifecycle, GameObjects, components, coroutines | |
| | `unity_physics.md` | Rigidbody, colliders, raycasting, physics vs frame step | |
| | `unity_rendering.md` | Materials, shaders, lighting, post-processing, LOD, fog | |
| | `unity_navigation.md` | NavMesh, NavMeshAgent, AI state machines, obstacles | |
| | `unity_input_system.md` | Legacy Input Manager, mouse-look, the new Input System | |
| | `unity_ui.md` | Canvas, HUD, health bars, TextMeshPro, layout | |
| | `unity_audio.md` | AudioSource, 3D audio, AudioMixer, AudioManager pattern | |
| | `open_world_design.md` | Procedural generation, LOD, streaming, day/night, save | |
|
|
| ## How the agent uses these |
|
|
| The orchestrator can embed the contents of these files as context for the |
| LLM. The system prompt instructs the LLM to "consult the knowledge entries |
| for [topic] when generating code that touches [topic]." |
|
|
| For example, when generating a third-person controller the LLM should pull |
| `unity_fundamentals.md` (for the lifecycle) and `unity_input_system.md` |
| (for the mouse-look recipe). |
|
|
| ## Adding entries |
|
|
| Create a new `.md` file in this directory and update the table above. The |
| file name (without `.md`) becomes the entry's slug. |
|
|
