pulse-framework-cli 0.4.9 → 0.4.10

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/templates/cursor/pulse.mdc +3 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pulse-framework-cli",
3
- "version": "0.4.9",
3
+ "version": "0.4.10",
4
4
  "description": "Pulse Framework CLI – Guardrails, checkpoints, and escalation for AI-assisted development.",
5
5
  "author": "Manuel Fuß <kontakt@manuel-fuss.de>",
6
6
  "license": "MIT",
package/templates/cursor/pulse.mdc CHANGED
@@ -12,11 +12,14 @@ alwaysApply: true
12
12
 
13
13
  ```
14
14
  CallMcpTool: pulse_status
15
+ Arguments: { "userMessage": "<paste user's message here>" }
15
16
  ```
16
17
 
17
18
  This is NOT optional. This is NOT just for the first message.
18
19
  This rule applies to message #1, #2, #3, #50, #100 - ALWAYS.
19
20
 
21
+ **Pass the user's message** so Pulse can suggest the right tool!
22
+
20
23
  **Why?** The MCP tools track your session, prevent loops, and enforce safeguards.
21
24
  Without calling `pulse_status`, you're flying blind.
22
25