@wenaixi/dsh-superpower 7.3.0 → 7.5.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +112 -105
- package/README.zh.md +216 -0
- package/lib/catalog.d.ts +8 -2
- package/lib/catalog.d.ts.map +1 -1
- package/lib/catalog.js +64 -9
- package/lib/catalog.js.map +1 -1
- package/lib/client.js +120 -75
- package/lib/document.d.ts +8 -2
- package/lib/document.d.ts.map +1 -1
- package/lib/document.js +14 -4
- package/lib/document.js.map +1 -1
- package/lib/superpowers.d.ts +6 -0
- package/lib/superpowers.d.ts.map +1 -1
- package/lib/superpowers.js +25 -2
- package/lib/superpowers.js.map +1 -1
- package/lib/switches.d.ts +17 -18
- package/lib/switches.d.ts.map +1 -1
- package/lib/switches.js +78 -31
- package/lib/switches.js.map +1 -1
- package/package.json +3 -3
- package/skills/brainstorming/SKILL.md +234 -170
- package/skills/brainstorming/spec-document-reviewer-prompt.md +27 -25
- package/skills/brainstorming/visual-companion.md +84 -231
- package/skills/diagnosing-superpowers/SKILL.md +107 -43
- package/skills/diagnosing-superpowers/prompts/analyst-common.md +32 -18
- package/skills/diagnosing-superpowers/prompts/cost-and-time.md +25 -9
- package/skills/diagnosing-superpowers/prompts/plan-adherence.md +26 -12
- package/skills/diagnosing-superpowers/prompts/quality-evidence.md +23 -8
- package/skills/diagnosing-superpowers/prompts/repeated-work.md +25 -14
- package/skills/diagnosing-superpowers/prompts/request-conflicts.md +18 -9
- package/skills/diagnosing-superpowers/prompts/scrub-audit.md +23 -10
- package/skills/diagnosing-superpowers/prompts/scrub.md +25 -12
- package/skills/diagnosing-superpowers/prompts/similar-session.md +30 -22
- package/skills/diagnosing-superpowers/prompts/skill-timeline.md +26 -12
- package/skills/diagnosing-superpowers/prompts/stumbles.md +24 -12
- package/skills/diagnosing-superpowers/references/context-safety.md +15 -7
- package/skills/diagnosing-superpowers/references/github-issues.md +17 -9
- package/skills/diagnosing-superpowers/references/redaction-policy.md +27 -15
- package/skills/diagnosing-superpowers/references/session-discovery.md +31 -20
- package/skills/diagnosing-superpowers/templates/bundle-README.md +66 -40
- package/skills/diagnosing-superpowers/templates/case.md +49 -42
- package/skills/diagnosing-superpowers/templates/issue.md +32 -26
- package/skills/diagnosing-superpowers/templates/report.md +54 -48
- package/skills/dispatching-parallel-agents/SKILL.md +92 -90
- package/skills/executing-plans/SKILL.md +345 -197
- package/skills/finishing-a-development-branch/SKILL.md +107 -82
- package/skills/receiving-code-review/SKILL.md +129 -127
- package/skills/requesting-code-review/SKILL.md +52 -50
- package/skills/requesting-code-review/code-reviewer.md +132 -111
- package/skills/subagent-driven-development/SKILL.md +521 -298
- package/skills/subagent-driven-development/implementer-prompt.md +138 -117
- package/skills/subagent-driven-development/re-review-prompt.md +80 -48
- package/skills/subagent-driven-development/task-reviewer-prompt.md +189 -110
- package/skills/systematic-debugging/CREATION-LOG.md +85 -85
- package/skills/systematic-debugging/SKILL.md +221 -219
- package/skills/systematic-debugging/condition-based-waiting.md +48 -49
- package/skills/systematic-debugging/defense-in-depth.md +46 -46
- package/skills/systematic-debugging/root-cause-tracing.md +63 -63
- package/skills/systematic-debugging/test-academic.md +10 -10
- package/skills/systematic-debugging/test-pressure-1.md +40 -40
- package/skills/systematic-debugging/test-pressure-2.md +58 -58
- package/skills/systematic-debugging/test-pressure-3.md +48 -48
- package/skills/test-driven-development/SKILL.md +161 -153
- package/skills/test-driven-development/writing-good-tests.md +137 -84
- package/skills/using-git-worktrees/SKILL.md +74 -72
- package/skills/using-superpowers/SKILL.md +40 -39
- package/skills/using-superpowers/references/dsh-tools.md +36 -36
- package/skills/verification-before-completion/SKILL.md +85 -83
- package/skills/writing-plans/SKILL.md +123 -84
- package/skills/writing-skills/SKILL.md +419 -417
- package/skills/writing-skills/persuasion-principles.md +118 -118
- package/skills/writing-skills/testing-skills-with-subagents.md +190 -190
- package/skills/brainstorming/scripts/frame-template.html +0 -213
- package/skills/brainstorming/scripts/helper.js +0 -167
- package/skills/brainstorming/scripts/server.cjs +0 -715
- package/skills/brainstorming/scripts/start-server.sh +0 -204
- package/skills/brainstorming/scripts/stop-server.sh +0 -120
|
@@ -1,187 +1,187 @@
|
|
|
1
|
-
# Skill
|
|
1
|
+
# Persuasion Principles for Skill Design
|
|
2
2
|
|
|
3
|
-
##
|
|
3
|
+
## Overview
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
LLMs respond to the same persuasion principles as humans. Understanding this psychology helps you design more effective skills - not to manipulate, but to ensure critical practices are followed even under pressure.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
**Research foundation:** Meincke et al. (2025) tested 7 persuasion principles with N=28,000 AI conversations. Persuasion techniques more than doubled compliance rates (33% → 72%, p < .001).
|
|
8
8
|
|
|
9
|
-
##
|
|
9
|
+
## The Seven Principles
|
|
10
10
|
|
|
11
|
-
### 1.
|
|
12
|
-
|
|
11
|
+
### 1. Authority
|
|
12
|
+
**What it is:** Deference to expertise, credentials, or official sources.
|
|
13
13
|
|
|
14
|
-
|
|
15
|
-
-
|
|
16
|
-
-
|
|
17
|
-
-
|
|
14
|
+
**How it works in skills:**
|
|
15
|
+
- Imperative language: "YOU MUST", "Never", "Always"
|
|
16
|
+
- Non-negotiable framing: "No exceptions"
|
|
17
|
+
- Eliminates decision fatigue and rationalization
|
|
18
18
|
|
|
19
|
-
|
|
20
|
-
-
|
|
21
|
-
-
|
|
22
|
-
-
|
|
19
|
+
**When to use:**
|
|
20
|
+
- Discipline-enforcing skills (TDD, verification requirements)
|
|
21
|
+
- Safety-critical practices
|
|
22
|
+
- Established best practices
|
|
23
23
|
|
|
24
|
-
|
|
24
|
+
**Example:**
|
|
25
25
|
```markdown
|
|
26
26
|
[OK] Write code before test? Delete it. Start over. No exceptions.
|
|
27
27
|
[FAIL] Consider writing tests first when feasible.
|
|
28
28
|
```
|
|
29
29
|
|
|
30
|
-
### 2.
|
|
31
|
-
|
|
30
|
+
### 2. Commitment
|
|
31
|
+
**What it is:** Consistency with prior actions, statements, or public declarations.
|
|
32
32
|
|
|
33
|
-
|
|
34
|
-
-
|
|
35
|
-
-
|
|
36
|
-
-
|
|
33
|
+
**How it works in skills:**
|
|
34
|
+
- Require announcements: "Announce skill usage"
|
|
35
|
+
- Force explicit choices: "Choose A, B, or C"
|
|
36
|
+
- Use tracking: todos for checklists
|
|
37
37
|
|
|
38
|
-
|
|
39
|
-
-
|
|
40
|
-
-
|
|
41
|
-
-
|
|
38
|
+
**When to use:**
|
|
39
|
+
- Ensuring skills are actually followed
|
|
40
|
+
- Multi-step processes
|
|
41
|
+
- Accountability mechanisms
|
|
42
42
|
|
|
43
|
-
|
|
43
|
+
**Example:**
|
|
44
44
|
```markdown
|
|
45
45
|
[OK] When you find a skill, you MUST announce: "I'm using [Skill Name]"
|
|
46
46
|
[FAIL] Consider letting your partner know which skill you're using.
|
|
47
47
|
```
|
|
48
48
|
|
|
49
|
-
### 3.
|
|
50
|
-
|
|
49
|
+
### 3. Scarcity
|
|
50
|
+
**What it is:** Urgency from time limits or limited availability.
|
|
51
51
|
|
|
52
|
-
|
|
53
|
-
-
|
|
54
|
-
-
|
|
55
|
-
-
|
|
52
|
+
**How it works in skills:**
|
|
53
|
+
- Time-bound requirements: "Before proceeding"
|
|
54
|
+
- Sequential dependencies: "Immediately after X"
|
|
55
|
+
- Prevents procrastination
|
|
56
56
|
|
|
57
|
-
|
|
58
|
-
-
|
|
59
|
-
-
|
|
60
|
-
-
|
|
57
|
+
**When to use:**
|
|
58
|
+
- Immediate verification requirements
|
|
59
|
+
- Time-sensitive workflows
|
|
60
|
+
- Preventing "I'll do it later"
|
|
61
61
|
|
|
62
|
-
|
|
62
|
+
**Example:**
|
|
63
63
|
```markdown
|
|
64
64
|
[OK] After completing a task, IMMEDIATELY request code review before proceeding.
|
|
65
65
|
[FAIL] You can review code when convenient.
|
|
66
66
|
```
|
|
67
67
|
|
|
68
|
-
### 4.
|
|
69
|
-
|
|
68
|
+
### 4. Social Proof
|
|
69
|
+
**What it is:** Conformity to what others do or what's considered normal.
|
|
70
70
|
|
|
71
|
-
|
|
72
|
-
-
|
|
73
|
-
-
|
|
74
|
-
-
|
|
71
|
+
**How it works in skills:**
|
|
72
|
+
- Universal patterns: "Every time", "Always"
|
|
73
|
+
- Failure modes: "X without Y = failure"
|
|
74
|
+
- Establishes norms
|
|
75
75
|
|
|
76
|
-
|
|
77
|
-
-
|
|
78
|
-
-
|
|
79
|
-
-
|
|
76
|
+
**When to use:**
|
|
77
|
+
- Documenting universal practices
|
|
78
|
+
- Warning about common failures
|
|
79
|
+
- Reinforcing standards
|
|
80
80
|
|
|
81
|
-
|
|
81
|
+
**Example:**
|
|
82
82
|
```markdown
|
|
83
83
|
[OK] Checklists without todo tracking = steps get skipped. Every time.
|
|
84
84
|
[FAIL] Some people find a todo list helpful for checklists.
|
|
85
85
|
```
|
|
86
86
|
|
|
87
|
-
### 5.
|
|
88
|
-
|
|
87
|
+
### 5. Unity
|
|
88
|
+
**What it is:** Shared identity, "we-ness", in-group belonging.
|
|
89
89
|
|
|
90
|
-
|
|
91
|
-
-
|
|
92
|
-
-
|
|
90
|
+
**How it works in skills:**
|
|
91
|
+
- Collaborative language: "our codebase", "we're colleagues"
|
|
92
|
+
- Shared goals: "we both want quality"
|
|
93
93
|
|
|
94
|
-
|
|
95
|
-
-
|
|
96
|
-
-
|
|
97
|
-
-
|
|
94
|
+
**When to use:**
|
|
95
|
+
- Collaborative workflows
|
|
96
|
+
- Establishing team culture
|
|
97
|
+
- Non-hierarchical practices
|
|
98
98
|
|
|
99
|
-
|
|
99
|
+
**Example:**
|
|
100
100
|
```markdown
|
|
101
101
|
[OK] We're colleagues working together. I need your honest technical judgment.
|
|
102
102
|
[FAIL] You should probably tell me if I'm wrong.
|
|
103
103
|
```
|
|
104
104
|
|
|
105
|
-
### 6.
|
|
106
|
-
|
|
105
|
+
### 6. Reciprocity
|
|
106
|
+
**What it is:** Obligation to return benefits received.
|
|
107
107
|
|
|
108
|
-
|
|
109
|
-
-
|
|
110
|
-
-
|
|
108
|
+
**How it works:**
|
|
109
|
+
- Use sparingly - can feel manipulative
|
|
110
|
+
- Rarely needed in skills
|
|
111
111
|
|
|
112
|
-
|
|
113
|
-
-
|
|
112
|
+
**When to avoid:**
|
|
113
|
+
- Almost always (other principles more effective)
|
|
114
114
|
|
|
115
|
-
### 7.
|
|
116
|
-
|
|
115
|
+
### 7. Liking
|
|
116
|
+
**What it is:** Preference for cooperating with those we like.
|
|
117
117
|
|
|
118
|
-
|
|
119
|
-
-
|
|
120
|
-
-
|
|
121
|
-
-
|
|
118
|
+
**How it works:**
|
|
119
|
+
- **DON'T USE for compliance**
|
|
120
|
+
- Conflicts with honest feedback culture
|
|
121
|
+
- Creates sycophancy
|
|
122
122
|
|
|
123
|
-
|
|
124
|
-
-
|
|
123
|
+
**When to avoid:**
|
|
124
|
+
- Always for discipline enforcement
|
|
125
125
|
|
|
126
|
-
##
|
|
126
|
+
## Principle Combinations by Skill Type
|
|
127
127
|
|
|
128
|
-
| Skill
|
|
128
|
+
| Skill Type | Use | Avoid |
|
|
129
129
|
|------------|-----|-------|
|
|
130
|
-
|
|
|
131
|
-
|
|
|
132
|
-
|
|
|
133
|
-
|
|
|
130
|
+
| Discipline-enforcing | Authority + Commitment + Social Proof | Liking, Reciprocity |
|
|
131
|
+
| Guidance/technique | Moderate Authority + Unity | Heavy authority |
|
|
132
|
+
| Collaborative | Unity + Commitment | Authority, Liking |
|
|
133
|
+
| Reference | Clarity only | All persuasion |
|
|
134
134
|
|
|
135
|
-
##
|
|
135
|
+
## Why This Works: The Psychology
|
|
136
136
|
|
|
137
|
-
|
|
138
|
-
- "YOU MUST"
|
|
139
|
-
-
|
|
140
|
-
-
|
|
137
|
+
**Bright-line rules reduce rationalization:**
|
|
138
|
+
- "YOU MUST" removes decision fatigue
|
|
139
|
+
- Absolute language eliminates "is this an exception?" questions
|
|
140
|
+
- Explicit anti-rationalization counters close specific loopholes
|
|
141
141
|
|
|
142
|
-
|
|
143
|
-
-
|
|
144
|
-
- "
|
|
145
|
-
-
|
|
142
|
+
**Implementation intentions create automatic behavior:**
|
|
143
|
+
- Clear triggers + required actions = automatic execution
|
|
144
|
+
- "When X, do Y" more effective than "generally do Y"
|
|
145
|
+
- Reduces cognitive load on compliance
|
|
146
146
|
|
|
147
|
-
|
|
148
|
-
-
|
|
149
|
-
-
|
|
150
|
-
-
|
|
151
|
-
-
|
|
147
|
+
**LLMs are parahuman:**
|
|
148
|
+
- Trained on human text containing these patterns
|
|
149
|
+
- Authority language precedes compliance in training data
|
|
150
|
+
- Commitment sequences (statement → action) frequently modeled
|
|
151
|
+
- Social proof patterns (everyone does X) establish norms
|
|
152
152
|
|
|
153
|
-
##
|
|
153
|
+
## Ethical Use
|
|
154
154
|
|
|
155
|
-
|
|
156
|
-
-
|
|
157
|
-
-
|
|
158
|
-
-
|
|
155
|
+
**Legitimate:**
|
|
156
|
+
- Ensuring critical practices are followed
|
|
157
|
+
- Creating effective documentation
|
|
158
|
+
- Preventing predictable failures
|
|
159
159
|
|
|
160
|
-
|
|
161
|
-
-
|
|
162
|
-
-
|
|
163
|
-
-
|
|
160
|
+
**Illegitimate:**
|
|
161
|
+
- Manipulating for personal gain
|
|
162
|
+
- Creating false urgency
|
|
163
|
+
- Guilt-based compliance
|
|
164
164
|
|
|
165
|
-
|
|
165
|
+
**The test:** Would this technique serve the user's genuine interests if they fully understood it?
|
|
166
166
|
|
|
167
|
-
##
|
|
167
|
+
## Research Citations
|
|
168
168
|
|
|
169
169
|
**Cialdini, R. B. (2021).** *Influence: The Psychology of Persuasion (New and Expanded).* Harper Business.
|
|
170
|
-
-
|
|
171
|
-
-
|
|
170
|
+
- Seven principles of persuasion
|
|
171
|
+
- Empirical foundation for influence research
|
|
172
172
|
|
|
173
173
|
**Meincke, L., Shapiro, D., Duckworth, A. L., Mollick, E., Mollick, L., & Cialdini, R. (2025).** Call Me A Jerk: Persuading AI to Comply with Objectionable Requests. University of Pennsylvania.
|
|
174
|
-
-
|
|
175
|
-
-
|
|
176
|
-
-
|
|
177
|
-
-
|
|
174
|
+
- Tested 7 principles with N=28,000 LLM conversations
|
|
175
|
+
- Compliance increased 33% → 72% with persuasion techniques
|
|
176
|
+
- Authority, commitment, scarcity most effective
|
|
177
|
+
- Validates parahuman model of LLM behavior
|
|
178
178
|
|
|
179
|
-
##
|
|
179
|
+
## Quick Reference
|
|
180
180
|
|
|
181
|
-
|
|
181
|
+
When designing a skill, ask:
|
|
182
182
|
|
|
183
|
-
1.
|
|
184
|
-
2.
|
|
185
|
-
3.
|
|
186
|
-
4.
|
|
187
|
-
5.
|
|
183
|
+
1. **What type is it?** (Discipline vs. guidance vs. reference)
|
|
184
|
+
2. **What behavior am I trying to change?**
|
|
185
|
+
3. **Which principle(s) apply?** (Usually authority + commitment for discipline)
|
|
186
|
+
4. **Am I combining too many?** (Don't use all seven)
|
|
187
|
+
5. **Is this ethical?** (Serves user's genuine interests?)
|