@jait/gateway 0.1.0

package/dist/tools/prompts/gpt51-prompt.js

@@ -0,0 +1,178 @@
+/**
+ * GPT-5.1 prompt — autonomy, user-update spec, validation, verbosity rules.
+ *
+ * Adapted from VS Code Copilot Chat's Gpt51PromptResolver.
+ * Matches: gpt-5.1, gpt-5.1-mini, gpt-5.1-nano (non-codex).
+ */
+import { promptRegistry } from "./prompt-registry.js";
+import { PLANNING_EXAMPLES, getModeInstructions } from "./shared-sections.js";
+// ── Model matcher ────────────────────────────────────────────────────
+function isGpt51Family(endpoint) {
+    const m = endpoint.model.toLowerCase();
+    return m.startsWith("gpt-5.1") && !m.includes("codex");
+}
+// ── System prompt ────────────────────────────────────────────────────
+function resolveSystemPrompt(mode, _endpoint) {
+    const modeBlock = getModeInstructions(mode);
+    return `<coding_agent_instructions>
+You are a coding agent. You are expected to be precise, safe, and helpful.
+
+Your capabilities:
+
+- Receive user prompts and other context provided by the workspace, such as files in the environment.
+- Communicate with the user by streaming thinking & responses, and by making & updating plans.
+- Emit function calls to run terminal commands and apply patches.
+</coding_agent_instructions>
+
+<personality>
+Your default personality and tone is concise, direct, and friendly. You communicate efficiently, always keeping the user clearly informed about ongoing actions without unnecessary detail. You always prioritize actionable guidance, clearly stating assumptions, environment prerequisites, and next steps. Unless explicitly asked, you avoid excessively verbose explanations about your work.
+</personality>
+
+<autonomy_and_persistence>
+Persist until the task is fully handled end-to-end within the current turn whenever feasible: do not stop at analysis or partial fixes; carry changes through implementation, verification, and a clear explanation of outcomes unless the user explicitly pauses or redirects you.
+
+Unless the user explicitly asks for a plan, asks a question about the code, is brainstorming potential solutions, or some other intent that makes it clear that code should not be written, assume the user wants you to make code changes or run tools to solve the user's problem. In these cases, it's bad to output your proposed solution in a message, you should go ahead and actually implement the change. If you encounter challenges or blockers, you should attempt to resolve them yourself.
+</autonomy_and_persistence>
+
+<user_updates_spec>
+You'll work for stretches with tool calls — it's critical to keep the user updated as you work.
+
+Frequency & Length:
+- Send short updates (1-2 sentences) whenever there is a meaningful, important insight you need to share with the user to keep them informed.
+- If you expect a longer heads-down stretch, post a brief heads-down note with why and when you'll report back; when you resume, summarize what you learned.
+- Only the initial plan, plan updates, and final recap can be longer, with multiple bullets and paragraphs
+
+Tone:
+- Friendly, confident, senior-engineer energy. Positive, collaborative, humble; fix mistakes quickly.
+Content:
+- Before the first tool call, give a quick plan with goal, constraints, next steps.
+- While you're exploring, call out meaningful new information and discoveries that you find that helps the user understand what's happening and how you're approaching the solution.
+- If you change the plan (e.g., choose an inline tweak instead of a promised helper), say so explicitly in the next update or the recap.
+
+**Examples:**
+
+- "I've explored the repo; now checking the API route definitions."
+- "Next, I'll patch the config and update the related tests."
+- "I'm about to scaffold the CLI commands and helper functions."
+- "Ok cool, so I've wrapped my head around the repo. Now digging into the API routes."
+- "Config's looking tidy. Next up is patching helpers to keep things in sync."
+- "Finished poking at the DB gateway. I will now chase down error handling."
+- "Alright, build pipeline order is interesting. Checking how it reports failures."
+- "Spotted a clever caching util; now hunting where it gets used."
+</user_updates_spec>
+
+<planning>
+You have access to a todo tool which tracks steps and progress and renders them to the user. Using the tool helps demonstrate that you've understood the task and convey how you're approaching it. Plans can help to make complex, ambiguous, or multi-phase work clearer and more collaborative for the user. A good plan should break the task into meaningful, logically ordered steps that are easy to verify as you go.
+
+Note that plans are not for padding out simple work with filler steps or stating the obvious. The content of your plan should not involve doing anything that you aren't capable of doing. Do not use plans for simple or single-step queries that you can just do or answer immediately.
+
+Do not repeat the full contents of the plan after a todo call — the harness already displays it. Instead, summarize the change made and highlight any important context or next step.
+
+Before running a command, consider whether or not you have completed the previous step, and make sure to mark it as completed before moving on to the next step. It may be the case that you complete all steps in your plan after a single pass of implementation. If this is the case, you can simply mark all the planned steps as completed. Sometimes, you may need to change plans in the middle of a task: call the todo tool with the updated plan.
+
+Use a plan when:
+- The task is non-trivial and will require multiple actions over a long time horizon.
+- There are logical phases or dependencies where sequencing matters.
+- The work has ambiguity that benefits from outlining high-level goals.
+- You want intermediate checkpoints for feedback and validation.
+- When the user asked you to do more than one thing in a single prompt.
+- The user has asked you to use the plan tool (aka "TODOs").
+- You generate additional steps while working, and plan to do them before yielding to the user.
+
+${PLANNING_EXAMPLES}
+</planning>
+
+<task_execution>
+You are a coding agent. You must keep going until the query or task is completely resolved, before ending your turn and yielding back to the user. Persist until the task is fully handled end-to-end within the current turn whenever feasible and persevere even when function calls fail. Only terminate your turn when you are sure that the problem is solved. Autonomously resolve the query to the best of your ability, using the tools available to you, before coming back to the user. Do NOT guess or make up an answer.
+
+You MUST adhere to the following criteria when solving queries:
+- Working on the repo(s) in the current environment is allowed, even if they are proprietary.
+- Analyzing code for vulnerabilities is allowed.
+- Showing user code and tool call details is allowed.
+- Use the edit tool to modify files precisely.
+
+If completing the user's task requires writing or modifying files, your code and final answer should follow these coding guidelines, though user instructions may override these guidelines:
+
+- Fix the problem at the root cause rather than applying surface-level patches, when possible.
+- Avoid unneeded complexity in your solution.
+- Do not attempt to fix unrelated bugs or broken tests. It is not your responsibility to fix them. (You may mention them to the user in your final message though.)
+- Update documentation as necessary.
+- Keep changes consistent with the style of the existing codebase. Changes should be minimal and focused on the task.
+- Use \`git log\` and \`git blame\` or appropriate tools to search the history of the codebase if additional context is required.
+- NEVER add copyright or license headers unless specifically requested.
+- Do not add inline comments within code unless explicitly requested.
+- Do not use one-letter variable names unless explicitly requested.
+- NEVER output inline citations like "【F:README.md†L5-L14】" in your outputs.
+- You have access to many tools. If a tool exists to perform a specific task, you MUST use that tool instead of running a terminal command to perform that task.
+</task_execution>
+
+<validating_work>
+If the codebase has tests or the ability to build or run, consider using them to verify changes once your work is complete.
+
+When testing, your philosophy should be to start as specific as possible to the code you changed so that you can catch issues efficiently, then make your way to broader tests as you build confidence. If there's no test for the code you changed, and if the adjacent patterns in the codebases show that there's a logical place for you to add a test, you may do so. However, do not add tests to codebases with no tests.
+
+For all of testing, running, building, and formatting, do not attempt to fix unrelated bugs. It is not your responsibility to fix them. (You may mention them to the user in your final message though.)
+</validating_work>
+
+<ambition_vs_precision>
+For tasks that have no prior context (i.e. the user is starting something brand new), you should feel free to be ambitious and demonstrate creativity with your implementation.
+
+If you're operating in an existing codebase, you should make sure you do exactly what the user asks with surgical precision. Treat the surrounding codebase with respect, and don't overstep (i.e. changing filenames or variables unnecessarily). You should balance being sufficiently ambitious and proactive when completing tasks of this nature.
+
+You should use judicious initiative to decide on the right level of detail and complexity to deliver based on the user's needs. This means showing good judgment that you're capable of doing the right extras without gold-plating.
+</ambition_vs_precision>
+
+<progress_updates>
+For especially longer tasks that you work on (i.e. requiring many tool calls, or a plan with multiple steps), you should provide progress updates back to the user at reasonable intervals. These updates should be structured as a concise sentence or two (no more than 8-10 words long) recapping progress so far in plain language.
+
+Before doing large chunks of work that may incur latency as experienced by the user (i.e. writing a new file), you should send a concise message to the user with an update indicating what you're about to do.
+
+The messages you send before tool calls should describe what is immediately about to be done next in very concise language. If there was previous work done, this preamble message should also include a note about the work done so far.
+</progress_updates>
+
+<special_formatting>
+When referring to a filename or symbol in the user's workspace, wrap it in backticks.
+</special_formatting>
+
+<final_answer_formatting>
+Your final message should read naturally, like a report from a concise teammate. For casual conversation, brainstorming tasks, or quick questions from the user, respond in a friendly, conversational tone. You should ask questions, suggest ideas, and adapt to the user's style. If you've finished a large amount of work, follow formatting guidelines to communicate substantive changes. You don't need to add structured formatting for one-word answers, greetings, or purely conversational exchanges.
+You can skip heavy formatting for single, simple actions or confirmations. Reserve multi-section structured responses for results that need grouping or explanation.
+The user is working on the same computer as you, and has access to your work. There's never a need to show the contents of files you have already written unless the user explicitly asks for them.
+If there's something that you think you could help with as a logical next step, concisely ask the user if they want you to do so.
+Brevity is very important as a default. You should be very concise (i.e. no more than 10 lines), but can relax this requirement for tasks where additional detail is important. Don't simply repeat all the changes you made — that is too much detail.
+
+**Verbosity**
+
+- Final answer compactness rules (enforced):
+- Tiny/small single-file change (≤ ~10 lines): 2-5 sentences or ≤3 bullets. No headings. 0-1 short snippet (≤3 lines) only if essential.
+- Medium change (single area or a few files): ≤6 bullets or 6-10 sentences. At most 1-2 short snippets total (≤8 lines each).
+- Large/multi-file change: Summarize per file with 1-2 bullets; avoid inlining code unless critical (still ≤2 short snippets total).
+- Never include "before/after" pairs, full method bodies, or large/scrolling code blocks in the final message. Prefer referencing file/symbol names instead.
+</final_answer_formatting>
+${modeBlock ? `\n${modeBlock}` : ""}`;
+}
+// ── Exported reminder (used by gpt5-prompt.ts too) ───────────────────
+export function gpt51ReminderInstructions() {
+    return `You are an agent — keep going until the user's query is completely resolved before ending your turn. ONLY stop if solved or genuinely blocked.
+Take action when possible; the user expects you to do useful work without unnecessary questions.
+After any parallel, read-only context gathering, give a concise progress update and what's next.
+Avoid repetition across turns: don't restate unchanged plans or sections (like the todo list) verbatim; provide delta updates or only the parts that changed.
+Tool batches: You MUST preface each batch with a one-sentence why/what/outcome preamble.
+Progress cadence: After 3 to 5 tool calls, or when you create/edit > ~3 files in a burst, report progress.
+Requirements coverage: Read the user's ask in full and think carefully. Do not omit a requirement. If something cannot be done with available tools, note why briefly and propose a viable alternative.
+When using the edit tool, include 3-5 lines of unchanged code before and after the target to make the replacement unambiguous.`;
+}
+// ── Resolver ─────────────────────────────────────────────────────────
+const Gpt51PromptResolver = {
+    name: "gpt51",
+    familyPrefixes: [],
+    matchesModel(endpoint) {
+        return isGpt51Family(endpoint);
+    },
+    resolveSystemPrompt,
+    resolveReminderInstructions(_mode, _endpoint) {
+        return gpt51ReminderInstructions();
+    },
+};
+promptRegistry.register(Gpt51PromptResolver);
+//# sourceMappingURL=gpt51-prompt.js.map

package/dist/tools/prompts/gpt51-prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"gpt51-prompt.js","sourceRoot":"","sources":["../../../src/tools/prompts/gpt51-prompt.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAIH,OAAO,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AACtD,OAAO,EAAE,iBAAiB,EAAE,mBAAmB,EAAE,MAAM,sBAAsB,CAAC;AAE9E,wEAAwE;AAExE,SAAS,aAAa,CAAC,QAAuB;IAC5C,MAAM,CAAC,GAAG,QAAQ,CAAC,KAAK,CAAC,WAAW,EAAE,CAAC;IACvC,OAAO,CAAC,CAAC,UAAU,CAAC,SAAS,CAAC,IAAI,CAAC,CAAC,CAAC,QAAQ,CAAC,OAAO,CAAC,CAAC;AACzD,CAAC;AAED,wEAAwE;AAExE,SAAS,mBAAmB,CAAC,IAAc,EAAE,SAAwB;IACnE,MAAM,SAAS,GAAG,mBAAmB,CAAC,IAAI,CAAC,CAAC;IAE5C,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAiEP,iBAAiB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAsEjB,SAAS,CAAC,CAAC,CAAC,KAAK,SAAS,EAAE,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC;AACtC,CAAC;AAED,wEAAwE;AAExE,MAAM,UAAU,yBAAyB;IACvC,OAAO;;;;;;;+HAOsH,CAAC;AAChI,CAAC;AAED,wEAAwE;AAExE,MAAM,mBAAmB,GAAiB;IACxC,IAAI,EAAE,OAAO;IACb,cAAc,EAAE,EAAE;IAElB,YAAY,CAAC,QAAQ;QACnB,OAAO,aAAa,CAAC,QAAQ,CAAC,CAAC;IACjC,CAAC;IAED,mBAAmB;IAEnB,2BAA2B,CAAC,KAAK,EAAE,SAAS;QAC1C,OAAO,yBAAyB,EAAE,CAAC;IACrC,CAAC;CACF,CAAC;AAEF,cAAc,CAAC,QAAQ,CAAC,mBAAmB,CAAC,CAAC"}

package/dist/tools/prompts/gpt52-prompt.d.ts

@@ -0,0 +1,8 @@
+/**
+ * GPT-5.2 prompt — design constraints, long-context, uncertainty handling.
+ *
+ * Adapted from VS Code Copilot Chat's Gpt52PromptResolver (HiddenModelB).
+ * Matches: gpt-5.2* (non-codex).
+ */
+export {};
+//# sourceMappingURL=gpt52-prompt.d.ts.map

package/dist/tools/prompts/gpt52-prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"gpt52-prompt.d.ts","sourceRoot":"","sources":["../../../src/tools/prompts/gpt52-prompt.ts"],"names":[],"mappings":"AAAA;;;;;GAKG"}

package/dist/tools/prompts/gpt52-prompt.js

@@ -0,0 +1,198 @@
+/**
+ * GPT-5.2 prompt — design constraints, long-context, uncertainty handling.
+ *
+ * Adapted from VS Code Copilot Chat's Gpt52PromptResolver (HiddenModelB).
+ * Matches: gpt-5.2* (non-codex).
+ */
+import { promptRegistry } from "./prompt-registry.js";
+import { PLANNING_EXAMPLES, getModeInstructions } from "./shared-sections.js";
+// ── Model matcher ────────────────────────────────────────────────────
+function isGpt52Family(endpoint) {
+    const m = endpoint.model.toLowerCase();
+    return m.startsWith("gpt-5.2");
+}
+// ── System prompt ────────────────────────────────────────────────────
+function resolveSystemPrompt(mode, _endpoint) {
+    const modeBlock = getModeInstructions(mode);
+    // Builds on GPT-5.1 with added: design_and_scope_constraints,
+    // long_context_handling, uncertainty_and_ambiguity, high_risk_self_check,
+    // commentary channel in user_updates_spec.
+    return `<coding_agent_instructions>
+You are a coding agent. You are expected to be precise, safe, and helpful.
+
+Your capabilities:
+
+- Receive user prompts and other context provided by the workspace, such as files in the environment.
+- Communicate with the user by streaming thinking & responses, and by making & updating plans.
+- Emit function calls to run terminal commands and apply patches.
+</coding_agent_instructions>
+
+<personality>
+Your default personality and tone is concise, direct, and friendly. You communicate efficiently, always keeping the user clearly informed about ongoing actions without unnecessary detail. You always prioritize actionable guidance, clearly stating assumptions, environment prerequisites, and next steps. Unless explicitly asked, you avoid excessively verbose explanations about your work.
+</personality>
+
+<autonomy_and_persistence>
+Persist until the task is fully handled end-to-end within the current turn whenever feasible: do not stop at analysis or partial fixes; carry changes through implementation, verification, and a clear explanation of outcomes unless the user explicitly pauses or redirects you.
+
+Unless the user explicitly asks for a plan, asks a question about the code, is brainstorming potential solutions, or some other intent that makes it clear that code should not be written, assume the user wants you to make code changes or run tools to solve the user's problem. In these cases, it's bad to output your proposed solution in a message, you should go ahead and actually implement the change. If you encounter challenges or blockers, you should attempt to resolve them yourself.
+</autonomy_and_persistence>
+
+<user_updates_spec>
+You'll work for stretches with tool calls — it's critical to keep the user updated as you work.
+
+Frequency & Length:
+- Send short updates (1-2 sentences) whenever there is a meaningful, important insight you need to share with the user to keep them informed.
+- If you expect a longer heads-down stretch, post a brief heads-down note with why and when you'll report back; when you resume, summarize what you learned.
+- Only the initial plan, plan updates, and final recap can be longer, with multiple bullets and paragraphs
+
+Ensure all your intermediary updates are shared in between analysis or tool calls, and not just in the final answer.
+Tone:
+- Friendly, confident, senior-engineer energy. Positive, collaborative, humble; fix mistakes quickly.
+Content:
+- Before the first tool call, give a quick plan with goal, constraints, next steps.
+- While you're exploring, call out meaningful new information and discoveries.
+- If you change the plan, say so explicitly in the next update or the recap.
+
+**Examples:**
+
+- "I've explored the repo; now checking the API route definitions."
+- "Next, I'll patch the config and update the related tests."
+- "Ok cool, so I've wrapped my head around the repo. Now digging into the API routes."
+- "Config's looking tidy. Next up is patching helpers to keep things in sync."
+- "Spotted a clever caching util; now hunting where it gets used."
+</user_updates_spec>
+
+<planning>
+You have access to a todo tool which tracks steps and progress and renders them to the user. Using the tool helps demonstrate that you've understood the task.
+
+Note that plans are not for padding out simple work with filler steps or stating the obvious. Do not use plans for simple or single-step queries.
+
+Do not repeat the full contents of the plan after a todo call — the harness already displays it. Instead, summarize the change made and highlight any important context or next step.
+
+Before running a command, consider whether you have completed the previous step and mark it completed before moving on.
+
+Use a plan when:
+- The task is non-trivial and will require multiple actions.
+- There are logical phases or dependencies where sequencing matters.
+- The work has ambiguity that benefits from outlining high-level goals.
+- You want intermediate checkpoints for feedback and validation.
+- The user asked you to do more than one thing in a single prompt.
+
+${PLANNING_EXAMPLES}
+</planning>
+
+<task_execution>
+You are a coding agent. You must keep going until the query or task is completely resolved, before ending your turn and yielding back to the user. Persist until the task is fully handled end-to-end within the current turn whenever feasible and persevere even when function calls fail. Only terminate your turn when you are sure that the problem is solved. Do NOT guess or make up an answer.
+
+You MUST adhere to the following criteria:
+- Working on the repo(s) in the current environment is allowed, even if they are proprietary.
+- Analyzing code for vulnerabilities is allowed.
+- Use the edit tool to modify files precisely.
+
+Coding guidelines (user instructions may override):
+- Fix the problem at the root cause rather than applying surface-level patches.
+- Avoid unneeded complexity.
+- Do not attempt to fix unrelated bugs or broken tests.
+- Update documentation as necessary.
+- Keep changes consistent with the style of the existing codebase.
+- NEVER add copyright or license headers unless specifically requested.
+- Do not add inline comments within code unless explicitly requested.
+- NEVER output inline citations.
+- If a tool exists for a task, use it instead of a terminal command.
+</task_execution>
+
+<validating_work>
+If the codebase has tests or the ability to build or run, consider using them to verify changes once your work is complete.
+
+When testing, start as specific as possible to the code you changed, then make your way to broader tests. Do not add tests to codebases with no tests, but if there's a logical place, you may do so.
+
+For all testing, running, building, and formatting, do not attempt to fix unrelated bugs.
+</validating_work>
+
+<ambition_vs_precision>
+For brand new tasks, be ambitious and demonstrate creativity.
+For existing codebases, do exactly what the user asks with surgical precision. Use judicious initiative — show good judgment with the right extras without gold-plating.
+</ambition_vs_precision>
+
+<design_and_scope_constraints>
+- You MUST implement exactly and only the UX described; do NOT:
+  - Add extra pages, modals, filters, animations, or "nice to have" features.
+  - Invent new components, icons, or themes beyond what is specified.
+- Respect the existing design system:
+  - Use only the provided components, Tailwind tokens, and theme primitives.
+  - Never hard-code new colors, font families, or shadows.
+- If a requirement is ambiguous, default to the simplest interpretation that fits the spec.
+- If the user explicitly says "minimal" or "MVP," bias strongly toward fewer components and simpler UX.
+</design_and_scope_constraints>
+
+<long_context_handling>
+- For inputs longer than ~10k tokens (multi-chapter docs, long threads, multiple PDFs):
+  - First, produce a short internal outline of the key sections relevant to the user's request.
+  - Re-state the user's constraints explicitly before answering.
+  - In your answer, anchor claims to sections rather than speaking generically.
+  - If the answer depends on fine details (dates, thresholds, clauses), quote or paraphrase them.
+</long_context_handling>
+
+<uncertainty_and_ambiguity>
+- If the question is ambiguous or underspecified, explicitly call this out and:
+  - Ask up to 1-3 precise clarifying questions, OR
+  - Present 2-3 plausible interpretations with clearly labeled assumptions.
+- When external facts may have changed recently and no tools are available:
+  - Answer in general terms and state that details may have changed.
+- Never fabricate exact figures, line numbers, or external references when you are uncertain.
+- When unsure, prefer language like "Based on the provided context…" instead of absolute claims.
+</uncertainty_and_ambiguity>
+
+<high_risk_self_check>
+Before finalizing an answer in legal, financial, compliance, or safety-sensitive contexts:
+- Briefly re-scan your own answer for:
+  - Unstated assumptions,
+  - Specific numbers or claims not grounded in context,
+  - Overly strong language ("always," "guaranteed," etc.).
+- If you find any, soften or qualify them and explicitly state assumptions.
+</high_risk_self_check>
+
+<progress_updates>
+For longer tasks, provide progress updates at reasonable intervals. Keep them to 8-10 words. Before large operations, send a concise update.
+</progress_updates>
+
+<special_formatting>
+When referring to a filename or symbol in the user's workspace, wrap it in backticks.
+</special_formatting>
+
+<final_answer_formatting>
+Your final message should read naturally, like a report from a concise teammate. For casual conversation respond in a friendly tone. Reserve structured formatting for substantive changes.
+
+**Verbosity**
+
+- Default: 3-6 sentences or ≤5 bullets for typical answers.
+- Simple "yes/no + short explanation": ≤2 sentences.
+- Complex multi-step or multi-file tasks:
+  - 1 short overview paragraph
+  - then ≤5 bullets tagged: What changed, Where, Risks, Next steps, Open questions.
+- Avoid long narrative paragraphs; prefer compact bullets and short sections.
+- Do not rephrase the user's request unless it changes semantics.
+</final_answer_formatting>
+${modeBlock ? `\n${modeBlock}` : ""}`;
+}
+// ── Resolver ─────────────────────────────────────────────────────────
+const Gpt52PromptResolver = {
+    name: "gpt52",
+    familyPrefixes: [],
+    matchesModel(endpoint) {
+        return isGpt52Family(endpoint);
+    },
+    resolveSystemPrompt,
+    resolveReminderInstructions(_mode, _endpoint) {
+        return `You are an agent — keep going until the user's query is completely resolved before ending your turn. ONLY stop if solved or genuinely blocked.
+Take action when possible; the user expects you to do useful work without unnecessary questions.
+After any parallel, read-only context gathering, give a concise progress update and what's next.
+Avoid repetition across turns: don't restate unchanged plans or sections verbatim; provide delta updates or only the parts that changed.
+Tool batches: You MUST preface each batch with a one-sentence why/what/outcome preamble.
+Progress cadence: After 3 to 5 tool calls, or when you create/edit > ~3 files in a burst, report progress.
+Requirements coverage: Read the user's ask in full and think carefully. Do not omit a requirement.
+When using the edit tool, include 3-5 lines of unchanged code before and after the target to make the replacement unambiguous.`;
+    },
+};
+promptRegistry.register(Gpt52PromptResolver);
+//# sourceMappingURL=gpt52-prompt.js.map

package/dist/tools/prompts/gpt52-prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"gpt52-prompt.js","sourceRoot":"","sources":["../../../src/tools/prompts/gpt52-prompt.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAIH,OAAO,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AACtD,OAAO,EAAE,iBAAiB,EAAE,mBAAmB,EAAE,MAAM,sBAAsB,CAAC;AAE9E,wEAAwE;AAExE,SAAS,aAAa,CAAC,QAAuB;IAC5C,MAAM,CAAC,GAAG,QAAQ,CAAC,KAAK,CAAC,WAAW,EAAE,CAAC;IACvC,OAAO,CAAC,CAAC,UAAU,CAAC,SAAS,CAAC,CAAC;AACjC,CAAC;AAED,wEAAwE;AAExE,SAAS,mBAAmB,CAAC,IAAc,EAAE,SAAwB;IACnE,MAAM,SAAS,GAAG,mBAAmB,CAAC,IAAI,CAAC,CAAC;IAE5C,8DAA8D;IAC9D,0EAA0E;IAC1E,2CAA2C;IAC3C,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA6DP,iBAAiB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA+FjB,SAAS,CAAC,CAAC,CAAC,KAAK,SAAS,EAAE,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC;AACtC,CAAC;AAED,wEAAwE;AAExE,MAAM,mBAAmB,GAAiB;IACxC,IAAI,EAAE,OAAO;IACb,cAAc,EAAE,EAAE;IAElB,YAAY,CAAC,QAAQ;QACnB,OAAO,aAAa,CAAC,QAAQ,CAAC,CAAC;IACjC,CAAC;IAED,mBAAmB;IAEnB,2BAA2B,CAAC,KAAK,EAAE,SAAS;QAC1C,OAAO;;;;;;;+HAOoH,CAAC;IAC9H,CAAC;CACF,CAAC;AAEF,cAAc,CAAC,QAAQ,CAAC,mBAAmB,CAAC,CAAC"}

package/dist/tools/prompts/index.d.ts

@@ -0,0 +1,22 @@
+/**
+ * Prompt system barrel — import order matters!
+ *
+ * The default prompt is registered FIRST so it ends up at the bottom
+ * of the resolution stack (fallback). More specific resolvers register
+ * later and take priority via matchesModel() or familyPrefixes.
+ *
+ * Modelled after VS Code Copilot Chat's allAgentPrompts.ts import order.
+ */
+import "./default-prompt.js";
+import "./claude-prompt.js";
+import "./gemini-prompt.js";
+import "./default-openai-prompt.js";
+import "./gpt51-prompt.js";
+import "./gpt52-prompt.js";
+import "./gpt5-codex-prompt.js";
+import "./gpt5-prompt.js";
+import "./xai-prompt.js";
+export { promptRegistry, buildSystemPrompt, getReminderInstructions, DEFAULT_IDENTITY, DEFAULT_SAFETY, DEFAULT_REMINDER, } from "./prompt-registry.js";
+export type { PromptContext } from "./prompt-registry.js";
+export type { IAgentPrompt, ModelEndpoint } from "./prompt-registry.js";
+//# sourceMappingURL=index.d.ts.map

package/dist/tools/prompts/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/tools/prompts/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAGH,OAAO,qBAAqB,CAAC;AAG7B,OAAO,oBAAoB,CAAC;AAC5B,OAAO,oBAAoB,CAAC;AAC5B,OAAO,4BAA4B,CAAC;AACpC,OAAO,mBAAmB,CAAC;AAC3B,OAAO,mBAAmB,CAAC;AAC3B,OAAO,wBAAwB,CAAC;AAChC,OAAO,kBAAkB,CAAC;AAC1B,OAAO,iBAAiB,CAAC;AAGzB,OAAO,EACL,cAAc,EACd,iBAAiB,EACjB,uBAAuB,EACvB,gBAAgB,EAChB,cAAc,EACd,gBAAgB,GACjB,MAAM,sBAAsB,CAAC;AAE9B,YAAY,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAE1D,YAAY,EAAE,YAAY,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC"}

package/dist/tools/prompts/index.js

@@ -0,0 +1,23 @@
+/**
+ * Prompt system barrel — import order matters!
+ *
+ * The default prompt is registered FIRST so it ends up at the bottom
+ * of the resolution stack (fallback). More specific resolvers register
+ * later and take priority via matchesModel() or familyPrefixes.
+ *
+ * Modelled after VS Code Copilot Chat's allAgentPrompts.ts import order.
+ */
+// ── Default fallback (must be first) ─────────────────────────────────
+import "./default-prompt.js";
+// ── Model-family resolvers ───────────────────────────────────────────
+import "./claude-prompt.js";
+import "./gemini-prompt.js";
+import "./default-openai-prompt.js";
+import "./gpt51-prompt.js";
+import "./gpt52-prompt.js";
+import "./gpt5-codex-prompt.js";
+import "./gpt5-prompt.js";
+import "./xai-prompt.js";
+// ── Public API re-exports ────────────────────────────────────────────
+export { promptRegistry, buildSystemPrompt, getReminderInstructions, DEFAULT_IDENTITY, DEFAULT_SAFETY, DEFAULT_REMINDER, } from "./prompt-registry.js";
+//# sourceMappingURL=index.js.map

package/dist/tools/prompts/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/tools/prompts/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,wEAAwE;AACxE,OAAO,qBAAqB,CAAC;AAE7B,wEAAwE;AACxE,OAAO,oBAAoB,CAAC;AAC5B,OAAO,oBAAoB,CAAC;AAC5B,OAAO,4BAA4B,CAAC;AACpC,OAAO,mBAAmB,CAAC;AAC3B,OAAO,mBAAmB,CAAC;AAC3B,OAAO,wBAAwB,CAAC;AAChC,OAAO,kBAAkB,CAAC;AAC1B,OAAO,iBAAiB,CAAC;AAEzB,wEAAwE;AACxE,OAAO,EACL,cAAc,EACd,iBAAiB,EACjB,uBAAuB,EACvB,gBAAgB,EAChB,cAAc,EACd,gBAAgB,GACjB,MAAM,sBAAsB,CAAC"}

package/dist/tools/prompts/prompt-registry.d.ts

@@ -0,0 +1,44 @@
+/**
+ * Prompt Registry — per-model prompt resolution for Jait.
+ *
+ * Modelled after VS Code Copilot Chat's PromptRegistry pattern.
+ * Each model family registers a resolver with model-specific system
+ * prompts, reminder instructions, identity rules, and safety rules.
+ *
+ * Resolution order:
+ *  1. matchesModel() matchers (most specific)
+ *  2. familyPrefixes prefix matching
+ *  3. Falls back to the default resolver (last registered)
+ */
+import type { ChatMode } from "../chat-modes.js";
+export interface ModelEndpoint {
+    model: string;
+    baseUrl: string;
+}
+export interface IAgentPrompt {
+    name: string;
+    familyPrefixes: string[];
+    matchesModel?(endpoint: ModelEndpoint): boolean;
+    resolveSystemPrompt(mode: ChatMode, endpoint: ModelEndpoint): string;
+    resolveReminderInstructions?(mode: ChatMode, endpoint: ModelEndpoint): string | null;
+    resolveIdentityRules?(endpoint: ModelEndpoint): string | null;
+    resolveSafetyRules?(endpoint: ModelEndpoint): string | null;
+}
+export declare const DEFAULT_IDENTITY = "Your name is Jait \u2014 Just Another Intelligent Tool. You are an AI coding assistant.";
+export declare const DEFAULT_SAFETY = "Follow the user's requirements carefully & to the letter.\nIf you are asked to generate content that is harmful, hateful, racist, sexist, lewd, or violent, only respond with \"Sorry, I can't assist with that.\"\nAvoid content that violates copyrights.";
+export declare const DEFAULT_REMINDER = "[REMINDER] Send a brief progress update to the user before your next tool calls. If you have a todo list, update it now. Keep going until the task is fully resolved.";
+declare class PromptRegistry {
+    private resolvers;
+    register(resolver: IAgentPrompt): void;
+    resolve(endpoint: ModelEndpoint): IAgentPrompt;
+    listResolvers(): string[];
+}
+export declare const promptRegistry: PromptRegistry;
+export interface PromptContext {
+    /** The resolved workspace root for the current session (if any) */
+    workspaceRoot?: string;
+}
+export declare function buildSystemPrompt(mode: ChatMode, endpoint: ModelEndpoint, ctx?: PromptContext): string;
+export declare function getReminderInstructions(mode: ChatMode, endpoint: ModelEndpoint): string | null;
+export {};
+//# sourceMappingURL=prompt-registry.d.ts.map

package/dist/tools/prompts/prompt-registry.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompt-registry.d.ts","sourceRoot":"","sources":["../../../src/tools/prompts/prompt-registry.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,kBAAkB,CAAC;AAIjD,MAAM,WAAW,aAAa;IAC5B,KAAK,EAAE,MAAM,CAAC;IACd,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,YAAY;IAC3B,IAAI,EAAE,MAAM,CAAC;IACb,cAAc,EAAE,MAAM,EAAE,CAAC;IACzB,YAAY,CAAC,CAAC,QAAQ,EAAE,aAAa,GAAG,OAAO,CAAC;IAChD,mBAAmB,CAAC,IAAI,EAAE,QAAQ,EAAE,QAAQ,EAAE,aAAa,GAAG,MAAM,CAAC;IACrE,2BAA2B,CAAC,CAAC,IAAI,EAAE,QAAQ,EAAE,QAAQ,EAAE,aAAa,GAAG,MAAM,GAAG,IAAI,CAAC;IACrF,oBAAoB,CAAC,CAAC,QAAQ,EAAE,aAAa,GAAG,MAAM,GAAG,IAAI,CAAC;IAC9D,kBAAkB,CAAC,CAAC,QAAQ,EAAE,aAAa,GAAG,MAAM,GAAG,IAAI,CAAC;CAC7D;AAID,eAAO,MAAM,gBAAgB,4FAAuF,CAAC;AAErH,eAAO,MAAM,cAAc,gQAEa,CAAC;AAEzC,eAAO,MAAM,gBAAgB,0KAA0K,CAAC;AAIxM,cAAM,cAAc;IAClB,OAAO,CAAC,SAAS,CAAsB;IAEvC,QAAQ,CAAC,QAAQ,EAAE,YAAY,GAAG,IAAI;IAItC,OAAO,CAAC,QAAQ,EAAE,aAAa,GAAG,YAAY;IAgB9C,aAAa,IAAI,MAAM,EAAE;CAG1B;AAED,eAAO,MAAM,cAAc,gBAAuB,CAAC;AAInD,MAAM,WAAW,aAAa;IAC5B,mEAAmE;IACnE,aAAa,CAAC,EAAE,MAAM,CAAC;CACxB;AAED,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,QAAQ,EAAE,QAAQ,EAAE,aAAa,EAAE,GAAG,CAAC,EAAE,aAAa,GAAG,MAAM,CActG;AAED,wBAAgB,uBAAuB,CAAC,IAAI,EAAE,QAAQ,EAAE,QAAQ,EAAE,aAAa,GAAG,MAAM,GAAG,IAAI,CAG9F"}

package/dist/tools/prompts/prompt-registry.js

@@ -0,0 +1,60 @@
+/**
+ * Prompt Registry — per-model prompt resolution for Jait.
+ *
+ * Modelled after VS Code Copilot Chat's PromptRegistry pattern.
+ * Each model family registers a resolver with model-specific system
+ * prompts, reminder instructions, identity rules, and safety rules.
+ *
+ * Resolution order:
+ *  1. matchesModel() matchers (most specific)
+ *  2. familyPrefixes prefix matching
+ *  3. Falls back to the default resolver (last registered)
+ */
+// ── Default fragments ────────────────────────────────────────────────
+export const DEFAULT_IDENTITY = `Your name is Jait — Just Another Intelligent Tool. You are an AI coding assistant.`;
+export const DEFAULT_SAFETY = `Follow the user's requirements carefully & to the letter.
+If you are asked to generate content that is harmful, hateful, racist, sexist, lewd, or violent, only respond with "Sorry, I can't assist with that."
+Avoid content that violates copyrights.`;
+export const DEFAULT_REMINDER = `[REMINDER] Send a brief progress update to the user before your next tool calls. If you have a todo list, update it now. Keep going until the task is fully resolved.`;
+// ── Registry singleton ───────────────────────────────────────────────
+class PromptRegistry {
+    resolvers = [];
+    register(resolver) {
+        this.resolvers.unshift(resolver);
+    }
+    resolve(endpoint) {
+        const modelLower = endpoint.model.toLowerCase();
+        for (const r of this.resolvers) {
+            if (r.matchesModel?.(endpoint))
+                return r;
+        }
+        for (const r of this.resolvers) {
+            for (const prefix of r.familyPrefixes) {
+                if (modelLower.startsWith(prefix.toLowerCase()))
+                    return r;
+            }
+        }
+        return this.resolvers[this.resolvers.length - 1];
+    }
+    listResolvers() {
+        return this.resolvers.map((r) => r.name);
+    }
+}
+export const promptRegistry = new PromptRegistry();
+export function buildSystemPrompt(mode, endpoint, ctx) {
+    const resolver = promptRegistry.resolve(endpoint);
+    const identity = resolver.resolveIdentityRules?.(endpoint) ?? DEFAULT_IDENTITY;
+    const safety = resolver.resolveSafetyRules?.(endpoint) ?? DEFAULT_SAFETY;
+    const systemPrompt = resolver.resolveSystemPrompt(mode, endpoint);
+    let prompt = `${identity}\n\n${safety}\n\n${systemPrompt}`;
+    // Inject workspace context so the agent knows its working directory
+    if (ctx?.workspaceRoot) {
+        prompt += `\n\n<workspaceContext>\nYou are working in the workspace: ${ctx.workspaceRoot}\nAll relative file paths and searches default to this directory. Use relative paths when possible. Do not search from the drive root — scope operations to this workspace.\n</workspaceContext>`;
+    }
+    return prompt;
+}
+export function getReminderInstructions(mode, endpoint) {
+    const resolver = promptRegistry.resolve(endpoint);
+    return resolver.resolveReminderInstructions?.(mode, endpoint) ?? DEFAULT_REMINDER;
+}
+//# sourceMappingURL=prompt-registry.js.map

package/dist/tools/prompts/prompt-registry.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompt-registry.js","sourceRoot":"","sources":["../../../src/tools/prompts/prompt-registry.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAqBH,wEAAwE;AAExE,MAAM,CAAC,MAAM,gBAAgB,GAAG,oFAAoF,CAAC;AAErH,MAAM,CAAC,MAAM,cAAc,GAAG;;wCAEU,CAAC;AAEzC,MAAM,CAAC,MAAM,gBAAgB,GAAG,uKAAuK,CAAC;AAExM,wEAAwE;AAExE,MAAM,cAAc;IACV,SAAS,GAAmB,EAAE,CAAC;IAEvC,QAAQ,CAAC,QAAsB;QAC7B,IAAI,CAAC,SAAS,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC;IACnC,CAAC;IAED,OAAO,CAAC,QAAuB;QAC7B,MAAM,UAAU,GAAG,QAAQ,CAAC,KAAK,CAAC,WAAW,EAAE,CAAC;QAEhD,KAAK,MAAM,CAAC,IAAI,IAAI,CAAC,SAAS,EAAE,CAAC;YAC/B,IAAI,CAAC,CAAC,YAAY,EAAE,CAAC,QAAQ,CAAC;gBAAE,OAAO,CAAC,CAAC;QAC3C,CAAC;QAED,KAAK,MAAM,CAAC,IAAI,IAAI,CAAC,SAAS,EAAE,CAAC;YAC/B,KAAK,MAAM,MAAM,IAAI,CAAC,CAAC,cAAc,EAAE,CAAC;gBACtC,IAAI,UAAU,CAAC,UAAU,CAAC,MAAM,CAAC,WAAW,EAAE,CAAC;oBAAE,OAAO,CAAC,CAAC;YAC5D,CAAC;QACH,CAAC;QAED,OAAO,IAAI,CAAC,SAAS,CAAC,IAAI,CAAC,SAAS,CAAC,MAAM,GAAG,CAAC,CAAE,CAAC;IACpD,CAAC;IAED,aAAa;QACX,OAAO,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC;IAC3C,CAAC;CACF;AAED,MAAM,CAAC,MAAM,cAAc,GAAG,IAAI,cAAc,EAAE,CAAC;AASnD,MAAM,UAAU,iBAAiB,CAAC,IAAc,EAAE,QAAuB,EAAE,GAAmB;IAC5F,MAAM,QAAQ,GAAG,cAAc,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC;IAClD,MAAM,QAAQ,GAAG,QAAQ,CAAC,oBAAoB,EAAE,CAAC,QAAQ,CAAC,IAAI,gBAAgB,CAAC;IAC/E,MAAM,MAAM,GAAG,QAAQ,CAAC,kBAAkB,EAAE,CAAC,QAAQ,CAAC,IAAI,cAAc,CAAC;IACzE,MAAM,YAAY,GAAG,QAAQ,CAAC,mBAAmB,CAAC,IAAI,EAAE,QAAQ,CAAC,CAAC;IAElE,IAAI,MAAM,GAAG,GAAG,QAAQ,OAAO,MAAM,OAAO,YAAY,EAAE,CAAC;IAE3D,oEAAoE;IACpE,IAAI,GAAG,EAAE,aAAa,EAAE,CAAC;QACvB,MAAM,IAAI,6DAA6D,GAAG,CAAC,aAAa,kMAAkM,CAAC;IAC7R,CAAC;IAED,OAAO,MAAM,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,uBAAuB,CAAC,IAAc,EAAE,QAAuB;IAC7E,MAAM,QAAQ,GAAG,cAAc,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC;IAClD,OAAO,QAAQ,CAAC,2BAA2B,EAAE,CAAC,IAAI,EAAE,QAAQ,CAAC,IAAI,gBAAgB,CAAC;AACpF,CAAC"}

package/dist/tools/prompts/shared-sections.d.ts

@@ -0,0 +1,28 @@
+/**
+ * Shared prompt sections used by all or most model-specific prompts.
+ *
+ * Adapted from VS Code Copilot Chat — tool names replaced with Jait
+ * equivalents, VS Code–specific features (notebooks, devcontainers,
+ * file-linkification) removed.
+ */
+import type { ChatMode } from "../chat-modes.js";
+export declare const JAIT_TOOLS: {
+    readonly read: "read";
+    readonly edit: "edit";
+    readonly execute: "execute";
+    readonly search: "search";
+    readonly web: "web";
+    readonly agent: "agent";
+    readonly todo: "todo";
+    readonly jait: "jait";
+};
+export declare const CORE_INSTRUCTIONS = "You are a highly sophisticated automated coding agent with expert-level knowledge across many different programming languages and frameworks and software engineering tasks \u2014 this encompasses debugging issues, implementing new features, restructuring code, and providing code explanations, among other engineering activities.\nThe user will ask a question, or ask you to perform a task, and it may require lots of research to answer correctly. There is a selection of tools that let you perform actions or retrieve helpful context to answer the user's question.\nBy default, implement changes rather than only suggesting them. If the user's intent is unclear, infer the most useful likely action and proceed with using tools to discover any missing details instead of guessing. When a tool call (like a file edit or read) is intended, make it happen rather than just describing it.\nYou can call tools repeatedly to take actions or gather as much context as needed until you have completed the task fully. Don't give up unless you are sure the request cannot be fulfilled with the tools you have. It's YOUR RESPONSIBILITY to make sure that you have done all you can to collect necessary context.\nContinue working until the user's request is completely resolved before ending your turn and yielding back to the user. Only terminate your turn when you are certain the task is complete. Do not stop or hand back to the user when you encounter uncertainty \u2014 research or deduce the most reasonable approach and continue.";
+export declare const TOOL_USE_INSTRUCTIONS = "If the user is requesting a code sample, you can answer it directly without using any tools.\nWhen using a tool, follow the JSON schema very carefully and make sure to include ALL required properties.\nNo need to ask permission before using a tool.\nNEVER say the name of a tool to a user. For example, instead of saying that you'll use the execute tool, say \"I'll run the command in a terminal\".\nIf you think running multiple tools can answer the user's question, prefer calling them in parallel whenever possible.\nWhen using the read tool, prefer reading a large section over calling the read tool many times in sequence. You can also think of all the pieces you may be interested in and read them in parallel. Read large enough context to ensure you get what you need.\nDon't call the execute tool multiple times in parallel. Instead, run one command and wait for the output before running the next command.\nWhen creating files, be intentional and avoid unnecessary file creation. Only create files that are essential to completing the user's request.\nNEVER try to edit a file by running terminal commands unless the user specifically asks for it.";
+export declare const EDITING_INSTRUCTIONS = "Before you edit an existing file, make sure you have read it first so that you can make proper changes.\nUse the edit tool to modify files precisely. Pay attention to surrounding context to ensure your changes are correct.\nWhen editing files, group your changes by file.\nNEVER show the changes to the user in a codeblock when you can use the edit tool instead.\nFor each file, give a short description of what needs to be changed, then use the edit tool.";
+export declare const SEARCH_INSTRUCTIONS = "For codebase exploration, prefer the agent tool to search and gather data across files.\nWhen using the search tool, prefer searching for specific patterns or identifiers.\nIf you don't know exactly what you're looking for, use broader search terms and refine.";
+export declare const TODO_INSTRUCTIONS = "You have access to the todo tool which tracks steps and progress. Using it helps demonstrate that you've understood the task and convey how you're approaching it.\n\nBreak complex work into logical, actionable steps that can be tracked and verified. Update task status consistently:\n- Mark tasks as in-progress when you begin working on them\n- Mark tasks as completed immediately after finishing each one \u2014 do not batch completions\n\nTask tracking is valuable for:\n- Multi-step work requiring careful sequencing\n- Breaking down ambiguous or complex requests\n- Maintaining checkpoints for feedback and validation\n- When users provide multiple requests or numbered tasks\n\nSkip task tracking for simple, single-step operations that can be completed directly without additional planning.";
+export declare const PLANNING_EXAMPLES = "### Examples\n\n**High-quality plans**\n\nExample 1:\n1. Add CLI entry with file args\n2. Parse Markdown via CommonMark library\n3. Apply semantic HTML template\n4. Handle code blocks, images, links\n5. Add error handling for invalid files\n\nExample 2:\n1. Define CSS variables for colors\n2. Add toggle with localStorage state\n3. Refactor components to use variables\n4. Verify all views for readability\n5. Add smooth theme-change transition\n\nExample 3:\n1. Set up Node.js + WebSocket server\n2. Add join/leave broadcast events\n3. Implement messaging with timestamps\n4. Add usernames + mention highlighting\n5. Persist messages in lightweight DB\n6. Add typing indicators + unread count\n\n**Low-quality plans**\n\nExample 1:\n1. Create CLI tool\n2. Add Markdown parser\n3. Convert to HTML\n\nExample 2:\n1. Add dark mode toggle\n2. Save preference\n3. Make styles look good\n\nIf you need to write a plan, only write high quality plans, not low quality ones.";
+export declare function getAskModeInstructions(): string;
+export declare function getPlanModeInstructions(): string;
+export declare function getModeInstructions(mode: ChatMode): string;
+//# sourceMappingURL=shared-sections.d.ts.map

package/dist/tools/prompts/shared-sections.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"shared-sections.d.ts","sourceRoot":"","sources":["../../../src/tools/prompts/shared-sections.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,kBAAkB,CAAC;AAIjD,eAAO,MAAM,UAAU;;;;;;;;;CASb,CAAC;AAIX,eAAO,MAAM,iBAAiB,0/CAIkS,CAAC;AAEjU,eAAO,MAAM,qBAAqB,yoCAQ8D,CAAC;AAEjG,eAAO,MAAM,oBAAoB,6cAI4D,CAAC;AAE9F,eAAO,MAAM,mBAAmB,yQAEwD,CAAC;AAEzF,eAAO,MAAM,iBAAiB,kyBAYoF,CAAC;AAEnH,eAAO,MAAM,iBAAiB,48BAsCoD,CAAC;AAInF,wBAAgB,sBAAsB,IAAI,MAAM,CAE/C;AAED,wBAAgB,uBAAuB,IAAI,MAAM,CAEhD;AAED,wBAAgB,mBAAmB,CAAC,IAAI,EAAE,QAAQ,GAAG,MAAM,CAS1D"}