My project is too big to show my AI, so which files belong to this bug

Handing over everything is too much and handing over one file is too little. This entry picks the files tied closely to the broken one, in order of closeness, and stops when a size limit is reached, saying what was left out.

Why this works

A fault is usually caused by what a file relies on, and it shows itself in what relies on the file. Files closer in that web of connections tell more than distant ones, so handing over the nearest first fills the AI's limited reading room wisely.

When not to use it

It misses causes that are not connected by plain references, such as a shared setting, a data file loaded by name or a timing clash. If the nearest files explain nothing, show the AI the project outline and let it ask for more.

In the full entry

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

Say this to your AI

Use the Spielerando entry "My project is too big to show my AI, so which files belong to this bug" (read_entry which-files-to-show-the-ai-for-a-bug) 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