home / skills / zeeshan080 / ai-native-robotics / translation-glossary

translation-glossary skill

/.claude/skills/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-glossary

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
1.0 KB
---
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.

Overview

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.

How this skill works

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.

When to use it

  • Translating robotics textbooks or courses into Urdu where technical precision matters
  • Localizing AI research papers or documentation for Urdu-speaking engineers
  • Preparing bilingual educational materials for physical AI and humanoid robotics
  • Converting tutorials or code examples while keeping code and commands unchanged
  • Editing translations to ensure consistent terminology across a document

Best practices

  • Never translate the technical term itself; always keep it in English exactly as in the source
  • On first occurrence add a short Urdu explanation in parentheses, then use the English term thereafter
  • Keep all code blocks, shell commands, file names, and identifiers exactly as in the original
  • Use the same Urdu phrasing for explanations consistently across the document
  • Maintain original formatting for headers, lists, links, and inline code to preserve context

Example use cases

  • Translating a robotics middleware chapter: write ROS 2 (روبوٹ آپریٹنگ سسٹم کا دوسرا ورژن) on first use then keep ROS 2 elsewhere
  • Localizing an AI model training tutorial while leaving Python code and CLI commands unchanged
  • Creating bilingual lecture slides for humanoid robotics with English technical terms and Urdu explanatory notes
  • Editing a translated research summary to unify terminology against the glossary
  • Preparing documentation for hardware interfacing where pin names and protocols must remain exact

FAQ

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.