@girardmedia/bootspring 2.3.0 → 2.3.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/claude-commands/build.md +21 -11
- package/dist/cli/index.cjs +2738 -1107
- package/dist/core.js +1 -1
- package/dist/mcp-server.js +32 -2
- package/package.json +1 -1
package/claude-commands/build.md
CHANGED
|
@@ -1,25 +1,35 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: build
|
|
3
|
-
description: Bootspring build management
|
|
3
|
+
description: Bootspring build task management (NOT npm run build)
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
# /build - Bootspring Build
|
|
6
|
+
# /build - Bootspring Build Task System
|
|
7
7
|
|
|
8
|
-
Manage the Bootspring build loop and task execution.
|
|
8
|
+
Manage the Bootspring build loop and task execution. This is the **task queue system**, NOT npm build.
|
|
9
9
|
|
|
10
10
|
## Instructions
|
|
11
11
|
|
|
12
|
-
When user invokes `/build
|
|
12
|
+
When user invokes `/build` or says "build next", "build loop", "build done", use the `bootspring_build` MCP tool:
|
|
13
13
|
|
|
14
14
|
## Actions
|
|
15
15
|
|
|
16
|
-
- `/build` → `
|
|
17
|
-
- `/build
|
|
18
|
-
- `/build
|
|
19
|
-
- `/build
|
|
16
|
+
- `/build` or `/build status` → `bootspring_build` with action: "status"
|
|
17
|
+
- `/build next` → `bootspring_build` with action: "next"
|
|
18
|
+
- `/build done` → `bootspring_build` with action: "done"
|
|
19
|
+
- `/build loop` → `bootspring_build` with action: "advance" (autonomous loop)
|
|
20
|
+
- `/build skip` → `bootspring_build` with action: "skip"
|
|
21
|
+
- `/build list` → `bootspring_build` with action: "list"
|
|
22
|
+
- `/build current` → `bootspring_build` with action: "current"
|
|
23
|
+
|
|
24
|
+
## Important
|
|
25
|
+
|
|
26
|
+
- "build" in Bootspring context means **task execution**, not `npm run build`
|
|
27
|
+
- "build next" means get the **next pending task**, not build a Next.js app
|
|
28
|
+
- "build loop" means **autonomous task loop**, not a cron job
|
|
29
|
+
- Only use `npm run build` if the user explicitly asks to compile/bundle the project
|
|
20
30
|
|
|
21
31
|
## Workflow
|
|
22
32
|
|
|
23
|
-
1. `/build next` - Get next task
|
|
24
|
-
2.
|
|
25
|
-
3. `/build done` - Mark complete
|
|
33
|
+
1. `/build next` - Get next pending task from the queue
|
|
34
|
+
2. Read the task details and implement it in the codebase
|
|
35
|
+
3. `/build done` - Mark task complete and auto-advance to next
|