@harness-engineering/cli 1.7.0 → 1.8.0

package/dist/agents/skills/shared/i18n-knowledge/anti-patterns/string-handling.yaml

@@ -0,0 +1,106 @@
+description: "String handling anti-patterns — common mistakes in text manipulation, concatenation, and string operations that break in localized contexts"
+
+patterns:
+  - name: "String concatenation for sentences"
+    severity: error
+    scope: all
+    detect:
+      method: "Check for string concatenation of user-facing text segments"
+      context: "Expressions like 'Hello, ' + name + '!' or `Welcome to ${place}`"
+    reason: "Word order varies by locale. 'Hello, {name}!' in English becomes '{name}さん、こんにちは！' in Japanese — the name comes first."
+    instead: "Use ICU MessageFormat or framework translation function with named placeholders: t('greeting', { name })"
+    strictness:
+      permissive: info
+      standard: warn
+      strict: error
+
+  - name: "Hardcoded user-facing strings"
+    severity: error
+    scope: all
+    detect:
+      method: "Check for string literals in JSX, templates, or UI rendering code"
+      context: "Text nodes in JSX, template literals in HTML attributes, string args to UI components"
+    reason: "Untranslated strings are invisible to the localization pipeline. They remain in the source language for all users."
+    instead: "Wrap all user-facing strings in the framework's translation function (t(), $t(), FormattedMessage, etc.)"
+    strictness:
+      permissive: info
+      standard: warn
+      strict: error
+
+  - name: "Substring or split on translated strings"
+    severity: warning
+    scope: all
+    detect:
+      method: "Check for .substring(), .split(), .slice() applied to translated text"
+      context: "Operations that assume word boundaries or character positions in translated strings"
+    reason: "Word boundaries differ by locale. CJK has no spaces. Thai has no word breaks. Splitting on space fails."
+    instead: "Use Intl.Segmenter for locale-aware text segmentation; redesign to avoid splitting translated text"
+    strictness:
+      permissive: info
+      standard: warn
+      strict: warn
+
+  - name: "Hardcoded plural logic"
+    severity: error
+    scope: all
+    detect:
+      method: "Check for ternary or if/else choosing singular vs plural form"
+      context: "count === 1 ? 'item' : 'items' or similar binary plural selection"
+    reason: "Arabic has 6 plural forms. Polish has 4. Welsh has 6. Binary singular/plural only works for a few languages."
+    instead: "Use CLDR plural rules via ICU MessageFormat: {count, plural, one {# item} other {# items}}"
+    strictness:
+      permissive: warn
+      standard: error
+      strict: error
+
+  - name: "String templates with positional assumptions"
+    severity: warning
+    scope: all
+    detect:
+      method: "Check for template literals or format strings that assume a fixed order of interpolated values"
+      context: "Patterns like `${greeting} ${name}` or String.format('%s %s', greeting, name)"
+    reason: "Interpolation order may need to change per locale. Japanese may need name before greeting."
+    instead: "Use named placeholders ({greeting} {name}) so translators can reorder: '{name}さん、{greeting}'"
+    strictness:
+      permissive: info
+      standard: warn
+      strict: warn
+
+  - name: "UI text in code comments used as display strings"
+    severity: warning
+    scope: all
+    detect:
+      method: "Check for display text stored in constants or enums without translation function wrapping"
+      context: "const LABEL = 'Submit' or enum Status { Active = 'Active' } used directly in UI"
+    reason: "Constants and enum values are not extracted by localization tools. They bypass the translation pipeline."
+    instead: "Map enum values to translation keys: const LABELS = { active: t('status.active') }"
+    strictness:
+      permissive: info
+      standard: warn
+      strict: warn
+
+  - name: "String length validation on translated input"
+    severity: warning
+    scope: all
+    detect:
+      method: "Check for maxLength validation on text that will be translated or on user input from localized forms"
+      context: "Input validation like value.length <= 50 applied to fields that accept multilingual input"
+    reason: "A 50-character limit may be too short for German translations (30-35% expansion) or too long for CJK (visual width differs)."
+    instead: "Use visual width constraints (CSS max-width) instead of character count; adjust limits per locale if needed"
+    strictness:
+      permissive: info
+      standard: warn
+      strict: warn
+
+  - name: "Case transformation without locale"
+    severity: error
+    scope: all
+    detect:
+      method: "Check for .toUpperCase() and .toLowerCase() without locale argument"
+      context: "String case operations that do not use toLocaleUpperCase() or toLocaleLowerCase()"
+    reason: "Turkish dotted-i bug: 'istanbul'.toUpperCase() produces 'ISTANBUL' (wrong) instead of 'ISTANBUL'. German eszett: 'strasse'.toUpperCase() should consider locale."
+    instead: "Always use toLocaleUpperCase(locale) and toLocaleLowerCase(locale) for user-facing text"
+    strictness:
+      permissive: info
+      standard: warn
+      strict: error

package/dist/agents/skills/shared/i18n-knowledge/frameworks/android-resources.yaml

@@ -0,0 +1,47 @@
+name: "Android Resources"
+description: "Android platform localization using XML string resources and the Android resource system"
+platforms: ["mobile"]
+message_format: "custom"
+
+detection:
+  package_json_keys:
+    dependencies: []
+    devDependencies: []
+  file_patterns: ["**/res/values*/strings.xml", "**/*.kt", "**/*.java"]
+  config_files: ["build.gradle", "build.gradle.kts", "AndroidManifest.xml"]
+
+conventions:
+  key_format: "snake_case"
+  file_format: "xml"
+  file_structure: "res/values-{locale}/strings.xml"
+  plural_syntax: "<plurals name='items'><item quantity='one'>%d item</item><item quantity='other'>%d items</item></plurals>"
+  interpolation_syntax: "%s (positional: %1$s, %2$s)"
+
+recommended_tooling:
+  extraction: ["Android Studio translation editor", "Lint checks"]
+  linting: ["Android Lint (MissingTranslation, HardcodedText)"]
+  pseudo_locale: ["Android built-in pseudolocales: en-XA (accented), ar-XB (bidi)"]
+
+anti_patterns:
+  - pattern: "String concatenation instead of getString() with format args"
+    severity: error
+    instead: "Use getString(R.string.greeting, userName) with %1$s placeholders in strings.xml"
+  - pattern: "Hardcoded strings in layout XML"
+    severity: error
+    instead: "Use @string/key references in all android:text and android:hint attributes; Android Lint flags these"
+  - pattern: "Missing quantity entries in <plurals>"
+    severity: error
+    instead: "Include all CLDR quantities for target locales (zero, one, two, few, many, other as applicable)"
+  - pattern: "Using string-array for translatable content without context"
+    severity: warning
+    instead: "Add translatorNote attributes or XML comments for string arrays to provide context for translators"
+  - pattern: "Not using Android pseudolocales for testing"
+    severity: warning
+    instead: "Enable en-XA (accented English) and ar-XB (bidi) pseudolocales in developer settings for testing"
+
+migration_notes:
+  from:
+    - framework: "legacy Java ResourceBundle"
+      guidance: "Move .properties files to Android XML resources; convert MessageFormat patterns to Android format strings; update getString() calls"
+    - framework: "custom key-value solution"
+      guidance: "Map keys to Android resource naming conventions (snake_case); create strings.xml per locale in res/values-{locale}/ directories"

package/dist/agents/skills/shared/i18n-knowledge/frameworks/apple-strings.yaml

@@ -0,0 +1,47 @@
+name: "Apple Strings"
+description: "Apple platform localization using .strings, .stringsdict, and .xcstrings (String Catalogs) files"
+platforms: ["mobile"]
+message_format: "custom"
+
+detection:
+  package_json_keys:
+    dependencies: []
+    devDependencies: []
+  file_patterns: ["**/*.strings", "**/*.stringsdict", "**/*.xcstrings", "**/*.lproj/**"]
+  config_files: ["*.xcodeproj/project.pbxproj", "*.xcworkspace"]
+
+conventions:
+  key_format: "dot-notation"
+  file_format: "strings"
+  file_structure: "{locale}.lproj/Localizable.strings"
+  plural_syntax: ".stringsdict plist format with NSStringLocalizedFormatKey"
+  interpolation_syntax: "%@ (positional: %1$@, %2$@)"
+
+recommended_tooling:
+  extraction: ["genstrings", "Xcode String Catalog auto-extraction"]
+  linting: ["SwiftLint custom rules", "Xcode build warnings"]
+  pseudo_locale: ["xcstrings pseudo-locale generation"]
+
+anti_patterns:
+  - pattern: "Missing .stringsdict for plurals"
+    severity: error
+    instead: "Create .stringsdict files for all pluralized strings; NSLocalizedString alone cannot handle plural forms"
+  - pattern: "Concatenating localized strings"
+    severity: error
+    instead: "Use String(format:) with positional specifiers: String(format: NSLocalizedString('greeting_%@_%@'), firstName, lastName)"
+  - pattern: "Not using String Catalogs (Xcode 15+)"
+    severity: info
+    instead: "Migrate from .strings/.stringsdict to .xcstrings (String Catalogs) for unified translation management"
+  - pattern: "Hardcoded strings in storyboards/XIBs without localization"
+    severity: warning
+    instead: "Use Base Internationalization with .strings files for Interface Builder, or switch to programmatic UI with NSLocalizedString"
+  - pattern: "Not testing with pseudolanguage locale on device"
+    severity: warning
+    instead: "Enable Double-Length Pseudolanguage in Xcode scheme settings to test text expansion"
+
+migration_notes:
+  from:
+    - framework: "legacy .strings"
+      guidance: "Open .strings files in Xcode 15+ and migrate to String Catalogs (.xcstrings); Xcode provides automatic migration; review pluralization rules post-migration"
+    - framework: "third-party (Lokalise SDK, Crowdin SDK)"
+      guidance: "Replace OTA SDK with build-time .xcstrings integration; use export/import workflows instead of runtime translation fetching"

package/dist/agents/skills/shared/i18n-knowledge/frameworks/backend-patterns.yaml

@@ -0,0 +1,50 @@
+name: "Backend Patterns"
+description: "Cross-platform backend i18n patterns for Node.js, Python, Go, and Java server-side localization"
+platforms: ["backend"]
+message_format: "varies"
+
+detection:
+  package_json_keys:
+    dependencies: ["i18next", "i18n-node", "messageformat", "globalize"]
+    devDependencies: []
+  file_patterns: ["**/*.py", "**/*.go", "**/*.java", "**/*.ts", "**/*.js", "**/locales/**", "**/translations/**"]
+  config_files: ["babel.cfg", "locale.go", "messages.properties", "i18n.config.*"]
+
+conventions:
+  key_format: "dot-notation"
+  file_format: "json"
+  file_structure: "locales/{locale}/{namespace}.json"
+  plural_syntax: "Varies by runtime: ICU (Node/Java), gettext (Python), go-i18n (Go)"
+  interpolation_syntax: "Varies: {variable} (ICU), %(variable)s (Python gettext), {{.Variable}} (Go)"
+
+recommended_tooling:
+  extraction: ["i18next-parser (Node)", "pybabel extract (Python)", "go-i18n extract (Go)", "ResourceBundle (Java)"]
+  linting: ["custom CI checks for missing translations"]
+  pseudo_locale: ["pseudo-localization npm package (Node)", "custom generators per platform"]
+
+anti_patterns:
+  - pattern: "Hardcoded error messages in API responses"
+    severity: error
+    instead: "Return error codes with locale-neutral keys; resolve to localized messages on the client or in a localization middleware"
+  - pattern: "Locale detection only from Accept-Language header"
+    severity: warning
+    instead: "Support explicit locale preference (user settings), URL path/query, cookie, then Accept-Language as fallback chain"
+  - pattern: "Storing translated content in code"
+    severity: warning
+    instead: "Externalize translations to resource files (JSON, PO, properties); load at runtime per locale"
+  - pattern: "Email templates with hardcoded language"
+    severity: error
+    instead: "Use locale-aware email template engines; store templates per locale; resolve from user's language preference"
+  - pattern: "Logging in the user's locale instead of a fixed locale"
+    severity: warning
+    instead: "Always log in English (or a fixed locale) for consistent log analysis; localize only user-facing output"
+  - pattern: "Date/time in API responses without timezone"
+    severity: error
+    instead: "Always return ISO 8601 with timezone (UTC preferred) in API responses; let clients format for display locale"
+
+migration_notes:
+  from:
+    - framework: "hardcoded strings"
+      guidance: "Extract all user-facing strings to resource files; implement a translation function (t/gettext); add locale resolution middleware"
+    - framework: "gettext to i18next"
+      guidance: "Convert PO/MO files to JSON format; map gettext plurals to i18next suffix convention; update translation function calls"

package/dist/agents/skills/shared/i18n-knowledge/frameworks/flutter-intl.yaml

@@ -0,0 +1,47 @@
+name: "Flutter Intl"
+description: "Dart/Flutter internationalization using the intl package and ARB (Application Resource Bundle) files"
+platforms: ["mobile"]
+message_format: "icu"
+
+detection:
+  package_json_keys:
+    dependencies: ["flutter_localizations", "intl"]
+    devDependencies: ["intl_utils", "flutter_gen"]
+  file_patterns: ["lib/**/*.dart", "lib/l10n/**/*.arb"]
+  config_files: ["l10n.yaml", "pubspec.yaml"]
+
+conventions:
+  key_format: "camelCase"
+  file_format: "arb"
+  file_structure: "lib/l10n/app_{locale}.arb"
+  plural_syntax: "ICU {count, plural, one {# item} other {# items}}"
+  interpolation_syntax: "{variable}"
+
+recommended_tooling:
+  extraction: ["flutter gen-l10n", "intl_utils"]
+  linting: ["dart analyze"]
+  pseudo_locale: ["custom ARB generator"]
+
+anti_patterns:
+  - pattern: "Hardcoded strings in Text() widgets"
+    severity: error
+    instead: "Use AppLocalizations.of(context)!.messageKey for all user-facing strings"
+  - pattern: "Not running flutter gen-l10n after adding new messages"
+    severity: warning
+    instead: "Run flutter gen-l10n to regenerate the AppLocalizations class after modifying ARB files"
+  - pattern: "Using string interpolation for plurals"
+    severity: error
+    instead: "Use ICU plural syntax in ARB files: {count, plural, one {# item} other {# items}}"
+  - pattern: "Missing @metadata descriptions in ARB files"
+    severity: info
+    instead: "Add @messageKey descriptions for translator context: '@greeting': {'description': 'Welcome message on home screen'}"
+  - pattern: "Not testing with different locale settings on device"
+    severity: warning
+    instead: "Use Flutter integration tests with different locale configurations; test RTL with Arabic locale"
+
+migration_notes:
+  from:
+    - framework: "easy_localization"
+      guidance: "Convert JSON translation files to ARB format; replace tr() calls with AppLocalizations.of(context); update locale loading configuration in MaterialApp"
+    - framework: "get (GetX i18n)"
+      guidance: "Move from Map-based translations to ARB files; replace 'key'.tr with AppLocalizations; configure locale resolution in MaterialApp.localizationsDelegates"

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

@@ -0,0 +1,47 @@
+name: "i18next"
+description: "Full-featured i18n framework with plugins for React, Vue, Node, and many other platforms"
+platforms: ["web", "mobile", "backend"]
+message_format: "i18next"
+
+detection:
+  package_json_keys:
+    dependencies: ["i18next", "react-i18next", "next-i18next", "i18next-http-backend", "i18next-browser-languagedetector"]
+    devDependencies: ["i18next-parser", "i18next-scanner"]
+  file_patterns: ["src/**/*.{ts,tsx,js,jsx}", "public/locales/**/*.json"]
+  config_files: ["i18next.config.js", "i18next.config.ts", "next-i18next.config.js"]
+
+conventions:
+  key_format: "nested"
+  file_format: "json"
+  file_structure: "public/locales/{locale}/{namespace}.json"
+  plural_syntax: "key_one: '# item', key_other: '# items' (suffix-based)"
+  interpolation_syntax: "{{variable}}"
+
+recommended_tooling:
+  extraction: ["i18next-parser", "i18next-scanner"]
+  linting: ["eslint-plugin-i18next"]
+  pseudo_locale: ["i18next-pseudo"]
+
+anti_patterns:
+  - pattern: "Not using the count option for pluralization"
+    severity: error
+    instead: "Pass { count: n } to t() function: t('items', { count: itemCount }) — i18next auto-selects the plural form"
+  - pattern: "Nesting translations with $t() inside translations"
+    severity: warning
+    instead: "Use flat interpolation or context-based keys instead of nested $t() references which are hard to extract"
+  - pattern: "Loading all namespaces upfront"
+    severity: warning
+    instead: "Use lazy loading with i18next-http-backend to load namespaces on demand for better performance"
+  - pattern: "Hardcoding the fallback language in multiple places"
+    severity: warning
+    instead: "Configure fallbackLng once in i18next.init(); use namespace-level fallbacks for granular control"
+  - pattern: "Using the t() function outside React components without proper initialization"
+    severity: error
+    instead: "Use i18next.t() directly for non-React code, or pass the t function from initialized context"
+
+migration_notes:
+  from:
+    - framework: "react-intl"
+      guidance: "Convert ICU {variable} to {{variable}}; convert ICU plural syntax to suffix-based keys (_one, _other); replace FormattedMessage with useTranslation() hook"
+    - framework: "custom-solution"
+      guidance: "Map existing key-value pairs to i18next namespace structure; configure fallback chains; add language detection plugin"

package/dist/agents/skills/shared/i18n-knowledge/frameworks/react-intl.yaml

@@ -0,0 +1,47 @@
+name: "React Intl (FormatJS)"
+description: "ICU MessageFormat-based i18n library for React, part of the FormatJS ecosystem"
+platforms: ["web"]
+message_format: "icu"
+
+detection:
+  package_json_keys:
+    dependencies: ["react-intl", "@formatjs/intl", "@formatjs/intl-messageformat"]
+    devDependencies: ["@formatjs/cli", "eslint-plugin-formatjs", "@formatjs/ts-transformer"]
+  file_patterns: ["src/**/*.{ts,tsx,js,jsx}"]
+  config_files: [".formatjsrc", ".formatjsrc.json"]
+
+conventions:
+  key_format: "dot-notation"
+  file_format: "json"
+  file_structure: "lang/{locale}.json"
+  plural_syntax: "ICU {count, plural, one {# item} other {# items}}"
+  interpolation_syntax: "{variable}"
+
+recommended_tooling:
+  extraction: ["@formatjs/cli extract"]
+  linting: ["eslint-plugin-formatjs"]
+  pseudo_locale: ["@formatjs/cli compile --pseudo-locale"]
+
+anti_patterns:
+  - pattern: "String concatenation inside FormattedMessage"
+    severity: error
+    instead: "Use ICU MessageFormat with placeholders: <FormattedMessage id='greeting' values={{name}} />"
+  - pattern: "Using defaultMessage as the translation key"
+    severity: warning
+    instead: "Use explicit message IDs (dot-notation) for stable keys; defaultMessage is a fallback, not an ID"
+  - pattern: "Inline messages without extraction"
+    severity: warning
+    instead: "Run @formatjs/cli extract to generate message catalogs; do not manually maintain translation files"
+  - pattern: "Using dangerouslySetInnerHTML with translated strings"
+    severity: error
+    instead: "Use FormattedMessage rich text support: <FormattedMessage values={{b: chunks => <b>{chunks}</b>}} />"
+  - pattern: "Not wrapping date/number formatting with FormatJS APIs"
+    severity: warning
+    instead: "Use intl.formatDate(), intl.formatNumber(), and intl.formatRelativeTime() for locale-aware formatting"
+
+migration_notes:
+  from:
+    - framework: "i18next"
+      guidance: "Convert {{variable}} interpolation to {variable}; convert i18next plural suffixes (_one, _other) to ICU plural syntax; update extraction pipeline from i18next-parser to @formatjs/cli"
+    - framework: "vue-i18n"
+      guidance: "Convert $t() calls to useIntl().formatMessage(); convert named interpolation to ICU syntax; move from SFC i18n blocks to centralized message files"

package/dist/agents/skills/shared/i18n-knowledge/frameworks/vue-i18n.yaml

@@ -0,0 +1,47 @@
+name: "Vue I18n"
+description: "Internationalization plugin for Vue.js with SFC support and composition API integration"
+platforms: ["web"]
+message_format: "icu"
+
+detection:
+  package_json_keys:
+    dependencies: ["vue-i18n", "@intlify/vue-i18n-extensions", "@intlify/unplugin-vue-i18n"]
+    devDependencies: ["@intlify/vite-plugin-vue-i18n", "@intlify/eslint-plugin-vue-i18n"]
+  file_patterns: ["src/**/*.vue", "src/locales/**/*.{json,yaml}"]
+  config_files: ["vue-i18n.config.ts", "i18n.ts"]
+
+conventions:
+  key_format: "dot-notation"
+  file_format: "json"
+  file_structure: "src/locales/{locale}.json"
+  plural_syntax: "ICU {count, plural, one {# item} other {# items}} or pipe syntax: item | items"
+  interpolation_syntax: "{variable} or @:key for linked messages"
+
+recommended_tooling:
+  extraction: ["@intlify/cli"]
+  linting: ["@intlify/eslint-plugin-vue-i18n"]
+  pseudo_locale: ["custom generator with vue-i18n message compiler"]
+
+anti_patterns:
+  - pattern: "Using v-html with translated strings"
+    severity: error
+    instead: "Use the <i18n-t> component with named slots for HTML in translations — v-html creates XSS risk"
+  - pattern: "Hardcoding messages in template attributes"
+    severity: warning
+    instead: "Use $t() in attribute bindings: :placeholder=\"$t('search.placeholder')\" instead of hardcoded strings"
+  - pattern: "Not using SFC <i18n> blocks for component-local messages"
+    severity: info
+    instead: "Put component-specific messages in <i18n> blocks to co-locate translations with the component"
+  - pattern: "Ignoring SSR hydration mismatch with locale detection"
+    severity: error
+    instead: "Detect locale server-side (Accept-Language header) and pass to client to prevent hydration mismatch"
+  - pattern: "Using legacy API ($t) in Composition API components"
+    severity: warning
+    instead: "Use useI18n() composable in <script setup> components for type-safe translation access"
+
+migration_notes:
+  from:
+    - framework: "vue-i18n v8 (Vue 2)"
+      guidance: "Migrate from VueI18n class to createI18n(); update $t() to useI18n().t() in Composition API; convert <i18n> blocks to new format"
+    - framework: "i18next"
+      guidance: "Convert {{variable}} to {variable}; map namespaces to vue-i18n scoped messages; replace useTranslation() with useI18n()"

package/dist/agents/skills/shared/i18n-knowledge/industries/ecommerce.yaml

@@ -0,0 +1,66 @@
+name: "Ecommerce"
+description: "i18n challenges in ecommerce — address formats, measurement units, tax display, and payment localization across markets"
+
+requirements:
+  - area: "Address Format"
+    description: "Address field order and content varies dramatically by country — Japan puts postal code first, US puts it last"
+    severity: error
+    locales_affected: "all"
+    examples:
+      - bad: "Fixed form: Street, City, State, Zip, Country"
+        good: "Use Google's libaddressinput or similar to render country-specific address forms"
+  - area: "Measurement Units"
+    description: "Product dimensions, weight, and volume must display in locale-expected units"
+    severity: warning
+    locales_affected: "all"
+    examples:
+      - bad: "Showing all dimensions in inches regardless of locale"
+        good: "Display metric units (cm, kg, L) for most locales; imperial (in, lb, fl oz) for US/UK where expected"
+  - area: "Tax Display"
+    description: "VAT-inclusive (most of world) vs tax-exclusive (US) pricing causes confusion if not handled per locale"
+    severity: error
+    locales_affected: "all"
+    examples:
+      - bad: "Showing $99.99 without indicating whether tax is included"
+        good: "Show 'incl. VAT' for EU locales, separate tax line for US locales, GST-inclusive for AU/NZ"
+  - area: "Phone Number Formatting"
+    description: "Phone number input and display must support international formats"
+    severity: warning
+    locales_affected: "all"
+    examples:
+      - bad: "Validating phone with regex: /^\\d{10}$/"
+        good: "Use libphonenumber for validation and formatting; store in E.164 format (+1234567890)"
+  - area: "Sizing Charts"
+    description: "Clothing and shoe sizes vary by country — US 8 is EU 38 for women's shoes"
+    severity: warning
+    locales_affected: "all"
+    examples:
+      - bad: "Showing only US sizes for international customers"
+        good: "Display size conversion charts; show locale-primary sizing with equivalents"
+
+anti_patterns:
+  - pattern: "Hardcoding address field order"
+    reason: "Japan: postal-code, prefecture, city, street; Germany: street, postal-code city; varied worldwide"
+    instead: "Use a country-aware address component that adapts field order per shipping country"
+  - pattern: "Validating postal codes with a single regex"
+    reason: "Postal code formats range from 5 digits (US) to alphanumeric (UK: SW1A 1AA) to none (Ireland historically)"
+    instead: "Use country-specific postal code validation or a library like i18n-postal-code"
+  - pattern: "Displaying prices without currency context"
+    reason: "$99 is ambiguous — USD, CAD, AUD, and others use $; customer may see wrong currency"
+    instead: "Always show the currency code or unambiguous symbol; use Intl.NumberFormat with currency"
+  - pattern: "Shipping method names not localized"
+    reason: "'2-Day Shipping' is meaningless outside the origin country's postal system"
+    instead: "Show estimated delivery date instead of carrier-specific service names"
+
+regulations:
+  - name: "EU Consumer Rights Directive"
+    locales: ["EU member states"]
+    impact: "Prices must be displayed inclusive of VAT in the currency of the target market"
+  - name: "GDPR"
+    locales: ["EU member states"]
+    impact: "Privacy policy and consent language must be in the user's language and legally accurate per jurisdiction"
+  - name: "California Consumer Privacy Act (CCPA)"
+    locales: ["en-US"]
+    impact: "Privacy notices must be accessible; consider multilingual California population"
+
+reference_products: ["shopify.com", "amazon.com", "etsy.com", "zalando.com"]

package/dist/agents/skills/shared/i18n-knowledge/industries/fintech.yaml

@@ -0,0 +1,66 @@
+name: "Fintech"
+description: "i18n challenges in financial technology — currency precision, number formatting, and regulatory compliance across markets"
+
+requirements:
+  - area: "Currency Display"
+    description: "Currency formatting varies by locale — symbol position, decimal precision, and grouping separators differ"
+    severity: error
+    locales_affected: "all"
+    examples:
+      - bad: "'$' + amount.toFixed(2)"
+        good: "new Intl.NumberFormat(locale, { style: 'currency', currency: currencyCode }).format(amount)"
+  - area: "Currency Precision"
+    description: "Decimal places vary by currency — JPY has 0, USD/EUR have 2, BHD/KWD have 3"
+    severity: error
+    locales_affected: "all"
+    examples:
+      - bad: "amount.toFixed(2) for all currencies"
+        good: "Use Intl.NumberFormat with currency option which auto-selects correct decimal places"
+  - area: "Number Formatting"
+    description: "Thousands separators and decimal points vary — 1,234.56 (en) vs 1.234,56 (de) vs 1 234,56 (fr)"
+    severity: error
+    locales_affected: "all"
+    examples:
+      - bad: "amount.toString().replace(/\\B(?=(\\d{3})+(?!\\d))/g, ',')"
+        good: "new Intl.NumberFormat(locale).format(amount)"
+  - area: "Regulatory Date Formats"
+    description: "Financial regulations often mandate specific date formats — ambiguous dates (01/02/2025) cause compliance issues"
+    severity: error
+    locales_affected: "all"
+    examples:
+      - bad: "01/02/2025 (is this Jan 2 or Feb 1?)"
+        good: "Use unambiguous formats (2025-01-02) for regulatory documents; locale-specific for user display"
+  - area: "Financial Amount Display"
+    description: "Negative amounts, accounting notation, and color coding must follow locale conventions"
+    severity: warning
+    locales_affected: "all"
+    examples:
+      - bad: "Showing -$1,234.56 in all locales"
+        good: "Use Intl.NumberFormat with signDisplay and currencySign: 'accounting' for locale-correct negative display"
+
+anti_patterns:
+  - pattern: "Hardcoding currency symbol position"
+    reason: "Symbol placement varies: $100 (en-US), 100$ (fr-CA), 100 $ (fr-FR)"
+    instead: "Use Intl.NumberFormat with currency style which handles symbol placement per locale"
+  - pattern: "Converting currencies with hardcoded exchange rates"
+    reason: "Exchange rates change constantly; stale rates in code cause incorrect financial displays"
+    instead: "Fetch exchange rates from a reliable API; cache with appropriate TTL"
+  - pattern: "Using floating point for financial calculations"
+    reason: "IEEE 754 floating point causes rounding errors: 0.1 + 0.2 !== 0.3"
+    instead: "Use integer arithmetic in smallest currency unit (cents) or a decimal library"
+  - pattern: "Displaying amounts without locale-specific accounting format"
+    reason: "Negative amounts display differently: -$100 (US), ($100) (accounting), -100$ (other locales)"
+    instead: "Use Intl.NumberFormat with currencySign: 'accounting' for financial contexts"
+
+regulations:
+  - name: "PSD2 (Payment Services Directive 2)"
+    locales: ["EU member states"]
+    impact: "Transaction amounts must be displayed in the customer's local currency with correct formatting"
+  - name: "MiFID II"
+    locales: ["EU member states"]
+    impact: "Financial documents must show costs in the client's preferred currency with mandated precision"
+  - name: "RBI Guidelines"
+    locales: ["hi", "en-IN"]
+    impact: "Indian Rupee amounts must use Indian number grouping (lakhs/crores) in customer-facing displays"
+
+reference_products: ["wise.com", "stripe.com", "revolut.com", "mercury.com"]

package/dist/agents/skills/shared/i18n-knowledge/industries/gaming.yaml

@@ -0,0 +1,69 @@
+name: "Gaming"
+description: "i18n challenges in gaming — character limits in UI, cultural adaptation, rating systems, and in-game text rendering"
+
+requirements:
+  - area: "Character Limits in HUD/UI"
+    description: "Game HUDs and menus have fixed-width pixel budgets — translated text must fit without overflow"
+    severity: error
+    locales_affected: "all"
+    examples:
+      - bad: "Fixed 120px button with English text 'Attack' that becomes 'Angreifen' (German, does not fit)"
+        good: "Design UI with flexible text containers or set per-locale character limits with translator guidance"
+  - area: "Cultural Adaptation"
+    description: "Colors, gestures, symbols, and themes have different meanings across cultures"
+    severity: warning
+    locales_affected: "all"
+    examples:
+      - bad: "Using white for death/mourning themes globally (white = mourning in East Asia, black in Western cultures)"
+        good: "Audit cultural symbols and adapt color meanings, gestures, and imagery per target market"
+  - area: "Rating Systems"
+    description: "Age ratings differ by region — ESRB (US), PEGI (EU), CERO (JP), USK (DE) have different criteria"
+    severity: error
+    locales_affected: "all"
+    examples:
+      - bad: "Showing ESRB rating to European players"
+        good: "Display the correct regional rating system with proper locale-specific rating icons and descriptions"
+  - area: "In-Game Text Rendering"
+    description: "Bitmap fonts may not support all scripts; dynamic text needs proper shaping for CJK, Arabic, Devanagari"
+    severity: error
+    locales_affected: ["ja", "zh-Hans", "zh-Hant", "ko", "ar", "he", "hi", "th"]
+    examples:
+      - bad: "Using a bitmap font that only contains Latin glyphs for all locales"
+        good: "Use Unicode-capable font rendering or locale-specific bitmap fonts with full glyph coverage"
+  - area: "Voiceover and Subtitle Synchronization"
+    description: "Dubbed audio and subtitles must match game timing — translated dialogue may be longer or shorter"
+    severity: warning
+    locales_affected: "all"
+    examples:
+      - bad: "Subtitles that flash too quickly because translated text is longer than English source"
+        good: "Adjust subtitle display timing based on translated text length; allow subtitle speed settings"
+
+anti_patterns:
+  - pattern: "Hardcoding text in texture/sprite assets"
+    reason: "Text baked into images cannot be translated without re-creating the entire asset per locale"
+    instead: "Render text dynamically over images; use text layers separate from background art"
+  - pattern: "Concatenating strings for item descriptions"
+    reason: "'Legendary' + 'Sword' + 'of Fire' — word order changes by language, adjective placement varies"
+    instead: "Use complete translatable strings: '{quality} {weapon} {element}' with locale-aware ordering"
+  - pattern: "Assuming left-to-right menu navigation for all locales"
+    reason: "Arabic and Hebrew players expect RTL menu flow and mirrored UI layouts"
+    instead: "Mirror the full game UI for RTL locales including menus, HUD, and inventory screens"
+  - pattern: "Using player-facing dates without locale formatting"
+    reason: "Event dates like '12/1' are ambiguous — December 1 or January 12 depending on locale"
+    instead: "Use locale-aware date formatting or unambiguous formats with month names for in-game events"
+  - pattern: "Embedding culturally specific humor or idioms"
+    reason: "Jokes and idioms rarely translate directly — they fall flat or cause offense in other cultures"
+    instead: "Flag humor/idioms for cultural adaptation (not just translation) in localization notes"
+
+regulations:
+  - name: "ESRB (Entertainment Software Rating Board)"
+    locales: ["en-US", "en-CA"]
+    impact: "Content descriptors and rating labels must be in English; may require Spanish for US market"
+  - name: "PEGI (Pan European Game Information)"
+    locales: ["EU member states"]
+    impact: "Rating icons and content descriptors must follow PEGI standards; some content prohibited in certain countries"
+  - name: "CERO (Computer Entertainment Rating Organization)"
+    locales: ["ja"]
+    impact: "Japanese rating system with different thresholds; some content requires modification for Japan market"
+
+reference_products: ["store.steampowered.com", "playstation.com", "xbox.com", "nintendo.com"]