localize

Scan source files for hardcoded strings and localization anti-patterns.

70|42|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tranhieutt/software_development_department --skill localize-tranhieutt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/localize
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill localize-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Localization teams often work blind, manually searching for hardcoded UI strings and balancing translators without a consistent workflow. Without enforcement, missing keys, placeholder mismatches, and stale translations slip into builds, causing broken experiences across languages.

Core Features & Use Cases

  • Scan anti-patterns: Search src/ for literal text, concatenations, and locale-unaware formatting while flagging embedded text in assets and assumptions that ignore right-to-left languages.
  • Extract keys and diff: Compare source strings against assets/data tables, propose descriptive keys following category conventions, and output diffs for reviewer approval.
  • Validate coverage and issues: Verify translator comments, placeholder consistency, character limits, missing translations, and orphaned entries while grouping results by locale. Use Case: After a UI sprint adds new copy, run the extract and validate commands to refresh the string tables and produce a coverage matrix before handing work to translators.

Quick Start

Ask the localization skill to run the scan command on src to list hardcoded strings and localization anti-patterns.

Frequently Asked Questions about localize

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

FAQPage Schema
How do I find hardcoded strings and localization anti-patterns in my source files?

To find hardcoded strings and localization anti-patterns, scan your src/ directory to detect literal text, string concatenations, and locale-unaware formatting, while also flagging embedded text in assets and assumptions that ignore right-to-left languages.

How do I validate translation coverage and check for missing keys in string tables?

Validate translation coverage by verifying translator comments, placeholder consistency, character limits, and missing translations, while grouping results by locale to identify missing keys and orphaned entries in your string tables.

How do I extract new localization keys and diff them against existing translation assets?

Extract new localization keys by comparing source strings against assets and data tables, propose descriptive keys following category conventions, and output diffs for reviewer approval to update translation assets.

What is the best way to maintain English as the authoritative locale and report coverage metrics?

Maintain English as the authoritative locale by scanning source files for missing keys and locale anti-patterns, then generate coverage metrics and status reports across UI code, string tables, and translation assets.

Why do placeholder mismatches and stale translations slip into builds, and how do I prevent it?

Placeholder mismatches and stale translations slip into builds without consistent enforcement; prevent them by validating placeholder consistency, checking character limits, and scanning for missing translations before handing work to translators.