dev-booster 1.17.1 → 1.18.0
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/package.json
CHANGED
package/src/index.js
CHANGED
|
@@ -20,6 +20,30 @@ const IDE_BRIDGE_BLOCK = [
|
|
|
20
20
|
"Before any action, read `.devbooster/rules/PROTOCOL.md` for full governance rules.",
|
|
21
21
|
];
|
|
22
22
|
const IDE_BRIDGE_MARKER = ".devbooster/rules/PROTOCOL.md";
|
|
23
|
+
|
|
24
|
+
const AGENTS_TRIGGER_BLOCK = [
|
|
25
|
+
"",
|
|
26
|
+
"## Instant Triggers",
|
|
27
|
+
"",
|
|
28
|
+
"You can instantly activate any Dev Booster behavior by typing the corresponding `@` trigger in chat.",
|
|
29
|
+
"",
|
|
30
|
+
"**Important:** A trigger activates the booster's contract mode only (Armed/Stage 0).",
|
|
31
|
+
"It does NOT authorize the booster to analyze, investigate, or modify the project.",
|
|
32
|
+
"After activation, provide the concrete task or symptom before the booster proceeds.",
|
|
33
|
+
"",
|
|
34
|
+
"Read `.devbooster/rules/TRIGGERS.md` for the complete trigger dictionary.",
|
|
35
|
+
"",
|
|
36
|
+
"Common examples:",
|
|
37
|
+
"- `@Frontend` — activate frontend specialist",
|
|
38
|
+
"- `@Backend` — activate backend architect",
|
|
39
|
+
"- `@Debug` — systematic root cause analysis",
|
|
40
|
+
"- `@Audit` — lint and typecheck audit",
|
|
41
|
+
"- `@Refactor` — clean code and SOLID refactoring",
|
|
42
|
+
"- `@Performance` — Web Vitals and optimization",
|
|
43
|
+
"- `@Testing` — test strategy and coordination",
|
|
44
|
+
"- `@Advisor` — kit GPS to choose the right booster",
|
|
45
|
+
];
|
|
46
|
+
const AGENTS_TRIGGER_MARKER = "TRIGGERS.md";
|
|
23
47
|
const IDE_BRIDGE_FALLBACK_FLAG = path.join("hub", "flags", "needs-ide-bridge");
|
|
24
48
|
const IDE_BRIDGE_TARGETS = [
|
|
25
49
|
".rules",
|
|
@@ -242,6 +266,41 @@ function setupIdeBridgeFiles(dryRun) {
|
|
|
242
266
|
);
|
|
243
267
|
}
|
|
244
268
|
|
|
269
|
+
function ensureAgentsTriggers(dryRun) {
|
|
270
|
+
const agentsPath = path.join(TARGET_DIR, "AGENTS.md");
|
|
271
|
+
|
|
272
|
+
if (!fs.existsSync(agentsPath)) {
|
|
273
|
+
if (!dryRun) {
|
|
274
|
+
const fullBlock = [
|
|
275
|
+
"# 🤖 DEV BOOSTER — AGENTIC KIT BOOTSTRAP",
|
|
276
|
+
"",
|
|
277
|
+
"Before any action, read `.devbooster/rules/PROTOCOL.md` for full governance rules.",
|
|
278
|
+
...AGENTS_TRIGGER_BLOCK,
|
|
279
|
+
"",
|
|
280
|
+
];
|
|
281
|
+
fs.writeFileSync(agentsPath, fullBlock.join("\n"));
|
|
282
|
+
}
|
|
283
|
+
console.log(
|
|
284
|
+
` status: ${dryRun ? "would be created" : "created"} with protocol + triggers`,
|
|
285
|
+
);
|
|
286
|
+
return;
|
|
287
|
+
}
|
|
288
|
+
|
|
289
|
+
const existing = fs.readFileSync(agentsPath, "utf8");
|
|
290
|
+
if (existing.includes(AGENTS_TRIGGER_MARKER)) {
|
|
291
|
+
console.log(" status: triggers already present (preserved)");
|
|
292
|
+
return;
|
|
293
|
+
}
|
|
294
|
+
|
|
295
|
+
if (!dryRun) {
|
|
296
|
+
const updated = existing.trimEnd() + "\n\n" + AGENTS_TRIGGER_BLOCK.join("\n") + "\n";
|
|
297
|
+
fs.writeFileSync(agentsPath, updated);
|
|
298
|
+
}
|
|
299
|
+
console.log(
|
|
300
|
+
` status: triggers section ${dryRun ? "would be appended" : "appended"}`,
|
|
301
|
+
);
|
|
302
|
+
}
|
|
303
|
+
|
|
245
304
|
function checkLocalInstall() {
|
|
246
305
|
try {
|
|
247
306
|
const localPkg = path.join(
|
|
@@ -348,6 +407,7 @@ async function runInstall() {
|
|
|
348
407
|
|
|
349
408
|
await maybeAddDevBoosterToGitignore(dryRun);
|
|
350
409
|
setupIdeBridgeFiles(dryRun);
|
|
410
|
+
ensureAgentsTriggers(dryRun);
|
|
351
411
|
|
|
352
412
|
console.log(`
|
|
353
413
|
╭──────────────────────────────────────────────╮
|
|
@@ -435,6 +495,8 @@ function runUpdate() {
|
|
|
435
495
|
console.log(" ✔ TRIGGERS.md (updated)");
|
|
436
496
|
console.log(" ℹ Whitelabel stack rules (preserved)\n");
|
|
437
497
|
|
|
498
|
+
ensureAgentsTriggers(dryRun);
|
|
499
|
+
|
|
438
500
|
console.log("▸ DEVBOOSTER_INIT.md");
|
|
439
501
|
console.log(" status: preserved (no changes made)\n");
|
|
440
502
|
|
|
@@ -32,6 +32,7 @@ These triggers execute background utility tasks and update persistent rule or st
|
|
|
32
32
|
These triggers instantly activate specific booster behavior contracts without requiring the user to manually load the booster files. Upon invocation, immediately read the corresponding booster file in `.devbooster/boosters/` and follow its execution instructions.
|
|
33
33
|
|
|
34
34
|
- **`@AutoTriage`** ➔ Activates `.devbooster/boosters/auto-triage.md` (Artifact-centered automatic engineering triage with separate Plan + Review and execution approvals).
|
|
35
|
+
- **`@SmartTask`** ➔ Activates `.devbooster/boosters/smart-task.md` (Lightweight triage with full investigation depth, single "pode seguir" approval, atomic plan + Builder execution, persisted artifact).
|
|
35
36
|
- **`@Context`** ➔ Actives `.devbooster/boosters/context.md` (Silent Sponge context mapping).
|
|
36
37
|
- **`@Coder`** ➔ Activates `.devbooster/boosters/coder.md` (Co-Creative design/writing).
|
|
37
38
|
- **`@Builder`** ➔ Activates `.devbooster/boosters/builder.md` (Senior plan audit & execution).
|
|
@@ -13,7 +13,8 @@ Execute each step in order. Do not skip steps. Do not ask for confirmation betwe
|
|
|
13
13
|
|
|
14
14
|
### STEP 1 — Read the Governance Protocol
|
|
15
15
|
Read `.devbooster/rules/PROTOCOL.md` in full.
|
|
16
|
-
This defines your conduct rules, communication style, and architectural constraints.
|
|
16
|
+
This defines your conduct rules, communication style, and architectural constraints.
|
|
17
|
+
For instant `@` shortcut triggers (`@Frontend`, `@Debug`, `@Audit`, etc.), see `AGENTS.md` at the project root (created in Step 6).
|
|
17
18
|
|
|
18
19
|
### STEP 2 — Bootstrap PROJECT.md
|
|
19
20
|
Read `.devbooster/rules/PROJECT.md`.
|
|
@@ -41,6 +42,26 @@ In that case, create `AGENTS.md` at the project root and insert the following bl
|
|
|
41
42
|
# 🤖 DEV BOOSTER — AGENTIC KIT BOOTSTRAP
|
|
42
43
|
|
|
43
44
|
Before any action, read `.devbooster/rules/PROTOCOL.md` for full governance rules.
|
|
45
|
+
|
|
46
|
+
## Instant Triggers
|
|
47
|
+
|
|
48
|
+
You can instantly activate any Dev Booster behavior by typing the corresponding `@` trigger in chat.
|
|
49
|
+
|
|
50
|
+
**Important:** A trigger activates the booster's contract mode only (Armed/Stage 0).
|
|
51
|
+
It does NOT authorize the booster to analyze, investigate, or modify the project.
|
|
52
|
+
After activation, provide the concrete task or symptom before the booster proceeds.
|
|
53
|
+
|
|
54
|
+
Read `.devbooster/rules/TRIGGERS.md` for the complete trigger dictionary.
|
|
55
|
+
|
|
56
|
+
Common examples:
|
|
57
|
+
- `@Frontend` — activate frontend specialist
|
|
58
|
+
- `@Backend` — activate backend architect
|
|
59
|
+
- `@Debug` — systematic root cause analysis
|
|
60
|
+
- `@Audit` — lint and typecheck audit
|
|
61
|
+
- `@Refactor` — clean code and SOLID refactoring
|
|
62
|
+
- `@Performance` — Web Vitals and optimization
|
|
63
|
+
- `@Testing` — test strategy and coordination
|
|
64
|
+
- `@Advisor` — kit GPS to choose the right booster
|
|
44
65
|
```
|
|
45
66
|
|
|
46
67
|
Do not duplicate the block if the file already references `.devbooster/rules/PROTOCOL.md`.
|