translate-docs

Translate and synchronize bilingual project documentation between Chinese and English.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hvrryh-web/RadiantX --skill translate-docs-hvrryh-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translate-docs
Source: https://github.com/hvrryh-web/RadiantX/tree/main/.agents/skills/translate-docs
Command: npx skills add https://github.com/hvrryh-web/RadiantX --skill translate-docs-hvrryh-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate and synchronize bilingual project documentation between Chinese and English, ensuring both language versions stay aligned as content evolves.

Core Features & Use Cases

  • Maintains translation direction rules (Changelog: English to Chinese; other pages: Chinese to English).
  • Keeps terminology consistent across documentation by aligning style and phrasing.
  • Supports incremental updates and references to code samples to ensure accuracy.

Quick Start

Run the translate-docs skill to translate the docs folder and synchronize bilingual content.

Frequently Asked Questions about translate-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate and synchronize bilingual project documentation between Chinese and English?

To translate and synchronize bilingual documentation, you can apply direction rules and terminology consistency to align both language versions as source content changes. This ensures developer guides and changelogs maintain bilingual parity during incremental updates.

What is the translation direction for changelogs versus other documentation pages?

The translation direction for changelogs is English to Chinese, while other documentation pages translate from Chinese to English. Enforcing these specific directions ensures accurate localization and consistent bilingual documentation across your project.

How do I keep terminology consistent across bilingual developer guides and reference pages?

To keep terminology consistent across bilingual developer guides, align style and phrasing by referencing code and documentation conventions. This approach enforces translation direction rules and maintains terminology parity throughout your project documentation.

Can I apply incremental updates to bilingual docs without retranslating the entire project?

Yes, you can apply incremental updates to bilingual docs without retranslating everything. The skill supports incremental synchronization, referencing code samples and documentation conventions to update only the changed content while maintaining bilingual parity.

Does this documentation localization approach work for projects requiring strict bilingual parity?

Yes, this documentation localization approach works for projects requiring strict bilingual parity. It enforces translation directions, terminology consistency, and alignment with project style by referencing code conventions, ensuring both language versions stay synchronized as content evolves.