# HyperTwist AI Instructions

- Treat `UnrealHyperTwist/` as the live project root and `UnrealHyperTwist/Source/UnrealHyperTwist/` as the primary owned code surface.
- Prefer Visual Studio MCP semantic tools when available:
  - use solution/project inspection instead of manual tree walks
  - use symbol/navigation tools instead of grep for C# and Unreal code
  - use document open/read/write tools for files already inside the loaded solution
- Only `UnrealHyperTwist/Plugins/UnrealMCPChong/` is a maintained in-repo plugin fork. Leave the other plugin folders alone unless the task explicitly targets them.
- Do not treat `mirrors/`, `zippedreposource/`, or `docs/refs/` as default edit surfaces.
- If Rust code appears inside dependencies or mirrors, use the nearest `Cargo.toml`; do not invent Rust project markers at repo root.