home / skills / zeeshan080 / ai-native-robotics / translation-glossary
This skill preserves technical terms in English when translating robotics or AI content to Urdu, with Urdu explanations on first use and consistent terminology.
npx playbooks add skill zeeshan080/ai-native-robotics --skill translation-glossaryReview the files below or copy the command above to add this skill to your agents.
---
name: translation-glossary
description: Technical terms to preserve in English when translating to Urdu. Use when translating robotics or AI content to Urdu while maintaining technical accuracy.
allowed-tools: Read
---
# Translation Glossary
## Instructions
When translating content to Urdu:
1. Keep all technical terms in English
2. Provide Urdu explanation in parentheses on first use
3. Maintain consistent terminology throughout
4. Preserve code blocks and commands exactly
## Golden Rules
1. **Never translate**: Technical terms, code, commands, file names
2. **Always explain**: First occurrence gets Urdu explanation
3. **Be consistent**: Use same term throughout document
4. **Preserve formatting**: Keep code blocks, links, headers
## Translation Pattern
**First occurrence**:
> ROS 2 (روبوٹ آپریٹنگ سسٹم کا دوسرا ورژن) is a robotics middleware.
**Subsequent occurrences**:
> ROS 2 provides many features...
## Reference
See [glossary.md](glossary.md) for the complete term list.
This skill defines a translation glossary and rules for translating robotics and AI content into Urdu while preserving technical accuracy. It instructs translators to keep technical terms in English and provide a concise Urdu explanation on first occurrence. The goal is consistent terminology, intact code and commands, and clear bilingual presentation for learners and engineers.
The skill inspects source text and flags technical terms that must remain in English. On the first occurrence of each term it appends a brief Urdu explanation in parentheses immediately after the English term. It also enforces preservation of code blocks, commands, file names, and formatting so examples remain runnable and unambiguous.
Should I translate acronyms like CPU or LIDAR?
No. Keep acronyms and technical names in English and provide a brief Urdu explanation only on their first occurrence.
What if a code example includes comments in English?
Preserve the code exactly. You may add a translated explanation outside the code block but do not alter code content or formatting.
How long should the Urdu explanation be?
Keep it concise—one short phrase or clause that clarifies the technical term for Urdu readers.