Global Rules
Rules that apply across every project and every session. Each rule is stored in _global\CLAUDE.md and documented here with how it is implemented.
_global\CLAUDE.md and document it on this page.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.
- Rule stored in the
# Rulessection ofC:\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]"
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 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
- 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\
- "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
- Rule updated in
# Rulessection ofC:\Users\matt_\OneDrive\Claude\_global\CLAUDE.mdto reference/handoverskill - Rule 2 card updated on
_claude-guide\global-rules.html /handoverskill saved to~/.claude/commands/handover.md
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 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)
- Any task involving creating or modifying multiple files or folders
- Any structural or architectural decision
- Anything where getting it wrong would require cleanup
- 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)
- Rule added to
# Rulessection ofC:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md - Rule documented as Rule 3 card on
_claude-guide\global-rules.html
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.
- Any new top-level folder created under
OneDrive\Claude\ - Update happens in the same response as the folder creation
- Rule added to
# Rulessection ofC:\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
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.
- 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
- Rule added to
# Rulessection ofC:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md - Rule documented as Rule 5 card on
_claude-guide\global-rules.html
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.
- 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
- 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
- Rule added to
# Rulessection ofC:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md - Rule documented as Rule 6 card on
_claude-guide\global-rules.html
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.
- 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
- Adding a real customer or project instance — the template stays generic
- Changes to file contents only (e.g. updating a CLAUDE.md template)
- Rule added to
# Rulessection ofC:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md - Rule documented as Rule 7 card on
_claude-guide\global-rules.html
When a new skill is saved to ~/.claude/commands/, two pages must be updated in the same response — no exceptions.
- 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
- Add the
.mdfilename to thecommands\section of the folder tree with a short inline comment
- Rule added to
# Rulessection ofC:\Users\matt_\OneDrive\Claude\_global\CLAUDE.md - Rule documented as Rule 8 card on
_claude-guide\global-rules.html
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).
- Project-level
_temp\first (if a project is open) - Customer-level
_temp\next - Root
C:\Users\matt_\OneDrive\Claude\_temp\as fallback
- Rule added to
# Rulessection ofC:\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"
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.
- Skill cards on
skills.html— ordered by slash command name - Command files in the
commands\tree onstructure.html - Any other named reference lists in Claude Compass pages
- Rule cards on
global-rules.html— must appear in numeric order (1, 2, 3…) - Any other sequentially numbered lists in Claude Compass pages
- Rule updated in
# Rulessection ofC:\Users\matt_\OneDrive\Claude\_global\CLAUDE.mdto cover numeric lists - Rule 10 card updated on
_claude-guide\global-rules.html - Rule cards on
global-rules.htmlreordered to 1–10