i18n

Generates translation keys and detects Chinese-language strings in code, supporting localization workflows.

Updated Jun 23, 2025
One-click install
npx skills add https://github.com/Dayopt/app --skill i18n-dayopt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/Dayopt/app/tree/main/.claude/skills/i18n
Command: npx skills add https://github.com/Dayopt/app --skill i18n-dayopt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI text often ends up hard-coded in components, causing localization drift and maintenance overhead. This skill automates detection of hard-coded strings and guides the addition of next-intl compatible translation keys to keep UI localized across languages.

Core Features & Use Cases

  • UIテキストのハードコードを検出し、next-intl キーの自動生成・検証を行います。
  • en/ja のローカライズ対応を想定したキー命名とファイル構造の整合性を維持します。
  • 新規翻訳キーの追加、既存キーの検証、翻訳ファイルの差分チェックを支援します。

Quick Start

UIテキストを含むコンポーネントを作成・編集する際に、ハードコードされた文字列を検出して翻訳キーを自動的に追加してください。

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I detect hard-coded strings in React components for next-intl localization?

Hard-coded UI text in React components is detected automatically, generating and validating next-intl compatible translation keys to prevent localization drift and ensure consistent multi-language maintenance across en/ja locales.

How do I add translation keys for UI text using next-intl in a Next.js project?

To add translation keys for UI text using next-intl, the skill scans your React components for hard-coded strings and automatically generates validated keys, conforming to translation file structure guidance and en/ja synchronization.

Does this next-intl translation tool support both English and Japanese locales?

Yes, the next-intl translation automation supports both English and Japanese locales, maintaining key naming conventions and file structure synchronization specifically for en/ja localization across server and client usage.

What is the best way to maintain en/ja translation file structure synchronization in Next.js?

The best way to maintain en/ja translation file synchronization is by automating hard-coded string detection and enforcing next-intl key naming conventions, which verifies existing keys and checks translation file diffs.

Can I validate existing next-intl translation keys and check translation file diffs?

Yes, you can validate existing next-intl translation keys and check translation file diffs; the skill verifies key naming conventions for server and client usage while ensuring en/ja localization structural integrity.