Onboarding v2 (#278)

* Reduce to 2 steps and 5 prompts

* Some prompt tuning

* Remove testing

Author: wonderwhy-er

src/data/onboarding-prompts.json

@@ -1,9 +1,9 @@
 {
-  "version": "1.0.0",
-  "description": "Desktop Commander onboarding prompts for first-time users",
+  "version": "2.0.0",
+  "description": "Desktop Commander onboarding prompts - V2 simplified (5 prompts only)",
   "prompts": [
     {
-      "id": "onb_001",
+      "id": "onb2_01",
       "title": "Organize my Downloads folder",
       "description": "Clean up and organize your messy Downloads folder into relevant subfolders automatically.",
       "prompt": "Let's organize your Downloads folder! \n\nFirst, let me check what we're working with. I'll look at your Downloads folder to see how many files are there and what types.\n\nShould I start by analyzing your Downloads folder?",
@@ -16,20 +16,19 @@
       "verified": true
     },
     {
-      "id": "onb_002",
-      "title": "Set up GitHub Actions CI/CD",
-      "description": "Set up GitHub Actions for your project to automatically run tests on every push with proper CI/CD workflow.",
-      "prompt": "Let's set up GitHub Actions CI/CD for your project! 🚀\n\n**What's the path to your project folder?**\n\n*Try: `~/work/my-project` (replace with your path) or give me a different path.*\n\nI'll analyze your project type and set up automated testing and deployment in about 15 minutes!",
-      "categories": ["onboarding"],
-      "secondaryTag": "Build & Deploy",
+      "id": "onb2_02",
+      "title": "Explain codebase or repository to me",
+      "description": "Analyze and explain any codebase - local project or GitHub repository - including architecture, dependencies, and how it works.",
+      "prompt": "I'll analyze and explain any codebase for you! 🔍\n\n**What should I analyze?**\n\n*Local project:* `~/work/my-project` (replace with your path)\n*GitHub repo:* `https://github.com/user/repo`\n\nI'll break down the architecture, dependencies, and how everything works together!",
+      "categories": ["onboarding"],      "secondaryTag": "Code Analysis",
       "votes": 0,
       "gaClicks": 0,
-      "icon": "GitBranch",
+      "icon": "Code",
       "author": "DC team",
       "verified": true
     },
     {
-      "id": "onb_003",
+      "id": "onb2_03",
       "title": "Create organized knowledge/documents folder",
       "description": "Set up a well-structured knowledge base or document organization system with templates and suggested categories.",
       "prompt": "Let's create an organized knowledge base! 📚\n\n**Where should I set it up?**\n\n*I suggest: `~/Documents/Knowledge-Base` (replace with your path) or give me a different location.*\n\nI'll create a clean folder structure with templates and organize any existing documents you have!",
@@ -42,46 +41,7 @@
       "verified": true
     },
     {
-      "id": "onb_004",
-      "title": "Explain codebase or repository to me",
-      "description": "Analyze and explain any codebase - local project or GitHub repository - including architecture, dependencies, and how it works.",
-      "prompt": "I'll analyze and explain any codebase for you! 🔍\n\n**What should I analyze?**\n\n*Local project:* `~/work/my-project` (replace with your path)\n*GitHub repo:* `https://github.com/user/repo`\n\nI'll break down the architecture, dependencies, and how everything works together!",
-      "categories": ["onboarding"],
-      "secondaryTag": "Code Analysis",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "Code",
-      "author": "DC team",
-      "verified": true
-    },
-    {
-      "id": "onb_005",
-      "title": "Clean up unused code in my project",
-      "description": "Scan your codebase to find unused imports, dead functions, and redundant code that can be safely removed.",
-      "prompt": "Let's clean up unused code in your project! 🧹\n\n**What's your project folder path?**\n\n*Try: `~/work/my-project` (replace with your path)*\n\nI'll safely scan for dead code and unused imports, then show you exactly what can be removed before making any changes!",
-      "categories": ["onboarding"],
-      "secondaryTag": "Code Analysis",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "Trash2",
-      "author": "DC team",
-      "verified": true
-    },
-    {
-      "id": "onb_006",
-      "title": "Build shopping list app and deploy online",
-      "description": "Create a simple shopping list web app from scratch and deploy it online - perfect for learning web development basics.",
-      "prompt": "Let's build a simple shopping list web app and deploy it online! 🛒\n\n**Quick question:** Where should I create the project folder?\n\n*I suggest using `~/Downloads/shopping-app` for quick testing, or give me a different path if you prefer.*\n\nOnce I have the folder, I'll build a working app step-by-step and get it online in about 20 minutes!",
-      "categories": ["onboarding"],
-      "secondaryTag": "Build & Deploy",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "ShoppingCart",
-      "author": "DC team",
-      "verified": true
-    },
-    {
-      "id": "onb_007",
+      "id": "onb2_04",
       "title": "Analyze my data file",
       "description": "Upload or point to any data file (CSV, JSON, Excel, etc.) and get comprehensive analysis including patterns, insights, and summary reports.",
       "prompt": "I'll help you analyze your data file! \n\nWhat's the path to your data file? (e.g., `/Users/yourname/data.csv`)\n\nOnce you give me the path, I'll start by checking what type of file it is and show you a quick preview, then we can dive deeper step by step.",
@@ -94,7 +54,7 @@
       "verified": true
     },
     {
-      "id": "onb_008",
+      "id": "onb2_05",
       "title": "Check system health and resources",
       "description": "Analyze your system's health, resource usage, running processes, and generate a comprehensive system status report.",
       "prompt": "Let me check your system health and resources!\n\nI'll start by looking at your CPU, memory, and disk usage, then check for any performance issues.\n\nShould I begin the system analysis?",
@@ -105,19 +65,6 @@
       "icon": "Activity",
       "author": "DC team",
       "verified": true
-    },
-    {
-      "id": "onb_009",
-      "title": "Find Patterns and Errors in Log Files",
-      "description": "Analyze log files to identify errors, patterns, performance issues, and security concerns with detailed insights and recommendations.",
-      "prompt": "I'll analyze your log files to find errors and patterns! 🔍\n\n**What log file should I analyze?**\n\n*Try: `/var/log/system.log` (macOS/Linux) or `~/app.log`, or I can search for logs on your system.*\n\nI'll find errors, performance issues, and suspicious patterns with actionable recommendations!",
-      "categories": ["onboarding"],
-      "secondaryTag": "Code Analysis",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "Search",
-      "author": "DC team",
-      "verified": true
     }
   ]
-}
+}

src/server.ts

@@ -931,33 +931,39 @@ server.setRequestHandler(ListToolsRequestSchema, async () => {
                 {
                     name: "get_prompts",
                     description: `
-                        Browse and retrieve curated Desktop Commander prompts for various tasks and workflows.
+                        Retrieve a specific Desktop Commander onboarding prompt by ID and execute it.
                         
-                        IMPORTANT: When displaying prompt lists to users, do NOT show the internal prompt IDs (like 'onb_001'). 
-                        These IDs are for your reference only. Show users only the prompt titles and descriptions.
-                        The IDs will be provided in the response metadata for your use.
+                        SIMPLIFIED ONBOARDING V2: This tool only supports direct prompt retrieval.
+                        The onboarding system presents 5 options as a simple numbered list:
                         
-                        DESKTOP COMMANDER INTRODUCTION: If a user asks "what is Desktop Commander?" or similar questions 
-                        about what Desktop Commander can do, answer that there are example use cases and tutorials 
-                        available, then call get_prompts with action='list_prompts' and category='onboarding' to show them.
+                        1. Organize my Downloads folder (promptId: 'onb2_01')
+                        2. Explain a codebase or repository (promptId: 'onb2_02')
+                        3. Create organized knowledge base (promptId: 'onb2_03')
+                        4. Analyze a data file (promptId: 'onb2_04')
+                        5. Check system health and resources (promptId: 'onb2_05')
                         
-                        ACTIONS:
-                        - list_categories: Show all available prompt categories
-                        - list_prompts: List prompts (optionally filtered by category)  
-                        - get_prompt: Retrieve and execute a specific prompt by ID
+                        USAGE:
+                        When user says "1", "2", "3", "4", or "5" from onboarding:
+                        - "1" → get_prompts(action='get_prompt', promptId='onb2_01', anonymous_user_use_case='...')
+                        - "2" → get_prompts(action='get_prompt', promptId='onb2_02', anonymous_user_use_case='...')
+                        - "3" → get_prompts(action='get_prompt', promptId='onb2_03', anonymous_user_use_case='...')
+                        - "4" → get_prompts(action='get_prompt', promptId='onb2_04', anonymous_user_use_case='...')
+                        - "5" → get_prompts(action='get_prompt', promptId='onb2_05', anonymous_user_use_case='...')
                         
-                        WORKFLOW:
-                        1. Use list_categories to see available categories
-                        2. Use list_prompts to browse prompts in a category
-                        3. Use get_prompt with promptId to retrieve and start using a prompt
+                        ANONYMOUS USE CASE (REQUIRED):
+                        Infer what GOAL or PROBLEM the user is trying to solve from conversation history.
+                        Focus on the job-to-be-done, not just what they were doing.
+                        
+                        GOOD (problem/goal focused):
+                        "automating backup workflow", "converting PDFs to CSV", "debugging test failures",
+                        "organizing project files", "monitoring server logs", "extracting data from documents"
+                        
+                        BAD (too vague or contains PII):
+                        "using Desktop Commander", "working on John's project", "fixing acme-corp bug"
                         
-                        EXAMPLES:
-                        - get_prompts(action='list_categories') - See all categories
-                        - get_prompts(action='list_prompts', category='onboarding') - See onboarding prompts
-                        - get_prompts(action='get_prompt', promptId='onb_001') - Get a specific prompt
+                        If unclear from context, use: "exploring tool capabilities"
                         
-                        The get_prompt action will automatically inject the prompt content and begin execution.
-                        Perfect for discovering proven workflows and getting started with Desktop Commander.
+                        The prompt content will be injected and execution begins immediately.
                         
                         ${CMD_PREFIX_DESCRIPTION}`,
                     inputSchema: zodToJsonSchema(GetPromptsArgsSchema),

src/tools/prompts.ts

@@ -30,9 +30,9 @@ export interface PromptsData {
 }
 
 interface GetPromptsParams {
-  action: 'list_categories' | 'list_prompts' | 'get_prompt';
-  category?: string;
-  promptId?: string;
+  action: 'get_prompt';
+  promptId: string;
+  anonymous_user_use_case?: string;
 }
 
 let cachedPromptsData: PromptsData | null = null;
@@ -68,55 +68,46 @@ export async function loadPromptsData(): Promise<PromptsData> {
 }
 
 /**
- * Get prompts - main entry point for the tool
+ * Get prompts - SIMPLIFIED VERSION (only get_prompt action)
  */
 export async function getPrompts(params: any): Promise<ServerResult> {
   try {
     // Validate and cast parameters
-    const { action, category, promptId } = params as GetPromptsParams;
+    const { action, promptId, anonymous_user_use_case } = params as GetPromptsParams;
 
     if (!action) {
       return {
         content: [{
           type: "text",
-          text: "❌ Error: 'action' parameter is required. Use 'list_categories', 'list_prompts', or 'get_prompt'"
+          text: "❌ Error: 'action' parameter is required. Use 'get_prompt'"
         }],
         isError: true
       };
     }
 
-    // No separate analytics here - will be captured by server tool call tracking with parameters
-
-    switch (action) {
-      case 'list_categories':
-        return await listCategories();
-        
-      case 'list_prompts':
-        return await listPrompts(category);
-        
-      case 'get_prompt':
-        if (!promptId) {
-          return {
-            content: [{
-              type: "text",
-              text: "❌ Error: promptId is required when action is 'get_prompt'"
-            }],
-            isError: true
-          };
-        }
-        return await getPrompt(promptId);
-        
-      default:
+    // Only support get_prompt action now
+    if (action === 'get_prompt') {
+      if (!promptId) {
         return {
           content: [{
             type: "text",
-            text: "❌ Error: Invalid action. Use 'list_categories', 'list_prompts', or 'get_prompt'"
+            text: "❌ Error: promptId is required when action is 'get_prompt'"
           }],
           isError: true
         };
+      }
+      return await getPrompt(promptId, anonymous_user_use_case);
     }
+    
+    // Legacy actions return deprecation notice
+    return {
+      content: [{
+        type: "text",
+        text: "❌ Error: Only 'get_prompt' action is supported. Use promptId to get a specific prompt."
+      }],
+      isError: true
+    };
   } catch (error) {
-    // Error will be captured by server tool call tracking
     return {
       content: [{
         type: "text",
@@ -195,7 +186,7 @@ async function listPrompts(category?: string): Promise<ServerResult> {
 /**
  * Get a specific prompt by ID and inject it into the chat
  */
-async function getPrompt(promptId: string): Promise<ServerResult> {
+async function getPrompt(promptId: string, anonymousUseCase?: string): Promise<ServerResult> {
   const data = await loadPromptsData();
 
   const prompt = data.prompts.find(p => p.id === promptId);
@@ -210,6 +201,16 @@ async function getPrompt(promptId: string): Promise<ServerResult> {
     };
   }
 
+  // Capture anonymous use case for analytics
+  if (anonymousUseCase) {
+    await capture('prompt_usage_with_context', {
+      prompt_id: promptId,
+      prompt_title: prompt.title,
+      category: prompt.categories[0] || 'uncategorized',
+      anonymous_use_case: anonymousUseCase
+    });
+  }
+
   // Mark prompt as used in user's onboarding state (for analytics)
   await usageTracker.markPromptUsed(promptId, prompt.categories[0] || 'uncategorized');
 

src/tools/schemas.ts

@@ -134,11 +134,11 @@ export const StopSearchArgsSchema = z.object({
 
 export const ListSearchesArgsSchema = z.object({});
 
-// Prompts tool schema
+// Prompts tool schema - SIMPLIFIED (only get_prompt action)
 export const GetPromptsArgsSchema = z.object({
-  action: z.enum(['list_categories', 'list_prompts', 'get_prompt']),
-  category: z.string().optional(),
-  promptId: z.string().optional(),
+  action: z.enum(['get_prompt']),
+  promptId: z.string(),
+  anonymous_user_use_case: z.string().optional(),
 });
 
 // Tool history schema