|
|
@@ -15,7 +15,7 @@ You write test cases (pressure scenarios with subagents), watch them fail (basel
|
|
|
|
|
|
**Core principle:** If you didn't watch an agent fail without the skill, you don't know if the skill teaches the right thing.
|
|
|
|
|
|
-See skills/testing/test-driven-development for the fundamental RED-GREEN-REFACTOR cycle. This skill adapts TDD to documentation.
|
|
|
+**REQUIRED BACKGROUND:** You MUST understand test-driven-development before using this skill. That skill defines the fundamental RED-GREEN-REFACTOR cycle. This skill adapts TDD to documentation.
|
|
|
|
|
|
**Official guidance:** For Anthropic's official skill authoring best practices, see anthropic-best-practices.md. This document provides additional patterns and guidelines that complement the TDD-focused approach in this skill.
|
|
|
|
|
|
@@ -210,7 +210,7 @@ When searching, dispatch subagent with template...
|
|
|
[20 lines of repeated instructions]
|
|
|
|
|
|
# ✅ GOOD: Reference other skill
|
|
|
-Always use subagents (50-100x context savings). See skills/using-skills for workflow.
|
|
|
+Always use subagents (50-100x context savings). REQUIRED: Use [other-skill-name] for workflow.
|
|
|
```
|
|
|
|
|
|
**Compress examples:**
|
|
|
@@ -252,9 +252,10 @@ wc -w skills/path/SKILL.md
|
|
|
|
|
|
**When writing documentation that references other skills:**
|
|
|
|
|
|
-Use path format without `@` prefix or `/SKILL.md` suffix:
|
|
|
-- ✅ Good: `test-driven-development`
|
|
|
-- ✅ Good: `systematic-debugging`
|
|
|
+Use skill name only, with explicit requirement markers:
|
|
|
+- ✅ Good: `**REQUIRED SUB-SKILL:** Use test-driven-development`
|
|
|
+- ✅ Good: `**REQUIRED BACKGROUND:** You MUST understand systematic-debugging`
|
|
|
+- ❌ Bad: `See skills/testing/test-driven-development` (unclear if required)
|
|
|
- ❌ 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.
|
|
|
@@ -356,7 +357,7 @@ Edit skill without testing? Same violation.
|
|
|
- Don't "adapt" while running tests
|
|
|
- Delete means delete
|
|
|
|
|
|
-See the test-driven-development skill for why this matters. Same principles apply to documentation.
|
|
|
+**REQUIRED BACKGROUND:** The test-driven-development skill explains why this matters. Same principles apply to documentation.
|
|
|
|
|
|
## Testing All Skill Types
|
|
|
|
|
|
@@ -519,7 +520,7 @@ Run same scenarios WITH skill. Agent should now comply.
|
|
|
|
|
|
Agent found new rationalization? Add explicit counter. Re-test until bulletproof.
|
|
|
|
|
|
-**See the testing-skills-with-subagents skill for:**
|
|
|
+**REQUIRED SUB-SKILL:** Use testing-skills-with-subagents for the complete testing methodology:
|
|
|
- How to write pressure scenarios
|
|
|
- Pressure types (time, sunk cost, authority, exhaustion)
|
|
|
- Plugging holes systematically
|