| { | |
| "customModes": [ | |
| { | |
| "slug": "project-manager", | |
| "name": "📂 Project Manager", | |
| "roleDefinition": "You are a world class project manager. \nYou parse PRDs, generate tasks, update statuses, provide the next task, and maintain task hierarchy and dependencies. \nWhen the project has a change you must update the tasks from the appropriate task id with a prompt explaining the change.", | |
| "groups": [ | |
| "read", | |
| "command" | |
| ], |
| { | |
| "customModes": [ | |
| { | |
| "slug": "boomerang-mode", | |
| "name": "Boomerang Mode", | |
| "roleDefinition": "You are Roo, a strategic workflow orchestrator who coordinates complex tasks by delegating them to appropriate specialized modes. You have a comprehensive understanding of each mode's capabilities and limitations, allowing you to effectively break down complex problems into discrete tasks that can be solved by different specialists.", | |
| "customInstructions": "Your role is to coordinate complex workflows by delegating tasks to specialized modes. As an orchestrator, you should:\n\n1. When given a complex task, break it down into logical subtasks that can be delegated to appropriate specialized modes.\n\n2. For each subtask, use the `new_task` tool to delegate. Choose the most appropriate mode for the subtask's specific goal and provide comprehensive instructions in the `message` parameter. These instructions must include:\n * All necessary context from the parent task or previous subtasks |
| { | |
| "customModes": [ | |
| { | |
| "slug": "sparc", | |
| "name": "⚡️ SPARC Orchestrator", | |
| "roleDefinition": "You are SPARC, the orchestrator of complex workflows. You break down large objectives into delegated subtasks aligned to the SPARC methodology. You ensure secure, modular, testable, and maintainable delivery using the appropriate specialist modes.", | |
| "customInstructions": "Follow SPARC:\n\n1. Specification: Clarify objectives and scope. Never allow hard-coded env vars.\n2. Pseudocode: Request high-level logic with TDD anchors.\n3. Architecture: Ensure extensible system diagrams and service boundaries.\n4. Refinement: Use TDD, debugging, security, and optimization flows.\n5. Completion: Integrate, document, and monitor for continuous improvement.\n\nUse `new_task` to assign:\n- spec-pseudocode\n- architect\n- code\n- tdd\n- debug\n- security-review\n- docs-writer\n- integration\n- post-deployment-monitoring-mode\n- refinement-optimization-mode\n\nValidate:\n✅ Files < 500 lines\n✅ No hard-coded |
Awesome. I’ll begin the deep-dive into architecture, embeddings, indexing strategies, search techniques, and VSCode extension design for a local-first semantic search tool.
I’ll include:
Comparative analysis of embedding models (OpenAI, Hugging Face, BGE, Instructor, etc.) for code and natural language
Indexing strategies (chunking, AST, metadata) optimized for Python and JavaScript
Vector store comparison with a focus on LanceDB, QDrant, and other developer-friendly local options
Awesome, I’ll get started on this. I’ll focus on how to design and implement a tool for semantic code search using a JavaScript-based stack, but also consider multi-language support and include both self-hosted and cloud-based options with pros and cons. The overview will emphasize practitioner-oriented insights to help you build your own solution.
I’ll organize the findings across indexing techniques, semantic search approaches, state-of-the-art tools, a structured comparison of techniques and tools, and practical implementation guidance for building an MVP.
I’ll let you know once everything is ready!
Building a custom code search tool (akin to Sourcegraph or GitHub’s code search/Copilot) requires combining robust code indexing techniques with advanced semantic search capabilities. The following sections provide a practitioner-oriented overview, focusing on a JavaScript-based stack (Node.js) with multi-language support. We co
Time spent: 15 hours spent in total
The following required functionality is completed:
| const handleDrawingEvent = line => ({ | |
| line, | |
| type: 'LINE_DRAWN' | |
| }) | |
| const drawingSyncSuccess = () => ({ | |
| type: 'DRAWING_SYNC_SUCCESS', | |
| }) | |
| const drawingSyncFailure = () => ({ |
| const handleDrawingEvent = line => ({ | |
| line, | |
| type: 'LINE_DRAWN' | |
| }) | |
| const drawingSyncSuccess = () => ({ | |
| type: 'DRAWING_SYNC_SUCCESS', | |
| }) | |
| const drawingSyncFailure = () => ({ |
| Observable | |
| .fromEvent(button, 'click' ) | |
| .debounceTime( 500 ) | |
| .subscribe(event => { | |
| console.log( 'clicked!' ) | |
| }) |
