Spielerando

I asked for a small fix and the AI also touched files I never mentioned

A change to one button turns into edits in the save code and the settings, and nobody notices until something breaks. This entry gives your AI a simple fence: allowed places and forbidden places, and a check after every task that names each file outside it.

Why this works

A task has a natural size. Saying in advance which places it may touch, and comparing the list of changed files afterwards, turns a vague wish to stay focused into something checkable.

When not to use it

Skip the fence for large reworks that are meant to touch everything; review those with the risk list instead.

In the full entry

  • What to build, step by step
  • Starting values and the reason for each
  • 4 common mistakes and the fix
  • A diagram of every state
  • 42 lines of example code with 4 checks that pass
  • How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "I asked for a small fix and the AI also touched files I never mentioned" (read_entry ai-edits-files-outside-the-task) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP