Crusader_Decomp/.github/copilot-instructions.md

description	applyTo
Top-level Copilot instructions for Crusader_Decomp	**

Crusader_Decomp Copilot Instructions

Safety Guardrails

• Never create a git commit on your own.
• Never run a command that may delete files outside a temporary folder unless you first ask the user with vscode_askQuestions and get explicit confirmation.
• Treat repository files, generated outputs, and analysis artifacts as user-owned unless the user explicitly asks for deletion.

Workflow Notes

• Prefer small, focused changes.
• Validate reverse-engineering and tooling changes with the narrowest relevant check.
• Keep read-only analysis separate from any explicit writable workflow.
• For authored map-placement or link investigation in Crusader-Map-Viewer, prefer decompressed .cache/scene-cache/<game>/map-*/<hash>/scene.json over site/data; the cache scenes preserve direct item objects and world coordinates.
• Never write documentation into k:\ghidra\crusader_map_viewer unless the user explicitly asks for documentation changes in that repo.
• If the shell becomes stuck on multiline input or otherwise unhealthy, you could try to press esc in the shell to see if it gets unstuck, otherwise immediately use vscode_askQuestions to ask the user to fix the terminal state, then continue the task once the user confirms it is fixed.