Built In 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 |
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 for the full picture, including the Evidence field on issue cards.