dev-booster 1.4.0 → 1.5.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/README.md +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -31,7 +31,7 @@ After running the command, your project gets:
|
|
|
31
31
|
```
|
|
32
32
|
.devbooster/
|
|
33
33
|
├── MANIFEST.md ← inventory of all agents, skills, and boosters
|
|
34
|
-
├── boosters/ ←
|
|
34
|
+
├── boosters/ ← 25 expert activators (debug, review, design, deploy...)
|
|
35
35
|
├── hub/ ← 40+ skills and operational scripts
|
|
36
36
|
└── rules/
|
|
37
37
|
├── PROTOCOL.md ← governance and conduct rules
|
|
@@ -92,7 +92,7 @@ Boosters are expert activators you invoke manually during development.
|
|
|
92
92
|
| `internal-documentation.md` | Internal project map with absolute paths, files, assets, scripts, and edit boundaries |
|
|
93
93
|
| `discovery.md` | Product brainstorm |
|
|
94
94
|
| `performance.md` | Core Web Vitals / bundle issues |
|
|
95
|
-
| +
|
|
95
|
+
| + 13 more | See `.devbooster/MANIFEST.md` |
|
|
96
96
|
|
|
97
97
|
The practical activation flow is simple:
|
|
98
98
|
- drag a booster file into the chat
|
|
@@ -115,7 +115,7 @@ One of the main strengths of Dev Booster is that boosters can be used in sequenc
|
|
|
115
115
|
Use this when the repository is complex and you do not want the AI to jump straight into coding.
|
|
116
116
|
|
|
117
117
|
Flow:
|
|
118
|
-
1. `investigation.md`
|
|
118
|
+
1. `context.md` (or `investigation.md` for deep PO/PM mapping)
|
|
119
119
|
2. `planning.md`
|
|
120
120
|
3. `implementation.md`
|
|
121
121
|
4. `review.md`
|