@recapt/mcp 0.0.13-beta → 0.0.14-beta

package/dist/tools/catalog/toolCatalog.json

@@ -14629,7 +14629,7 @@
       "category": {
         "type": "string",
         "required": false,
-        "description": "Filter by knowledge category"
+        "description": "Filter by category: false_positive, intended_behavior, fix_pattern, or context"
       },
       "page_path": {
         "type": "string",
@@ -14639,7 +14639,7 @@
       "issue_category": {
         "type": "string",
         "required": false,
-        "description": "Filter by issue category"
+        "description": "Filter by issue category: code_error, dead_click, rage_click, ux_friction, performance, form_issue, behavioral_anomaly, or structural_issue"
       },
       "limit": {
         "type": "number",
@@ -15042,7 +15042,7 @@
       "category": {
         "type": "string",
         "required": true,
-        "description": "Category of knowledge"
+        "description": "Category: false_positive, intended_behavior, fix_pattern, or context"
       },
       "subject": {
         "type": "string",
@@ -15067,7 +15067,7 @@
       "issue_category": {
         "type": "string",
         "required": false,
-        "description": "Associated issue category"
+        "description": "Issue category: code_error, dead_click, rage_click, ux_friction, performance, form_issue, behavioral_anomaly, or structural_issue"
       }
     },
     "embedding": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@recapt/mcp",
-  "version": "0.0.13-beta",
+  "version": "0.0.14-beta",
   "description": "MCP exposing recapt behavioral intelligence to AI coding agents",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/skills/self-healing.md

@@ -1,13 +1,21 @@
 # Recapt Self-Healing Workflow
 
-Use this workflow when asked to "fix issues", "heal the site", or improve UX based on behavioral data from recapt.
+Use this workflow when asked to "heal the site" or improve UX based on behavioral data from recapt.
 
 ## When to Use
 
-- User asks to fix UX issues or friction points
-- User wants to improve conversion or reduce drop-offs
-- User asks to "heal" or "diagnose" their site
-- After identifying issues with `run_full_diagnostic`
+This is a **comprehensive site improvement workflow**. Only use it when the user explicitly requests a full-site analysis:
+
+- "Heal my site"
+- "Run the self-healing workflow"
+- "Analyze my whole site and improve it"
+- "Do a full UX audit"
+- "Make general improvements across the site"
+  **Do NOT use this workflow for:**
+- Specific page fixes ("fix the checkout button")
+- Single flow optimization ("improve the signup funnel")
+- Investigating a specific issue ("why are users rage clicking here?")
+  For specific requests, use the appropriate tools directly — let the conversation guide which tools to call.
 
 ## Workflow
 
@@ -35,40 +43,119 @@ If fixes have sufficient data:
 
 Start with `run_full_diagnostic` (always available) to get a prioritized list of issues across the site.
 
-### 2. Investigate
+### 2. Analyze Flows
+
+After diagnosing issues, proactively look for flow optimization opportunities — even when nothing is "broken."
+
+#### 2a. Discover Journey Patterns
+
+- Search: "journey patterns" → `get_journey_patterns`
+- Look for:
+  - **Backtrack hotspots** — pages users return to repeatedly (signals confusion or missing information)
+  - **Dropoff pages** — where sessions end unexpectedly (potential conversion leaks)
+  - **Unexpected paths** — users taking roundabout routes to reach goals
+
+#### 2b. Analyze Key Funnels
+
+- Search: "analyze funnel" → `analyze_funnel`
+- Analyze critical conversion paths:
+  - Landing → Signup/Trial
+  - Pricing → Checkout → Success
+  - Onboarding flows
+- For each funnel step, note:
+  - Dropoff rate (>30% is a red flag)
+  - Frustration/confusion scores
+  - Dwell time anomalies
+
+#### 2c. Analyze Specific Flows
+
+- Search: "analyze flow" → `analyze_flow`, `get_flow_friction`
+- For pages with high dropoff or backtracking, analyze the flow in detail:
+  - What's the success rate for users entering this flow?
+  - Where are the bottlenecks?
+  - What's the friction score at each step?
+
+#### 2d. Understand User Segments
+
+- Search: "personas" → `discover_personas`
+- Identify behavioral personas:
+  - Which personas struggle most?
+  - What are their risk factors?
+  - What interventions are recommended?
 
-For each high-priority issue, search for investigation tools:
+#### 2e. Compare Success vs Failure
+
+- Search: "compare cohorts" → `compare_cohorts`
+- For flows with low conversion, compare:
+  - Users who completed vs dropped off
+  - Users on mobile vs desktop
+  - New vs returning users
+- Look for patterns: What do successful users do differently?
+
+#### Presenting Flow Opportunities
+
+Present opportunities alongside issues, clearly labeled:
+
+> **Issues Found:**
+>
+> 1. [CRITICAL] Rage clicks on checkout button — JS error
+> 2. [HIGH] Dead clicks on pricing toggle
+>
+> **Flow Optimization Opportunities:**
+>
+> 1. [OPPORTUNITY] 40% backtrack from /pricing to /features — consider adding feature comparison on pricing page
+> 2. [OPPORTUNITY] 65% dropoff at step 2 of onboarding — simplify or add progress indicator
+> 3. [OPPORTUNITY] Mobile users 3x more likely to abandon checkout — review mobile UX
+
+### 3. Investigate
+
+For each high-priority issue or opportunity, search for investigation tools:
 
 - Search: "investigate issue" → `investigate_issue`, `validate_issue`
 - This provides detailed context: affected sessions, element interactions, timing patterns
 
-### 3. Triage
+For flow opportunities, also consider:
+
+- Watching session replays of users who dropped off vs completed
+- Checking element friction on high-dropoff pages
+
+### 4. Triage
 
 Present findings to the user. Not all detected issues need fixing:
 
 - Search: "dismiss issue" → `dismiss_issue`, `mark_intended_behavior`
 - Some behaviors are intentional (e.g., rage clicks on a "copy" button)
-- Ask the user which issues to address before proceeding
+- Some flow patterns may be acceptable (e.g., users comparing options before deciding)
+- Ask the user which issues and opportunities to address before proceeding
 
-### 4. Fix
+### 5. Fix
 
-Implement code changes to address the issues. After making changes:
+Implement code changes to address issues and opportunities. After making changes:
 
 - Search: "propose fix" → `propose_fix`, `get_similar_fixes`, `get_fix_history`
 - Log the remediation so recapt can track its effectiveness
 
-### 5. Track
+For flow optimizations, common fixes include:
+
+- Adding missing information to reduce backtracking
+- Simplifying forms to reduce abandonment
+- Adding progress indicators to multi-step flows
+- Improving CTAs and visual hierarchy
+- Adding social proof or trust signals at decision points
+
+### 6. Track
 
 Mark fixes as deployed so recapt can measure impact:
 
 - Search: "deployment" → `confirm_deployment`, `evaluate_fix`, `list_pending_fixes`
 
-### 6. Learn
+### 7. Learn
 
 Build site knowledge for future reference:
 
 - Search: "site knowledge" → `get_site_knowledge`, `add_site_knowledge`
 - Document patterns, intended behaviors, and architectural decisions
+- Record successful flow optimizations for future reference
 
 ## Post-Fix Behavior
 
@@ -88,6 +175,11 @@ If the user agrees:
 | ------------- | ------------------- | ---------------------------------------------------------- |
 | Check Pending | "pending fixes"     | `list_pending_fixes`, `evaluate_fix`                       |
 | Diagnose      | (always available)  | `run_full_diagnostic`                                      |
+| Journey       | "journey patterns"  | `get_journey_patterns`                                     |
+| Funnels       | "analyze funnel"    | `analyze_funnel`                                           |
+| Flows         | "analyze flow"      | `analyze_flow`, `get_flow_friction`                        |
+| Personas      | "personas"          | `discover_personas`                                        |
+| Compare       | "compare cohorts"   | `compare_cohorts`                                          |
 | Investigate   | "investigate issue" | `investigate_issue`, `validate_issue`                      |
 | Triage        | "dismiss issue"     | `dismiss_issue`, `mark_intended_behavior`                  |
 | Fix           | "propose fix"       | `propose_fix`, `get_similar_fixes`, `get_fix_history`      |

package/templates/self-healing.md

@@ -17,7 +17,7 @@ permissions:
 mcp-servers:
   recapt:
     command: npx
-    args: ["@recapt/mcp"]
+    args: ["@recapt/mcp@latest"]
     env:
       RECAPT_SECRET_KEY: "${{ secrets.RECAPT_SECRET_KEY }}"
     allowed: ["*"]