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 <noreply@anthropic.com>

plugins/ai-psychosis/CLAUDE.md

@@ -92,3 +92,20 @@ node --test tests/*.test.mjs
 - Conventional Commits: `type(scope): description`
 - English for all code, comments, and documentation
 - Norwegian for project-internal communication
+
+## 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:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)

plugins/claude-design/CLAUDE.md

@@ -0,0 +1,60 @@
+# claude-design
+
+## Kontekst
+
+Plugin som skal være ekspert på **Claude Design** (claude.ai/design) — Anthropics surface for å lage interaktive artifacts via prompt.
+
+Skal dekke hele prosessen fra idé til ferdig artifact:
+
+1. Forstå hva brukeren vil lage
+2. Velge riktig artifact-type og prompt-strategi
+3. Generere effektive prompts for Claude Design
+4. Iterere og refine basert på preview
+5. Polere og levere
+
+Den endelige sammensetningen — skills, agenter, kommandoer — defineres gjennom Voyage-pipelinen og er IKKE fastlagt på forhånd.
+
+## Status
+
+`0.1.0-pre` — bootstrap. Innholdet bygges via `/trekbrief` → `/trekresearch` → `/trekplan` → `/trekexecute` → `/trekreview`.
+
+## Marketplace-kontekst
+
+Plugin ligger inne i `ktg-plugin-marketplace`. Ingen egen git-repo, ingen egen Forgejo-remote. Alle commits til marketplace-repoet på `git.fromaitochitta.com/open/ktg-plugin-marketplace`.
+
+Følg marketplace-konvensjonene fra rot-CLAUDE.md:
+
+- Norsk dialog, engelsk kode/dokumentasjon
+- Conventional Commits: `type(scope): description` — scope er `claude-design`
+- Hooks i Node.js (.mjs), ikke bash
+- Null npm-avhengigheter i hooks
+- Docs-trippel oppdatert i samme commit ved feature-endringer: plugin `README.md`, plugin `CLAUDE.md`, rot-`README.md`
+
+## Arbeidsflyt
+
+Pipelinen er sannhet inntil release:
+
+1. Brief lukker scope og scope-grenser
+2. Research samler eksterne kilder (Anthropic cookbook, claude.ai/design-dokumentasjon, community-mønstre)
+3. Plan beskriver fil-for-fil hva som skal lages
+4. Execute leverer kode/innhold
+5. Review er release-gate
+
+Voyage-policy: Opus på alle sub-agenter og orchestrator-faser.
+
+## 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:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)

plugins/config-audit/CLAUDE.md

@@ -225,3 +225,20 @@ node --test 'tests/**/*.test.mjs'
 - Session directories accumulate — use `/config-audit cleanup` to manage
 - Scanners run on Node.js >= 18 (uses node:test, node:fs/promises)
 - Plugin CLAUDE.md files in node_modules should be excluded via scope
+
+## 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:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)

plugins/graceful-handoff/CLAUDE.md

@@ -63,3 +63,20 @@ node --test plugins/graceful-handoff/tests/
 - v1.0.0 (2026-04-19): initial declarative command
 - v2.0.0 (2026-05-01): skill-arkitektur + JSON-pipeline + 3 hooks + auto-trigger (BREAKING)
 - v2.1.0 (2026-05-01): modell-bevisst kontekstvindu — 4-stegs resolution-kjede (used_percentage → payload-size → model-map → 1M default). Fikser for-tidlig auto-handoff på Opus 4.7
+
+## 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:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)

plugins/human-friendly-style/CLAUDE.md

@@ -45,3 +45,20 @@ If `keep-coding-instructions` is removed or set to `false`, Claude Code will str
 - Per-plugin variants (code-focused, deep-technical, etc.) — would belong in a future v1.1 if there's real demand
 - Forcing the style on other plugins — it remains opt-in. Other plugins may reference it in their READMEs.
 - Translation of the style file itself into Norwegian — defeats the purpose of language-agnostic 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 `<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:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)

plugins/linkedin-thought-leadership/CLAUDE.md

@@ -98,3 +98,20 @@ All content commands (post, quick, react, pipeline, first-post, video, multiplat
 5. Topic must align with user's 5 core expertise areas (360Brew signal)
 6. Topic rotation: no back-to-back same pillar, no pillar >50% in 14 days (warn-only)
 7. Progressive onboarding: personalization score hidden until 3+ posts; voice guardian suppressed until 5+ voice samples
+
+## 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:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)

plugins/llm-security/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 `<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:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)

plugins/ms-ai-architect/CLAUDE.md

@@ -288,3 +288,20 @@ kopi av marketplace-rotens `shared/playground-design-system/`. Dette holder plug
 
 **Tilsynsmyndigheter:** Datatilsynet (personvern), nasjonal AI-tilsynsmyndighet (under etablering), sektortilsyn.
 
+
+## 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:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)

plugins/okr/CLAUDE.md

@@ -75,3 +75,20 @@ Cycle archival: `/okr:oppsett arkiver` — moves `syklus/` to `historikk/`, gene
 /okr:oppsett arkiver ──→ cycle archival + retrospektiv-generering
 SessionStart ──→ coaching-hook.mjs (proactive coaching)
 ```
+
+## 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:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)

plugins/voyage/CLAUDE.md

@@ -8,6 +8,8 @@ Voyage — a contract-driven Claude Code pipeline: brief, research, plan, execut
 
 > **Trinity context (2026-05-13, informational).** Voyage is Tier 1 (per-task) of a three-tier architecture in active design under the author's private marketplace: Tier 2 `app-creator` (per-app — "what does the app need, what's the next brief?") produces briefs Voyage consumes; Tier 3 `app-factory` (per-portfolio — "which app needs me now?") aggregates state across multiple app-creator instances. Both are pre-implementation and will ship to Forgejo when ready. **Asymmetry is a hard invariant:** Voyage stays unaware of Tier 2/3. Handover 1 (brief format) is the only integration point — any compatible producer can feed Voyage, app-creator is not privileged. Brief-schema changes are therefore breaking changes for downstream consumers, formalized as a public contract in v5.4.
 
+> **Cross-cutting invariant: brief framing must match operator intent (2026-05-15).** Etablert etter residiv. Briefen er pipelinens source of truth; operatørens intent lever i hodet + i memory-filer (`feedback_*`, `project_*`); pipelinen tvinger ikke alignment. Høyere reasoning-kraft polerer feil premiss istedenfor å utfordre det. **Tre lag av forsvar (input-siden), alle BLOCKER ved brudd når v5.5 shipper:** (1) eksplisitt `framing: preserve|refine|replace|new-direction` i brief-frontmatter, `AskUserQuestion`-validert før brief-prosa skrives; (2) memory-alignment check som ny dimensjon i `brief-reviewer` — sammenlikner brief-prosa mot relevante memory-filer og rapporterer eksplisitte motsigelser; (3) obligatorisk `## TL;DR`-seksjon (≤ 5 linjer) øverst i `brief.md`. Implementeres i v5.5 — se [ROADMAP.md](ROADMAP.md). Inntil shipping: operatør må manuelt sjekke at briefens framingord ikke motsier intent, særlig etter avvist iterasjon hvor "delta fra forrige" er en farlig default-ankring.
+
 ## Commands
 
 | Command | Description | Model |
@@ -301,3 +303,20 @@ Stats:
 - **Session state** — `.session-state.local.json` per project. **Handover 7** — produced by any session-end mechanism (`/trekexecute` Phase 8/2.55/4, `/trekendsession` helper, future graceful-handoff v2.2). Consumed by `/trekcontinue` to resume the next session in a fresh chat. Schema v1 is forward-compat (unknown top-level keys ignored). Never committed (gitignored via `*.local.json`).
 
 A project typically has 1 task brief, 0–N research briefs, 0 or 1 architecture note, 0–N reviews (one per review iteration), and 0 or 1 session-state file (overwritten on every session-end).
+
+## 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:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)