Rules

Every time a global rule is created, Claude must add it to _global\CLAUDE.md and document it on this page — including what the rule is and exactly how it is implemented.

When the conversation is getting long and context is at risk of running out, Claude must warn Matthew proactively — before it becomes critical. Claude then runs the /handover skill to save a structured note so the session can be picked up cleanly.

In a new session, saying "read the handover" tells Claude to load the latest handover file, read the files listed in it, then confirm its understanding before proceeding.

Before implementing anything non-trivial, Claude must present a clear plan and wait for explicit approval. No files are created, no folders built, no code written until Matthew says to go ahead.

When any new folder is created directly under C:\Users\matt_\OneDrive\Claude\, it must be added to the Folder Structure page with a description of its purpose. No folder should exist in the root without being documented.

After using a file from _temp\, once the task is complete and the output looks good, Claude must ask whether to delete the file — never delete silently.

Once Matthew approves a plan, Claude has full permission to carry out all steps in that plan without pausing to re-confirm individual actions. This applies to everything under C:\Users\matt_\OneDrive\Claude\ and downward.

When the standard folder template changes — for example a new subfolder becomes part of the standard customer or project structure — structure.html must be updated to reflect it in the same response.

When a new skill is saved to ~/.claude/commands/, two pages must be updated in the same response — no exceptions.

Saying "can you see [filename]" or "@[filename]" tells Claude to find and read that file from the nearest _temp\ folder. After using the file, Claude asks if it should be deleted (per Rule 5).

All reference lists in Claude Compass documentation must be kept in the correct order. When adding a new item, insert it in the right position — never append to the end.

When adding a note via /notes add, also add a card to notes.html in _claude-guide\ and commit all changes together in a single commit.

When creating or updating a memory file, also update memories.html in _claude-guide\ to reflect the new or changed entry. Do not show secrets or sensitive references on the page.

When creating a new global agent: use /create-agent to ensure the agent file, agents.html, and structure.html are all created and updated together. Never create an agent file manually without running /create-agent.

When providing a command or any text that needs to be copied, write it to C:\Users\matt_\OneDrive\Claude\_temp\cmd.txt and open it in Notepad — never display it inline in chat where line wrapping causes copy errors.

Do not use em dashes or hyphens as connectives in any written text (letters, documents, responses). They make writing look AI-generated. Use full sentences instead.

Claude must never run any git command without explicit permission from Matthew. This is a hard rule with no exceptions for convenience — git operations change state that can be difficult to reverse.

Before sending any email on Matthew's behalf, display the full draft — To address, Subject, and body — and wait for explicit approval before sending. Write the To and CC addresses to _temp\cmd.txt and open in Notepad so they are easily copyable.

Exception: emails that are part of a pre-authorised agent task where the template or intent was already explicitly approved (e.g. a campaign already signed off, or a scheduled task sending a predetermined message). If the template was approved as part of the task plan, it does not need re-approval each time it fires.