fjy8018/superpowers-lite
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Create Superpowers Lite fork

Browse Source
This commit is contained in:
mujing
2026-05-12 16:05:03 +08:00
parent f2cbfbefeb
commit dd2eb8b351
33 changed files with 221 additions and 399 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
skills/writing-skills/SKILL.md
View File

@@ -1,6 +1,6 @@
---
name: writing-skills
description: Use when creating new skills, editing existing skills, or verifying skills work before deployment
description: Manual-only skill. Activate only after an explicit user request for superpowers-lite:writing-skills.
---
# Writing Skills
@@ -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.
**REQUIRED BACKGROUND:** You MUST understand superpowers:test-driven-development before using this skill. That skill defines the fundamental RED-GREEN-REFACTOR cycle. This skill adapts TDD to documentation.
**REQUIRED BACKGROUND:** You MUST understand superpowers-lite: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.
@@ -159,7 +159,7 @@ When the description was changed to just "Use when executing implementation plan
```yaml
# ❌ BAD: Summarizes workflow - Claude may follow this instead of reading skill
description: Use when executing plans - dispatches subagent per task with code review between tasks
description: Manual-only skill. Activate only after an explicit user request for superpowers-lite:executing-plans.
# ❌ BAD: Too much process detail
description: Use for TDD - write test first, watch it fail, write minimal code, refactor
@@ -280,8 +280,8 @@ wc -w skills/path/SKILL.md
**When writing documentation that references other skills:**
Use skill name only, with explicit requirement markers:
- ✅ Good: `**REQUIRED SUB-SKILL:** Use superpowers:test-driven-development`
- ✅ Good: `**REQUIRED BACKGROUND:** You MUST understand superpowers:systematic-debugging`
- ✅ Good: `**REQUIRED SUB-SKILL:** Use superpowers-lite:test-driven-development`
- ✅ Good: `**REQUIRED BACKGROUND:** You MUST understand superpowers-lite:systematic-debugging`
- ❌ Bad: `See skills/testing/test-driven-development` (unclear if required)
- ❌ Bad: `@skills/testing/test-driven-development/SKILL.md` (force-loads, burns context)
@@ -390,7 +390,7 @@ Edit skill without testing? Same violation.
- Don't "adapt" while running tests
- Delete means delete
**REQUIRED BACKGROUND:** The superpowers:test-driven-development skill explains why this matters. Same principles apply to documentation.
**REQUIRED BACKGROUND:** The superpowers-lite:test-driven-development skill explains why this matters. Same principles apply to documentation.
## Testing All Skill Types