Read first: non-destructive rules

Read and follow these first, on every prompt and every interaction, before any other rule or section.

The rules

• NEVER-DESTRUCTIVE (HARD, locked) — never do anything destructive, except where a platform store or legal requirement mandates it; then follow the mandated flow and still confirm with the user before executing.
• Rule: not "ask first", never. If a task seems to need destruction, find a non-destructive path, even if it takes more steps.
• Exception: a destructive action that a platform store or legal requirement mandates (for example player account deletion, which Steam, PlayStation and Xbox all mandate for store compliance). The agent follows the mandated flow exactly and confirms with the user before executing it. Nothing else qualifies.
• Why: lost work cannot be rebuilt from a rule, and a confident destructive step is the most expensive mistake an agent can make.
• Check: the session contains no delete, overwrite or irreversible operation, other than a mandated one the user confirmed.
• NEVER-DELETE-OR-OVERWRITE (HARD, locked) — never delete or overwrite projects, folders or files.
• Rule: write new files next to old ones, or move the old one aside first. The only exception is the mandated one under NEVER-DESTRUCTIVE, with the user's confirmation. Editing lines inside a tracked source file is an edit, not destruction; removing a whole file or folder always means moving it aside.
• Check: every path that existed before the session still exists, or sits in a named backup.
• NEVER-DESTRUCTIVE-OUTSIDE-THE-PROJECT (HARD, locked) — never take destructive actions outside the game project.
• Rule: files outside the project (global agent files, shared rules, Editor and system config) are never deleted or overwritten. Non-destructive edits there also follow ASK-BEFORE-EDITING-OUTSIDE-THE-PROJECT on the Project setup page.
• Check: nothing outside the project folder was removed or replaced.
• NEVER-IRREVERSIBLE (HARD, locked) — never run irreversible operations.
• Rule: no git reset --hard, no force push, no history rewrite, no mass rename or wipe. A cache the Editor regenerates (such as Library/) is moved aside, not deleted. The only exception is the mandated one under NEVER-DESTRUCTIVE (such as a store-required account deletion), run in the mandated flow after the user confirms.
• Check: the session's commands include none of these.
• ALWAYS-MOVE-ASIDE (HARD, locked) — always back up or move aside instead of deleting.
• Rule: commit or copy before a risky edit; when something must go, move it into a dated backup folder.
• Check: every removal in the session is a move into a backup you can name.
• WHEN-UNSURE-STOP-AND-ASK (HARD, locked) — when you are unsure, stop and ask.
• Rule: asking is for unclear cases. It is never permission to destroy.
• Check: no action was taken on a guess.

Adopt the library

Use Customize the rules to distinguish locked evidence from project defaults.