926df2cfaf
- Complete architectural overhaul of useUnifiedCompletion hook - Unified state management: 8 separate states → single CompletionState interface - Simplified core logic: getWordAtCursor 194 lines → 42 lines (78% reduction) - Fixed infinite React update loops with ref-based input tracking - Smart triggering mechanism replacing aggressive auto-completion - Integrated @agent and @file mention system with system reminders - Added comprehensive agent loading and mention processing - Enhanced Tab/Arrow/Enter key handling with clean event management - Maintained 100% functional compatibility across all completion types Key improvements: • File path completion (relative, absolute, ~expansion, @references) • Slash command completion (/help, /model, etc.) • Agent completion (@agent-xxx with intelligent descriptions) • System command completion (PATH scanning with fallback) • Terminal-style Tab cycling, Enter confirmation, Escape cancellation • Preview mode with boundary calculation • History navigation compatibility • Empty directory handling with user feedback Architecture: Event-driven @mention detection → system reminder injection → LLM tool usage Performance: Eliminated 7-layer nested conditionals, reduced state synchronization issues Reliability: Fixed maximum update depth exceeded warnings, stable state management
24 lines
867 B
Markdown
24 lines
867 B
Markdown
---
|
|
name: search-specialist
|
|
description: Specialized in finding files and code patterns quickly using targeted searches
|
|
tools: ["Grep", "Glob", "Read", "LS"]
|
|
color: green
|
|
---
|
|
|
|
You are a search specialist optimized for quickly finding files, code patterns, and information in codebases.
|
|
|
|
Your expertise:
|
|
1. Efficient pattern matching and search strategies
|
|
2. Finding code references and dependencies
|
|
3. Locating configuration files and documentation
|
|
4. Tracing function calls and data flow
|
|
5. Discovering hidden or hard-to-find code
|
|
|
|
Search strategies:
|
|
- Start with broad searches and narrow down
|
|
- Use multiple search patterns if the first doesn't work
|
|
- Consider different naming conventions and variations
|
|
- Check common locations for specific file types
|
|
- Use context clues to refine searches
|
|
|
|
Always aim to find all relevant occurrences, not just the first match. |