snow-ai 0.3.26 → 0.3.27

package/dist/api/systemPrompt.js

@@ -101,30 +101,50 @@ const SYSTEM_PROMPT_TEMPLATE = `You are Snow AI CLI, an intelligent command-line
 
 **Golden Rule: Read what you need to write correct code, nothing more.**
 
-### 📋 TODO Management - For Complex Programming Tasks
-
-**🚫 CRITICAL: TODO tools MUST be called in parallel with other tools - NEVER call TODO tools alone!**
-
-**When to use TODO:**
-- Complex tasks with 5+ steps requiring tracking
-- Multi-file implementations needing coordination
-- User explicitly requests TODO
-
-**When to skip TODO:**
-- Simple 1-3 step tasks (just do them)
-- Single file edits or quick fixes
-
-**Usage rules:**
-1. **Parallel calls only**: Always combine TODO with action tools (filesystem-edit, etc.)
-2. **Action-focused**: "Fix parser.ts timeout" ✅, "Read parser.ts" ❌
-3. **Update immediately**: Mark completed right after task is done
-4. **Keep minimal**: 3-7 tasks max, avoid over-planning
-
-**Example workflow:**
-- ✅ CORRECT: Call todo-create with filesystem-edit in parallel
-- ✅ CORRECT: Call todo-update with filesystem-edit in parallel
-- ❌ WRONG: Call todo-create alone, then wait, then call filesystem-edit
-- ❌ WRONG: Call todo-update alone, then wait, then proceed
+### 📋 TODO Management - STRONGLY RECOMMENDED for Better Results!
+
+**🎯 DEFAULT BEHAVIOR: Use TODO for ALL multi-step tasks (3+ steps)**
+
+**✨ WHY TODO IS ESSENTIAL:**
+- 📊 **Track progress** - Never lose your place in complex work
+- ✅ **Ensure completeness** - Verify all steps are done
+- 🎯 **Stay focused** - Clear roadmap prevents confusion
+- 💪 **Build confidence** - Users see structured progress
+- 🚀 **Better quality** - Systematic approach reduces errors
+
+**⚡ WHEN TO USE TODO (Default for most tasks):**
+- ✅ **ANY multi-file modification** (always use)
+- ✅ **ANY feature implementation** (always use)
+- ✅ **ANY refactoring task** (always use)
+- ✅ **Bug fixes touching 2+ files** (recommended)
+- ✅ **User requests with multiple requirements** (always use)
+- ✅ **Unfamiliar codebase changes** (recommended)
+- ⚠️ **SKIP ONLY for**: Single-file trivial edits (1-2 lines)
+
+**🔧 USAGE RULES (Critical):**
+1. **⚠️ PARALLEL CALLS ONLY**: ALWAYS call TODO tools with action tools in the SAME function call block
+2. **Immediate updates**: Mark completed while performing work (not after)
+3. **Right sizing**: 3-7 main tasks, add subtasks if needed
+4. **Lifecycle Management**:
+   - New task = Create TODO at start
+   - Major requirement change = Delete old + create new
+   - Minor adjustment = Use todo-add or todo-update
+   - **CRITICAL**: Keep using TODO throughout the entire conversation!
+
+**✅ CORRECT PATTERNS (Do this):**
+- ✅ todo-create + filesystem-read → Plan while gathering info
+- ✅ todo-update(completed) + filesystem-edit → Update as you work
+- ✅ todo-get + filesystem-read → Check status while reading
+- ✅ todo-add + filesystem-edit → Add new task while working
+
+**❌ FORBIDDEN PATTERNS (NEVER do this - WILL FAIL):**
+- ❌ todo-create alone, wait for result, then work → VIOLATION! Call together!
+- ❌ todo-update alone, wait, then continue → VIOLATION! Update while working!
+- ❌ todo-get alone just to check → VIOLATION! Call with other tools!
+- ❌ Skipping TODO for multi-file tasks → VIOLATION! Always use TODO!
+- ❌ **Abandoning TODO mid-conversation** → VIOLATION! Keep using throughout dialogue!
+
+**💡 BEST PRACTICE: Start every non-trivial task with todo-create + initial action in parallel!**
 
 ## 🛠️ Available Tools
 

package/dist/hooks/useCommandPanel.js

@@ -53,8 +53,40 @@ export function useCommandPanel(buffer, isProcessing = false) {
         if (!text.startsWith('/'))
             return [];
         const query = text.slice(1).toLowerCase();
-        return commands.filter(command => command.name.toLowerCase().includes(query) ||
-            command.description.toLowerCase().includes(query));
+        // Filter and sort commands by priority
+        // Priority order:
+        // 1. Command starts with query (highest)
+        // 2. Command contains query
+        // 3. Description starts with query
+        // 4. Description contains query (lowest)
+        const filtered = commands
+            .filter(command => command.name.toLowerCase().includes(query) ||
+            command.description.toLowerCase().includes(query))
+            .map(command => {
+            const nameLower = command.name.toLowerCase();
+            const descLower = command.description.toLowerCase();
+            let priority = 4; // Default: description contains query
+            if (nameLower.startsWith(query)) {
+                priority = 1; // Command starts with query
+            }
+            else if (nameLower.includes(query)) {
+                priority = 2; // Command contains query
+            }
+            else if (descLower.startsWith(query)) {
+                priority = 3; // Description starts with query
+            }
+            return { command, priority };
+        })
+            .sort((a, b) => {
+            // Sort by priority (lower number = higher priority)
+            if (a.priority !== b.priority) {
+                return a.priority - b.priority;
+            }
+            // If same priority, sort alphabetically by name
+            return a.command.name.localeCompare(b.command.name);
+        })
+            .map(item => item.command);
+        return filtered;
     }, [buffer]);
     // Update command panel state
     const updateCommandPanelState = useCallback((text) => {

package/dist/mcp/todo.js

@@ -213,36 +213,43 @@ export class TodoService {
         return [
             {
                 name: 'todo-create',
-                description: `Create a TODO list for complex multi-step tasks (optional planning tool).
+                description: `✅ RECOMMENDED: Create TODO list for structured task execution. Use this for ALL multi-step tasks!
 
-## CORE PRINCIPLE - FOCUS ON EXECUTION:
-TODO lists are OPTIONAL helpers for complex tasks. Your PRIMARY goal is COMPLETING THE WORK, not maintaining perfect TODO lists. Use this tool only when it genuinely helps organize complex work - don't let TODO management slow you down.
+⚠️ MANDATORY RULE - PARALLEL CALLS ONLY:
+🚫 NEVER call todo-create alone! MUST call with other tools in the SAME function call block.
+✅ ALWAYS: todo-create + filesystem-read (or other action tool) in parallel
+❌ FORBIDDEN: Call todo-create, wait for result, then call other tools
 
-## WHEN TO USE (Optional):
-- Complex tasks with 5+ distinct steps that benefit from tracking
-- Long-running tasks where progress visibility helps the user
-- Tasks with multiple dependencies that need careful ordering
-- User explicitly requests a TODO list
+## 🎯 DEFAULT USAGE - Use TODO by default for:
+✅ ANY multi-file changes (always create TODO first)
+✅ ANY feature implementation (plan with TODO)
+✅ ANY refactoring work (track with TODO)
+✅ Bug fixes involving 2+ files (use TODO)
+✅ Tasks with 3+ distinct steps (create TODO)
+⚠️ SKIP ONLY: Single-file trivial edits (1-2 lines)
 
-## WHEN TO SKIP:
-- Simple 1-3 step tasks (just do the work directly)
-- Straightforward file edits or single-function changes
-- Quick fixes or minor modifications
-- When TODO creation takes longer than just doing the task
+## 🚀 WHY CREATE TODO:
+- Ensures all requirements are addressed
+- Prevents missing critical steps
+- Provides clear progress tracking
+- Improves code quality through systematic approach
+- Builds user confidence with visible structure
 
-## LIFECYCLE MANAGEMENT:
-1. **NEW REQUEST = NEW TODO LIST**: Completely new requirement? Delete old todos first, then create new list.
-2. **INCREMENTAL REQUEST = USE TODO-ADD**: Adding to existing requirement? Use "todo-add" instead.
-3. Use this tool ONLY when starting fresh (new session or new requirement after cleanup).
+## 📋 WHEN TO CALL:
+1. **NEW TASK**: Create TODO immediately when starting work (with parallel action)
+2. **NEW REQUIREMENT**: Delete old todos, create fresh list (with parallel action)
+3. **BEST PRACTICE**: Call todo-create + filesystem-read in parallel
 
-## CREATION GUIDELINES:
-- Keep it simple and actionable
-- 3-7 main tasks is usually sufficient (don't over-plan)
-- Include verification steps only if critical
-- Order by dependencies
+## ⚡ CREATION GUIDELINES:
+- Break work into 3-7 clear, actionable tasks
+- Order by logical dependencies
+- Be specific (e.g., "Modify validateInput in form.ts" not "fix validation")
+- Include verification step if critical
 
-## WARNING:
-This REPLACES the entire TODO list. Never use it to "add more tasks" - use "todo-add" instead.`,
+## ⚠️ LIFECYCLE:
+This REPLACES the entire TODO list. For adding tasks to existing list, use "todo-add" instead.
+
+## 💡 REMEMBER: MUST call with other tools - never alone!`,
                 inputSchema: {
                     type: 'object',
                     properties: {
@@ -270,7 +277,19 @@ This REPLACES the entire TODO list. Never use it to "add more tasks" - use "todo
             },
             {
                 name: 'todo-get',
-                description: `Get current TODO list with task IDs, status, and hierarchy. Call with other tools in parallel when needed.`,
+                description: `Get current TODO list with task IDs, status, and hierarchy.
+
+⚠️ MANDATORY RULE - PARALLEL CALLS ONLY:
+🚫 NEVER call todo-get alone! MUST call with other tools in the SAME function call block.
+✅ ALWAYS: todo-get + filesystem-read/terminal-execute/etc in parallel
+❌ FORBIDDEN: Call todo-get alone to check status
+
+## 🔄 WHEN TO USE IN DIALOGUE:
+- **User provides additional info**: Use todo-get + filesystem-read to check what's done
+- **User requests modifications**: Check current progress before adding/updating tasks
+- **Continuing work**: Always check status first to avoid redoing completed tasks
+
+USAGE: Combine with filesystem-read, terminal-execute, or other actions to check progress while working.`,
                 inputSchema: {
                     type: 'object',
                     properties: {},
@@ -278,7 +297,17 @@ This REPLACES the entire TODO list. Never use it to "add more tasks" - use "todo
             },
             {
                 name: 'todo-update',
-                description: `Update TODO status/content. MUST call with other tools - mark "completed" ONLY after task is verified and done.`,
+                description: `Update TODO status/content - USE THIS FREQUENTLY to track progress!
+
+⚠️ MANDATORY RULE - PARALLEL CALLS ONLY:
+🚫 NEVER call todo-update alone! MUST call with other tools in the SAME function call block.
+✅ ALWAYS: todo-update + filesystem-edit/terminal-execute/etc in parallel
+❌ FORBIDDEN: Call todo-update, wait for result, then proceed
+
+BEST PRACTICE: Mark "completed" ONLY after task is verified.
+Example: todo-update(task1, completed) + filesystem-edit(task2) → Update while working!
+
+💡 This ensures efficient workflow and prevents unnecessary wait times.`,
                 inputSchema: {
                     type: 'object',
                     properties: {
@@ -301,7 +330,19 @@ This REPLACES the entire TODO list. Never use it to "add more tasks" - use "todo
             },
             {
                 name: 'todo-add',
-                description: `Add task to existing TODO (rare use). MUST call with other tools. Only for user-requested or complex tasks, not small steps.`,
+                description: `Add new task to existing TODO list when requirements expand.
+
+⚠️ MANDATORY RULE - PARALLEL CALLS ONLY:
+🚫 NEVER call todo-add alone! MUST call with other tools in the SAME function call block.
+✅ ALWAYS: todo-add + filesystem-edit/filesystem-read/etc in parallel
+❌ FORBIDDEN: Call todo-add alone to add task
+
+USE WHEN:
+- User adds new requirements during work
+- You discover additional necessary steps
+- Breaking down a complex task into subtasks
+
+DO NOT use for initial planning - use todo-create instead.`,
                 inputSchema: {
                     type: 'object',
                     properties: {
@@ -319,7 +360,14 @@ This REPLACES the entire TODO list. Never use it to "add more tasks" - use "todo
             },
             {
                 name: 'todo-delete',
-                description: `Delete TODO item. MUST call with other tools. Deleting parent auto-deletes children (cascade).`,
+                description: `Delete TODO item from the list.
+
+⚠️ MANDATORY RULE - PARALLEL CALLS ONLY:
+🚫 NEVER call todo-delete alone! MUST call with other tools in the SAME function call block.
+✅ ALWAYS: todo-delete + filesystem-edit/todo-get/etc in parallel
+❌ FORBIDDEN: Call todo-delete alone
+
+NOTE: Deleting a parent task will cascade delete all its children automatically.`,
                 inputSchema: {
                     type: 'object',
                     properties: {

package/dist/ui/components/TodoTree.js

@@ -23,6 +23,8 @@ export default function TodoTree({ todos }) {
                 return '[✓]';
             case 'pending':
                 return '[ ]';
+            default:
+                return '[ ]';
         }
     };
     const getStatusColor = (status) => {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "snow-ai",
-	"version": "0.3.26",
+	"version": "0.3.27",
 	"description": "Intelligent Command Line Assistant powered by AI",
 	"license": "MIT",
 	"bin": {