update-multilingual-docs

Synchronize English documentation updates into localized README and store description files.

41|5|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/Tai-ch0802/arc-like-chrome-extension --skill update-multilingual-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-multilingual-docs
Source: https://github.com/Tai-ch0802/arc-like-chrome-extension/tree/main/.agent/skills/update-multilingual-docs
Command: npx skills add https://github.com/Tai-ch0802/arc-like-chrome-extension --skill update-multilingual-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of updating project documentation, ensuring consistency across multiple languages after changes are made to the English source.

Core Features & Use Cases

  • Centralized English Source: Updates are made to a single English file, serving as the master.
  • Multilingual Synchronization: Facilitates the translation and insertion of new content into corresponding files for each supported language.
  • Store Description Updates: Manages updates to Chrome Web Store descriptions across all localized versions.
  • Use Case: After adding a new feature to the extension, use this Skill to update the main README, contributing guide, and store descriptions in English, Spanish, French, and Japanese simultaneously.

Quick Start

Update the documentation for the new 'dark mode' feature by editing the English README and then running the update-multilingual-docs skill.

Frequently Asked Questions about update-multilingual-docs

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

FAQPage Schema
How do I sync documentation across multiple languages after updating the English source?

To sync multilingual documentation, you update a centralized English master file and the skill propagates the translated content into corresponding localized files within specified project directories.

What is the best way to update store descriptions for international releases?

Updating store descriptions for international releases is handled by synchronizing content from the English source to each localized Chrome Web Store description file, ensuring consistency across all supported language versions.

Can I use this to update a multilingual README and contributing guide simultaneously?

Yes, you can update a multilingual README and contributing guide simultaneously by editing the English source files and triggering the synchronization process to push changes to all supported language versions.

Do I need to manually translate content for each localized documentation file?

No, you do not need to manually translate content for each localized file. The skill manages the translation and insertion of new content from the English source into the corresponding files for each supported language.

Does multilingual documentation synchronization work with any specified directory structure?

Multilingual documentation synchronization works by managing content insertion within specified directories, ensuring localized versions match the English source while maintaining the existing project folder structure.

When should I avoid using an English source file for content localization?

You should avoid using a single English source file for content localization if your project requires region-specific documentation that deviates structurally from the master English version and cannot be managed through direct synchronization.