Translate Docs logo

Translate Docs

OrganizationPopular
reactive
translate-docs

Translate the docs site into another language (website/i18n), or update translations after the English docs changed; the repo lists the work and validates it, any model can translate

Overview

Publisherreactive
Repositorydata-client
Skill nametranslate-docs
Stars
2K
Forks
98
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by reactive on GitHub. Read the source before you install it.

Installation

Install the Translate Docs AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/reactive/data-client/tree/master/.agents/skills/translate-docs
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/reactive/data-client.git /tmp/data-client
mkdir -p .claude/skills
cp -r /tmp/data-client/.agents/skills/translate-docs .claude/skills/translate-docs
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Translate Docs in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Translate Docs on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Translate Docs is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Translate the docs

English in docs/ is the only source. website/translate/translate.mjs lists what to translate and checks what you wrote; you do the translating. How the pieces fit: website/translate/README.md.

Procedure

  1. node website/translate/translate.mjs prepare --json (add --locale es for one locale). For each locale it prints:
    • language: the language to write, and glossary: the terms file to follow.
    • pages: each source page to translate into its translation file. new pages need a full translation. update pages already have one: when a diff command is given, run it to see what changed in English and change only the matching parts of the translation, keeping every other line as it is (reviewed wording survives this way). Without a diff, compare the translation against the English yourself.
    • removed: translations it deleted because their page is no longer translated; commit the deletion.
    • ui: UI strings (navbar, footer, sidebar labels) still in English. Each id is <json file>#<key>; translate the message of that key in the file. previous is its translation of older English, to update.
  2. Translate, following the rules below. Write each page to its translation path; create folders as needed.
  3. Before committing, node website/translate/translate.mjs finalize. It checks every changed translation against its English, adds heading anchors, and records the English it translates in website/translate/lock/<locale>.json. Fix each ✗ problem it prints and run it again until it passes. A UI string that should read the same as English (a product name) is accepted with --same <id>.
  4. Commit the translations, the UI JSON files and the lock together.

Weekly run

A Claude Code routine runs this early every Sunday morning; run by hand the same way.

  1. Start from the latest master. If a translation PR from an earlier run is still open, stop: one update at a time keeps review small.
  2. Run the procedure above for every locale. If prepare lists no pages, no UI strings and nothing removed, stop without a PR.
  3. Run node --test website/translate/mdx.test.mjs and node website/translate/translate.mjs check, then open a PR titled docs(i18n): Update translations listing per locale the pages translated, updated and removed.

Never edit website/translate/lock/*.json or the generated website/i18n/<locale>/docusaurus-plugin-content-docs*/current/ folders yourself.

Translation rules

The docs are for Reactive Data Client (@data-client), a TypeScript library for fetching, caching and mutating async data in React and Vue apps.

Write natural, precise technical prose for developers, as a native-speaking engineer would. Keep the meaning, tone and level of detail; never add, drop or summarize content.

Pages are MDX (Markdown with JSX) for Docusaurus. Translate only human-readable prose: paragraphs, headings, list items, table cells, admonition titles (the text in :::tip[...]), link text, image alt text, text between JSX tags, label/title/alt/description attribute strings, and the title, sidebar_label and description front matter values (and their react_/vue_ variants).

Keep everything else byte for byte (finalize rejects changes to it):

  • Code blocks, inline code (like this), import and export lines, JSX tags and their other attributes, {expressions} and HTML.
  • Directive lines: :::react, :::vue, :::tip and other ::: lines, and inline :react[...]/:vue[...] (translate only the text in their brackets).
  • Link and image URLs, front matter keys and every other front matter value, and heading ids like {#some-id}.
  • Markdown structure: the same headings at the same levels, paragraphs, lists, tables and blank lines.

Product, API and package names stay in English. The glossary of each language has the rest.

Frequently asked questions

What does the Translate Docs AI skill do?

Translate the docs site into another language (website/i18n), or update translations after the English docs changed; the repo lists the work and validates it, any model can translate

Why use Translate Docs on TypingMind?

Because you install it once and use it with any model. Translate Docs is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Translate Docs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/reactive/data-client/tree/master/.agents/skills/translate-docs. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Translate Docs?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Translate Docs?

As many as you like. As long as a model supports skills, you can use Translate Docs with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Translate Docs AI skill free?

Yes. It is published on GitHub by reactive under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇