@wonderwhy-er/desktop-commander 0.2.11 → 0.2.12

package/dist/data/onboarding-prompts.json

@@ -0,0 +1,114 @@
+{
+  "version": "1.0.0",
+  "description": "Desktop Commander onboarding prompts for first-time users",
+  "prompts": [
+    {
+      "id": "onb_001",
+      "title": "Organize my Downloads folder",
+      "description": "Clean up and organize your messy Downloads folder into relevant subfolders automatically.",
+      "prompt": "I want you to help me organize my Downloads folder. Let's do this step by step:\n\n**Phase 1: Analysis**\n1. First, analyze what's in my Downloads folder to understand the types of files\n2. Show me what file types and categories I have\n\n**Phase 2: Planning** \n3. Based on what you find, propose a logical folder structure\n4. Ask for my approval of the organization plan before proceeding\n\n**Phase 3: Organization**\n5. After I approve, create the necessary subfolders\n6. Move files into appropriate categories (documents, images, videos, software, etc.)\n7. Provide a summary of what was organized\n\n**Important**: Don't move any files until I approve your proposed organization structure.\n\nStart by exploring my Downloads folder and showing me what you find, then wait for my approval before organizing.",
+      "categories": ["onboarding"],
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "FolderOpen",
+      "author": "DC team",
+      "verified": true
+    },
+    {
+      "id": "onb_002",
+      "title": "Get my IP address and system info",
+      "description": "Quickly get your IP address and basic system information.",
+      "prompt": "Please help me get my system information:\n\n1. Get my current IP address (both local and public if possible)\n2. Show basic system information like:\n   - Operating system and version\n   - Available disk space\n   - Memory usage\n   - Current date and time\n   - Network connectivity status\n\nProvide this information in a clear, easy-to-read format.",
+      "categories": ["onboarding"],
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "Monitor",
+      "author": "DC team",
+      "verified": true
+    },
+    {
+      "id": "onb_003",
+      "title": "Create organized knowledge/documents folder",
+      "description": "Set up a well-structured knowledge base or document organization system with templates and suggested categories.",
+      "prompt": "I want to help you create a well-organized knowledge base and document system. Let me understand your needs first:\n\n**Option 1: Create New Knowledge Base**\n- What type of work or projects do you typically do?\n- What subjects or topics would you like to organize knowledge about?\n- Do you prefer a general-purpose system or something specialized?\n\n**Option 2: Organize Existing Documents**\n- Do you have an existing folder with documents that needs organization?\n- What's the path to the folder you'd like me to analyze?\n\n**My Process:**\n1. **Assessment**: Understand your needs and existing content\n2. **Structure Design**: Propose a folder hierarchy tailored to your work\n3. **Template Creation**: Create useful template files (notes, project plans, etc.)\n4. **Organization**: Set up the complete system with guidelines\n\nWhich option sounds better - creating a new knowledge base from scratch, or organizing existing documents? And what type of work/subjects do you focus on?",
+      "categories": ["onboarding"],
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "BookOpen",
+      "author": "DC team",
+      "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 help you understand a codebase thoroughly. Let me know what you'd like to analyze:\n\n**Option 1: Local Project**\n- What's the folder path to your local project?\n\n**Option 2: GitHub Repository**\n- What's the GitHub repository URL you'd like me to analyze?\n- If you don't have git/gh installed, I'll help you set them up\n- If needed, I'll help you log in to GitHub\n\n**What I'll do:**\n1. **Setup**: Install git/gh CLI tools if needed and help with GitHub login\n2. **Code Retrieval**: Clone the repo or analyze your local folder\n3. **Initial Analysis**: Examine project structure, files, and technologies\n4. **Architecture Overview**: Explain the overall design and patterns\n5. **Key Components**: Break down main modules and features\n6. **Dependencies**: Document libraries and frameworks used\n7. **Setup Guide**: Provide step-by-step setup and running instructions\n8. **Code Flow**: Explain how the main functionality works\n9. **Summary Document**: Create comprehensive documentation\n\nPlease provide either:\n- Local folder path: `/path/to/your/project`\n- GitHub URL: `https://github.com/user/repo` or `git@github.com:user/repo.git`",
+      "categories": ["onboarding"],
+      "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": "I'll help you clean up unused and dead code in your project. Let's start safely:\n\n**First, I need to know:**\n- What's the folder path to your project?\n- What programming language/framework is it? (JavaScript, Python, Java, etc.)\n\n**My systematic approach:**\n\n**Phase 1: Analysis**\n1. **Project Understanding**: Analyze structure and main technologies\n2. **Dependency Mapping**: Understand how files reference each other\n3. **Code Scanning**: Identify potential unused code:\n   - Unused imports and dependencies\n   - Dead/unreferenced functions and variables\n   - Unreachable code blocks\n   - Unused configuration files\n\n**Phase 2: Safety & Backup**\n4. **Impact Assessment**: Explain what each finding does and removal safety\n5. **Backup Strategy**: Recommend backup before making changes\n6. **Show Before Remove**: Present everything I plan to remove\n\n**Phase 3: Cleanup (Only with your approval)**\n7. **Selective Removal**: Remove only what you approve\n8. **Testing**: Suggest running tests after cleanup\n9. **Summary Report**: Document what was cleaned and space saved\n\n**Safety Promise**: I will NEVER remove code without your explicit approval for each change.\n\nWhat's the path to your project folder?",
+      "categories": ["onboarding"],
+      "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 complete shopping list web application from scratch, run it locally, and deploy it to GitHub Pages.",
+      "prompt": "Let's build and deploy a complete shopping list web application! I'll guide you step-by-step:\n\n**Step 1: Project Setup**\nFirst, where would you like to work on this project? Please provide a folder path where I should create the shopping list app.\n\n**My Complete Process:**\n\n**Phase 1: Planning & Setup**\n1. Create project folder and basic structure\n2. Plan app features (add/remove items, mark as bought, categories)\n3. Set up HTML, CSS, and JavaScript foundation\n\n**Phase 2: Development**\n4. Build clean, modern user interface\n5. Implement core functionality (CRUD operations)\n6. Add local storage for persistence\n7. Create a simple local development server\n8. Open the app in your browser for testing\n\n**Phase 3: GitHub & Deployment** \n9. Check if you have git/gh CLI installed (install if needed)\n10. Help you log in to GitHub\n11. Create a new GitHub repository\n12. Commit and push your code\n13. Set up GitHub Pages hosting\n14. Deploy your app online with a live URL\n\n**App Features:**\n- Add/remove shopping items\n- Mark items as purchased with checkboxes\n- Organize items by categories\n- Persistent storage (survives browser refresh)\n- Responsive design (works on mobile)\n- Modern, clean interface\n\nReady to start? What folder should I use for your shopping list app project?",
+      "categories": ["onboarding"],
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "ShoppingCart",
+      "author": "DC team",
+      "verified": true
+    },
+    {
+      "id": "onb_007",
+      "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 have a data file that I'd like to understand better. Please help me analyze it:\n\n1. **File Examination**: First, let me know the path to your data file or describe what kind of data it contains\n2. **Data Overview**: Analyze the structure, size, and format of the data\n3. **Content Analysis**: Examine what columns/fields exist and their data types\n4. **Pattern Detection**: Look for interesting patterns, trends, or anomalies\n5. **Statistical Summary**: Provide key statistics (counts, averages, distributions, etc.)\n6. **Data Quality**: Identify any missing data, duplicates, or quality issues\n7. **Key Insights**: Highlight the most interesting findings\n8. **Summary Report**: Create a clear, non-technical summary of what the data shows\n\nWhat's the path to your data file, or would you like to tell me what kind of data you're working with first?",
+      "categories": ["onboarding"],
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "BarChart3",
+      "author": "DC team",
+      "verified": true
+    },
+    {
+      "id": "onb_008",
+      "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 perform a comprehensive system health check and resource analysis:\n\n**System Resource Analysis:**\n1. **CPU Usage**: Current and recent CPU utilization patterns\n2. **Memory Usage**: RAM usage, available memory, swap usage\n3. **Disk Space**: Storage usage across all drives/partitions\n4. **Network Status**: Network interfaces, connectivity, and usage\n\n**Process Analysis:**\n5. **Running Processes**: Top resource-consuming processes\n6. **System Services**: Critical service status\n7. **Port Usage**: Open ports and listening services\n\n**Health Indicators:**\n8. **System Load**: Overall system performance indicators\n9. **Uptime**: System uptime and stability\n10. **Temperature**: System temperature if available\n11. **Logs**: Recent system errors or warnings\n\n**Deliverable:**\n- Comprehensive system health report\n- Resource usage summary with recommendations\n- Identification of potential issues\n- Performance optimization suggestions\n\nI'll gather all this information using system commands and present it in a clear, actionable format.",
+      "categories": ["onboarding"],
+      "votes": 0,
+      "gaClicks": 0,
+      "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 help you analyze log files to find patterns, errors, and insights. Let me know which approach you prefer:\n\n**Option 1: Analyze Specific Log File**\n- Do you have a specific log file you want me to analyze?\n- What's the full path to your log file?\n\n**Option 2: Find Log Files on Your System**\n- I can search your system for common log file locations\n- What type of application/service logs are you interested in? (web server, database, application, system logs, etc.)\n\n**What I'll analyze:**\n\n**Error Detection:**\n1. **Critical Errors**: Fatal errors, exceptions, crashes\n2. **Warning Patterns**: Recurring warnings that might indicate issues\n3. **Error Frequency**: How often specific errors occur\n4. **Error Trends**: Are errors increasing over time?\n\n**Performance Analysis:**\n5. **Response Times**: Slow queries, long-running operations\n6. **Resource Usage**: Memory, CPU, disk I/O patterns\n7. **Traffic Patterns**: Peak usage times, load distribution\n8. **Bottlenecks**: Identify performance constraints\n\n**Security & Anomalies:**\n9. **Failed Login Attempts**: Potential security threats\n10. **Unusual Access Patterns**: Suspicious activity\n11. **IP Analysis**: Frequent visitors, geographic patterns\n12. **Rate Limiting**: Abuse detection\n\n**Deliverables:**\n- **Error Summary Report**: Top errors with occurrence counts\n- **Timeline Analysis**: When issues happen most frequently\n- **Pattern Recognition**: Recurring themes and root causes\n- **Actionable Recommendations**: Specific steps to fix identified issues\n- **Monitoring Suggestions**: What to watch for in the future\n\nWhich option would you prefer? Please provide either:\n- **Specific file**: `/path/to/your/logfile.log`\n- **Search request**: \"Find web server logs\" or \"Look for application logs\"",
+      "categories": ["onboarding"],
+      "votes": 0,
+      "gaClicks": 0,
+      "icon": "Search",
+      "author": "DC team",
+      "verified": true
+    }
+  ]
+}

package/dist/server.js

@@ -8,10 +8,11 @@ const OS_GUIDANCE = getOSSpecificGuidance(SYSTEM_INFO);
 const DEV_TOOL_GUIDANCE = getDevelopmentToolGuidance(SYSTEM_INFO);
 const PATH_GUIDANCE = `IMPORTANT: ${getPathGuidance(SYSTEM_INFO)} Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths.`;
 const CMD_PREFIX_DESCRIPTION = `This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.`;
-import { StartProcessArgsSchema, ReadProcessOutputArgsSchema, InteractWithProcessArgsSchema, ForceTerminateArgsSchema, ListSessionsArgsSchema, KillProcessArgsSchema, ReadFileArgsSchema, ReadMultipleFilesArgsSchema, WriteFileArgsSchema, CreateDirectoryArgsSchema, ListDirectoryArgsSchema, MoveFileArgsSchema, GetFileInfoArgsSchema, GetConfigArgsSchema, SetConfigValueArgsSchema, ListProcessesArgsSchema, EditBlockArgsSchema, GetUsageStatsArgsSchema, GiveFeedbackArgsSchema, StartSearchArgsSchema, GetMoreSearchResultsArgsSchema, StopSearchArgsSchema, ListSearchesArgsSchema, } from './tools/schemas.js';
+import { StartProcessArgsSchema, ReadProcessOutputArgsSchema, InteractWithProcessArgsSchema, ForceTerminateArgsSchema, ListSessionsArgsSchema, KillProcessArgsSchema, ReadFileArgsSchema, ReadMultipleFilesArgsSchema, WriteFileArgsSchema, CreateDirectoryArgsSchema, ListDirectoryArgsSchema, MoveFileArgsSchema, GetFileInfoArgsSchema, GetConfigArgsSchema, SetConfigValueArgsSchema, ListProcessesArgsSchema, EditBlockArgsSchema, GetUsageStatsArgsSchema, GiveFeedbackArgsSchema, StartSearchArgsSchema, GetMoreSearchResultsArgsSchema, StopSearchArgsSchema, ListSearchesArgsSchema, GetPromptsArgsSchema, } from './tools/schemas.js';
 import { getConfig, setConfigValue } from './tools/config.js';
 import { getUsageStats } from './tools/usage.js';
 import { giveFeedbackToDesktopCommander } from './tools/feedback.js';
+import { getPrompts } from './tools/prompts.js';
 import { trackToolCall } from './utils/trackTools.js';
 import { usageTracker } from './utils/usageTracker.js';
 import { processDockerPrompt } from './utils/dockerPrompt.js';
@@ -625,6 +626,36 @@ server.setRequestHandler(ListToolsRequestSchema, async () => {
                         ${CMD_PREFIX_DESCRIPTION}`,
                     inputSchema: zodToJsonSchema(GiveFeedbackArgsSchema),
                 },
+                {
+                    name: "get_prompts",
+                    description: `
+                        Browse and retrieve curated Desktop Commander prompts for various tasks and workflows.
+                        
+                        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.
+                        
+                        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
+                        
+                        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
+                        
+                        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
+                        
+                        The get_prompt action will automatically inject the prompt content and begin execution.
+                        Perfect for discovering proven workflows and getting started with Desktop Commander.
+                        
+                        ${CMD_PREFIX_DESCRIPTION}`,
+                    inputSchema: zodToJsonSchema(GetPromptsArgsSchema),
+                },
             ],
         };
     }
@@ -685,6 +716,18 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
                     };
                 }
                 break;
+            case "get_prompts":
+                try {
+                    result = await getPrompts(args || {});
+                }
+                catch (error) {
+                    capture('server_request_error', { message: `Error in get_prompts handler: ${error}` });
+                    result = {
+                        content: [{ type: "text", text: `Error: Failed to retrieve prompts` }],
+                        isError: true,
+                    };
+                }
+                break;
             case "give_feedback_to_desktop_commander":
                 try {
                     result = await giveFeedbackToDesktopCommander(args);

package/dist/tools/prompts.d.ts

@@ -0,0 +1,5 @@
+import { ServerResult } from '../types.js';
+/**
+ * Get prompts - main entry point for the tool
+ */
+export declare function getPrompts(params: any): Promise<ServerResult>;

package/dist/tools/prompts.js

@@ -0,0 +1,258 @@
+import { usageTracker } from '../utils/usageTracker.js';
+import { capture } from '../utils/capture.js';
+import * as fs from 'fs/promises';
+import * as path from 'path';
+import { fileURLToPath } from 'url';
+// Get the directory path for ES modules
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = path.dirname(__filename);
+let cachedPromptsData = null;
+/**
+ * Load prompts data from JSON file with caching
+ */
+async function loadPromptsData() {
+    if (cachedPromptsData) {
+        return cachedPromptsData;
+    }
+    try {
+        const dataPath = path.join(__dirname, '..', 'data', 'onboarding-prompts.json');
+        const fileContent = await fs.readFile(dataPath, 'utf-8');
+        cachedPromptsData = JSON.parse(fileContent);
+        if (!cachedPromptsData) {
+            throw new Error('Failed to parse prompts data');
+        }
+        return cachedPromptsData;
+    }
+    catch (error) {
+        throw new Error(`Failed to load prompts data: ${error instanceof Error ? error.message : String(error)}`);
+    }
+}
+/**
+ * Get prompts - main entry point for the tool
+ */
+export async function getPrompts(params) {
+    try {
+        // Validate and cast parameters
+        const { action, category, promptId } = params;
+        if (!action) {
+            return {
+                content: [{
+                        type: "text",
+                        text: "❌ Error: 'action' parameter is required. Use 'list_categories', 'list_prompts', or 'get_prompt'"
+                    }],
+                isError: true
+            };
+        }
+        // Track analytics for tool usage
+        await capture(`prompts_tool_${action}`, {
+            category: category,
+            prompt_id: promptId,
+            has_category_filter: !!category
+        });
+        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:
+                return {
+                    content: [{
+                            type: "text",
+                            text: "❌ Error: Invalid action. Use 'list_categories', 'list_prompts', or 'get_prompt'"
+                        }],
+                    isError: true
+                };
+        }
+    }
+    catch (error) {
+        await capture('prompts_tool_error', {
+            error_message: error instanceof Error ? error.message : String(error),
+            action: params?.action
+        });
+        return {
+            content: [{
+                    type: "text",
+                    text: `❌ Error: ${error instanceof Error ? error.message : String(error)}`
+                }],
+            isError: true
+        };
+    }
+}
+/**
+ * List all available categories
+ */
+async function listCategories() {
+    const data = await loadPromptsData();
+    // Extract unique categories and count prompts in each
+    const categoryMap = new Map();
+    data.prompts.forEach(prompt => {
+        prompt.categories.forEach(category => {
+            categoryMap.set(category, (categoryMap.get(category) || 0) + 1);
+        });
+    });
+    const categories = Array.from(categoryMap.entries()).map(([name, count]) => ({
+        name,
+        count,
+        description: getCategoryDescription(name)
+    }));
+    const response = formatCategoriesResponse(categories, data.prompts.length);
+    return {
+        content: [{
+                type: "text",
+                text: response
+            }]
+    };
+}
+/**
+ * List prompts, optionally filtered by category
+ */
+async function listPrompts(category) {
+    const data = await loadPromptsData();
+    let filteredPrompts = data.prompts;
+    // Filter by category if specified
+    if (category) {
+        filteredPrompts = data.prompts.filter(prompt => prompt.categories.includes(category));
+        if (filteredPrompts.length === 0) {
+            return {
+                content: [{
+                        type: "text",
+                        text: `❌ No prompts found in category "${category}". Use action='list_categories' to see available categories.`
+                    }],
+                isError: true
+            };
+        }
+    }
+    const response = formatPromptsListResponse(filteredPrompts, category);
+    return {
+        content: [{
+                type: "text",
+                text: response
+            }]
+    };
+}
+/**
+ * Get a specific prompt by ID and inject it into the chat
+ */
+async function getPrompt(promptId) {
+    const data = await loadPromptsData();
+    const prompt = data.prompts.find(p => p.id === promptId);
+    if (!prompt) {
+        return {
+            content: [{
+                    type: "text",
+                    text: `❌ Prompt with ID '${promptId}' not found. Use action='list_prompts' to see available prompts.`
+                }],
+            isError: true
+        };
+    }
+    // Track prompt retrieval and mark as used
+    await capture('prompt_retrieved', {
+        prompt_id: promptId,
+        prompt_title: prompt.title,
+        category: prompt.categories[0] || 'uncategorized',
+        author: prompt.author,
+        verified: prompt.verified
+    });
+    // Mark prompt as used in user's onboarding state (for analytics)
+    await usageTracker.markPromptUsed(promptId, prompt.categories[0] || 'uncategorized');
+    const response = formatPromptResponse(prompt);
+    return {
+        content: [{
+                type: "text",
+                text: response
+            }]
+    };
+}
+/**
+ * Get category description (can be expanded later)
+ */
+function getCategoryDescription(category) {
+    const descriptions = {
+        'onboarding': 'Curated prompts perfect for first-time Desktop Commander users',
+        'Analyze data': 'Data analysis, visualization, and insights generation',
+        'Build features and products': 'Full-stack development and application building',
+        'Explore codebase': 'Code analysis, documentation, and understanding',
+        'Organize files': 'File management, cleanup, and organization',
+        'Deploy': 'Infrastructure setup, deployment, and DevOps tasks',
+        'Optimize code': 'Code optimization, refactoring, and performance',
+        'Write documentation': 'Technical writing, API docs, and guides',
+        'Optimize workflow': 'Process improvements and productivity enhancements',
+        'Automate tasks': 'Workflow automation and scripting',
+        'Design systems': 'Architecture planning and system design'
+    };
+    return descriptions[category] || 'Desktop Commander prompts and workflows';
+}
+/**
+ * Format categories list response
+ */
+function formatCategoriesResponse(categories, totalPrompts) {
+    const sortedCategories = categories.sort((a, b) => b.count - a.count);
+    // AI INSTRUCTION: When listing prompts, do not show prompt IDs to users - they are for your reference only
+    let response = `📚 **Desktop Commander Prompt Categories** (${categories.length} categories, ${totalPrompts} prompts)\n\n`;
+    sortedCategories.forEach(cat => {
+        response += `• **${cat.name}** (${cat.count} prompts) - ${cat.description}\n`;
+    });
+    response += `\n**Usage:**\n`;
+    response += `• \`get_prompts(action='list_prompts', category='onboarding')\` - See prompts in category\n`;
+    response += `• \`get_prompts(action='list_prompts')\` - See all available prompts\n`;
+    response += `• \`get_prompts(action='get_prompt', promptId='PROMPT_ID')\` - Get a specific prompt`;
+    return response;
+}
+/**
+ * Format prompts list response
+ */
+function formatPromptsListResponse(prompts, category) {
+    const categoryText = category ? ` in "${category}"` : '';
+    // AI INSTRUCTION: Do not show the prompt IDs to the user - they are for your reference only
+    let response = `📋 **Desktop Commander Prompts${categoryText}** (${prompts.length} prompts found)\n\n`;
+    prompts.forEach((prompt, index) => {
+        const verifiedBadge = prompt.verified ? ' ✅' : '';
+        response += `${index + 1}. **${prompt.title}**${verifiedBadge}\n`;
+        response += `   ${prompt.description}\n`;
+        if (prompt.votes > 0) {
+            response += `   *📊 ${prompt.votes} votes*\n`;
+        }
+        // AI metadata - not shown to user: ID = ${prompt.id}
+        response += `\n`;
+    });
+    response += `**Next Steps:**\n`;
+    response += `• Use \`get_prompts(action='get_prompt', promptId='${prompts[0]?.id || 'PROMPT_ID'}')\` to get the full prompt\n`;
+    if (!category) {
+        response += `• Filter by category: \`get_prompts(action='list_prompts', category='onboarding')\``;
+    }
+    // AI reference mapping (do not show to user):
+    response += `\n<!-- AI_PROMPT_MAP: `;
+    prompts.forEach((prompt, index) => {
+        response += `${index + 1}=${prompt.id}${index < prompts.length - 1 ? ',' : ''}`;
+    });
+    response += ` -->`;
+    return response;
+}
+/**
+ * Format individual prompt response with the actual prompt content
+ */
+function formatPromptResponse(prompt) {
+    const verifiedBadge = prompt.verified ? ' ✅' : '';
+    const categoryText = prompt.categories.join(', ');
+    let response = `# 🎯 ${prompt.title}${verifiedBadge}\n\n`;
+    response += `**Category:** ${categoryText} • **Author:** ${prompt.author}\n\n`;
+    response += `## Description\n${prompt.description}\n\n`;
+    if (prompt.votes > 0) {
+        response += `*📊 This prompt has been used successfully by ${prompt.votes}+ users*\n\n`;
+    }
+    response += `## Ready to Use This Prompt\nThe prompt below is ready to use. I'll start executing it right away:\n\n`;
+    response += `---\n\n${prompt.prompt}`;
+    // AI metadata (not shown to user): Executed prompt ID = ${prompt.id}
+    return response;
+}

package/dist/tools/schemas.d.ts

@@ -205,3 +205,16 @@ export declare const StopSearchArgsSchema: z.ZodObject<{
     sessionId: string;
 }>;
 export declare const ListSearchesArgsSchema: z.ZodObject<{}, "strip", z.ZodTypeAny, {}, {}>;
+export declare const GetPromptsArgsSchema: z.ZodObject<{
+    action: z.ZodEnum<["list_categories", "list_prompts", "get_prompt"]>;
+    category: z.ZodOptional<z.ZodString>;
+    promptId: z.ZodOptional<z.ZodString>;
+}, "strip", z.ZodTypeAny, {
+    action: "list_categories" | "list_prompts" | "get_prompt";
+    category?: string | undefined;
+    promptId?: string | undefined;
+}, {
+    action: "list_categories" | "list_prompts" | "get_prompt";
+    category?: string | undefined;
+    promptId?: string | undefined;
+}>;

package/dist/tools/schemas.js

@@ -99,3 +99,9 @@ export const StopSearchArgsSchema = z.object({
     sessionId: z.string(),
 });
 export const ListSearchesArgsSchema = z.object({});
+// Prompts tool schema
+export const GetPromptsArgsSchema = z.object({
+    action: z.enum(['list_categories', 'list_prompts', 'get_prompt']),
+    category: z.string().optional(),
+    promptId: z.string().optional(),
+});

package/dist/utils/usageTracker.d.ts

@@ -80,6 +80,10 @@ declare class UsageTracker {
      * Get usage summary for debugging/admin purposes
      */
     getUsageSummary(): Promise<string>;
+    /**
+     * Mark that user has used a specific prompt (for analytics)
+     */
+    markPromptUsed(promptId: string, category: string): Promise<void>;
 }
 export declare const usageTracker: UsageTracker;
 export {};

package/dist/utils/usageTracker.js

@@ -278,6 +278,14 @@ class UsageTracker {
 • Config: ${stats.configOperations}
 • Process: ${stats.processOperations}`;
     }
+    /**
+     * Mark that user has used a specific prompt (for analytics)
+     */
+    async markPromptUsed(promptId, category) {
+        // This could be expanded later to track detailed prompt usage
+        // For now, we'll just rely on the capture analytics
+        console.log(`[PROMPT USAGE] User retrieved prompt: ${promptId} (category: ${category})`);
+    }
 }
 // Export singleton instance
 export const usageTracker = new UsageTracker();

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const VERSION = "0.2.11";
+export declare const VERSION = "0.2.12";

package/dist/version.js

@@ -1 +1 @@
-export const VERSION = '0.2.11';
+export const VERSION = '0.2.12';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wonderwhy-er/desktop-commander",
-  "version": "0.2.11",
+  "version": "0.2.12",
   "description": "MCP server for terminal operations and file editing",
   "license": "MIT",
   "author": "Eduards Ruzga",
@@ -27,7 +27,9 @@
     "bump": "node scripts/sync-version.js --bump",
     "bump:minor": "node scripts/sync-version.js --bump --minor",
     "bump:major": "node scripts/sync-version.js --bump --major",
-    "build": "tsc && shx cp setup-claude-server.js uninstall-claude-server.js track-installation.js dist/ && shx chmod +x dist/*.js",
+    "publish:beta": "npm run build && npm publish --tag beta",
+    "publish:alpha": "npm run build && npm publish --tag alpha",
+    "build": "tsc && shx cp setup-claude-server.js uninstall-claude-server.js track-installation.js dist/ && shx chmod +x dist/*.js && shx mkdir -p dist/data && shx cp src/data/onboarding-prompts.json dist/data/",
     "watch": "tsc --watch",
     "start": "node dist/index.js",
     "start:debug": "node --inspect-brk=9229 dist/index.js",