# Modding Workshop Rules (for your AI agent)

Save this file in your modding workshop folder (for example `C:\Modding`) and rename it:

- `CLAUDE.md` if you use Claude Code
- `AGENTS.md` if you use Codex

Your agent reads it automatically whenever you start it in that folder. Fill in "About my setup" first.

Guide: https://www.classified.llc/ai-guides/modding-setup-with-ai-agents

---

## About my setup

- Games I mod: [fill in]
- Mod manager, if any: [Vortex / Mod Organizer 2 / the game's own launcher / none]
- Where my saves live: [fill in, or ask the agent to find them]
- Game versions I have frozen: [fill in]

## Rules for the agent

### Protect what works

- Treat my saves and my current working mod setup as irreplaceable.
- Before any change to mods, saves, or game settings, back up the affected files to `backups\<date>_<what>\`, check the copy against the originals file by file, and leave a short restore note in that folder.
- Never delete, move, or overwrite anything without asking me first. Tell me exactly what and why.
- Never update the game or a mod without asking.
- If the game is running, do not change its files. Ask me to close it first.

### Work in the workshop

- Original downloads go in `archives\` and stay untouched.
- Unpack and inspect mods in `staging\` before installing them.
- Before installing a mod, read its readme and requirements and report: the mods it needs, the game version it needs, conflicts with what I have, and whether it ships copies of the game's own files.
- If the mod page lists a checksum, compare it to the download.
- Install a few mods at a time, then have me test in the game.

### Keep records

- Keep `records\mod-list.md` current: every installed mod, its version, and why I have it.
- Log every change in `records\changelog.md` with the date, what changed, and how to undo it.
- At the start of a session, read the records folder first. At the end, update it.

### When something breaks

- Save the evidence first: copy crash reports and logs to `crash-archive\<date>_<what>\` before anything relaunches the game.
- Show me the evidence (the exact log line), then your conclusion, then how sure you are.
- Do not blame a mod without evidence. Test it.

### How to talk to me

- Plain English. Define any technical term the first time you use it.
- When there is a choice to make, end with a clear "here's what I'd do".
- If you cannot do something (a login, a permission prompt, a download), say so and tell me exactly what to do instead.