Claude Compass

Rules

ℹ️
To add a new rule say "create a global rule — [your rule]". Claude will add it to _global\CLAUDE.md and document it on this page.
1
Document every global rule on the Global Rules page
Added 18 May 2026

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.

Implementation
  • Rule stored in the # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule documented as a numbered card on _claude-guide\global-rules.html
  • Both updates happen in the same response — never one without the other
  • Trigger phrase: "create a global rule — [rule text]"
2
Warn when context is getting full and save a handover note
Added 18 May 2026

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.

When to warn
  • When the conversation has become very long and complex
  • Before Claude Code triggers automatic compaction (which can lose nuance)
  • Always warn early — never let context silently run out
How it works
  • Claude runs /handover — the skill asks for a session name and save location
  • Filename format: handover-YYYY-MM-DD-{session-name}.md
  • Project work → Customers\{Customer}\{Project}\_output\
  • Root / global work → C:\Users\matt_\OneDrive\Claude\_output\
New session pickup
  • "read the handover" — loads the most recent handover file
  • "read the handover from [date]" — e.g. "read the handover from 18 May"
  • "read the handover [session-name]" — e.g. "read the handover claude-guide-setup"
  • Claude reads the note, reads the files listed, confirms understanding, then proceeds
How this rule was implemented
  • Rule updated in # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md to reference /handover skill
  • Rule 2 card updated on _claude-guide\global-rules.html
  • /handover skill saved to ~/.claude/commands/handover.md
3
Plan first — do not implement until told to proceed
Added 18 May 2026

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.

What a plan must include
  • What is going to be created or changed
  • Where each file or folder will live (full paths)
  • Any decisions or trade-offs Matthew should be aware of
  • What will NOT be done (to confirm scope)
When this applies
  • Any task involving creating or modifying multiple files or folders
  • Any structural or architectural decision
  • Anything where getting it wrong would require cleanup
When this does not apply
  • Single, mechanical, agreed-upon actions — e.g. adding a rule that was just discussed
  • Direct instructions with no ambiguity — e.g. "open the guide"
  • Reading or checking files (no implementation involved)
How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule documented as Rule 3 card on _claude-guide\global-rules.html
4
Document every new root-level folder in the structure page
Added 18 May 2026

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.

When this applies
  • Any new top-level folder created under OneDrive\Claude\
  • Update happens in the same response as the folder creation
How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule documented as Rule 4 card on _claude-guide\global-rules.html
  • Existing undocumented folders _global\, _output\ and _temp\ added to _claude-guide\structure.html
5
Ask before deleting temp files
Added 18 May 2026

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.

Implementation
  • After completing work that used a _temp\ file, ask: "Do you want me to delete the file from _temp\?"
  • Only delete after explicit confirmation — never proactively
  • If Matthew says no or doesn't respond, leave the file in place
  • Only ever delete from _temp\ — never delete files from any other folder unless explicitly instructed to do so
How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule documented as Rule 5 card on _claude-guide\global-rules.html
6
Plan approval = permission to execute within the Claude workspace
Added 18 May 2026

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.

What this means
  • Approval of a plan covers all files, folders, and edits described in that plan
  • Do not stop mid-task to ask "is it okay if I…" for steps already in the agreed plan
  • Scope is limited to C:\Users\matt_\OneDrive\Claude\ and everything beneath it
What this does not cover
  • Any deletion — always confirm before deleting anything, even if deletion was mentioned in the plan
  • Actions outside the Claude workspace — always confirm those separately
  • Anything in a customer repo or external system — those always need explicit instruction
How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule documented as Rule 6 card on _claude-guide\global-rules.html
7
Keep structure.html in sync with the standard template
Added 18 May 2026

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 this applies
  • A new subfolder is added to the standard customer template (e.g. _temp\)
  • A new subfolder is added to the standard project template
  • Any structural convention changes that affect how customers or projects are laid out
When this does not apply
  • Adding a real customer or project instance — the template stays generic
  • Changes to file contents only (e.g. updating a CLAUDE.md template)
How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule documented as Rule 7 card on _claude-guide\global-rules.html
8
Update Skills page and Structure page when a new skill is saved
Added 18 May 2026

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

skills.html
  • Add a new skill card with: slash command name, badge (Global or Project), description of what it does, file path, and any required arguments
  • Move any matching "Coming soon" card to the active Global Skills section
structure.html
  • Add the .md filename to the commands\ section of the folder tree with a short inline comment
How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule documented as Rule 8 card on _claude-guide\global-rules.html
9
"Can you see [filename]" or "@[filename]" looks in _temp\
Added 18 May 2026 · Updated 18 May 2026

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).

Search order
  • Project-level _temp\ first (if a project is open)
  • Customer-level _temp\ next
  • Root C:\Users\matt_\OneDrive\Claude\_temp\ as fallback
How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule documented as Rule 9 card on _claude-guide\global-rules.html
  • Trigger phrase added to _claude-guide\trigger-phrases.html
  • Updated 18 May 2026: @[filename] added as an alternative shortcut trigger alongside "can you see"
10
Keep all reference lists in documentation ordered correctly
Added 18 May 2026 · Updated 18 May 2026

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.

Alphabetical lists
  • Skill cards on skills.html — ordered by slash command name
  • Command files in the commands\ tree on structure.html
  • Any other named reference lists in Claude Compass pages
Numeric lists
  • Rule cards on global-rules.html — must appear in numeric order (1, 2, 3…)
  • Any other sequentially numbered lists in Claude Compass pages
How this rule was implemented
  • Rule updated in # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md to cover numeric lists
  • Rule 10 card updated on _claude-guide\global-rules.html
  • Rule cards on global-rules.html reordered to 1–10
13
Keep notes.html in sync with the notes store
Added 18 May 2026

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.

How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule 13 card added to _claude-guide\global-rules.html
  • /notes skill created at ~/.claude/commands/notes.md
  • _notes\notes.md created as the note store
  • notes.html created in _claude-guide\
12
Keep memories.html in sync with memory files
Added 18 May 2026

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.

Each memory card must include
  • Level — Global, Disseminate, Customer: {name}, or Project: {name}
  • Type badge — project, reference, user, or feedback
  • Summary of content — what Claude will use this memory for
How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule 12 card added to _claude-guide\global-rules.html
  • memories.html updated: level badges added, secrets card removed
14
Use /create-agent when creating a new agent
Added 19 May 2026

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.

How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule 14 card added to _claude-guide\global-rules.html
  • _global\agents\ directory created; ~/.claude/agents\ junction pointing to it
  • agents.html created in _claude-guide\
  • create-agent.md skill created in ~/.claude/commands\
  • Agents nav link added to all 10 Compass pages between Skills and Handovers
  • structure.html updated: agents\ added to global config tree and project tree
11
Write commands and copyable text to a file, not inline in chat
Added 18 May 2026

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

The timestamp suffix prevents concurrent Claude windows (even on the same project) from overwriting each other. The project slug is derived from the working directory (e.g. reapit for the Reapit project). Example: cmd-reapit-20260701-113045.txt.

How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\.claude\CLAUDE.md (18 May 2026)
  • Rule 11 card added to _claude-guide\global-rules.html (18 May 2026)
  • Rule updated 1 Jul 2026 to add timestamped filename to prevent concurrent Claude windows overwriting each other
  • Companion path in Rule 15 (email drafts) also updated to the timestamped pattern
16
Never use dashes in written text
Added 3 June 2026

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.

How this rule was implemented
  • Rule added to # Writing Style section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule 16 card added to _claude-guide\global-rules.html
  • Feedback memory saved to ~\.claude\projects\...\memory\feedback_no_dashes_in_text.md
17
Never run git commands without explicit permission
Added 15 June 2026

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.

Covered by this rule — always ask first
  • git commit — never stage or commit changes without being told to
  • git push — never push to a remote without explicit instruction
  • git pull / git fetch — ask before pulling or fetching
  • git checkout / git switch — ask before changing branches or checking out files
  • git merge, git rebase, git reset — always ask
  • git add / staging — never stage files independently of a commit
Always permitted without asking
  • Read-only inspection: git status, git log, git diff, git show, git branch
Exception
  • Git operations directly implied by an explicitly agreed task instruction — e.g. "update this folder from branch X" authorises the necessary fetch and checkout to complete that specific task
How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule 17 card added to _claude-guide\global-rules.html
15
Show email draft and wait for approval before sending
Added 21 May 2026

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-{project-slug}-{YYYYMMDD-HHMMSS}.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.

How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md
  • Rule 15 card added to _claude-guide\global-rules.html
  • Feedback memory saved to ~\.claude\projects\...\memory\feedback_show_email_before_sending.md
18
Never add a Claude co-author tag to commits or authored content
Added 1 July 2026

Never add Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> (or any variant referencing Claude) to git commit messages, PR descriptions, or any other authored content. Commits should show only Matthew as the author.

Covered by this rule
  • Git commit messages — no Co-Authored-By footer referencing Claude, Anthropic, or an AI model
  • Pull request titles and descriptions
  • Any other authored artefact where Claude might otherwise attribute itself
How this rule was implemented
  • Rule added to # Rules section of C:\Users\matt_\.claude\CLAUDE.md
  • Rule 18 card added to _claude-guide\global-rules.html