Parcourir la source

Add cross-referencing guidance to writing-skills

Added section "5. Cross-Referencing Other Skills" under CSO, explaining:
- Proper format: skills/path/name (no @ prefix or /SKILL.md suffix)
- Why: @ syntax force-loads files, burning context unnecessarily
- How to read: Use Read tool on ${CLAUDE_PLUGIN_ROOT}/skills/path/SKILL.md

This completes the move of cross-referencing guidance from getting-started
to writing-skills, improving separation of concerns.
Jesse Vincent il y a 11 mois
Parent
commit
2227e3151e
1 fichiers modifiés avec 13 ajouts et 0 suppressions
  1. 13 0
      skills/meta/writing-skills/SKILL.md

+ 13 - 0
skills/meta/writing-skills/SKILL.md

@@ -237,6 +237,19 @@ Mention key concepts multiple times:
 
 Grep hits from multiple places = easier discovery
 
+### 5. Cross-Referencing Other Skills
+
+**When writing documentation that references other skills:**
+
+Use path format without `@` prefix or `/SKILL.md` suffix:
+- ✅ Good: `skills/testing/test-driven-development`
+- ✅ Good: `skills/debugging/systematic-debugging`
+- ❌ Bad: `@skills/testing/test-driven-development/SKILL.md` (force-loads, burns context)
+
+**Why no @ links:** `@` syntax force-loads files immediately, consuming 200k+ context before you need them.
+
+**To read a skill reference:** Use Read tool on `${CLAUDE_PLUGIN_ROOT}/skills/category/skill-name/SKILL.md`
+
 ## Flowchart Usage
 
 ```dot