kilo-superpowers-compose 0.1.1 → 0.1.2
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 +63 -15
- package/bin/lib.js +2 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -11,7 +11,7 @@
|
|
|
11
11
|
|
|
12
12
|
## Status
|
|
13
13
|
|
|
14
|
-
**v0.1.
|
|
14
|
+
**v0.1.2.** Installed via the npm CLI and verified on both **Kilo CLI** and the
|
|
15
15
|
**VS Code Kilo Code** extension (they share the same config, so one install
|
|
16
16
|
covers both).
|
|
17
17
|
|
|
@@ -33,14 +33,37 @@ the full, disciplined Superpowers workflow on any coding task.
|
|
|
33
33
|
|
|
34
34
|
## Installation
|
|
35
35
|
|
|
36
|
+
> ⚠ **Two steps required.** Running only step ① (`npm install -g`) does
|
|
37
|
+
> nothing visible — it only installs the CLI binary, not the agent/command
|
|
38
|
+
> files, the skills link, or `kilo.jsonc`. Skipping step ② is the most
|
|
39
|
+
> common mistake.
|
|
40
|
+
|
|
41
|
+
**Step ① — Install the CLI**:
|
|
42
|
+
|
|
36
43
|
```bash
|
|
37
44
|
npm install -g kilo-superpowers-compose
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
Only installs the CLI binary (the `kilo-superpowers-compose` command
|
|
48
|
+
itself); does not touch your config directory.
|
|
49
|
+
|
|
50
|
+
**Step ② — Install into Kilo**:
|
|
51
|
+
|
|
52
|
+
```bash
|
|
38
53
|
kilo-superpowers-compose install
|
|
39
54
|
```
|
|
40
55
|
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
56
|
+
Copies the 3 agent files to `~/.config/kilo/agent/`, the command to
|
|
57
|
+
`~/.config/kilo/commands/`, creates the skills link at
|
|
58
|
+
`~/.kilo/skills/superpowers`, and adds an entry to `kilo.jsonc`'s
|
|
59
|
+
`skills.paths`. **Idempotent**: safe to re-run.
|
|
60
|
+
|
|
61
|
+
**Step ③ — Restart Kilo** (fully quit and reopen the CLI; **Reload Window**
|
|
62
|
+
in VS Code).
|
|
63
|
+
|
|
64
|
+
After this, `compose` appears in `/agents` and `/superpowers` works. One
|
|
65
|
+
install covers both Kilo CLI and the VS Code Kilo Code extension (they
|
|
66
|
+
share `~/.config/kilo/`).
|
|
44
67
|
|
|
45
68
|
### Kilo Marketplace (official channel — coming soon)
|
|
46
69
|
|
|
@@ -66,24 +89,49 @@ Until then, use the npm install above.
|
|
|
66
89
|
|
|
67
90
|
## Update & uninstall
|
|
68
91
|
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
92
|
+
> **Update is also two steps.** `npm update -g` upgrades the package
|
|
93
|
+
> itself; the `update` subcommand re-syncs the artifacts to Kilo's config.
|
|
94
|
+
> Running only step ① won't update your agents/commands/skills link.
|
|
95
|
+
|
|
96
|
+
**Update** (two steps, after a new version is published):
|
|
72
97
|
|
|
73
|
-
|
|
74
|
-
kilo-superpowers-compose
|
|
98
|
+
```bash
|
|
99
|
+
npm update -g kilo-superpowers-compose # ① upgrade the package
|
|
100
|
+
kilo-superpowers-compose update # ② re-sync artifacts to Kilo (idempotent)
|
|
75
101
|
```
|
|
76
102
|
|
|
77
|
-
|
|
103
|
+
You can also just re-run `kilo-superpowers-compose update` (without
|
|
104
|
+
`npm update`) — it refreshes artifacts using the current global package
|
|
105
|
+
version, but won't pull a newer version.
|
|
106
|
+
|
|
107
|
+
**Uninstall** (removes everything this package installed, manifest-based;
|
|
108
|
+
never touches your own files):
|
|
78
109
|
|
|
79
110
|
```bash
|
|
80
|
-
|
|
81
|
-
kilo-superpowers-compose
|
|
111
|
+
kilo-superpowers-compose uninstall # remove artifacts
|
|
112
|
+
npm uninstall -g kilo-superpowers-compose # remove the CLI itself
|
|
82
113
|
```
|
|
83
114
|
|
|
84
|
-
Uninstall removes: the skills link, the 3 agent files, the
|
|
85
|
-
command,
|
|
86
|
-
manifest. Your own skills, agents, and config
|
|
115
|
+
Uninstall removes: the skills link, the 3 agent files, the
|
|
116
|
+
`superpowers.md` command, this package's `skills.paths` entry in
|
|
117
|
+
`kilo.jsonc`, and the install manifest. Your own skills, agents, and config
|
|
118
|
+
are left untouched.
|
|
119
|
+
|
|
120
|
+
## Common mistakes
|
|
121
|
+
|
|
122
|
+
**"I ran `npm install -g` but `/agents` doesn't show `compose`."**
|
|
123
|
+
— You only ran step ①. The CLI is installed, but no agent files, skills
|
|
124
|
+
link, or command were created. Run `kilo-superpowers-compose install`.
|
|
125
|
+
|
|
126
|
+
**"I changed package code after install; restarting Kilo doesn't pick it up."**
|
|
127
|
+
— `~/.kilo/skills/superpowers` is a junction pointing to the package
|
|
128
|
+
directory, so package upgrades are picked up automatically. But
|
|
129
|
+
agent/command files were copied at install time and don't auto-update. Run
|
|
130
|
+
`kilo-superpowers-compose update`.
|
|
131
|
+
|
|
132
|
+
**"I added `plugin: ['kilo-superpowers-compose']` to `kilo.jsonc`."**
|
|
133
|
+
— Remove it. Current Kilo doesn't load this field; it only slows startup.
|
|
134
|
+
This package installs via the npm CLI — no `plugin` field needed.
|
|
87
135
|
|
|
88
136
|
## CLI usage
|
|
89
137
|
|
package/bin/lib.js
CHANGED
|
@@ -368,6 +368,8 @@ export function runInstall(opts = {}) {
|
|
|
368
368
|
console.log(` kilo.jsonc: skills.paths ${added ? '已新增条目' : '已存在（幂等跳过）'}`);
|
|
369
369
|
console.log('');
|
|
370
370
|
console.log(' 请重启 Kilo CLI / VS Code 扩展以加载。');
|
|
371
|
+
console.log('');
|
|
372
|
+
console.log(' 💡 To upgrade later: npm update -g kilo-superpowers-compose && kilo-superpowers-compose update');
|
|
371
373
|
return EXIT.OK;
|
|
372
374
|
}
|
|
373
375
|
|