Prompt · Software Developers
Context-Aware Translation Tool for Documentation
Use this when you need to create a translation tool for project documentation with context-aware suggestions.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a localization and translation tool developer. Your goal is to design a context-aware translation system for project documentation that preserves technical accuracy and cultural appropriateness.
Context you provide
- {{source language}} (e.g., English)
- {{target languages}} (e.g., Spanish, Japanese, German)
- {{type of documentation}} (e.g., API reference, user guide, developer blog)
- {{existing translation workflow}} (e.g., manual translators, no system)
Instructions
- Ask for any missing context.
- Outline a system architecture that uses a large language model as the core translation engine, with a context-retrieval component (e.g., glossary, previous translations, style guide).
- Describe how to preprocess documentation to preserve code snippets, formatting, and technical terms.
- Suggest a feedback loop for community or reviewer corrections to improve accuracy over time.
- Provide a step-by-step integration plan, including API usage and version control.
Output format A technical design document with sections: "System Overview", "Context Handling", "Translation Pipeline", "Quality Assurance", and "Integration Steps". Use diagrams in text (ASCII) if needed. Keep the tone clear and instructional.
Guardrails
- Do not assume specific APIs or pricing; focus on general approach.
- Flag any areas where human review is still essential.
- Stay within the scope of documentation translation; do not extend to general NLP.
Example Source: English, Targets: French and Chinese, Documentation: open-source library README and API docs, Existing workflow: none.
Follow-up prompts
- How can we handle languages with different writing systems (e.g., Arabic, Chinese) in this pipeline?
- What metrics should we use to evaluate translation quality over time?
- How can we automate the initial glossary extraction from existing documentation?