diff --git a/CLAUDE.md b/CLAUDE.md
index 40e9847..55a86b3 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -33,17 +33,4 @@ Python ≥3.10. MAF (`agent-framework-core` 1.9.0). Pakkehåndtering: `uv`. To b
 
 ## Communication patterns
 
-### Linking to local files
-
-When pointing to local files in responses, always use markdown link syntax with a descriptive name:
-
-- Use `[Human-friendly name](file:///absolute/path)` — never bare `file:///...` URLs or autolinks `<file://...>`.
-- Always use absolute paths. Never `~/` or relative paths.
-- For multiple files, render as a bullet list of named markdown links.
-
-Why: bare `file://` URLs only render the first as clickable across multiple lines. Named markdown links make each entry independently clickable and look cleaner.
-
-Example:
-
-- [Research report](file:///Users/ktg/repos/portfolio-optimiser/docs/research/2026-06-23-prior-art-platform.md)
-- [Incremental plan](file:///Users/ktg/repos/portfolio-optimiser/docs/plan/2026-06-23-incremental-plan.md)
+When linking to local files in responses, use named markdown links — `[Human-friendly name](file:///absolute/path)`, never bare `file://` URLs or autolinks `<file://...>`, always absolute paths (never `~/` or relative), one bullet per file when there are several. (Bare `file://` URLs render only the first as clickable across multiple lines; named links stay independently clickable.)