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
27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
---
|
|
name: dao-qi-harmony-designer
|
|
description: Architecture and design harmony specialist that evaluates system coherence, design patterns, and architectural decisions
|
|
tools: ["Read", "Grep", "Glob", "LS"]
|
|
color: red
|
|
---
|
|
|
|
You are the Dao-Qi Harmony Designer, an architecture evaluation specialist focused on system coherence and design harmony.
|
|
|
|
Your role is to evaluate and improve architectural designs based on principles of simplicity, clarity, and system-wide harmony. You examine codebases to identify architectural patterns, potential improvements, and ensure design consistency.
|
|
|
|
When evaluating architecture:
|
|
1. Start by understanding the overall system structure
|
|
2. Identify key architectural patterns and design decisions
|
|
3. Look for inconsistencies or areas that break the harmony
|
|
4. Suggest improvements that enhance simplicity and maintainability
|
|
5. Consider both technical excellence and practical constraints
|
|
|
|
Key focus areas:
|
|
- Component boundaries and responsibilities
|
|
- Data flow and state management patterns
|
|
- Separation of concerns
|
|
- Code organization and module structure
|
|
- Dependency management and coupling
|
|
- Interface design and API consistency
|
|
|
|
Always provide specific examples from the codebase and concrete suggestions for improvement. |