/**
 * Context strings injected when keywords are detected.
 * These provide mode-specific guidance to the agent.
 */
export declare const ULTRAWORK_CONTEXT = "<ultrawork-mode>\nULTRAWORK MODE ACTIVE - Maximum multi-agent coordination engaged.\n\n**Mandatory behaviors**:\n1. Fire explore + librarian in PARALLEL BACKGROUND for ANY research task\n2. Use pre-delegation reasoning before EVERY delegation\n3. Continue productive work while background agents run (never idle)\n4. Consult oracle for architectural decisions before implementing\n5. Verify ALL delegated work before marking tasks complete\n\n**Pre-delegation reasoning** (do this before every Task/background_task):\n- What type of work? (search \u2192 background, decision \u2192 sync, visual \u2192 sync)\n- Can I continue working while this runs? If yes \u2192 background_task\n- Do I need this answer RIGHT NOW to proceed? If no \u2192 background_task\n\n**Stay within limits**: launch focused batches of 3\u20135 background agents (hard cap ~6 running). If a launch is rejected, wait and collect results with background_output before firing more. Breadth comes from sequential batches, not from spawning everything at once.\n\n**Parallel research pattern**:\n```\n// Fire research immediately\nbackground_task(agent=\"explorer\", description=\"Find patterns\", prompt=\"...\")\nbackground_task(agent=\"librarian\", description=\"Find best practices\", prompt=\"...\")\n\n// Continue working while they run:\n// - Plan implementation approach\n// - Read files you know about\n// - Identify edge cases\n\n// When notified \u2192 retrieve and synthesize\nbackground_output(task_id=\"bg_xxx\")\n```\n</ultrawork-mode>";
export declare const DEEP_RESEARCH_CONTEXT = "<deep-research-mode>\nDEEP RESEARCH MODE - Comprehensive exploration requested.\n\n**Required actions**:\n1. Fire 3-5 parallel background agents before proceeding (cap ~6 running at once)\n2. Search BOTH internal (explorer) AND external (librarian) sources\n3. Explore multiple angles: implementations, tests, patterns, docs\n4. DO NOT proceed until you have comprehensive context\n5. Synthesize all findings before making decisions\n6. If a launch is rejected for hitting the limit, wait and use background_output, then run another batch\n\n**Research pattern**:\n```\n// Fire comprehensive research\nbackground_task(agent=\"explorer\", description=\"Find implementations\", prompt=\"...\")\nbackground_task(agent=\"explorer\", description=\"Find related tests\", prompt=\"...\")\nbackground_task(agent=\"librarian\", description=\"Find official docs\", prompt=\"...\")\nbackground_task(agent=\"librarian\", description=\"Find OSS examples\", prompt=\"...\")\n\n// Wait for ALL results before proceeding\n// When notified \u2192 retrieve, synthesize, then act\n```\n</deep-research-mode>";
export declare const EXPLORE_CONTEXT = "<explore-mode>\nEXPLORE MODE - Codebase exploration active.\n\n**Required actions**:\n1. Fire multiple explorer agents in background for parallel search\n2. Search for: patterns, implementations, tests, related code\n3. Map out the relevant code landscape before modifying\n4. Look for existing conventions and follow them\n\n**Exploration pattern**:\n```\n// Fire multiple explorers in parallel\nbackground_task(agent=\"explorer\", description=\"Find main implementation\", prompt=\"...\")\nbackground_task(agent=\"explorer\", description=\"Find related tests\", prompt=\"...\")\nbackground_task(agent=\"explorer\", description=\"Find usage examples\", prompt=\"...\")\n\n// Continue analyzing what you know while they search\n```\n</explore-mode>";
export declare const REVIEW_CONTEXT = "<review-mode>\nREVIEW MODE \u2014 Code review and self-review active.\n\n**Required actions**:\n1. Run `git diff` (or `git diff HEAD~1`) to capture the actual changes\n2. Fire exactly ONE Oracle `task` call \u2014 include the full diff output in the prompt\n3. Do NOT create multiple oracle tasks (one per file, one per concern, etc.)\n4. Oracle reviews the diff directly \u2014 it will NOT read files or search the codebase\n5. Collect Oracle's review before marking the task complete\n6. Address any Critical or High severity findings before delivering\n\n**Review pattern**:\n```\n// Step 1: Get the diff\nconst diff = bash(\"git diff HEAD~1\")\n\n// Step 2: Fire ONE oracle task with the diff included\ntask(\n  subagent_type: \"oracle\",\n  description: \"Review recent changes\",\n  prompt: \"Review this implementation. Here is the git diff:\\n\\n```diff\\n[actual diff output]\\n```\\n\\nFocus on correctness, security, regressions, and architecture fit.\"\n)\n\n// Step 3: Wait for verdict \u2192 address Critical/High findings \u2192 deliver\n```\n\n**Anti-patterns (DO NOT do these)**:\n- Creating separate oracle tasks per file or per concern area\n- Invoking oracle with just file names and no diff/code content\n- Running multiple review passes or follow-up oracle calls\n\n**Verdict categories**: Ship it / Ship with minor fixes / Needs changes / Needs rethinking.\n</review-mode>";
export type KeywordType = "ultrawork" | "deep-research" | "explore" | "review";
export interface KeywordConfig {
    type: KeywordType;
    pattern: RegExp;
    context: string;
    toast: {
        title: string;
        message: string;
    };
}
export declare const KEYWORD_CONFIGS: KeywordConfig[];