# Default Prompts

The plugin ships with default prompts organised into three categories:

| Category          | Prompts                                                                                                                                                                      | Used in              |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- |
| **Translate**     | Default Translation Prompt                                                                                                                                                   | Batch Translate mode |
| **Proofread**     | Default Proofreading Prompt                                                                                                                                                  | Batch Proofread mode |
| **QuickLauncher** | Assess translation, Define, Explain (in general), Explain (within project context), Translate segment using fuzzy matches, Translate selection in context of current project | QuickLauncher menu   |

:::note The Default Translation Prompt is a general-purpose starting point. For domain-specific projects, use [**AutoPrompt**](/help/features/batch-operations/generate-prompt.md) to automatically create a comprehensive prompt tailored to your document – or duplicate the default prompt in the Prompt Manager and customise it manually. :::

#### About the Default Proofreading Prompt

The Default Proofreading Prompt is intentionally short. Most of the structure proofreading needs – persona, the five quality categories (accuracy / completeness / terminology / grammar / number formatting), the output format, the "no full corrected translations" rule, language-specific checks for Dutch / German / French – is **already in the hardcoded base** that every Batch Proofread uses, so the prompt itself only adds what the base doesn't have:

* **Default to OK** – raise an issue only when there's a specific, demonstrable problem in the translation, never speculative concerns.
* **Citation discipline** – terminology consistency claims must cite specific source segment numbers in the **Evidence:** field, against the full bilingual document context that's auto-included.
* **Source query distinction** – source-side errors (typos, duplications, internal inconsistencies) get prefixed with "Source query:" rather than triggering target changes.
* **Explicit boundaries** – the AI doesn't re-engineer the source, propose alternative terminology without a citation, flag stylistic preferences, or flag empty target lines.

These behaviours target the false-positive patterns most users encounter: the AI fabricating "term X used elsewhere" claims, second-guessing the source's substantive claims, and treating stylistic preferences as errors. See [AI Proofreader](/help/features/batch-operations/ai-proofreader.md) for the full picture, including the Evidence field on issue cards.

:::note **To customise:** clone the default in the Prompt Manager and edit your copy. Defaults are read-only and get refreshed when the plugin updates – your clone keeps all your changes regardless. When the Prompt Library writes the default to disk, it includes a `default: true` flag in the YAML frontmatter; clones get `default: false` and are never touched by future updates. :::


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://supervertaler.gitbook.io/help/settings/prompts/built-in-prompts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
