From 6b3ece96a8215f3765bde7fa3887606d8087ade4 Mon Sep 17 00:00:00 2001 From: Kjell Tore Guttormsen Date: Sat, 16 May 2026 21:01:45 +0200 Subject: [PATCH] docs: add Communication patterns section to all plugin CLAUDE.md Standardize named-markdown-link guidance across all plugins so file:// references render as independently clickable links in terminals like Ghostty (bare file:// URLs only make the first clickable). Co-Authored-By: Claude Opus 4.7 --- CLAUDE.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 9b152de..bb11c41 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -392,3 +392,20 @@ Prompt injection is **structurally unsolvable** with current architectures (join - Agents operate read-only unless the specific command explicitly grants Write/Edit (`clean` and `harden` do) - Irreversible operations (baseline overwrites, file edits) require user confirmation via AskUserQuestion - Do not access paths outside the project root without explicit user instruction + +## 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 ``. +- 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: + +- [Brief](file:///Users/ktg/.../brief.html) +- [Research summary](file:///Users/ktg/.../research/summary.md)