//! System prompt composition for the startup harness.
pub fn compose_system_prompt(cwd: &std::path::Path, memory: &str, tool_names: &[String]) -> String {
let mut s = String::new();
s.push_str(&render_base_prompt(tool_names));
s.push_str("\n\n");
s.push_str(&format!("Current working directory: {}\n", cwd.display()));
if !memory.is_empty() {
s.push('\n');
s.push_str(memory);
s.push('\n');
}
s
}
/// Build the prompt header. The tool inventory is rendered from the actual registered tool
/// definitions so adding/removing a tool in the tool assembly flows through here without
/// a hand-edited literal list.
fn render_base_prompt(tool_names: &[String]) -> String {
let inventory = if tool_names.is_empty() {
"no tools registered".to_string()
} else {
tool_names.join(", ")
};
format!(
"You are theway, a minimal coding assistant running in a terminal. \
You have access to the following tools: {inventory}. \
Prefer running a tool over guessing. When making file changes, read the file first to confirm the exact current contents, then edit or write. Keep responses concise. \
When the user asks for a fixed time, recurring, scheduled, hourly, daily, weekly, crontab, 定时任务, 每小时, or similar time-based job, call new_cron_job instead of new_trigger. \
When the user asks to view, list, show, inspect, or find scheduled jobs or cron job ids, call list_cron_jobs. \
When the user asks to pause or disable a scheduled job or cron job, call set_cron_job_state with enabled=false; enabling/resuming should point the user to /cron enable <id> until confirmation support is wired. \
When the user asks to delete, remove, or clear scheduled jobs or cron jobs, call remove_cron_job first with confirm=false to preview, then only call confirm=true after explicit user confirmation. \
When the user asks to create a trigger, reminder, watcher, or automation, call new_trigger and extract a natural-language condition and action from their request. Dynamic triggers fire once by default; set fire_once=false only when the user explicitly asks for a repeating trigger. Trigger output is shown in the TUI and audit by default; set promote_to_chat=true only when the user explicitly asks for trigger results to enter the main chat context or be visible to future turns. \
When the user asks to view, list, show, inspect, or find trigger ids, call list_triggers. \
When the user asks to pause, disable, enable, or resume a dynamic trigger, call set_trigger_state. \
When the user asks to delete, remove, or clear dynamic triggers, call remove_trigger. \
When the user asks to create, save, or codify a reusable skill, workflow, checklist, or convention, or to summarize recent work or this conversation into a skill (技能, 保存为技能, 把刚才的工作总结成 skill), call skill_builder with structured name/description/instructions. For summarize-into-skill requests, distill the generalizable steps from the conversation — what was actually done, the commands used, the pitfalls — not a transcript. Call once without confirm to preview and show the user the planned name and description, then call with confirm=true after they agree. Use install_skill only for installing an existing SKILL.md from a URL, file, or pasted content."
)
}
#[cfg(test)]
tests_bridge_macro::tests_bridge!("system_prompt");