feat: Adds .windsurfrules to the init package. It's composed of the 3 rules we currently package, and has been edited to be Windsurf specific. Rules are added in as sections. The init function will search for an existing .windsurfrules document, and if it finds it, it will append to it. Otherwise it will create it.

tasks/task_033.txt

@@ -0,0 +1,44 @@
+# Task ID: 33
+# Title: Create and Integrate Windsurf Rules Document from MDC Files
+# Status: done
+# Dependencies: None
+# Priority: medium
+# Description: Develop functionality to generate a .windsurfrules document by combining and refactoring content from three primary .mdc files used for Cursor Rules, ensuring it's properly integrated into the initialization pipeline.
+# Details:
+This task involves creating a mechanism to generate a Windsurf-specific rules document by combining three existing MDC (Markdown Content) files that are currently used for Cursor Rules. The implementation should:
+
+1. Identify and locate the three primary .mdc files used for Cursor Rules
+2. Extract content from these files and merge them into a single document
+3. Refactor the content to make it Windsurf-specific, replacing Cursor-specific terminology and adapting guidelines as needed
+4. Create a function that generates a .windsurfrules document from this content
+5. Integrate this function into the initialization pipeline
+6. Implement logic to check if a .windsurfrules document already exists:
+   - If it exists, append the new content to it
+   - If it doesn't exist, create a new document
+7. Ensure proper error handling for file operations
+8. Add appropriate logging to track the generation and modification of the .windsurfrules document
+
+The implementation should be modular and maintainable, with clear separation of concerns between content extraction, refactoring, and file operations.
+
+# Test Strategy:
+Testing should verify both the content generation and the integration with the initialization pipeline:
+
+1. Unit Tests:
+   - Test the content extraction function with mock .mdc files
+   - Test the content refactoring function to ensure Cursor-specific terms are properly replaced
+   - Test the file operation functions with mock filesystem
+
+2. Integration Tests:
+   - Test the creation of a new .windsurfrules document when none exists
+   - Test appending to an existing .windsurfrules document
+   - Test the complete initialization pipeline with the new functionality
+
+3. Manual Verification:
+   - Inspect the generated .windsurfrules document to ensure content is properly combined and refactored
+   - Verify that Cursor-specific terminology has been replaced with Windsurf-specific terminology
+   - Run the initialization process multiple times to verify idempotence (content isn't duplicated on multiple runs)
+
+4. Edge Cases:
+   - Test with missing or corrupted .mdc files
+   - Test with an existing but empty .windsurfrules document
+   - Test with an existing .windsurfrules document that already contains some of the content

tasks/tasks.json

@@ -1661,6 +1661,16 @@
       "priority": "high",
       "details": "Implement a new command in the task-master CLI that enables Cursor to learn from successful coding patterns:\n\n1. Create a new module `commands/learn.js` that implements the command logic\n2. Update `index.js` to register the new command\n3. The command should:\n   - Accept an optional parameter for specifying which patterns to focus on\n   - Use git diff to extract code changes since the last commit\n   - Access the Cursor chat history if possible (investigate API or file storage location)\n   - Call Claude via ai-services.js with the following context:\n     * Code diffs\n     * Chat history excerpts showing challenges and solutions\n     * Existing rules from .cursor/rules if present\n   - Parse Claude's response to extract rule definitions\n   - Create or update .mdc files in the .cursor/rules directory\n   - Provide a summary of what was learned and which rules were updated\n\n4. Create helper functions to:\n   - Extract relevant patterns from diffs\n   - Format the prompt for Claude to focus on identifying reusable patterns\n   - Parse Claude's response into valid rule definitions\n   - Handle rule conflicts or duplications\n\n5. Ensure the command handles errors gracefully, especially if chat history is inaccessible\n6. Add appropriate logging to show the learning process\n7. Document the command in the README.md file",
       "testStrategy": "1. Unit tests:\n   - Create tests for each helper function in isolation\n   - Mock git diff responses and chat history data\n   - Verify rule extraction logic works with different input patterns\n   - Test error handling for various failure scenarios\n\n2. Integration tests:\n   - Test the command in a repository with actual code changes\n   - Verify it correctly generates .mdc files in the .cursor/rules directory\n   - Check that generated rules follow the correct format\n   - Verify the command correctly updates existing rules without losing custom modifications\n\n3. Manual testing scenarios:\n   - Run the command after implementing a feature with specific patterns\n   - Verify the generated rules capture the intended patterns\n   - Test the command with and without existing rules\n   - Verify the command works when chat history is available and when it isn't\n   - Test with large diffs to ensure performance remains acceptable\n\n4. Validation:\n   - After generating rules, use them in Cursor to verify they correctly guide future implementations\n   - Have multiple team members test the command to ensure consistent results"
+    },
+    {
+      "id": 33,
+      "title": "Create and Integrate Windsurf Rules Document from MDC Files",
+      "description": "Develop functionality to generate a .windsurfrules document by combining and refactoring content from three primary .mdc files used for Cursor Rules, ensuring it's properly integrated into the initialization pipeline.",
+      "status": "done",
+      "dependencies": [],
+      "priority": "medium",
+      "details": "This task involves creating a mechanism to generate a Windsurf-specific rules document by combining three existing MDC (Markdown Content) files that are currently used for Cursor Rules. The implementation should:\n\n1. Identify and locate the three primary .mdc files used for Cursor Rules\n2. Extract content from these files and merge them into a single document\n3. Refactor the content to make it Windsurf-specific, replacing Cursor-specific terminology and adapting guidelines as needed\n4. Create a function that generates a .windsurfrules document from this content\n5. Integrate this function into the initialization pipeline\n6. Implement logic to check if a .windsurfrules document already exists:\n   - If it exists, append the new content to it\n   - If it doesn't exist, create a new document\n7. Ensure proper error handling for file operations\n8. Add appropriate logging to track the generation and modification of the .windsurfrules document\n\nThe implementation should be modular and maintainable, with clear separation of concerns between content extraction, refactoring, and file operations.",
+      "testStrategy": "Testing should verify both the content generation and the integration with the initialization pipeline:\n\n1. Unit Tests:\n   - Test the content extraction function with mock .mdc files\n   - Test the content refactoring function to ensure Cursor-specific terms are properly replaced\n   - Test the file operation functions with mock filesystem\n\n2. Integration Tests:\n   - Test the creation of a new .windsurfrules document when none exists\n   - Test appending to an existing .windsurfrules document\n   - Test the complete initialization pipeline with the new functionality\n\n3. Manual Verification:\n   - Inspect the generated .windsurfrules document to ensure content is properly combined and refactored\n   - Verify that Cursor-specific terminology has been replaced with Windsurf-specific terminology\n   - Run the initialization process multiple times to verify idempotence (content isn't duplicated on multiple runs)\n\n4. Edge Cases:\n   - Test with missing or corrupted .mdc files\n   - Test with an existing but empty .windsurfrules document\n   - Test with an existing .windsurfrules document that already contains some of the content"
     }
   ]
 }