translate-craft

Generate professional translations and app localization across eight languages with ICU syntax.

110|14|Updated May 12, 2026
One-click install
npx skills add https://github.com/EliasOulkadi/shokunin --skill translate-craft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translate-craft
Source: https://github.com/EliasOulkadi/shokunin/tree/main/.pack/skills/translate-craft
Command: npx skills add https://github.com/EliasOulkadi/shokunin --skill translate-craft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents awkward, overly literal translations by producing localization that matches the target language’s tone, formality, grammar patterns, and UI constraints.

Core Features & Use Cases

  • Tone & Register Adaptation: Choose appropriate formality levels per language (e.g., Spanish tú/usted, French tu/vous, Japanese casual/polite/honorific, Arabic RTL and register).
  • Localization-Ready i18n: Support i18n patterns and message formats for React environments, including pluralization and gender via ICU Message Syntax.
  • Quality Audit & UI Safety: Review existing translations, preserve placeholders, and verify layout impacts like expansion (e.g., German/Spanish) and RTL mirroring.

Example use case: You’re launching a React app in German and Arabic and need consistent UI tone, correct plural/gender phrasing, properly formatted dates/currency, and RTL-safe styling.

Quick Start

Translate the attached product onboarding copy from English to Japanese with polite default tone, preserve all placeholders, and return a localization-ready set of strings with correct ICU plural forms.

Frequently Asked Questions about translate-craft

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

FAQPage Schema
How do I localize a React app with ICU Message Syntax for plural and gender forms?

Localize a React app by applying ICU Message Syntax to handle pluralization and gender rules correctly. This approach generates production-ready strings compatible with react-intl and i18next frameworks, ensuring proper grammar across eight supported languages.

What's the best way to handle RTL layout and Arabic tone adaptation during app localization?

Handle RTL layout and Arabic tone adaptation by applying language-specific register rules and mirroring UI components during app localization. This ensures Arabic text reads natively while maintaining correct right-to-left styling and cultural formatting constraints.

How do I preserve placeholders when translating UI and marketing copy?

Preserve placeholders when translating UI and marketing copy by applying formatting rules that protect variable syntax. This ensures localized strings remain fully functional within i18n frameworks without breaking dynamic content injection.

Does this translation approach support different formality levels like Spanish tú/usted and French tu/vous?

Yes, this translation approach supports different formality levels including Spanish tú/usted, French tu/vous, and Japanese casual, polite, and honorific registers. Tone and register adaptation is applied per language to match target audience expectations.

How do I audit existing translations for UI layout expansion and cultural correctness?

Audit existing translations for UI layout expansion by reviewing string length impacts in languages like German and Spanish, checking placeholder preservation, and verifying cultural adaptation. This catches layout-breaking issues before production release.

Can I use this for localizing locale-sensitive values like dates and currency across multiple languages?

Yes, you can use this for localizing locale-sensitive values like dates and currency across eight languages. It applies language-specific formatting rules to ensure dates, numbers, and currency display correctly for each target locale.