89 lines
5.0 KiB
TypeScript
89 lines
5.0 KiB
TypeScript
export const CODE_BLOCK_PATTERN = /```[\s\S]*?```/g
|
|
export const INLINE_CODE_PATTERN = /`[^`]+`/g
|
|
|
|
export const KEYWORD_DETECTORS: Array<{ pattern: RegExp; message: string }> = [
|
|
// ULTRAWORK: ulw, ultrawork
|
|
{
|
|
pattern: /\b(ultrawork|ulw)\b/i,
|
|
message: `<ultrawork-mode>
|
|
[CODE RED] Maximum precision required. Ultrathink before acting.
|
|
|
|
YOU MUST LEVERAGE ALL AVAILABLE AGENTS TO THEIR FULLEST POTENTIAL.
|
|
TELL THE USER WHAT AGENTS YOU WILL LEVERAGE NOW TO SATISFY USER'S REQUEST.
|
|
|
|
## AGENT UTILIZATION PRINCIPLES (by capability, not by name)
|
|
- **Codebase Exploration**: Spawn exploration agents using BACKGROUND TASKS for file patterns, internal implementations, project structure
|
|
- **Documentation & References**: Use librarian-type agents via BACKGROUND TASKS for API references, examples, external library docs
|
|
- **Planning & Strategy**: NEVER plan yourself - ALWAYS spawn a dedicated planning agent for work breakdown
|
|
- **High-IQ Reasoning**: Leverage specialized agents for architecture decisions, code review, strategic planning
|
|
- **Frontend/UI Tasks**: Delegate to UI-specialized agents for design and implementation
|
|
|
|
## EXECUTION RULES
|
|
- **TODO**: Track EVERY step. Mark complete IMMEDIATELY after each.
|
|
- **PARALLEL**: Fire independent agent calls simultaneously via background_task - NEVER wait sequentially.
|
|
- **BACKGROUND FIRST**: Use background_task for exploration/research agents (10+ concurrent if needed).
|
|
- **VERIFY**: Re-read request after completion. Check ALL requirements met before reporting done.
|
|
- **DELEGATE**: Don't do everything yourself - orchestrate specialized agents for their strengths.
|
|
|
|
## WORKFLOW
|
|
1. Analyze the request and identify required capabilities
|
|
2. Spawn exploration/librarian agents via background_task in PARALLEL (10+ if needed)
|
|
3. Always Use Plan agent with gathered context to create detailed work breakdown
|
|
4. Execute with continuous verification against original requirements
|
|
|
|
## TDD (if test infrastructure exists)
|
|
|
|
1. Write spec (requirements)
|
|
2. Write tests (failing)
|
|
3. RED: tests fail
|
|
4. Implement minimal code
|
|
5. GREEN: tests pass
|
|
6. Refactor if needed (must stay green)
|
|
7. Next feature, repeat
|
|
|
|
## ZERO TOLERANCE FAILURES
|
|
- **NO Scope Reduction**: Never make "demo", "skeleton", "simplified", "basic" versions - deliver FULL implementation
|
|
- **NO MockUp Work**: When user asked you to do "port A", you must "port A", fully, 100%. No Extra feature, No reduced feature, no mock data, fully working 100% port.
|
|
- **NO Partial Completion**: Never stop at 60-80% saying "you can extend this..." - finish 100%
|
|
- **NO Assumed Shortcuts**: Never skip requirements you deem "optional" or "can be added later"
|
|
- **NO Premature Stopping**: Never declare done until ALL TODOs are completed and verified
|
|
- **NO TEST DELETION**: Never delete or skip failing tests to make the build pass. Fix the code, not the tests.
|
|
|
|
THE USER ASKED FOR X. DELIVER EXACTLY X. NOT A SUBSET. NOT A DEMO. NOT A STARTING POINT.
|
|
|
|
</ultrawork-mode>
|
|
|
|
---
|
|
|
|
`,
|
|
},
|
|
// SEARCH: EN/KO/JP/CN/VN
|
|
{
|
|
pattern:
|
|
/\b(search|find|locate|lookup|look\s*up|explore|discover|scan|grep|query|browse|detect|trace|seek|track|pinpoint|hunt)\b|where\s+is|show\s+me|list\s+all|검색|찾아|탐색|조회|스캔|서치|뒤져|찾기|어디|추적|탐지|찾아봐|찾아내|보여줘|목록|検索|探して|見つけて|サーチ|探索|スキャン|どこ|発見|捜索|見つけ出す|一覧|搜索|查找|寻找|查询|检索|定位|扫描|发现|在哪里|找出来|列出|tìm kiếm|tra cứu|định vị|quét|phát hiện|truy tìm|tìm ra|ở đâu|liệt kê/i,
|
|
message: `[search-mode]
|
|
MAXIMIZE SEARCH EFFORT. Launch multiple background agents IN PARALLEL:
|
|
- explore agents (codebase patterns, file structures, ast-grep)
|
|
- librarian agents (remote repos, official docs, GitHub examples)
|
|
Plus direct tools: Grep, ripgrep (rg), ast-grep (sg)
|
|
NEVER stop at first result - be exhaustive.`,
|
|
},
|
|
// ANALYZE: EN/KO/JP/CN/VN
|
|
{
|
|
pattern:
|
|
/\b(analyze|analyse|investigate|examine|research|study|deep[\s-]?dive|inspect|audit|evaluate|assess|review|diagnose|scrutinize|dissect|debug|comprehend|interpret|breakdown|understand)\b|why\s+is|how\s+does|how\s+to|분석|조사|파악|연구|검토|진단|이해|설명|원인|이유|뜯어봐|따져봐|평가|해석|디버깅|디버그|어떻게|왜|살펴|分析|調査|解析|検討|研究|診断|理解|説明|検証|精査|究明|デバッグ|なぜ|どう|仕組み|调查|检查|剖析|深入|诊断|解释|调试|为什么|原理|搞清楚|弄明白|phân tích|điều tra|nghiên cứu|kiểm tra|xem xét|chẩn đoán|giải thích|tìm hiểu|gỡ lỗi|tại sao/i,
|
|
message: `[analyze-mode]
|
|
ANALYSIS MODE. Gather context before diving deep:
|
|
|
|
CONTEXT GATHERING (parallel):
|
|
- 1-2 explore agents (codebase patterns, implementations)
|
|
- 1-2 librarian agents (if external library involved)
|
|
- Direct tools: Grep, AST-grep, LSP for targeted searches
|
|
|
|
IF COMPLEX (architecture, multi-system, debugging after 2+ failures):
|
|
- Consult oracle for strategic guidance
|
|
|
|
SYNTHESIZE findings before proceeding.`,
|
|
},
|
|
]
|