What problem does it solve? Adding user-visible text to a multilingual website often leads to hardcoded strings, missing translations, and inconsistent locale pages. This Skill enforces a structured i18n workflow so every string is typed, translated into all locales, and rendered through a shared translation helper. ## Core Features & Use Cases - 4-Step Translation Workflow: Define keys in a TypeScript types file, add strings to every locale file (en, ca, es), consume them via a useTranslations helper, and create localized page variants. - Type-Safe Completeness: TypeScript compilation catches any locale missing a key defined in the central types file. - Translation Guardrails: Maintains a list of product names, CLI flags, and acronyms that must never be translated, and forbids hardcoded text or version numbers. - Use Case: When adding a new pricing section to the Envilder website, use this Skill to define the keys, translate them into English, Catalan, and Spanish, and create the localized Astro pages. ## Quick Start Add a new translated section to the website by defining its keys in the i18n types file and filling in all locale files.
