@vybestack/llxprt-code-core 0.1.15 → 0.1.16

package/dist/src/prompt-config/defaults/env/ide-mode.md

@@ -0,0 +1,3 @@
+# IDE Mode
+
+Instructions for IDE companion mode.

package/dist/src/prompt-config/defaults/env/macos-seatbelt.md

@@ -0,0 +1,3 @@
+# macOS Seatbelt
+
+You are running under macos seatbelt with limited access to files outside the project directory or system temp directory, and with limited access to host system resources such as ports. If you encounter failures that could be due to macOS Seatbelt (e.g. if a command fails with 'Operation not permitted' or similar error), as you report the error to the user, also explain why you think it could be due to macOS Seatbelt, and how the user may need to adjust their Seatbelt profile.

package/dist/src/prompt-config/defaults/env/outside-of-sandbox.md

@@ -0,0 +1,3 @@
+# Outside of Sandbox
+
+You are running outside of a sandbox container, directly on the user's system. For critical commands that are particularly likely to modify the user's system outside of the project directory or system temp directory, as you explain the command to the user (per the Explain Critical Commands rule above), also remind the user to consider enabling sandboxing.

package/dist/src/prompt-config/defaults/env/sandbox.md

@@ -0,0 +1,3 @@
+# Sandbox
+
+You are running in a sandbox container with limited access to files outside the project directory or system temp directory, and with limited access to host system resources such as ports. If you encounter failures that could be due to sandboxing (e.g. if a command fails with 'Operation not permitted' or similar error), when you report the error to the user, also explain why you think it could be due to sandboxing, and how the user may need to adjust their sandbox configuration.

package/dist/src/prompt-config/defaults/index.d.ts

@@ -0,0 +1,14 @@
+/**
+ * Main export for all default prompts
+ * Combines core, tool, and provider-specific defaults
+ */
+import { CORE_DEFAULTS } from './core-defaults.js';
+import { TOOL_DEFAULTS } from './tool-defaults.js';
+import { PROVIDER_DEFAULTS } from './provider-defaults.js';
+import { SERVICE_DEFAULTS } from './service-defaults.js';
+/**
+ * All default prompts combined into a single record
+ * Keys are relative paths from ~/.llxprt/prompts/
+ */
+export declare const ALL_DEFAULTS: Record<string, string>;
+export { CORE_DEFAULTS, TOOL_DEFAULTS, PROVIDER_DEFAULTS, SERVICE_DEFAULTS };

package/dist/src/prompt-config/defaults/index.js

@@ -0,0 +1,21 @@
+/**
+ * Main export for all default prompts
+ * Combines core, tool, and provider-specific defaults
+ */
+import { CORE_DEFAULTS } from './core-defaults.js';
+import { TOOL_DEFAULTS } from './tool-defaults.js';
+import { PROVIDER_DEFAULTS } from './provider-defaults.js';
+import { SERVICE_DEFAULTS } from './service-defaults.js';
+/**
+ * All default prompts combined into a single record
+ * Keys are relative paths from ~/.llxprt/prompts/
+ */
+export const ALL_DEFAULTS = {
+    ...CORE_DEFAULTS,
+    ...TOOL_DEFAULTS,
+    ...PROVIDER_DEFAULTS,
+    ...SERVICE_DEFAULTS,
+};
+// Export individual collections for specific use cases
+export { CORE_DEFAULTS, TOOL_DEFAULTS, PROVIDER_DEFAULTS, SERVICE_DEFAULTS };
+//# sourceMappingURL=index.js.map

package/dist/src/prompt-config/defaults/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../src/prompt-config/defaults/index.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAE,aAAa,EAAE,MAAM,oBAAoB,CAAC;AACnD,OAAO,EAAE,aAAa,EAAE,MAAM,oBAAoB,CAAC;AACnD,OAAO,EAAE,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AAC3D,OAAO,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AAEzD;;;GAGG;AACH,MAAM,CAAC,MAAM,YAAY,GAA2B;IAClD,GAAG,aAAa;IAChB,GAAG,aAAa;IAChB,GAAG,iBAAiB;IACpB,GAAG,gBAAgB;CACpB,CAAC;AAEF,uDAAuD;AACvD,OAAO,EAAE,aAAa,EAAE,aAAa,EAAE,iBAAiB,EAAE,gBAAgB,EAAE,CAAC"}

package/dist/src/prompt-config/defaults/provider-defaults.d.ts

@@ -0,0 +1,5 @@
+/**
+ * Provider and model-specific default prompts
+ * These constants contain the default content for provider/model overrides
+ */
+export declare const PROVIDER_DEFAULTS: Record<string, string>;

package/dist/src/prompt-config/defaults/provider-defaults.js

@@ -0,0 +1,26 @@
+/**
+ * Provider and model-specific default prompts
+ * These constants contain the default content for provider/model overrides
+ */
+export const PROVIDER_DEFAULTS = {
+    'providers/gemini/models/gemini-1-5-flash/core.md': `IMPORTANT: You MUST use the provided tools when appropriate. For example:
+- When asked to list files or directories, use the 'Ls' tool
+- When asked to read file contents, use the 'ReadFile' tool
+- When asked to search for patterns in files, use the 'Grep' tool
+- When asked to find files by name, use the 'Glob' tool
+- When asked to create files, use the 'WriteFile' tool
+- When asked to modify files, use the 'Edit' tool
+- When asked to run commands, use the 'Shell' tool
+Do not describe what you would do - actually execute the tool calls.`,
+    'providers/gemini/models/gemini-2-5-flash/core.md': `IMPORTANT: You MUST use the provided tools when appropriate. For example:
+- When asked to list files or directories, use the 'Ls' tool
+- When asked to read file contents, use the 'ReadFile' tool
+- When asked to search for patterns in files, use the 'Grep' tool
+- When asked to find files by name, use the 'Glob' tool
+- When asked to create files, use the 'WriteFile' tool
+- When asked to modify files, use the 'Edit' tool
+- When asked to run commands, use the 'Shell' tool
+Do not describe what you would do - actually execute the tool calls.`,
+    // Future provider-specific defaults can be added here
+};
+//# sourceMappingURL=provider-defaults.js.map

package/dist/src/prompt-config/defaults/provider-defaults.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"provider-defaults.js","sourceRoot":"","sources":["../../../../src/prompt-config/defaults/provider-defaults.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,CAAC,MAAM,iBAAiB,GAA2B;IACvD,kDAAkD,EAAE;;;;;;;;qEAQe;IACnE,kDAAkD,EAAE;;;;;;;;qEAQe;IACnE,sDAAsD;CACvD,CAAC"}

package/dist/src/prompt-config/defaults/providers/gemini/models/gemini-2.5-flash/core.md

@@ -0,0 +1,10 @@
+IMPORTANT: You MUST use the provided tools when appropriate. For example:
+
+- When asked to list files or directories, use the '${LSTool.Name}' tool
+- When asked to read file contents, use the '${ReadFileTool.Name}' tool
+- When asked to search for patterns in files, use the '${GrepTool.Name}' tool
+- When asked to find files by name, use the '${GlobTool.Name}' tool
+- When asked to create files, use the '${WriteFileTool.Name}' tool
+- When asked to modify files, use the '${EditTool.Name}' tool
+- When asked to run commands, use the '${ShellTool.Name}' tool
+  Do not describe what you would do - actually execute the tool calls.

package/dist/src/prompt-config/defaults/service-defaults.d.ts

@@ -0,0 +1,5 @@
+/**
+ * Service-specific default prompts
+ * These contain prompts used by various internal services
+ */
+export declare const SERVICE_DEFAULTS: Record<string, string>;

package/dist/src/prompt-config/defaults/service-defaults.js

@@ -0,0 +1,52 @@
+/**
+ * Service-specific default prompts
+ * These contain prompts used by various internal services
+ */
+export const SERVICE_DEFAULTS = {
+    'services/loop-detection.md': `You are a sophisticated AI diagnostic agent specializing in identifying when a conversational AI is stuck in an unproductive state. Your task is to analyze the provided conversation history and determine if the assistant has ceased to make meaningful progress.
+
+An unproductive state is characterized by one or more of the following patterns over the last 5 or more assistant turns:
+
+Repetitive Actions: The assistant repeats the same tool calls or conversational responses a decent number of times. This includes simple loops (e.g., tool_A, tool_A, tool_A) and alternating patterns (e.g., tool_A, tool_B, tool_A, tool_B, ...).
+
+Cognitive Loop: The assistant seems unable to determine the next logical step. It might express confusion, repeatedly ask the same questions, or generate responses that don't logically follow from the previous turns, indicating it's stuck and not advancing the task.
+
+Crucially, differentiate between a true unproductive state and legitimate, incremental progress.
+For example, a series of 'tool_A' or 'tool_B' tool calls that make small, distinct changes to the same file (like adding docstrings to functions one by one) is considered forward progress and is NOT a loop. A loop would be repeatedly replacing the same text with the same content, or cycling between a small set of files with no net change.
+
+Please analyze the conversation history to determine the possibility that the conversation is stuck in a repetitive, non-productive state.`,
+    'commands/init-command.md': `You are an AI agent that brings the power of multiple LLM providers directly into the terminal. Your task is to analyze the current directory and generate a comprehensive LLXPRT.md file to be used as instructional context for future interactions.
+
+**Analysis Process:**
+
+1.  **Initial Exploration:**
+    *   Start by listing the files and directories to get a high-level overview of the structure.
+    *   Read the README file (e.g., \`README.md\`, \`README.txt\`) if it exists. This is often the best place to start.
+
+2.  **Iterative Deep Dive (up to 10 files):**
+    *   Based on your initial findings, select a few files that seem most important (e.g., configuration files, main source files, documentation).
+    *   Read them. As you learn more, refine your understanding and decide which files to read next. You don't need to decide all 10 files at once. Let your discoveries guide your exploration.
+
+3.  **Identify Project Type:**
+    *   **Code Project:** Look for clues like \`package.json\`, \`requirements.txt\`, \`pom.xml\`, \`go.mod\`, \`Cargo.toml\`, \`build.gradle\`, or a \`src\` directory. If you find them, this is likely a software project.
+    *   **Non-Code Project:** If you don't find code-related files, this might be a directory for documentation, research papers, notes, or something else.
+
+**LLXPRT.md Content Generation:**
+
+**For a Code Project:**
+
+*   **Project Overview:** Write a clear and concise summary of the project's purpose, main technologies, and architecture.
+*   **Building and Running:** Document the key commands for building, running, and testing the project. Infer these from the files you've read (e.g., \`scripts\` in \`package.json\`, \`Makefile\`, etc.). If you can't find explicit commands, provide a placeholder with a TODO.
+*   **Development Conventions:** Describe any coding styles, testing practices, or contribution guidelines you can infer from the codebase.
+
+**For a Non-Code Project:**
+
+*   **Directory Overview:** Describe the purpose and contents of the directory. What is it for? What kind of information does it hold?
+*   **Key Files:** List the most important files and briefly explain what they contain.
+*   **Usage:** Explain how the contents of this directory are intended to be used.
+
+**Final Output:**
+
+Write the complete content to the \`LLXPRT.md\` file. The output must be well-formatted Markdown.`,
+};
+//# sourceMappingURL=service-defaults.js.map

package/dist/src/prompt-config/defaults/service-defaults.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"service-defaults.js","sourceRoot":"","sources":["../../../../src/prompt-config/defaults/service-defaults.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,CAAC,MAAM,gBAAgB,GAA2B;IACtD,4BAA4B,EAAE;;;;;;;;;;;2IAW2G;IAEzI,0BAA0B,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;kGAgCoE;CACjG,CAAC"}

package/dist/src/prompt-config/defaults/tool-defaults.d.ts

@@ -0,0 +1,5 @@
+/**
+ * Tool-specific default prompts
+ * These constants contain the default content for tool-related prompts
+ */
+export declare const TOOL_DEFAULTS: Record<string, string>;

package/dist/src/prompt-config/defaults/tool-defaults.js

@@ -0,0 +1,81 @@
+/**
+ * Tool-specific default prompts
+ * These constants contain the default content for tool-related prompts
+ */
+export const TOOL_DEFAULTS = {
+    'tools/shell.md': `- Use the '\${ShellTool.Name}' tool for running shell commands, remembering the safety rule to explain modifying commands first.
+- **Explain Critical Commands:** Before executing commands with '\${ShellTool.Name}' that modify the file system, codebase, or system state, you *must* provide a brief explanation of the command's purpose and potential impact. Prioritize user understanding and safety. You should not ask permission to use the tool; the user will be presented with a confirmation dialogue upon use (you do not need to tell them this).
+- **Command Execution:** Use the '\${ShellTool.Name}' tool for running shell commands, remembering the safety rule to explain modifying commands first.
+- **Background Processes:** Use background processes (via \\\`&\\\`) for commands that are unlikely to stop on their own, e.g. \\\`node server.js &\\\`. If unsure, ask the user.
+- **Interactive Commands:** Try to avoid shell commands that are likely to require user interaction (e.g. \\\`git rebase -i\\\`). Use non-interactive versions of commands (e.g. \\\`npm init -y\\\` instead of \\\`npm init\\\`) when available, and otherwise remind the user that interactive shell commands are not supported and may cause hangs until canceled by the user.`,
+    'tools/read-file.md': `- **File Paths:** Always use absolute paths when referring to files with tools like '\${ReadFileTool.Name}' or '\${WriteFileTool.Name}'. Relative paths are not supported. You must provide an absolute path.
+- **Path Construction:** Before using any file system tool (e.g., \${ReadFileTool.Name}' or '\${WriteFileTool.Name}'), you must construct the full absolute path for the file_path argument. Always combine the absolute path of the project's root directory with the file's path relative to the root. For example, if the project root is /path/to/project/ and the file is foo/bar/baz.txt, the final path you must use is /path/to/project/foo/bar/baz.txt. If the user provides a relative path, you must resolve it against the root directory to create an absolute path.
+- Use '\${ReadFileTool.Name}' and '\${ReadManyFilesTool.Name}' to understand context and validate any assumptions you may have.
+- Never make assumptions about the contents of files; instead use '\${ReadFileTool.Name}' or '\${ReadManyFilesTool.Name}' to ensure you aren't making broad assumptions.`,
+    'tools/edit.md': `- Use the available tools (e.g., '\${EditTool.Name}', '\${WriteFileTool.Name}' '\${ShellTool.Name}' ...) to act on the plan, strictly adhering to the project's established conventions (detailed under 'Core Mandates').
+- When asked to modify files, use the '\${EditTool.Name}' tool`,
+    'tools/write-file.md': `- **File Paths:** Always use absolute paths when referring to files with tools like '\${ReadFileTool.Name}' or '\${WriteFileTool.Name}'. Relative paths are not supported. You must provide an absolute path.
+- **Path Construction:** Before using any file system tool (e.g., \${ReadFileTool.Name}' or '\${WriteFileTool.Name}'), you must construct the full absolute path for the file_path argument. Always combine the absolute path of the project's root directory with the file's path relative to the root. For example, if the project root is /path/to/project/ and the file is foo/bar/baz.txt, the final path you must use is /path/to/project/foo/bar/baz.txt. If the user provides a relative path, you must resolve it against the root directory to create an absolute path.
+- Some tools you may especially find useful are '\${WriteFileTool.Name}', '\${EditTool.Name}' and '\${ShellTool.Name}'.
+- When asked to create files, use the '\${WriteFileTool.Name}' tool`,
+    'tools/grep.md': `- Use '\${GrepTool.Name}' and '\${GlobTool.Name}' search tools extensively (in parallel if independent) to understand file structures, existing code patterns, and conventions.
+- When asked to search for patterns in files, use the '\${GrepTool.Name}' tool`,
+    'tools/glob.md': `- Use '\${GrepTool.Name}' and '\${GlobTool.Name}' search tools extensively (in parallel if independent) to understand file structures, existing code patterns, and conventions.
+- When asked to find files by name, use the '\${GlobTool.Name}' tool`,
+    'tools/ls.md': `- When asked to list files or directories, use the '\${LSTool.Name}' tool`,
+    'tools/memory.md': `- **Remembering Facts:** Use the '\${MemoryTool.Name}' tool to remember specific, *user-related* facts or preferences when the user explicitly asks, or when they state a clear, concise piece of information that would help personalize or streamline *your future interactions with them* (e.g., preferred coding style, common project paths they use, personal tool aliases). This tool is for user-specific information that should persist across sessions. Do *not* use it for general project context or information. If unsure whether to save something, you can ask the user, "Should I remember that for you?"`,
+    'tools/read-many-files.md': `- Use '\${ReadFileTool.Name}' and '\${ReadManyFilesTool.Name}' to understand context and validate any assumptions you may have.
+- Never make assumptions about the contents of files; instead use '\${ReadFileTool.Name}' or '\${ReadManyFilesTool.Name}' to ensure you aren't making broad assumptions.`,
+    'tools/todo-read.md': `# Task Management
+You have access to the TodoWrite and TodoRead tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.`,
+    'tools/todo-write.md': `# Task Management
+You have access to the TodoWrite and TodoRead tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.
+
+## When to Use This Tool
+Use this tool proactively in these scenarios:
+
+1. Complex multi-step tasks - When a task requires 3 or more distinct steps or actions
+2. Non-trivial and complex tasks - Tasks that require careful planning or multiple operations
+3. User explicitly requests todo list - When the user directly asks you to use the todo list
+4. User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
+5. After receiving new instructions - Immediately capture user requirements as todos
+6. When you start working on a task - Mark it as in_progress BEFORE beginning work
+7. After completing a task - Mark it as completed and add any new follow-up tasks discovered during implementation
+
+## When NOT to Use This Tool
+Skip using this tool when:
+1. There is only a single, straightforward task
+2. The task is trivial and tracking it provides no organizational benefit
+3. The task can be completed in less than 3 trivial steps
+4. The task is purely conversational or informational
+
+## Task States and Management
+1. **Task States**: Use these states to track progress:
+   - pending: Task not yet started
+   - in_progress: Currently working on (limit to ONE task at a time)
+   - completed: Task finished successfully
+
+2. **Task Management**:
+   - Update task status in real-time as you work
+   - Mark tasks complete IMMEDIATELY after finishing (don't batch completions)
+   - Only have ONE task in_progress at any time
+   - Complete current tasks before starting new ones
+   - Remove tasks that are no longer relevant from the list entirely
+
+3. **Task Completion Requirements**:
+   - ONLY mark a task as completed when you have FULLY accomplished it
+   - If you encounter errors, blockers, or cannot finish, keep the task as in_progress
+   - When blocked, create a new task describing what needs to be resolved
+   - Never mark a task as completed if:
+     - Tests are failing
+     - Implementation is partial
+     - You encountered unresolved errors
+     - You couldn't find necessary files or dependencies
+
+When in doubt, use this tool. Being proactive with task management demonstrates attentiveness and ensures you complete all requirements successfully.`,
+    'tools/web-fetch.md': `# Web Fetch Tool
+Use this tool to fetch content from URLs when needed.`,
+    'tools/web-search.md': `# Web Search Tool
+Use this tool to search the web when needed.`,
+};
+//# sourceMappingURL=tool-defaults.js.map

package/dist/src/prompt-config/defaults/tool-defaults.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"tool-defaults.js","sourceRoot":"","sources":["../../../../src/prompt-config/defaults/tool-defaults.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,CAAC,MAAM,aAAa,GAA2B;IACnD,gBAAgB,EAAE;;;;kXAI8V;IAEhX,oBAAoB,EAAE;;;yKAGiJ;IAEvK,eAAe,EAAE;+DAC4C;IAE7D,qBAAqB,EAAE;;;oEAG2C;IAElE,eAAe,EAAE;+EAC4D;IAE7E,eAAe,EAAE;qEACkD;IAEnE,aAAa,EAAE,2EAA2E;IAE1F,iBAAiB,EAAE,6lBAA6lB;IAEhnB,0BAA0B,EAAE;yKAC2I;IAEvK,oBAAoB,EAAE;qNAC6L;IAEnN,qBAAqB,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;sJA4C6H;IAEpJ,oBAAoB,EAAE;sDAC8B;IAEpD,qBAAqB,EAAE;6CACoB;CAC5C,CAAC"}

package/dist/src/prompt-config/defaults/tools/edit.md

@@ -0,0 +1,2 @@
+- Use the available tools (e.g., '${EditTool.Name}', '${WriteFileTool.Name}' '${ShellTool.Name}' ...) to act on the plan, strictly adhering to the project's established conventions (detailed under 'Core Mandates').
+- When asked to modify files, use the '${EditTool.Name}' tool

package/dist/src/prompt-config/defaults/tools/glob.md

@@ -0,0 +1,2 @@
+- Use '${GrepTool.Name}' and '${GlobTool.Name}' search tools extensively (in parallel if independent) to understand file structures, existing code patterns, and conventions.
+- When asked to find files by name, use the '${GlobTool.Name}' tool

package/dist/src/prompt-config/defaults/tools/grep.md

@@ -0,0 +1,2 @@
+- Use '${GrepTool.Name}' and '${GlobTool.Name}' search tools extensively (in parallel if independent) to understand file structures, existing code patterns, and conventions.
+- When asked to search for patterns in files, use the '${GrepTool.Name}' tool

package/dist/src/prompt-config/defaults/tools/ls.md

@@ -0,0 +1 @@
+- When asked to list files or directories, use the '${LSTool.Name}' tool

package/dist/src/prompt-config/defaults/tools/memory.md

@@ -0,0 +1 @@
+- **Remembering Facts:** Use the '${MemoryTool.Name}' tool to remember specific, _user-related_ facts or preferences when the user explicitly asks, or when they state a clear, concise piece of information that would help personalize or streamline _your future interactions with them_ (e.g., preferred coding style, common project paths they use, personal tool aliases). This tool is for user-specific information that should persist across sessions. Do _not_ use it for general project context or information. If unsure whether to save something, you can ask the user, "Should I remember that for you?"

package/dist/src/prompt-config/defaults/tools/read-file.md

@@ -0,0 +1,4 @@
+- **File Paths:** Always use absolute paths when referring to files with tools like '${ReadFileTool.Name}' or '${WriteFileTool.Name}'. Relative paths are not supported. You must provide an absolute path.
+- **Path Construction:** Before using any file system tool (e.g., ${ReadFileTool.Name}' or '${WriteFileTool.Name}'), you must construct the full absolute path for the file_path argument. Always combine the absolute path of the project's root directory with the file's path relative to the root. For example, if the project root is /path/to/project/ and the file is foo/bar/baz.txt, the final path you must use is /path/to/project/foo/bar/baz.txt. If the user provides a relative path, you must resolve it against the root directory to create an absolute path.
+- Use '${ReadFileTool.Name}' and '${ReadManyFilesTool.Name}' to understand context and validate any assumptions you may have.
+- Never make assumptions about the contents of files; instead use '${ReadFileTool.Name}' or '${ReadManyFilesTool.Name}' to ensure you aren't making broad assumptions.

package/dist/src/prompt-config/defaults/tools/read-many-files.md

@@ -0,0 +1,2 @@
+- Use '${ReadFileTool.Name}' and '${ReadManyFilesTool.Name}' to understand context and validate any assumptions you may have.
+- Never make assumptions about the contents of files; instead use '${ReadFileTool.Name}' or '${ReadManyFilesTool.Name}' to ensure you aren't making broad assumptions.

package/dist/src/prompt-config/defaults/tools/shell.md

@@ -0,0 +1,5 @@
+- Use the '${ShellTool.Name}' tool for running shell commands, remembering the safety rule to explain modifying commands first.
+- **Explain Critical Commands:** Before executing commands with '${ShellTool.Name}' that modify the file system, codebase, or system state, you _must_ provide a brief explanation of the command's purpose and potential impact. Prioritize user understanding and safety. You should not ask permission to use the tool; the user will be presented with a confirmation dialogue upon use (you do not need to tell them this).
+- **Command Execution:** Use the '${ShellTool.Name}' tool for running shell commands, remembering the safety rule to explain modifying commands first.
+- **Background Processes:** Use background processes (via \`&\`) for commands that are unlikely to stop on their own, e.g. \`node server.js &\`. If unsure, ask the user.
+- **Interactive Commands:** Try to avoid shell commands that are likely to require user interaction (e.g. \`git rebase -i\`). Use non-interactive versions of commands (e.g. \`npm init -y\` instead of \`npm init\`) when available, and otherwise remind the user that interactive shell commands are not supported and may cause hangs until canceled by the user.

package/dist/src/prompt-config/defaults/tools/todo-read.md

@@ -0,0 +1,3 @@
+# Task Management
+
+You have access to the TodoWrite and TodoRead tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.

package/dist/src/prompt-config/defaults/tools/todo-write.md

@@ -0,0 +1,50 @@
+# Task Management
+
+You have access to the TodoWrite and TodoRead tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.
+
+## When to Use This Tool
+
+Use this tool proactively in these scenarios:
+
+1. Complex multi-step tasks - When a task requires 3 or more distinct steps or actions
+2. Non-trivial and complex tasks - Tasks that require careful planning or multiple operations
+3. User explicitly requests todo list - When the user directly asks you to use the todo list
+4. User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
+5. After receiving new instructions - Immediately capture user requirements as todos
+6. When you start working on a task - Mark it as in_progress BEFORE beginning work
+7. After completing a task - Mark it as completed and add any new follow-up tasks discovered during implementation
+
+## When NOT to Use This Tool
+
+Skip using this tool when:
+
+1. There is only a single, straightforward task
+2. The task is trivial and tracking it provides no organizational benefit
+3. The task can be completed in less than 3 trivial steps
+4. The task is purely conversational or informational
+
+## Task States and Management
+
+1. **Task States**: Use these states to track progress:
+   - pending: Task not yet started
+   - in_progress: Currently working on (limit to ONE task at a time)
+   - completed: Task finished successfully
+
+2. **Task Management**:
+   - Update task status in real-time as you work
+   - Mark tasks complete IMMEDIATELY after finishing (don't batch completions)
+   - Only have ONE task in_progress at any time
+   - Complete current tasks before starting new ones
+   - Remove tasks that are no longer relevant from the list entirely
+
+3. **Task Completion Requirements**:
+   - ONLY mark a task as completed when you have FULLY accomplished it
+   - If you encounter errors, blockers, or cannot finish, keep the task as in_progress
+   - When blocked, create a new task describing what needs to be resolved
+   - Never mark a task as completed if:
+     - Tests are failing
+     - Implementation is partial
+     - You encountered unresolved errors
+     - You couldn't find necessary files or dependencies
+
+When in doubt, use this tool. Being proactive with task management demonstrates attentiveness and ensures you complete all requirements successfully.

package/dist/src/prompt-config/defaults/tools/web-fetch.md

@@ -0,0 +1,3 @@
+# Web Fetch Tool
+
+Use this tool to fetch content from URLs when needed.

package/dist/src/prompt-config/defaults/tools/web-search.md

@@ -0,0 +1,3 @@
+# Web Search Tool
+
+Use this tool to search the web when needed.

package/dist/src/prompt-config/defaults/tools/write-file.md

@@ -0,0 +1,4 @@
+- **File Paths:** Always use absolute paths when referring to files with tools like '${ReadFileTool.Name}' or '${WriteFileTool.Name}'. Relative paths are not supported. You must provide an absolute path.
+- **Path Construction:** Before using any file system tool (e.g., ${ReadFileTool.Name}' or '${WriteFileTool.Name}'), you must construct the full absolute path for the file_path argument. Always combine the absolute path of the project's root directory with the file's path relative to the root. For example, if the project root is /path/to/project/ and the file is foo/bar/baz.txt, the final path you must use is /path/to/project/foo/bar/baz.txt. If the user provides a relative path, you must resolve it against the root directory to create an absolute path.
+- Some tools you may especially find useful are '${WriteFileTool.Name}', '${EditTool.Name}' and '${ShellTool.Name}'.
+- When asked to create files, use the '${WriteFileTool.Name}' tool

package/dist/src/prompt-config/index.d.ts

@@ -0,0 +1,16 @@
+/**
+ * Main exports for the prompt-config module
+ */
+export { TemplateEngine } from './TemplateEngine.js';
+export { PromptLoader } from './prompt-loader.js';
+export { PromptCache } from './prompt-cache.js';
+export { PromptResolver } from './prompt-resolver.js';
+export { PromptInstaller } from './prompt-installer.js';
+export { PromptService } from './prompt-service.js';
+export type { TemplateVariables, TemplateProcessingOptions, PromptContext, PromptEnvironment, } from './types.js';
+export type { LoadFileResult, EnvironmentInfo, FileWatcher, FileChangeCallback, } from './prompt-loader.js';
+export type { CacheEntry, CacheStats } from './prompt-cache.js';
+export type { ResolveFileResult, ResolvedFile, AvailableFile, ValidationResult, } from './prompt-resolver.js';
+export type { InstallOptions, InstallResult, UninstallOptions, UninstallResult, ValidationResult as InstallerValidationResult, RepairOptions, RepairResult, BackupResult, DefaultsMap, } from './prompt-installer.js';
+export { DEFAULT_BASE_DIR, REQUIRED_DIRECTORIES } from './prompt-installer.js';
+export type { PromptServiceConfig, ValidationResult as PromptServiceValidationResult, } from './prompt-service.js';

package/dist/src/prompt-config/index.js

@@ -0,0 +1,11 @@
+/**
+ * Main exports for the prompt-config module
+ */
+export { TemplateEngine } from './TemplateEngine.js';
+export { PromptLoader } from './prompt-loader.js';
+export { PromptCache } from './prompt-cache.js';
+export { PromptResolver } from './prompt-resolver.js';
+export { PromptInstaller } from './prompt-installer.js';
+export { PromptService } from './prompt-service.js';
+export { DEFAULT_BASE_DIR, REQUIRED_DIRECTORIES } from './prompt-installer.js';
+//# sourceMappingURL=index.js.map

package/dist/src/prompt-config/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/prompt-config/index.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,cAAc,EAAE,MAAM,qBAAqB,CAAC;AACrD,OAAO,EAAE,YAAY,EAAE,MAAM,oBAAoB,CAAC;AAClD,OAAO,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAChD,OAAO,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AACtD,OAAO,EAAE,eAAe,EAAE,MAAM,uBAAuB,CAAC;AACxD,OAAO,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AA+BpD,OAAO,EAAE,gBAAgB,EAAE,oBAAoB,EAAE,MAAM,uBAAuB,CAAC"}

package/dist/src/prompt-config/prompt-cache.d.ts

@@ -0,0 +1,72 @@
+import { PromptContext } from './types.js';
+/**
+ * Represents a cached prompt entry with metadata
+ */
+export interface CacheEntry {
+    assembledPrompt: string;
+    metadata: {
+        files: string[];
+        tokenCount?: number;
+        assemblyTimeMs: number;
+    };
+}
+/**
+ * Statistics about cache usage
+ */
+export interface CacheStats {
+    entryCount: number;
+    totalSizeMB: number;
+    maxSizeMB: number;
+    utilizationPercent: number;
+    averageEntrySizeKB: number;
+    totalAccesses: number;
+    mostAccessedKey: string | null;
+    mostAccessedCount: number;
+}
+/**
+ * In-memory prompt cache with LRU eviction
+ */
+export declare class PromptCache {
+    private cache;
+    private totalSize;
+    private maxSize;
+    private accessOrder;
+    private requestedSizeMB;
+    constructor(maxSizeMB?: number);
+    /**
+     * Generate a unique cache key from context
+     */
+    generateKey(context: PromptContext | null | undefined): string;
+    /**
+     * Store a prompt in the cache
+     */
+    set(context: PromptContext, prompt: string, metadata: CacheEntry['metadata']): void;
+    /**
+     * Retrieve a cached prompt
+     */
+    get(context: PromptContext): CacheEntry | null;
+    /**
+     * Check if a prompt exists in cache
+     */
+    has(context: PromptContext | null | undefined): boolean;
+    /**
+     * Clear all cached entries
+     */
+    clear(): void;
+    /**
+     * Get the number of cached entries
+     */
+    size(): number;
+    /**
+     * Remove a specific entry from cache
+     */
+    remove(key: string | null | undefined): boolean;
+    /**
+     * Get cache statistics
+     */
+    getStats(): CacheStats;
+    /**
+     * Preload cache with multiple contexts
+     */
+    preload(contexts: PromptContext[] | null | undefined): number;
+}