//! System prompts for built-in subagent profiles.
//!
//!
//! ## Tool name resolution
//!
//! All tool names in these prompts use the `${{ tools.by_kind.* }}` template
//! syntax from the `TemplateRenderer`. When the prompt is rendered via
//! `PromptContext::render()` → `ToolBridge::render_prompt()`, MiniJinja
//! resolves each variable to the current session's tool names.
//!
//! This means:
//! - Tool names are NEVER hardcoded — they adapt to name overrides and
//!   alternate tool namespaces
//! - If a tool kind is absent from the renderer's context, MiniJinja
//!   resolves it to an empty string (templates can also use
//!   `${%- if tools.by_kind.X %}` conditionals to hide entire sections)
//!
//! Tool-kind mapping (common names → ToolKind):
//!   Read       → `${{ tools.by_kind.read }}`
//!   Write/Edit → `${{ tools.by_kind.edit }}`
//!   Glob       → `${{ tools.by_kind.list }}`
//!   Grep       → `${{ tools.by_kind.search }}`
//!   Bash       → `${{ tools.by_kind.execute }}`
//!   WebSearch  → `${{ tools.by_kind.web_search }}`

pub use kigi_tool_types::{EXPLORE_PROMPT, GENERAL_PURPOSE_PROMPT, PLAN_PROMPT};
