Specification Translation Expert

Translate English specification files to Japanese while preserving code blocks and formatting.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/teliha/dev-workflows --skill specification-translation-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Specification Translation Expert
Source: https://github.com/teliha/dev-workflows/tree/main/skills/translate-specs
Command: npx skills add https://github.com/teliha/dev-workflows --skill specification-translation-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill breaks down language barriers in development by automatically translating English specifications into Japanese while preserving all technical terms, code blocks, and formatting.

Core Features & Use Cases

  • Technical Translation: Preserve code blocks and formatting while translating documentation.
  • Consistent Terminology: Use standardized translations for technical terms across all documents.

Quick Start

Translate the specifications to Japanese Translate docs/api/ to Japanese Run translate-specs command

Frequently Asked Questions about Specification Translation Expert

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

FAQPage Schema
How do I translate specification files from English to Japanese while preserving code blocks?

Technical translation of specs preserves code blocks and formatting by identifying Markdown structure, translating prose content only, and maintaining all code snippets intact. The Skill automatically detects and protects code blocks during the translation process across your repository.

Can I maintain consistent technical terminology across translated documentation?

Consistent terminology translation ensures standardized technical terms appear uniformly throughout all translated documents. The Skill applies defined term mappings across the entire documentation set to avoid inconsistencies between files.

What's the best way to translate repository documentation to Japanese at scale?

Batch translation of Markdown specs across directories like docs/api/ processes multiple files while preserving structure and formatting. Run the translate-specs command to automatically identify, translate, and verify all specification files in scope.

Does this work with existing Markdown documentation structure?

Markdown spec translation preserves all formatting, headers, lists, and code blocks while translating text content. The Skill maintains the original document structure and layout so translated specs render identically to English versions.

How do I verify translation completeness and consistency across all specs?

Verification checks ensure all specification files are translated completely and technical terms remain consistent throughout the documentation set. The Skill confirms scope coverage and flags any missing or inconsistent terminology before completion.

Can I integrate technical translation into my localization workflow?

Technical translation fits into i18n and localization workflows by handling specification files as core documentation assets. The Skill outputs fully translated, ready-to-deploy Japanese specs that integrate with standard localization processes.