@harness-engineering/cli 1.7.0 → 1.8.0

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"

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

@@ -0,0 +1,56 @@
+name: "Lingo.dev"
+description: "AI-powered translation platform with brand voice consistency, multi-engine machine translation, and glossary management"
+mcp_server_id: "lingo-dev-mcp"
+source: "https://github.com/anthropics/lingo-dev-mcp"
+
+capabilities:
+  - name: "Multi-Engine Machine Translation"
+    description: "Translate content using multiple AI/MT engines with quality comparison"
+    tools: ["translate_text", "translate_file", "batch_translate"]
+  - name: "Glossary Management"
+    description: "Manage terminology glossaries to ensure translation consistency"
+    tools: ["create_glossary_term", "list_glossary", "update_glossary_term"]
+  - name: "Brand Voice Consistency"
+    description: "Configure and enforce brand voice profiles for translations"
+    tools: ["set_brand_voice", "check_brand_consistency"]
+  - name: "Translation Memory"
+    description: "Leverage previously approved translations for consistency and cost savings"
+    tools: ["search_translation_memory", "add_to_translation_memory"]
+
+when_to_use:
+  - scenario: "Team needs high-quality machine translation with terminology consistency"
+    reason: "Lingo.dev specializes in AI translation quality with glossary enforcement and brand voice"
+  - scenario: "Project has established brand terminology that must be preserved across languages"
+    reason: "Glossary management ensures product names, features, and key terms are translated consistently"
+  - scenario: "Rapid iteration with frequent string changes"
+    reason: "AI translation with translation memory enables fast turnaround without waiting for human translators"
+
+when_not_to_use:
+  - scenario: "Content requiring certified or sworn translations (legal, medical)"
+    reason: "AI translation, even high quality, does not meet certification requirements for regulated content"
+  - scenario: "Team prefers full human translation workflow"
+    reason: "Lingo.dev's value proposition centers on AI translation; pure human workflows are better served by a traditional TMS"
+
+integration_patterns:
+  - pattern: "Harness workflow with Lingo.dev for rapid translation"
+    description: "Use Lingo.dev MCP tools to translate new strings immediately, then queue for human review"
+    config_example: |
+      // harness.config.json
+      {
+        "mcp": {
+          "servers": {
+            "lingo-dev": {
+              "command": "npx",
+              "args": ["-y", "@anthropic/lingo-dev-mcp"],
+              "env": {
+                "LINGO_API_KEY": "<your-api-key>"
+              }
+            }
+          }
+        }
+      }
+
+limitations:
+  - "AI translation quality varies by language pair; low-resource languages may have lower quality"
+  - "Brand voice enforcement requires initial setup and training on existing approved translations"
+  - "Translation memory benefits increase over time; initial runs have no prior context"

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

@@ -0,0 +1,60 @@
+name: "Lokalise"
+description: "Enterprise translation management system with team collaboration, branching, QA checks, and extensive integration ecosystem"
+mcp_server_id: "lokalise-mcp"
+source: "https://github.com/anthropics/lokalise-mcp"
+
+capabilities:
+  - name: "Key Management"
+    description: "Create, update, delete, and filter translation keys with tags and platform labels"
+    tools: ["create_key", "update_key", "delete_key", "list_keys", "bulk_update_keys"]
+  - name: "File Operations"
+    description: "Upload source files and download translated files in any format"
+    tools: ["upload_file", "download_files", "list_files"]
+  - name: "Task Management"
+    description: "Create and manage translation tasks for team members and external translators"
+    tools: ["create_task", "list_tasks", "complete_task"]
+  - name: "Branching"
+    description: "Create and merge translation branches aligned with code branches"
+    tools: ["create_branch", "merge_branch", "list_branches"]
+  - name: "QA Checks"
+    description: "Run automated quality assurance checks on translations (placeholders, length, glossary)"
+    tools: ["run_qa_checks", "get_qa_results"]
+
+when_to_use:
+  - scenario: "Larger team with multiple translators and complex review workflows"
+    reason: "Lokalise excels at team collaboration with task assignment, review stages, and comments"
+  - scenario: "Project with release branching that needs translation branching to match"
+    reason: "Lokalise's branching model maps to git branches, keeping translations in sync with code releases"
+  - scenario: "Enterprise requiring SOC 2 compliance and uptime SLA"
+    reason: "Lokalise offers enterprise security certifications and guaranteed uptime SLAs"
+
+when_not_to_use:
+  - scenario: "Small team or solo developer with simple translation needs"
+    reason: "Lokalise's enterprise features add complexity; simpler tools like Tolgee may be more appropriate"
+  - scenario: "Team wanting self-hosted translation infrastructure"
+    reason: "Lokalise is cloud-only; use Tolgee or Weblate for self-hosted requirements"
+
+integration_patterns:
+  - pattern: "Harness workflow with Lokalise for enterprise translation management"
+    description: "Use Lokalise MCP tools to sync translation keys with code changes, create tasks for translators, and download completed translations"
+    config_example: |
+      // harness.config.json
+      {
+        "mcp": {
+          "servers": {
+            "lokalise": {
+              "command": "npx",
+              "args": ["-y", "@anthropic/lokalise-mcp"],
+              "env": {
+                "LOKALISE_API_TOKEN": "<your-api-token>",
+                "LOKALISE_PROJECT_ID": "<your-project-id>"
+              }
+            }
+          }
+        }
+      }
+
+limitations:
+  - "Per-seat pricing can be expensive for large teams"
+  - "API rate limits may affect large batch operations via MCP"
+  - "Branch merging requires manual conflict resolution for overlapping translations"

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

@@ -0,0 +1,60 @@
+name: "Tolgee"
+description: "Open-source translation management system with in-context editing, AI translation, and comprehensive MCP server exposing 59 tools"
+mcp_server_id: "tolgee-mcp"
+source: "https://github.com/tolgee/tolgee-mcp"
+
+capabilities:
+  - name: "Project Management"
+    description: "Create, list, and manage translation projects"
+    tools: ["create_project", "list_projects", "get_project"]
+  - name: "Key Management"
+    description: "Create, update, delete, and search translation keys with namespace support"
+    tools: ["create_key", "update_key", "delete_key", "search_keys", "import_keys"]
+  - name: "Translation Operations"
+    description: "Get, set, and batch-update translations per locale"
+    tools: ["get_translations", "set_translation", "batch_set_translations"]
+  - name: "Screenshot Management"
+    description: "Upload and manage screenshots linked to translation keys for translator context"
+    tools: ["upload_screenshot", "get_screenshots", "delete_screenshot"]
+  - name: "Import/Export"
+    description: "Import and export translation files in various formats (JSON, XLIFF, PO, etc.)"
+    tools: ["import_file", "export_translations"]
+
+when_to_use:
+  - scenario: "Team wants a self-hosted TMS with developer-friendly workflow"
+    reason: "Tolgee can be self-hosted (Docker) and provides in-context editing for developers to see translations in the actual UI"
+  - scenario: "Project needs AI-assisted translation with human review"
+    reason: "Tolgee integrates AI translation providers while maintaining a human review workflow"
+  - scenario: "Small to medium team without budget for enterprise TMS"
+    reason: "Open-source core with generous free tier; self-hosting eliminates per-seat costs"
+
+when_not_to_use:
+  - scenario: "Enterprise requiring SOC 2 compliance and SLA guarantees"
+    reason: "Self-hosted requires managing your own infrastructure and compliance; Tolgee Cloud has fewer enterprise certifications than Lokalise"
+  - scenario: "Project with complex branching/versioning workflows"
+    reason: "Tolgee's branching support is less mature than Lokalise or Crowdin for complex release management"
+
+integration_patterns:
+  - pattern: "Harness workflow with Tolgee MCP for key management"
+    description: "Use Tolgee MCP tools during the i18n audit phase to check translation coverage and create missing keys"
+    config_example: |
+      // harness.config.json
+      {
+        "mcp": {
+          "servers": {
+            "tolgee": {
+              "command": "npx",
+              "args": ["-y", "@anthropic/tolgee-mcp"],
+              "env": {
+                "TOLGEE_API_URL": "https://app.tolgee.io",
+                "TOLGEE_API_KEY": "<your-api-key>"
+              }
+            }
+          }
+        }
+      }
+
+limitations:
+  - "59 MCP tools may cause token overhead in LLM context; consider filtering to used capabilities"
+  - "Self-hosted instance requires Docker and PostgreSQL infrastructure"
+  - "In-context editing SDK adds bundle size to the frontend application"

package/dist/agents/skills/shared/i18n-knowledge/testing/locale-testing.yaml

@@ -0,0 +1,107 @@
+description: "Locale testing techniques — systematic approaches to verify i18n correctness across real locales"
+
+techniques:
+  - name: "Functional testing per locale"
+    description: "Run functional test suites with different locale configurations to verify locale-dependent behavior"
+    catches:
+      - "Form submission failures with locale-formatted input (commas vs periods in numbers)"
+      - "Date picker displaying wrong format or first day of week"
+      - "Number input rejecting valid locale-formatted values"
+      - "Sort order bugs with locale-specific collation"
+    implementation:
+      approach: "Parameterize functional tests with locale fixtures; run core user flows per locale"
+      tools: ["Playwright with locale option", "Cypress with cy.clock locale", "Jest with Intl mocks"]
+      example: |
+        // Playwright locale-parameterized test
+        for (const locale of ['en-US', 'de-DE', 'ja-JP', 'ar-SA']) {
+          test(`checkout flow works in ${locale}`, async ({ browser }) => {
+            const context = await browser.newContext({ locale });
+            const page = await context.newPage();
+            // ... test checkout flow
+          });
+        }
+    when_to_use: "In CI pipeline for every PR that touches i18n-sensitive code"
+    automation: "Run locale matrix in CI: en-US (baseline), de-DE (expansion), ja-JP (CJK), ar-SA (RTL)"
+
+  - name: "Visual regression testing across locales"
+    description: "Capture screenshots per locale and compare against baselines to detect text overflow and layout shifts"
+    catches:
+      - "Text overflow from translation expansion"
+      - "RTL layout mirroring regressions"
+      - "Font rendering differences across locales"
+      - "Container height changes from multi-line wrapping"
+    implementation:
+      approach: "Run visual regression tool with locale-specific baselines; flag visual differences above threshold"
+      tools: ["Playwright screenshot comparison", "Percy", "Chromatic", "BackstopJS"]
+      example: |
+        // Capture screenshots for visual comparison
+        for (const locale of ['en', 'de', 'ar', 'ja']) {
+          await page.goto(`/?locale=${locale}`);
+          await expect(page).toHaveScreenshot(`homepage-${locale}.png`);
+        }
+    when_to_use: "In CI for PRs that touch layout, typography, or translation files"
+    automation: "Maintain per-locale visual baselines; auto-update baselines when translations change"
+
+  - name: "Boundary locale testing"
+    description: "Test with the most extreme locales to find edge cases: longest translations, most plural forms, RTL"
+    catches:
+      - "Worst-case text expansion overflow (German/Finnish)"
+      - "Complex pluralization bugs (Arabic with 6 forms)"
+      - "Bidi rendering issues (Arabic RTL)"
+      - "CJK-specific line breaking and width issues (Japanese)"
+    implementation:
+      approach: "Select boundary locales that represent extremes: de (long), fi (longest), ar (RTL + 6 plurals), ja (CJK)"
+      tools: ["Any test framework with locale configuration"]
+      example: |
+        // Boundary locale set for maximum coverage
+        const BOUNDARY_LOCALES = {
+          'de': 'Longest Western European text expansion',
+          'fi': 'Extreme expansion with agglutinative grammar',
+          'ar': 'RTL + 6 plural forms + letter reshaping',
+          'ja': 'CJK no-space + multiple scripts + contraction',
+          'th': 'Dictionary-based line breaking + stacking diacritics',
+        };
+    when_to_use: "For every release; as smoke test in CI for i18n-related changes"
+    automation: "Run boundary locale tests as a required CI check; block release if any boundary locale fails"
+
+  - name: "Input method testing"
+    description: "Test text input with locale-specific input methods (CJK IME, Arabic keyboard, Devanagari input)"
+    catches:
+      - "IME composition events not handled (text appears garbled during CJK input)"
+      - "Keyboard layout assumptions (QWERTY vs AZERTY vs others)"
+      - "Input field not accepting non-Latin characters"
+      - "Search and filter not working with IME-composed text"
+    implementation:
+      approach: "Use Playwright's keyboard IME simulation or manual testing with actual input methods"
+      tools: ["Playwright keyboard API", "BrowserStack with device keyboards", "manual testing with OS IME"]
+      example: |
+        // Test CJK IME input in Playwright
+        await page.locator('input[name="search"]').click();
+        await page.keyboard.imeSetComposition('にほん', 3, 3);
+        await page.keyboard.imeCommit();
+        // Verify search results include Japanese text
+    when_to_use: "Before releasing to CJK, Arabic, or Devanagari markets; for search and text input features"
+    automation: "Include IME input tests in smoke test suite for markets with non-Latin input methods"
+
+  - name: "Locale switching testing"
+    description: "Test runtime locale change without page reload to verify all components update correctly"
+    catches:
+      - "Components that cache translated text and do not re-render on locale change"
+      - "Date/number formatters that initialize once and do not update"
+      - "Stale translations in error messages or toast notifications"
+      - "Layout direction not updating when switching between LTR and RTL locales"
+    implementation:
+      approach: "Switch locale at runtime and verify all visible text, formatting, and layout update"
+      tools: ["Framework-specific locale switching API", "Playwright for E2E verification"]
+      example: |
+        // Test locale switching
+        await page.click('[data-testid="language-selector"]');
+        await page.click('[data-value="ar"]');
+        // Verify RTL layout applied
+        const dir = await page.getAttribute('html', 'dir');
+        expect(dir).toBe('rtl');
+        // Verify translated content
+        const heading = await page.textContent('h1');
+        expect(heading).toMatch(/[\u0600-\u06FF]/); // Arabic characters
+    when_to_use: "When the app supports runtime locale switching; after changes to locale provider or context"
+    automation: "Include locale switching in E2E test suite; test switching from LTR to RTL and back"

package/dist/agents/skills/shared/i18n-knowledge/testing/pseudo-localization.yaml

@@ -0,0 +1,86 @@
+description: "Pseudo-localization testing techniques — automated methods to detect i18n issues without real translations"
+
+techniques:
+  - name: "Accent character replacement"
+    description: "Replace ASCII characters with accented Unicode equivalents (a to a, e to e, etc.) to simulate translated text"
+    catches:
+      - "Hardcoded strings missed by extraction tools (they remain in plain ASCII)"
+      - "Character encoding issues (accented characters display as mojibake)"
+      - "Font coverage gaps (missing glyphs for accented characters)"
+      - "String comparison bugs (accented versions fail equality checks)"
+    implementation:
+      approach: "Transform each ASCII letter to its accented equivalent using a lookup table"
+      tools: ["pseudo-localization (npm)", "@formatjs/cli --pseudo-locale xx-AC"]
+      example: |
+        // Input: "Hello, World!"
+        // Output: "[Ĥéĺĺö, Ŵöŕĺð!]"
+        import { pseudoLocalize } from 'pseudo-localization';
+        const pseudo = pseudoLocalize('Hello, World!');
+    when_to_use: "During development, before real translations are available"
+    automation: "Generate pseudo-locale as part of the build pipeline; run visual regression tests against it"
+
+  - name: "Text expansion padding"
+    description: "Add extra characters to simulate the text expansion that occurs in verbose languages (German, Finnish)"
+    catches:
+      - "Fixed-width layout overflow"
+      - "Text truncation in buttons, labels, and navigation"
+      - "Container height overflow from multi-line wrapping"
+      - "Tooltip and popup sizing issues"
+    implementation:
+      approach: "Pad translated strings with repeated characters to simulate 35-40% expansion"
+      tools: ["pseudo-localization (npm)", "custom expansion generator"]
+      example: |
+        // Input: "Settings" (8 chars)
+        // Output with 35% expansion: "Settingsxxx" (11 chars)
+        // Realistic: "[Séţţîñĝšxxxxx]" (accent + expansion)
+    when_to_use: "Before UI review; especially before locking down layout dimensions"
+    automation: "Include expansion pseudo-locale in visual regression test suite"
+
+  - name: "Bracket wrapping"
+    description: "Wrap each translated string with brackets [like this] to reveal concatenation boundaries"
+    catches:
+      - "String concatenation (brackets break across concatenation: '[Hello, ][World!]' instead of '[Hello, World!]')"
+      - "Strings assembled from multiple translation calls"
+      - "Missing translations (bracketed strings are visually distinct)"
+    implementation:
+      approach: "Prepend '[' and append ']' to every translated string"
+      tools: ["pseudo-localization (npm)", "custom i18next post-processor"]
+      example: |
+        // Correct: "[Hello, World!]"
+        // Concatenation bug: "[Hello, ]" + "[World!]"
+        // The broken brackets reveal the concatenation point
+    when_to_use: "During string extraction audit; verifying all strings go through translation pipeline"
+    automation: "Enable bracket wrapping in development/staging environments as a QA overlay"
+
+  - name: "Mirror/bidi simulation"
+    description: "Reverse text direction to simulate RTL layout without needing a real RTL locale"
+    catches:
+      - "Layout mirroring issues (margins, padding, flex direction)"
+      - "Icon placement that should or should not mirror"
+      - "CSS left/right vs logical properties usage"
+      - "Mixed-direction text rendering problems"
+    implementation:
+      approach: "Apply dir='rtl' to the document and reverse string characters for visual simulation"
+      tools: ["@formatjs/cli --pseudo-locale xx-HA", "Android ar-XB pseudolocale"]
+      example: |
+        // Input: "Hello, World!"
+        // Output: "!dlroW ,olleH" (reversed for visual RTL simulation)
+        // Combined with accent: "[!ðĺŕöŴ ,öĺĺéĤ]"
+    when_to_use: "Before adding RTL locale support; during RTL layout review"
+    automation: "Include bidi pseudo-locale in visual regression tests alongside standard pseudo-locale"
+
+  - name: "Placeholder preservation verification"
+    description: "Verify that interpolation placeholders ({variable}, {{variable}}, %s) survive pseudo-localization intact"
+    catches:
+      - "Broken interpolation from accent-replacing characters inside placeholders"
+      - "Format string corruption from text transformation"
+      - "Missing placeholder values at runtime"
+    implementation:
+      approach: "Pseudo-localize text while preserving content inside interpolation markers"
+      tools: ["pseudo-localization (npm) with placeholder regex", "custom preserving transformer"]
+      example: |
+        // Input: "Hello, {name}! You have {count} items."
+        // Correct: "[Ĥéĺĺö, {name}! Ýöû ĥàvé {count} îţéḿš.]"
+        // Wrong: "[Ĥéĺĺö, {ñàḿé}! Ýöû ĥàvé {çöûñţ} îţéḿš.]"
+    when_to_use: "When configuring pseudo-localization pipeline; validating custom pseudo generators"
+    automation: "Add unit test that pseudo-localizes all messages and verifies placeholders are preserved"