Apply Stella i18n conventions to user-facing strings across apps.
npx skills add https://github.com/stella/stella --skill conventions-i18n
Please help me install this Agent Skill. Skill: conventions-i18n Source: https://github.com/stella/stella/tree/main/.agents/skills/conventions-i18n Command: npx skills add https://github.com/stella/stella --skill conventions-i18n
Internationalization conventions for Stella ensure consistent, scalable translations across the UI, reducing duplication and errors.
Consult the conventions whenever adding or updating user-facing strings to maintain coherence.
High-intent search queries and answers about installing and using this skill.
I18n naming conventions standardize translation keys to ensure scalable, consistent UI localization. They define key naming patterns and type declarations, reducing duplication and errors across multiple applications when adding or updating user-facing strings.
Standardize the translation workflow by applying established i18n conventions whenever adding or updating user-facing strings. This involves following specific steps for key naming, maintaining language coverage, and updating translations to ensure coherence across apps.
I18n conventions are needed for maintaining translations to prevent duplication and errors across different apps. They provide clear guidelines for language coverage and string flow, ensuring internationalization remains consistent and scalable as the UI grows.
Yes, the i18n convention covers type declarations and language coverage. It satisfies specific guidelines for naming, flow, and type declarations, while providing actionable steps for ensuring comprehensive language coverage across your applications.
Apply i18n conventions during UI development whenever introducing new strings or updating existing user-facing text. Consulting these standards during development maintains coherence and ensures translation files are consistently updated.
The best way to manage localization key naming is to apply standardized i18n conventions that define clear rules for keys and type declarations. This reduces duplication and errors, providing a consistent translation workflow for scalable UI localization.
kaeligDetect hardcoded user-facing strings in UI components and suggest i18n replacements.
noartemConfigure Laravel locale middleware and language files for multi-locale translation workflows.
naviktImplement and validate type-safe nb/nn i18n with parameter and semantic checks.
lobehubManage react-i18next translations and locale data in React applications.
