@harness-engineering/cli 1.6.2 → 1.8.0

package/dist/agents/skills/shared/i18n-knowledge/locales/fr.yaml

@@ -0,0 +1,35 @@
+locale: "fr"
+name: "French"
+native_name: "Français"
+script: "Latin"
+direction: ltr
+cldr_plural_categories: [one, other]
+expansion_factor: 1.20
+script_characteristics:
+  avg_char_width: "narrow"
+  requires_complex_shaping: false
+  line_break_rules: "standard"
+number_format:
+  decimal_separator: ","
+  grouping_separator: "\u202F"
+  grouping_size: 3
+date_format:
+  short: "DD/MM/YYYY"
+  long: "DD Month YYYY"
+  first_day_of_week: "monday"
+common_pitfalls:
+  - pitfall: "Missing spaces before high punctuation"
+    example: "Bonjour! instead of 'Bonjour !' — French requires a non-breaking space before ; : ! and ?"
+    fix: "Insert a narrow non-breaking space (U+202F) before semicolon, colon, exclamation, and question marks"
+  - pitfall: "Confusing French number grouping"
+    example: "Displaying 1,234 instead of 1 234 — French uses narrow no-break space as grouping separator"
+    fix: "Use Intl.NumberFormat('fr') which correctly uses U+202F as the grouping separator"
+  - pitfall: "Not handling fr-FR vs fr-CA differences"
+    example: "Canadian French uses different vocabulary ('courriel' vs 'email') and some formatting conventions"
+    fix: "Support fr-FR and fr-CA as separate locales when targeting both markets"
+  - pitfall: "Gendered agreement in dynamic strings"
+    example: "'Vous etes connecte' vs 'Vous etes connectee' — adjective ending depends on user gender"
+    fix: "Use inclusive writing patterns or avoid gendered past participles in UI strings where possible"
+  - pitfall: "Quotation mark style"
+    example: "Using English \"quotes\" instead of French guillemets with spaces: 'texte'"
+    fix: "Ensure translation process converts quotation marks to locale-appropriate style (guillemets for French)"

package/dist/agents/skills/shared/i18n-knowledge/locales/he.yaml

@@ -0,0 +1,41 @@
+locale: "he"
+name: "Hebrew"
+native_name: "עברית"
+script: "Hebrew"
+direction: rtl
+cldr_plural_categories: [one, two, other]
+expansion_factor: 1.20
+script_characteristics:
+  avg_char_width: "standard"
+  requires_complex_shaping: false
+  line_break_rules: "standard"
+bidi_considerations:
+  mirror_icons: true
+  mirror_layout: true
+  mixed_direction_text: true
+  calendar_system: "gregorian"
+  digit_system: "western"
+number_format:
+  decimal_separator: "."
+  grouping_separator: ","
+  grouping_size: 3
+date_format:
+  short: "DD.MM.YYYY"
+  long: "DD b-Month YYYY"
+  first_day_of_week: "sunday"
+common_pitfalls:
+  - pitfall: "Dual number form (unique to Hebrew among major languages)"
+    example: "Hebrew has a special form for exactly two: 'יום אחד' (1 day), 'יומיים' (2 days), 'ימים' (3+ days)"
+    fix: "Use CLDR plural categories [one, two, many, other] — do not skip the 'two' form"
+  - pitfall: "RTL layout mirroring without Hebrew-specific testing"
+    example: "Icons that should NOT mirror in RTL (checkmarks, media play buttons) get mirrored anyway"
+    fix: "Create an icon exception list for bidirectional layouts; test with native Hebrew speakers"
+  - pitfall: "Nikud (vowel diacritics) in UI text"
+    example: "Modern Hebrew usually omits nikud — adding it looks childish or overly formal in a UI context"
+    fix: "Use unvocalized Hebrew for UI strings unless targeting children's educational content"
+  - pitfall: "Mixed Hebrew and English in tech interfaces"
+    example: "Hebrew UI with English brand names, code, or tech terms creates complex bidi paragraphs"
+    fix: "Wrap English terms in spans with dir='ltr' to prevent bidi algorithm from reordering them"
+  - pitfall: "Hebrew calendar for date display"
+    example: "Some users expect Hebrew calendar dates alongside or instead of Gregorian dates"
+    fix: "Use Intl.DateTimeFormat('he-IL', {calendar: 'hebrew'}) when Hebrew calendar is needed"

package/dist/agents/skills/shared/i18n-knowledge/locales/hi.yaml

@@ -0,0 +1,35 @@
+locale: "hi"
+name: "Hindi"
+native_name: "हिन्दी"
+script: "Devanagari"
+direction: ltr
+cldr_plural_categories: [one, other]
+expansion_factor: 1.30
+script_characteristics:
+  avg_char_width: "standard"
+  requires_complex_shaping: true
+  line_break_rules: "standard"
+number_format:
+  decimal_separator: "."
+  grouping_separator: ","
+  grouping_sizes: [3, 2]
+date_format:
+  short: "DD/MM/YYYY"
+  long: "DD Month YYYY"
+  first_day_of_week: "sunday"
+common_pitfalls:
+  - pitfall: "Indian number grouping system"
+    example: "1,23,45,678 not 12,345,678 — groups of 2 after the initial group of 3 (from the right)"
+    fix: "Use Intl.NumberFormat('hi-IN') which produces correct Indian grouping automatically"
+  - pitfall: "Devanagari ligatures and conjunct consonants"
+    example: "Two or more consonants combine into a single ligature glyph — font must support conjuncts"
+    fix: "Use fonts with comprehensive Devanagari OpenType support (Noto Sans Devanagari, Mangal)"
+  - pitfall: "Shirorekha (headline) connecting characters"
+    example: "Devanagari characters connect via a horizontal line at the top — breaking this line breaks readability"
+    fix: "Never insert spaces or line breaks within a Devanagari word; use proper shaping-aware text rendering"
+  - pitfall: "Hindi vs English digit display"
+    example: "Hindi can use Devanagari digits (१२३) or Western digits (123) — preference varies by context"
+    fix: "Default to Western digits for digital interfaces; use Devanagari digits only for traditional/cultural contexts"
+  - pitfall: "Font size requirements for Devanagari"
+    example: "Devanagari script has more vertical complexity than Latin — 12px may be too small for readability"
+    fix: "Use minimum 14px for Devanagari body text; the script has ascenders, descenders, and matras that need space"

package/dist/agents/skills/shared/i18n-knowledge/locales/it.yaml

@@ -0,0 +1,32 @@
+locale: "it"
+name: "Italian"
+native_name: "Italiano"
+script: "Latin"
+direction: ltr
+cldr_plural_categories: [one, other]
+expansion_factor: 1.20
+script_characteristics:
+  avg_char_width: "narrow"
+  requires_complex_shaping: false
+  line_break_rules: "standard"
+number_format:
+  decimal_separator: ","
+  grouping_separator: "."
+  grouping_size: 3
+date_format:
+  short: "DD/MM/YYYY"
+  long: "DD Month YYYY"
+  first_day_of_week: "monday"
+common_pitfalls:
+  - pitfall: "Article-noun gender agreement in dynamic content"
+    example: "'il file' (masculine) vs 'la cartella' (feminine) — article must match noun gender"
+    fix: "Include the article in the translatable string with the noun, never construct 'article + noun' dynamically"
+  - pitfall: "Double consonant sensitivity"
+    example: "Truncating words can break meaning — 'anno' (year) vs 'ano' (anus)"
+    fix: "Never truncate Italian words programmatically; use ellipsis on full word boundaries"
+  - pitfall: "Apostrophe handling in articles"
+    example: "'l'utente' (the user) — the apostrophe is grammatically required, not optional punctuation"
+    fix: "Ensure text processing and search indexing handle apostrophes within Italian words correctly"
+  - pitfall: "Text expansion in button labels"
+    example: "'Save' (4 chars) becomes 'Salva' (5 chars); 'Cancel' becomes 'Annulla' (7 chars)"
+    fix: "Allow for 15-20% expansion in Italian; test button and navigation labels with translated strings"

package/dist/agents/skills/shared/i18n-knowledge/locales/ja.yaml

@@ -0,0 +1,38 @@
+locale: "ja"
+name: "Japanese"
+native_name: "日本語"
+script: "CJK"
+direction: ltr
+cldr_plural_categories: [other]
+expansion_factor: 0.8
+script_characteristics:
+  avg_char_width: "wide"
+  requires_complex_shaping: false
+  line_break_rules: "no-spaces"
+  cjk_width_handling: true
+  vertical_text_support: true
+  multiple_scripts: true
+number_format:
+  decimal_separator: "."
+  grouping_separator: ","
+  grouping_size: 3
+date_format:
+  short: "YYYY/MM/DD"
+  long: "YYYY年MM月DD日"
+  first_day_of_week: "sunday"
+common_pitfalls:
+  - pitfall: "No word boundaries for line breaking"
+    example: "Japanese text has no spaces between words — standard word-wrap algorithms fail"
+    fix: "Use CSS word-break: auto or overflow-wrap: anywhere; rely on browser's built-in CJK line-break rules"
+  - pitfall: "Three writing systems in one string"
+    example: "A single sentence may mix kanji, hiragana, and katakana — font fallback chains must cover all three"
+    fix: "Specify comprehensive font stacks: system CJK fonts first, then fallback Latin fonts"
+  - pitfall: "Full-width vs half-width characters"
+    example: "Full-width 'A' (U+FF21) vs half-width 'A' (U+0041) — both valid but visually different widths"
+    fix: "Normalize input to consistent width forms; use Unicode normalization (NFKC) for search and comparison"
+  - pitfall: "Character count vs visual width"
+    example: "10 CJK characters occupy roughly the same width as 20 Latin characters"
+    fix: "Use visual width measurement (canvas measureText or CSS ch units) instead of string.length for layout"
+  - pitfall: "Honorific levels affecting string length"
+    example: "Polite forms (desu/masu) are longer than casual forms — UI strings vary by politeness level"
+    fix: "Establish consistent politeness level (typically polite/desu-masu for apps) and apply uniformly"

package/dist/agents/skills/shared/i18n-knowledge/locales/ko.yaml

@@ -0,0 +1,38 @@
+locale: "ko"
+name: "Korean"
+native_name: "한국어"
+script: "Hangul"
+direction: ltr
+cldr_plural_categories: [other]
+expansion_factor: 1.0
+script_characteristics:
+  avg_char_width: "wide"
+  requires_complex_shaping: false
+  line_break_rules: "standard"
+  cjk_width_handling: true
+  vertical_text_support: false
+  multiple_scripts: false
+number_format:
+  decimal_separator: "."
+  grouping_separator: ","
+  grouping_size: 3
+date_format:
+  short: "YYYY. MM. DD."
+  long: "YYYY년 MM월 DD일"
+  first_day_of_week: "sunday"
+common_pitfalls:
+  - pitfall: "Korean has spaces between words unlike Japanese and Chinese"
+    example: "Korean uses spaces between words: '한국어 번역' — do not apply CJK no-space rules blindly"
+    fix: "Use standard word-wrap for Korean; it breaks between words unlike Chinese/Japanese character-level breaking"
+  - pitfall: "Honorific speech levels affecting text length"
+    example: "Korean has 7 speech levels — formal polite forms are longer than casual forms"
+    fix: "Standardize on formal polite level (합니다체) for apps and ensure consistent usage across all strings"
+  - pitfall: "Postposition particles attached to words"
+    example: "'파일을' (file + object marker) vs '파일이' (file + subject marker) — particle depends on context"
+    fix: "Include particles in the translatable string; never programmatically append Korean particles"
+  - pitfall: "Hangul syllable block composition"
+    example: "One Hangul syllable is composed of 2-3 jamo but displays as one character block"
+    fix: "Use Unicode NFC normalization for Korean text; decomposed jamo (NFD) render as separate components"
+  - pitfall: "Number grouping with man (10,000) convention"
+    example: "Large numbers sometimes group by 10,000 (만) instead of 1,000 in informal contexts"
+    fix: "Use Intl.NumberFormat('ko') for standard grouping; add 만/억 suffixes only where culturally appropriate"

package/dist/agents/skills/shared/i18n-knowledge/locales/nl.yaml

@@ -0,0 +1,32 @@
+locale: "nl"
+name: "Dutch"
+native_name: "Nederlands"
+script: "Latin"
+direction: ltr
+cldr_plural_categories: [one, other]
+expansion_factor: 1.20
+script_characteristics:
+  avg_char_width: "narrow"
+  requires_complex_shaping: false
+  line_break_rules: "standard"
+number_format:
+  decimal_separator: ","
+  grouping_separator: "."
+  grouping_size: 3
+date_format:
+  short: "DD-MM-YYYY"
+  long: "DD Month YYYY"
+  first_day_of_week: "monday"
+common_pitfalls:
+  - pitfall: "Long compound words similar to German"
+    example: "'arbeidsongeschiktheidsverzekering' (disability insurance) — 35 characters without spaces"
+    fix: "Apply CSS hyphens: auto with lang='nl' and test overflow behavior with real Dutch translations"
+  - pitfall: "Confusing nl-NL and nl-BE (Flemish)"
+    example: "Using 'fiets' vs regional vocabulary differences between Netherlands and Belgium"
+    fix: "Support nl-NL and nl-BE separately when targeting both markets; formatting conventions differ"
+  - pitfall: "IJ digraph capitalization"
+    example: "Capitalizing only the I in 'IJsselmeer' — IJ is a single unit and both letters must capitalize"
+    fix: "When applying text-transform: capitalize, handle the IJ digraph as a special case for Dutch"
+  - pitfall: "Diminutive suffixes in UI labels"
+    example: "Dutch uses diminutives extensively (-je, -tje, -pje) which can change word length unpredictably"
+    fix: "Test with actual translations rather than estimating expansion; diminutives can shorten or lengthen labels"

package/dist/agents/skills/shared/i18n-knowledge/locales/pl.yaml

@@ -0,0 +1,35 @@
+locale: "pl"
+name: "Polish"
+native_name: "Polski"
+script: "Latin"
+direction: ltr
+cldr_plural_categories: [one, few, many, other]
+expansion_factor: 1.30
+script_characteristics:
+  avg_char_width: "narrow"
+  requires_complex_shaping: false
+  line_break_rules: "standard"
+number_format:
+  decimal_separator: ","
+  grouping_separator: "\u00A0"
+  grouping_size: 3
+date_format:
+  short: "DD.MM.YYYY"
+  long: "DD Month YYYY"
+  first_day_of_week: "monday"
+common_pitfalls:
+  - pitfall: "Four plural forms with complex modular rules"
+    example: "1 plik, 2 pliki, 5 plikow, 22 pliki — similar to Russian but with different thresholds"
+    fix: "Use CLDR plural rules: one (1), few (2-4,22-24...), many (5-21,25-31...), other (fractional)"
+  - pitfall: "Special Polish characters in sorting and search"
+    example: "Polish has a, c, e, l, n, o, s, z, z — these sort differently than their base Latin equivalents"
+    fix: "Use Intl.Collator('pl') for sorting; Polish letters with diacritics have specific sort positions"
+  - pitfall: "Text expansion of 20-30%"
+    example: "'Settings' (8 chars) becomes 'Ustawienia' (10 chars); 'Delete' becomes 'Usun' (4 chars, shorter)"
+    fix: "Design for 30% expansion overall; individual strings may expand or contract unpredictably"
+  - pitfall: "Gendered past tense verbs"
+    example: "'You logged in' differs by gender: 'Zalogowales sie' (m) vs 'Zalogowalas sie' (f)"
+    fix: "Avoid past tense constructions in UI or use gender-neutral alternatives when possible"
+  - pitfall: "Consonant clusters in words"
+    example: "Polish has consonant clusters like 'wspolprace' that affect text-to-speech and hyphenation"
+    fix: "Use proper Polish hyphenation dictionaries; do not apply English hyphenation rules to Polish text"

package/dist/agents/skills/shared/i18n-knowledge/locales/pt.yaml

@@ -0,0 +1,32 @@
+locale: "pt"
+name: "Portuguese"
+native_name: "Português"
+script: "Latin"
+direction: ltr
+cldr_plural_categories: [one, other]
+expansion_factor: 1.25
+script_characteristics:
+  avg_char_width: "narrow"
+  requires_complex_shaping: false
+  line_break_rules: "standard"
+number_format:
+  decimal_separator: ","
+  grouping_separator: "."
+  grouping_size: 3
+date_format:
+  short: "DD/MM/YYYY"
+  long: "DD de Month de YYYY"
+  first_day_of_week: "monday"
+common_pitfalls:
+  - pitfall: "Treating pt-BR and pt-PT as identical"
+    example: "Using 'celular' (Brazil) where 'telemovel' (Portugal) is expected, or vice versa"
+    fix: "Support pt-BR and pt-PT as separate locales; vocabulary, spelling, and formatting differ significantly"
+  - pitfall: "Spelling reform inconsistencies"
+    example: "Mixing pre-2009 and post-2009 orthographic agreement spellings in the same interface"
+    fix: "Standardize on post-reform spelling and ensure all translation memory is updated consistently"
+  - pitfall: "Gendered language in user-facing strings"
+    example: "'Bem-vindo' (masculine) vs 'Bem-vinda' (feminine) — greeting depends on user gender"
+    fix: "Use gender-neutral alternatives like 'Boas-vindas' or provide both forms based on user profile"
+  - pitfall: "Brazilian vs European number formatting"
+    example: "pt-BR and pt-PT both use comma for decimal, but currency symbol placement may differ"
+    fix: "Use locale-specific formatting (pt-BR vs pt-PT) rather than generic pt for currency display"

package/dist/agents/skills/shared/i18n-knowledge/locales/ru.yaml

@@ -0,0 +1,35 @@
+locale: "ru"
+name: "Russian"
+native_name: "Русский"
+script: "Cyrillic"
+direction: ltr
+cldr_plural_categories: [one, few, many, other]
+expansion_factor: 1.25
+script_characteristics:
+  avg_char_width: "standard"
+  requires_complex_shaping: false
+  line_break_rules: "standard"
+number_format:
+  decimal_separator: ","
+  grouping_separator: "\u00A0"
+  grouping_size: 3
+date_format:
+  short: "DD.MM.YYYY"
+  long: "DD Month YYYY g."
+  first_day_of_week: "monday"
+common_pitfalls:
+  - pitfall: "Four plural forms with complex rules"
+    example: "1 файл, 2 файла, 5 файлов, 21 файл — the rule depends on the last two digits"
+    fix: "Use CLDR plural rules: one (1,21,31...), few (2-4,22-24...), many (5-20,25-30...), other (fractional)"
+  - pitfall: "Six grammatical cases affecting dynamic content"
+    example: "'Москва' changes form by case: Москвы (genitive), Москве (dative), Москву (accusative)"
+    fix: "Include case-inflected forms in translation strings; never try to programmatically decline Russian nouns"
+  - pitfall: "Cyrillic characters that look identical to Latin"
+    example: "Cyrillic 'а' (U+0430) looks like Latin 'a' (U+0061) but they are different characters"
+    fix: "Use Unicode-aware text comparison; visually identical Cyrillic/Latin chars cause search and auth issues"
+  - pitfall: "Number grouping with non-breaking space"
+    example: "1 000 000 not 1,000,000 — Russian uses non-breaking space as grouping separator"
+    fix: "Use Intl.NumberFormat('ru') for correct space-based number grouping"
+  - pitfall: "Abbreviated month and day names"
+    example: "Russian abbreviations follow different patterns than English — 'янв.' not 'Янв'"
+    fix: "Use Intl.DateTimeFormat('ru') for abbreviated date components; do not manually truncate month names"

package/dist/agents/skills/shared/i18n-knowledge/locales/sv.yaml

@@ -0,0 +1,32 @@
+locale: "sv"
+name: "Swedish"
+native_name: "Svenska"
+script: "Latin"
+direction: ltr
+cldr_plural_categories: [one, other]
+expansion_factor: 1.10
+script_characteristics:
+  avg_char_width: "narrow"
+  requires_complex_shaping: false
+  line_break_rules: "standard"
+number_format:
+  decimal_separator: ","
+  grouping_separator: "\u00A0"
+  grouping_size: 3
+date_format:
+  short: "YYYY-MM-DD"
+  long: "DD Month YYYY"
+  first_day_of_week: "monday"
+common_pitfalls:
+  - pitfall: "Definite article suffixes changing word length"
+    example: "'hus' (house) becomes 'huset' (the house) — suffix adds characters unpredictably"
+    fix: "Account for suffix-based articles when estimating text length; Swedish words grow with definiteness"
+  - pitfall: "Special characters in sorting"
+    example: "Swedish alphabet ends with A, A, O — these sort AFTER Z, not with A and O"
+    fix: "Use locale-aware string comparison (Intl.Collator('sv')) for sorting Swedish text"
+  - pitfall: "ISO 8601 date format as default"
+    example: "Swedish natively uses YYYY-MM-DD (ISO 8601) — displaying DD/MM/YYYY feels foreign"
+    fix: "Use Intl.DateTimeFormat('sv') which correctly produces the ISO-style date format"
+  - pitfall: "Number grouping with space separator"
+    example: "Displaying 1,000 instead of 1 000 — Swedish uses non-breaking space as grouping separator"
+    fix: "Use Intl.NumberFormat('sv') for correct space-based number grouping"

package/dist/agents/skills/shared/i18n-knowledge/locales/th.yaml

@@ -0,0 +1,35 @@
+locale: "th"
+name: "Thai"
+native_name: "ภาษาไทย"
+script: "Thai"
+direction: ltr
+cldr_plural_categories: [other]
+expansion_factor: 1.15
+script_characteristics:
+  avg_char_width: "standard"
+  requires_complex_shaping: true
+  line_break_rules: "dictionary"
+number_format:
+  decimal_separator: "."
+  grouping_separator: ","
+  grouping_size: 3
+date_format:
+  short: "DD/MM/YYYY"
+  long: "DD Month YYYY"
+  first_day_of_week: "sunday"
+common_pitfalls:
+  - pitfall: "No spaces between words — dictionary-based line breaking required"
+    example: "Thai text runs words together without spaces; standard word-wrap fails completely"
+    fix: "Use ICU or dictionary-based word segmentation (Intl.Segmenter with granularity: 'word') for line breaking"
+  - pitfall: "Stacking diacritics above and below characters"
+    example: "Thai uses above-character vowels, tone marks, and below-character vowels — vertical space needed"
+    fix: "Increase line-height to at least 1.8 for Thai text to accommodate stacking diacritics"
+  - pitfall: "Thai digits vs Western digits"
+    example: "Thai has its own digit set (๐๑๒๓๔๕๖๗๘๙) but Western digits are common in digital contexts"
+    fix: "Default to Western digits for apps; Thai digits are used mainly in formal/traditional documents"
+  - pitfall: "Buddhist Era calendar year"
+    example: "Thai calendar year = Gregorian + 543, so 2025 CE = 2568 BE — some users expect BE years"
+    fix: "Use Intl.DateTimeFormat('th', {calendar: 'buddhist'}) when Buddhist Era dates are appropriate"
+  - pitfall: "Complex character composition affecting string operations"
+    example: "A visual Thai 'character' may be composed of multiple Unicode code points (base + vowel + tone)"
+    fix: "Use grapheme cluster-aware string operations; never split Thai text by code point or char index"

package/dist/agents/skills/shared/i18n-knowledge/locales/tr.yaml

@@ -0,0 +1,35 @@
+locale: "tr"
+name: "Turkish"
+native_name: "Türkçe"
+script: "Latin"
+direction: ltr
+cldr_plural_categories: [one, other]
+expansion_factor: 1.20
+script_characteristics:
+  avg_char_width: "narrow"
+  requires_complex_shaping: false
+  line_break_rules: "standard"
+number_format:
+  decimal_separator: ","
+  grouping_separator: "."
+  grouping_size: 3
+date_format:
+  short: "DD.MM.YYYY"
+  long: "DD Month YYYY"
+  first_day_of_week: "monday"
+common_pitfalls:
+  - pitfall: "Dotted vs dotless I — the most famous i18n bug"
+    example: "'istanbul'.toUpperCase() produces 'ISTANBUL' (ASCII I) instead of correct Turkish 'İSTANBUL' (İ, U+0130 Latin Capital Letter I With Dot Above)"
+    fix: "Always use locale-aware case conversion: toLocaleUpperCase('tr') and toLocaleLowerCase('tr')"
+  - pitfall: "Case-insensitive comparison breaking with Turkish locale"
+    example: "Comparing 'FILE' and 'file' with Turkish locale fails because I != i in Turkish"
+    fix: "Use locale-aware comparison (Intl.Collator) or normalize to a known locale for case-insensitive checks"
+  - pitfall: "Agglutinative grammar creating long words"
+    example: "'Avrupalilasamayanlardan' (from those who cannot be Europeanized) — suffixes stack"
+    fix: "Design for text expansion from suffix stacking; use CSS overflow-wrap: break-word for safety"
+  - pitfall: "Vowel harmony in suffixes"
+    example: "Suffixes change based on the last vowel: 'evde' (in the house) vs 'okulda' (in the school)"
+    fix: "Never programmatically append Turkish suffixes; always use translator-provided complete forms"
+  - pitfall: "Currency formatting for Turkish Lira"
+    example: "Turkish Lira symbol (₺) placement and number formatting must follow Turkish conventions"
+    fix: "Use Intl.NumberFormat('tr-TR', {style: 'currency', currency: 'TRY'}) for proper Lira formatting"

package/dist/agents/skills/shared/i18n-knowledge/locales/zh-Hans.yaml

@@ -0,0 +1,38 @@
+locale: "zh-Hans"
+name: "Chinese (Simplified)"
+native_name: "简体中文"
+script: "CJK"
+direction: ltr
+cldr_plural_categories: [other]
+expansion_factor: 0.6
+script_characteristics:
+  avg_char_width: "wide"
+  requires_complex_shaping: false
+  line_break_rules: "no-spaces"
+  cjk_width_handling: true
+  vertical_text_support: false
+  multiple_scripts: false
+number_format:
+  decimal_separator: "."
+  grouping_separator: ","
+  grouping_size: 3
+date_format:
+  short: "YYYY/MM/DD"
+  long: "YYYY年MM月DD日"
+  first_day_of_week: "sunday"
+common_pitfalls:
+  - pitfall: "Text contraction causing UI elements to look empty"
+    example: "'Internationalization' (20 chars) becomes '国际化' (3 chars) — a 85% reduction"
+    fix: "Use min-width on buttons and containers to prevent them from collapsing with short CJK translations"
+  - pitfall: "No word spaces means no natural line breaks"
+    example: "A long Chinese sentence has no spaces — wrapping can break between any two characters"
+    fix: "Use CSS word-break: normal for CJK; browsers handle character-level breaking correctly by default"
+  - pitfall: "Confusing zh-Hans with zh-Hant"
+    example: "Showing traditional characters (繁體) to mainland China users who expect simplified (简体)"
+    fix: "Use explicit zh-Hans (simplified) vs zh-Hant (traditional) subtags; never use bare 'zh'"
+  - pitfall: "CJK punctuation width"
+    example: "Chinese uses full-width punctuation (。，！) not half-width (.  , !) — affects text measurement"
+    fix: "Account for full-width punctuation in text width calculations and do not replace with ASCII equivalents"
+  - pitfall: "Font size minimum for CJK readability"
+    example: "Complex characters become illegible below 12px — strokes merge at small sizes"
+    fix: "Set minimum font size of 12px for CJK text; 14px is recommended for body text"

package/dist/agents/skills/shared/i18n-knowledge/locales/zh-Hant.yaml

@@ -0,0 +1,35 @@
+locale: "zh-Hant"
+name: "Chinese (Traditional)"
+native_name: "繁體中文"
+script: "CJK"
+direction: ltr
+cldr_plural_categories: [other]
+expansion_factor: 0.6
+script_characteristics:
+  avg_char_width: "wide"
+  requires_complex_shaping: false
+  line_break_rules: "no-spaces"
+  cjk_width_handling: true
+  vertical_text_support: true
+  multiple_scripts: false
+number_format:
+  decimal_separator: "."
+  grouping_separator: ","
+  grouping_size: 3
+date_format:
+  short: "YYYY/MM/DD"
+  long: "YYYY年MM月DD日"
+  first_day_of_week: "sunday"
+common_pitfalls:
+  - pitfall: "Regional vocabulary differences (Taiwan vs Hong Kong vs Macau)"
+    example: "'Software' is '軟體' in Taiwan but '軟件' in Hong Kong — same script, different terms"
+    fix: "Support zh-Hant-TW and zh-Hant-HK as separate locales when targeting both markets"
+  - pitfall: "Automatic simplified-to-traditional conversion producing wrong characters"
+    example: "One simplified character may map to multiple traditional characters based on context"
+    fix: "Never use automated character conversion; commission proper traditional Chinese translations"
+  - pitfall: "More complex characters requiring larger minimum font size"
+    example: "Traditional characters have more strokes than simplified — 體 vs 体 — needing higher resolution"
+    fix: "Use minimum 13-14px for traditional Chinese body text to ensure stroke clarity"
+  - pitfall: "Mixed CJK and Latin text spacing"
+    example: "No space between Chinese and English words looks cramped: '使用GitHub' vs '使用 GitHub'"
+    fix: "Apply CSS text-autospace or insert thin spaces between CJK and Latin text runs programmatically"

package/dist/agents/skills/shared/i18n-knowledge/mcp-interop/i18next-mcp.yaml

@@ -0,0 +1,56 @@
+name: "i18next MCP"
+description: "i18next-specific MCP server for project analysis, translation coverage reporting, key usage analysis, and namespace management"
+mcp_server_id: "i18next-mcp"
+source: "https://github.com/anthropics/i18next-mcp"
+
+capabilities:
+  - name: "Project Analysis"
+    description: "Analyze i18next project structure, configuration, and translation file organization"
+    tools: ["analyze_project", "get_config", "list_namespaces"]
+  - name: "Translation Coverage"
+    description: "Report translation coverage per locale and namespace, identifying missing translations"
+    tools: ["get_coverage_report", "find_missing_translations", "find_unused_keys"]
+  - name: "Key Usage Analysis"
+    description: "Trace translation key usage in source code to find unused or missing keys"
+    tools: ["find_key_usage", "find_hardcoded_strings", "extract_keys"]
+  - name: "Namespace Management"
+    description: "Create, merge, and split translation namespaces"
+    tools: ["create_namespace", "merge_namespaces", "move_keys"]
+
+when_to_use:
+  - scenario: "Project already using i18next that wants deeper translation insights"
+    reason: "i18next MCP understands i18next conventions (namespaces, pluralization suffixes, interpolation) natively"
+  - scenario: "Auditing an existing codebase for i18n completeness"
+    reason: "Key usage analysis finds hardcoded strings and unused translation keys without manual code review"
+  - scenario: "Refactoring translation file organization"
+    reason: "Namespace management tools help split large translation files or merge fragmented namespaces"
+
+when_not_to_use:
+  - scenario: "Project using react-intl, vue-i18n, or other non-i18next frameworks"
+    reason: "i18next MCP tools are specific to i18next conventions and file structures"
+  - scenario: "Team needing full TMS capabilities (translator collaboration, review workflows)"
+    reason: "i18next MCP is a developer tool, not a TMS; use Tolgee or Lokalise for translator workflows"
+
+integration_patterns:
+  - pattern: "Harness workflow with i18next MCP for translation audit"
+    description: "Use i18next MCP tools during the i18n assessment phase to analyze coverage and identify gaps"
+    config_example: |
+      // harness.config.json
+      {
+        "mcp": {
+          "servers": {
+            "i18next": {
+              "command": "npx",
+              "args": ["-y", "@anthropic/i18next-mcp"],
+              "env": {
+                "I18NEXT_PROJECT_PATH": "."
+              }
+            }
+          }
+        }
+      }
+
+limitations:
+  - "Only supports i18next ecosystem; not compatible with other i18n frameworks"
+  - "Key extraction may miss dynamically constructed translation keys (t(`error.${code}`))"
+  - "Coverage reporting depends on consistent file structure matching the configured pattern"