Translates English text to Turkish while preserving technical terms in English. Use when the user wants to translate documentation, messages, user stories, or any text from English to Turkish.
Activate when the user wants to:
Keep globally recognized technical terms in English. Translate headers and body text to Turkish, but preserve technical vocabulary exactly as listed in references/TECHNICAL_TERMS.md.
Copy this checklist and track progress:
Translation Progress:
- [ ] Phase 1: Input Validation
- [ ] Phase 2: Technical Term Scan
- [ ] Phase 3: Translation
- [ ] Phase 4: Post-Translation Validation
- [ ] Phase 5: Output
Accept input as one of:
.md, .txt, or other text fileValidate the input is in English. If mixed or unclear, ask: "Is this text fully in English?"
If an output file path is specified, confirm the path before proceeding.
Load the protected terms dictionary from references/TECHNICAL_TERMS.md.
Scan the input text and tag every occurrence of a protected technical term.
These tagged terms must not be translated in Phase 3.
If a term looks technical but is not in the dictionary, flag it:
Unrecognized term: "<term>". Keep in English or translate?
Count tagged terms. Maintain a running total of all protected term occurrences. This count is reported in the Phase 5 output summary.
Apply these rules strictly:
Follow references/GRAMMAR_RULES.md for:
siz form)Run these checks on the translated output:
| Check | Action if Failed | |-------|-----------------| | Any protected term translated? | Revert to English form | | Turkish suffix harmony correct? | Fix vowel/consonant harmony | | Sentence structure natural? | Restructure to SOV if needed | | Code blocks untouched? | Restore original code blocks | | Consistent terminology? | Align all occurrences |
Present the translated text to the user.
If an output file path was specified, write the result to file.
Summary:
Translation complete.
- Input: [source description]
- Output: [target description]
- Protected terms preserved: [count]
- Flagged terms: [count, if any]
| Phase | Purpose | |-------|---------| | Phase 1 | Validate input text | | Phase 2 | Identify and protect technical terms | | Phase 3 | Translate to Turkish | | Phase 4 | Verify translation quality | | Phase 5 | Deliver output |
The deploy pipeline failed. Create a merge request with the bugfix
and push it to the feature branch. Set the timeout to 5000ms and
add a retry mechanism for the endpoint.
Deploy Pipeline başarısız oldu. Bugfix ile bir Merge Request oluşturun
ve Feature branch'e Push edin. Endpoint için Timeout'u 5000ms olarak
ayarlayın ve bir Retry mekanizması ekleyin.
Dağıtım boru hattı başarısız oldu. Hata düzeltme ile bir birleştirme
isteği oluşturun ve özellik dalına itin.
siz form for professional documentation.Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer