Loading...
Loading...
Found 197 Skills
Localization (i18n) across all CometChat UI Kit families — React, React Native, Angular, Android (V5/V6), iOS, Flutter (V5/V6). Covers CometChatLocalize.init signature differences (positional vs object), bundled languages, custom-language registration, RTL support, fallback to English, and cross-family drift risks. Cross-family — applies wherever the agent is configuring CometChat localization.
Implement internationalization (i18n) and localization including message extraction, translation catalogs, pluralization rules, date/time/number formatting, RTL language support, and i18n libraries like i18next and gettext. Use for multi-language, translation, or localization needs.
Manage In-App Purchases (IAPs) using the `asc` CLI tool. Use this skill when: (1) Listing IAPs: "asc iap list --app-id ID" (2) Creating IAPs: "asc iap create --type consumable|non-consumable|non-renewing-subscription" (3) IAP localizations: "asc iap-localizations create/list" (4) Submitting IAP: "asc iap submit --iap-id ID" (5) IAP pricing: "asc iap price-points list", "asc iap prices set" (6) IAP offer codes: "asc iap-offer-codes list/create/update" (7) IAP custom codes: "asc iap-offer-code-custom-codes list/create/update" (8) IAP one-time codes: "asc iap-offer-code-one-time-codes list/create/update" (9) User says "create in-app purchase", "list IAPs", "submit IAP", "IAP offer code", "custom code", "one-time codes"
Manage App Store app info and per-locale metadata using the `asc` CLI tool. Use this skill when: (1) Listing app info records: "asc app-infos list --app-id ID" (2) Updating app categories: "asc app-infos update --app-info-id ID --primary-category 6014" (3) Browsing categories: "asc app-categories list --platform IOS" (4) Listing per-locale app metadata: "asc app-info-localizations list --app-info-id ID" (5) Creating a new locale entry: "asc app-info-localizations create --app-info-id ID --locale en-US --name 'My App'" (6) Updating name, subtitle, or privacy URLs: "asc app-info-localizations update --localization-id ID --name 'New Name'" (7) Deleting a locale entry: "asc app-info-localizations delete --localization-id ID" (8) Navigating to age rating: "asc age-rating get --app-info-id ID" (use getAgeRating affordance) (9) User says "update app name", "update subtitle", "set privacy policy URL", "list app info", "manage app metadata", "set category", "update category"
Apply when implementing localization and translated copy in VTEX IO apps. Covers the `messages` builder, `/messages/*.json`, `context.json`, frontend message usage, and how VTEX apps integrate with `vtex.messages` for runtime translation. Use for storefront, admin, or backend flows that should use VTEX IO message infrastructure instead of hardcoded strings.
Develop e-commerce strategy for Southeast Asian markets including platform selection, payment infrastructure, logistics challenges, and localization requirements. Use this skill when the user is expanding e-commerce to SEA, evaluating Shopee vs Lazada vs Tokopedia, or needs to understand SEA market differences — even if they say 'sell to Southeast Asia', 'which platform in Vietnam', 'SEA payment methods', or 'cross-border e-commerce in ASEAN'.
Optimize multilingual product listings for international e-commerce including SEO localization, machine translation workflows, and cultural adaptation. Use this skill when the user needs to create product listings in multiple languages, optimize for local search, or adapt marketing content for different markets — even if they say 'translate our listings', 'optimize for local SEO', 'adapt for the Japanese market', or 'our translated listings don't convert'.
Guides all better-i18n integration decisions — SDK selection (Next.js, React, Expo, Swift, Flutter, Remix), CDN vs GitHub workflow, AI-powered translation management via MCP tools, CLI health checks (scan, doctor, sync), Content CMS (localized models, entries, custom fields), file format conventions (flat / nested / namespaced), key naming, publish flows, and quality analytics. Use whenever building, modifying, or reviewing any localization feature — including i18n setup, adding languages, managing translation keys, publishing, or integrating AI workflows.
Sync and validate App Store metadata and localizations with asc, including Fastlane format migration. Use when updating metadata or translations.
Use when building internationalization features, managing translation keys, setting up localization workflows, integrating AI translation, connecting GitHub repositories, delivering translations via CDN, using MCP tools for translation management, or implementing i18n SDKs in React/Next.js applications.
Laravel localization - __(), trans_choice(), lang files, JSON translations, pluralization, middleware, formatting. Use when implementing translations.
Metadata and localization sync (including Fastlane format) for Google Play Store listings. Use when updating app descriptions, screenshots, or managing multi-locale metadata.