Does it perform any validation after updating strings?

Yes, it includes verification steps such as running 'yarn lint' and 'yarn build' to ensure the changes are valid and don't break the application.

What is the i18n-ops skill?

i18n-ops is a specialized Claude Code skill designed to automate the addition, updating, and management of translation strings and locale files in software projects.

Does it support Chrome extension development?

Yes, it specifically handles workflows for the chrome.i18n API and the _locales directory structure used in Chrome and Firefox extensions.

Can it help find hard-coded strings?

Yes, the workflow includes searching for hard-coded text via pattern matching and replacing it with standardized i18n references.

How does it ensure translation consistency?

The skill verifies that placeholders like {name} are identical across all locale files and ensures that no unused keys are left in the codebase.

Internationalization (i18n) Workflow Manager

Name: Internationalization (i18n) Workflow Manager
Author: daichan132

bydaichan132

•

Developer Tools

Automates internationalization workflows by standardizing locale keys, updating translation files, and ensuring consistency across UI components.

About

The i18n-ops skill streamlines the complex process of managing multi-language support within browser extensions and web projects. It provides a structured approach to adding or updating translation strings, enforcing consistent key naming conventions, and synchronizing locale files such as the _locales directory for Chrome and Firefox extensions. By automating pattern discovery and performing validation checks like placeholder verification and linting, it prevents common i18n errors and ensures a seamless localization experience for global users.

Key Features

Standardized management of _locales and shared i18n assets
Integrated verification through linting and build command validation
Automated discovery of existing i18n patterns and naming conventions
28 GitHub stars
Consistent placeholder synchronization across all supported languages
Automated identification and cleanup of unused translation keys

Use Cases

Refactoring hard-coded UI strings into localized keys and shared assets
Adding support for a new language to a Chrome or Firefox extension
Updating complex UI features with dynamic placeholders across multiple locales

About

Key Features

Standardized management of _locales and shared i18n assets
Integrated verification through linting and build command validation
Automated discovery of existing i18n patterns and naming conventions
28 GitHub stars
Consistent placeholder synchronization across all supported languages
Automated identification and cleanup of unused translation keys

Use Cases

Refactoring hard-coded UI strings into localized keys and shared assets
Adding support for a new language to a Chrome or Firefox extension
Updating complex UI features with dynamic placeholders across multiple locales