vtex-io-messages-and-i18n

Manage localization and translation for VTEX IO applications using message infrastructure.

Updated May 8, 2026
One-click install
npx skills add https://github.com/Willjeanne/faststore-soliverdemo --skill vtex-io-messages-and-i18n-willjeanne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vtex-io-messages-and-i18n
Source: https://github.com/Willjeanne/faststore-soliverdemo/tree/main/.agents/skills/vtex-io-messages-and-i18n
Command: npx skills add https://github.com/Willjeanne/faststore-soliverdemo --skill vtex-io-messages-and-i18n-willjeanne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill ensures that VTEX IO applications have consistent and easily maintained localization and translation, replacing hardcoded strings with a structured message system.

Core Features & Use Cases

  • Localizable UI Text: Facilitates the addition of localized text for storefront or Admin applications.
  • Translation File Management: Offers a method to create and update translation files.
  • Context Management: Allows defining message keys in the app's context file for easier discovery and management by VTEX IO.
  • In-Depth Integration: Integrates with the vtex.messages infrastructure for runtime translation.
  • Use Case: When a company wants to translate their VTEX storefront into multiple languages while keeping the process maintainable and centralized.

Quick Start

Run the script to generate the context file for your messages and update the corresponding language files within the 'messages/' directory.

Frequently Asked Questions about vtex-io-messages-and-i18n

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

FAQPage Schema
How do I manage localization and translation in VTEX IO applications?

To translate VTEX IO storefront or Admin applications, you replace hardcoded strings with structured message keys. This process involves setting up context files and corresponding language files within the app's messages/ directory for centralized management.

How does VTEX IO message infrastructure handle runtime translation?

The VTEX IO message infrastructure handles runtime translation by integrating with the vtex.messages system. It uses defined message keys in the app's context file to dynamically fetch and display localized text during application execution.

What is the best way to structure translation files for a VTEX storefront?

The best way to structure translation files for a VTEX storefront is by placing them inside a dedicated messages/ directory. You define message keys in a context file and generate corresponding language files to maintain a centralized translation system.

Can I use this approach to translate both storefront and Admin apps?

Yes, this message infrastructure approach supports adding localized UI text for both VTEX storefront and Admin applications. It allows you to manage translation files and context definitions across multiple interfaces centrally.

Why should I replace hardcoded strings with message keys in VTEX IO?

You should replace hardcoded strings with message keys in VTEX IO to ensure consistent and easily maintained localization. This structured message system allows VTEX IO to discover and manage message keys for scalable multi-language support.