My folder holds three hundred copies of the project and I do not dare to delete any

Copies pile up after every big AI session, and the one you need is always the one you deleted. Your AI can apply a plain keep rule to the list of copies and name exactly which to keep and which are safe to remove, with milestones you marked staying for good.

Why this works

Recent copies matter in detail, old ones only in outline. Keeping the latest few, one per day for a while, and what you marked yourself, covers the realistic ways of needing to go back, at a fraction of the space.

When not to use it

Never run it without looking at the delete list first, and never on the only copy of a project. Do not prune at all while a bug is being hunted: the older copies are what you compare against.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 25 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 folder holds three hundred copies of the project and I do not dare to delete any" (read_entry rpg-which-backups-to-keep) 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