chore: WIP marketplace doc adjustments across plugins
Pre-trekexecute snapshot of in-progress CLAUDE.md/SKILL.md edits and extracted docs/ files. Captured as one commit so /trekexecute claude-design can run against a clean working tree. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
parent
3754230f94
commit
0cdade720d
1 changed files with 0 additions and 17 deletions
17
CLAUDE.md
17
CLAUDE.md
|
|
@ -41,20 +41,3 @@ Pipelinen er sannhet inntil release:
|
||||||
5. Review er release-gate
|
5. Review er release-gate
|
||||||
|
|
||||||
Voyage-policy: Opus på alle sub-agenter og orchestrator-faser.
|
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)
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue