deck-localizer

Localize DexCode MDX decks between Japanese and English while preserving structure.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/co-r-e/dexcode --skill deck-localizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deck-localizer
Source: https://github.com/co-r-e/dexcode/tree/main/.claude/skills/deck-localizer
Command: npx skills add https://github.com/co-r-e/dexcode --skill deck-localizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @google/genai, gray-matter, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Localize DexCode MDX decks between Japanese and English while preserving MDX/JSX syntax and placeholders, reducing manual effort and preventing structural drift.

Core Features & Use Cases

  • Structure-safe translation of MDX decks with dry-run support
  • Selective file scope translation (all, body, notes) and per-file control
  • Validation checks for code fences, asset paths, CSS variables, and imports/exports
  • Batch-localization workflows across decks under decks/<deck-name>

Quick Start

Run the deck-localizer against your deck with --to ja or --to en, review the dry-run results, and then apply changes if acceptable.

Frequently Asked Questions about deck-localizer

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

FAQPage Schema
How do I translate MDX deck content between Japanese and English without breaking JSX syntax?

You can localize MDX decks safely by running the tool with --to ja or --to en. It uses Gemini to translate text while strictly validating code fences, asset paths, CSS variables, and import/export lines to prevent structural drift.

Can I preview MDX localization changes before applying them to my files?

Yes, you can preview localization changes by using the dry-run mode. This allows you to review the proposed Japanese or English translations and verify structural integrity before applying any modifications to your deck files.

How do I translate only the speaker notes in an MDX deck?

You can translate only the speaker notes by using the selective scope feature with the 'notes' option. This focuses the translation on specific sections, alongside 'all' and 'body' scopes, without modifying other deck components.

Does this localization tool validate MDX asset paths and CSS variables during translation?

Yes, the localization tool enforces strict validation checks for code fences, asset paths, CSS variables, and import/export lines during translation. This ensures your MDX deck remains structurally sound and functional after the Japanese or English conversion.

What is the best way to batch translate multiple MDX decks under a specific directory?

The best way to batch translate multiple MDX decks is to target the decks/<deck-name> directory. The tool applies structure-safe translation and strict validation across all targeted files within that batch workflow.