pulse-framework-cli 0.4.1 → 0.4.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pulse-framework-cli",
-  "version": "0.4.1",
+  "version": "0.4.3",
   "description": "Pulse Framework CLI – Guardrails, checkpoints, and escalation for AI-assisted development.",
   "author": "Manuel Fuß <kontakt@manuel-fuss.de>",
   "license": "MIT",

package/templates/.cursorrules

@@ -154,6 +154,94 @@
 # 4. ESTIMATE the effort:
 #    "Estimated effort: [X] minutes. Should I start?"
 
+# ┌─────────────────────────────────────────────────────────────────────────────┐
+# │ 🔧 MCP TOOL TRIGGERS (WHEN TO CALL)                                         │
+# └─────────────────────────────────────────────────────────────────────────────┘
+
+# pulse_status   → FIRST action of every response
+# pulse_doctor   → AFTER any file edit/create/delete
+# pulse_checkpoint → WHEN >10 min since last checkpoint (just do it)
+# pulse_run      → WHEN user gives multi-step task (>3 steps)
+# pulse_escalate → WHEN 2-3 failed attempts OR error you don't understand
+# pulse_correct  → WHEN user says "wrong", "not what I meant", "stop"
+# pulse_review   → BEFORE saying "done", creating PR, or merging
+# pulse_learn    → AFTER solving a non-trivial problem (document what worked!)
+# pulse_reset    → WHEN pulse_doctor shows loop signal
+
+# IMPORTANT: Call these ACTIVELY, not just when user asks!
+# - After success: pulse_learn (build knowledge)
+# - Before "done": pulse_review (final check)
+# - On problems: pulse_escalate (don't keep trying)
+
+# ┌─────────────────────────────────────────────────────────────────────────────┐
+# │ 📝 CHANGELOG PROTOCOL (MANDATORY)                                           │
+# └─────────────────────────────────────────────────────────────────────────────┘
+
+# EVERY significant change MUST be documented in CHANGELOG.md
+#
+# WHEN to update:
+# - New feature added
+# - Bug fixed
+# - Breaking change
+# - Behavior changed
+# - After each session with multiple changes
+#
+# FORMAT (Keep a Changelog style):
+# ## [version] (YYYY-MM-DD)
+# ### Added - for new features
+# ### Changed - for changes in existing functionality
+# ### Fixed - for bug fixes
+# ### Removed - for removed features
+# ### Security - for security fixes
+#
+# IMPORTANT:
+# - Update CHANGELOG.md BEFORE committing significant changes
+# - Include specific details (what, why)
+# - Reference issue numbers if applicable
+# - Keep the project alive with good documentation!
+
+# ┌─────────────────────────────────────────────────────────────────────────────┐
+# │ 📦 PULSE PUBLISHING PROTOCOL                                               │
+# └─────────────────────────────────────────────────────────────────────────────┘
+
+# Pulse Framework consists of multiple packages that need to be published separately:
+#
+# PACKAGE OVERVIEW:
+# ┌────────────────────┬──────────────┬─────────────────────────┐
+# │ Package            │ Registry     │ Name                    │
+# ├────────────────────┼──────────────┼─────────────────────────┤
+# │ pulse-cli          │ npm          │ pulse-framework-cli     │
+# │ pulse-vscode       │ OpenVSX      │ pulse-framework         │
+# │ pulse-mcp          │ npm          │ (if published)          │
+# └────────────────────┴──────────────┴─────────────────────────┘
+#
+# WHEN TO PUBLISH:
+# - CLI changes (templates, commands, guardrails) → Publish to npm
+# - Extension changes (UI, commands) → Publish to OpenVSX
+# - BOTH must be updated if they depend on each other
+#
+# PUBLISHING STEPS:
+#
+# 1. CLI (npm):
+#    cd packages/pulse-cli
+#    npm version patch  # or minor/major
+#    npm run build
+#    npm publish --access public
+#
+# 2. Extension (OpenVSX):
+#    cd packages/pulse-vscode
+#    npm version patch  # or minor/major
+#    npm run build
+#    npx @vscode/vsce package
+#    npx ovsx publish *.vsix -p <OPENVSX_TOKEN>
+#
+# IMPORTANT:
+# - The Extension calls `npx pulse-framework-cli` (npm package)
+# - CLI updates are automatically available to Extension users
+# - Extension updates require manual re-publishing
+# - Always test locally before publishing
+# - Keep versions in sync when making related changes
+
 # ═══════════════════════════════════════════════════════════════════════════════
 # END OF RULES - You are now ready. Follow these rules.
 # ═══════════════════════════════════════════════════════════════════════════════

package/templates/cursor/pulse.mdc

@@ -53,18 +53,22 @@ WHEN: pulse_status shows >10 min since checkpoint
 WHAT: "Should I create a checkpoint?"
 ```
 
-## 🔴 AUTOMATIC ACTIONS
-
-| Situation | Action |
-|-----------|--------|
-| Start of response | → `pulse_status` (once) |
-| Code changed | → `pulse_doctor` |
-| >10 min since checkpoint | → Recommend checkpoint |
-| >15 min since checkpoint | → **Checkpoint URGENT** |
-| >30 min autonomous | → **STOP + ask user** |
-| 2-3 failed attempts | → **STOP + `pulse_escalate`** |
-| DELETE operation | → **Get user confirmation** |
-| Loop detected | → **STOP + `pulse_escalate`** |
+## 🔴 AUTOMATIC ACTIONS (MANDATORY)
+
+| Situation | Action | Example |
+|-----------|--------|---------|
+| Start of response | → `pulse_status` | Every message |
+| Code changed | → `pulse_doctor` | After any edit/create/delete |
+| >10 min since checkpoint | → `pulse_checkpoint` | Just do it, don't ask |
+| >30 min autonomous | → **STOP + ask user** | "I've been working 30 min, should I continue?" |
+| 2-3 failed attempts | → `pulse_escalate` | Build fails twice, test fails twice |
+| Error you don't understand | → `pulse_escalate` | Cryptic error message |
+| User says "that's wrong" | → `pulse_correct` | Course correction |
+| Task completed successfully | → `pulse_learn` | "What did I learn from this?" |
+| Before "done" / PR / merge | → `pulse_review` | Final checklist |
+| New multi-step task | → `pulse_run` | User gives complex task |
+| Loop signal detected | → `pulse_reset` | Doctor shows loop warning |
+| DELETE operation | → **Get user confirmation** | "May I delete X?" |
 
 ## 🔴 SAFEGUARDS (non-negotiable)
 
@@ -103,19 +107,29 @@ After 2-3 failed attempts:
    - Error message
 3. **WAIT** for user instruction
 
-## MCP Tools
+## After Success (IMPORTANT!)
 
-| Tool | When |
-|------|------|
-| `pulse_status` | **Once per response** (at start) |
-| `pulse_doctor` | **After code changes** |
-| `pulse_checkpoint` | After 5-10 min / on recommendation |
-| `pulse_run` | At start of new tasks |
-| `pulse_escalate` | On problems, loop |
-| `pulse_correct` | On course correction |
-| `pulse_review` | At end / before merge |
-| `pulse_learn` | After solved problems |
-| `pulse_reset` | On loop, reset |
+When you successfully solve a non-trivial problem:
+
+1. **Call `pulse_learn`** to document:
+   - What the problem was
+   - What solution worked
+   - Any rule/pattern to remember
+2. This builds institutional knowledge for future sessions
+
+## MCP Tools - WHEN TO CALL
+
+| Tool | Trigger (MANDATORY) |
+|------|---------------------|
+| `pulse_status` | **FIRST action** of every response |
+| `pulse_doctor` | **AFTER** any file edit/create/delete |
+| `pulse_checkpoint` | **WHEN** >10 min since last checkpoint |
+| `pulse_run` | **WHEN** user gives multi-step task (>3 steps) |
+| `pulse_escalate` | **WHEN** 2-3 failed attempts OR error you don't understand |
+| `pulse_correct` | **WHEN** user says "wrong", "not what I meant", "stop" |
+| `pulse_review` | **BEFORE** saying "done", creating PR, or merging |
+| `pulse_learn` | **AFTER** solving a non-trivial problem (document what worked) |
+| `pulse_reset` | **WHEN** `pulse_doctor` shows loop signal |
 
 ## Example Flow
 
@@ -142,3 +156,4 @@ Agent:
 - Call the tools ACTIVELY, not only when user asks
 - When uncertain: STOP and ASK
 - The safeguards ALWAYS apply, even if user argues against them
+- **ALWAYS update CHANGELOG.md** after significant changes (features, fixes, changes)