expo-docs-ja-translatorlisted

# expo-docs-ja-translator Translate one Expo MDX docs page from English to Japanese. Output to `pages/ja/<same-path>` mirroring the English source path. This skill is Expo-specific: it knows the product vocabulary, the custom JSX components used in Expo MDX, the formatting rules MDX requires for Japanese text, and the structural invariants that the rendered page depends on. ## When to use - User pastes or names a single English MDX path under `expo/docs/pages/...` and asks for a Japanese version. - User says "translate this page", "translate to ja", "ja translate", "/expo-docs-ja-translator". ## When NOT to use - Translating UI strings in `messages/*.json` — that's react-intl chrome, not docs prose. Edit those files directly. - API reference pages auto-generated from JSDoc — those are not authored MDX prose. - Bulk translation of many pages at once — run this skill once per page so each page can be reviewed. ## Inputs - **Source file path:** absolute or repo-relative path to an MDX page under `expo/docs/pages/...`. If the user does not provide one, ask for it. - **Output path (auto-derived):** `expo/docs/pages/ja/<same subpath>`. Confirm before writing if the target file already exists. ## Workflow ### Step 1 — Read the source Read the full English MDX file. Note: - Frontmatter keys (`title`, `sidebar_title`, `description`, `hideTOC`, etc.). - Top-of-file `import` statements. - Every JSX component used (`<BoxLink>`, `<Step>`, `<Tabs>`, `<Terminal>`, `<ContentSpotli