An agentic skills framework & software development methodology that works.
Move cross-referencing guidance from getting-started to writing-skills
Jesse Vincentcd83c0aac8e1
diff --git a/skills/getting-started/SKILL.md b/skills/getting-started/SKILL.mdindex 9f2f4a9ff..64a3d2d42 100644--- a/skills/getting-started/SKILL.md+++ b/skills/getting-started/SKILL.md@@ -138,19 +138,6 @@ Personal skills go in `~/.config/superpowers/skills/` and shadow core skills wheThe skill itself tells you which type it is.-## Referencing Skills in Documentation--**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`-## Instructions ≠ Permission to Skip WorkflowsYour human partner's specific instructions describe WHAT to do, not HOW.