cells-i18n

Convert component literals to this.t calls and sync locale files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-i18n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cells-i18n
Source: https://github.com/PixelDroid19/cells-agents/tree/main/skills/cells-i18n
Command: npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The skill ensures Cells components are properly internationalized, preventing hard‑coded user‑facing strings and guaranteeing that translation keys and locale files stay in sync.

Core Features & Use Cases

  • Identify all user‑visible string surfaces in a component.
  • Convert literals to this.t calls with stable, component‑prefixed keys.
  • Verify and update locale files in demo/locales to maintain parity across languages.
  • Set up IntlMsg in demos and tests for deterministic loading and runtime verification.
  • Provide a checklist to confirm no hard‑coded strings remain and all keys are present.

Quick Start

Ask the cells-i18n skill to scan the component, add missing translation keys, and verify locale configuration.

Frequently Asked Questions about cells-i18n

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

FAQPage Schema
How do I convert hard-coded component literals to translation keys?

How do I convert hard-coded component literals to translation keys? Identify user-visible string surfaces and replace them with this.t calls using stable, component-prefixed keys to ensure consistent internationalization and prevent raw text from rendering in the UI.

What is the best way to keep translation keys and locale files synced?

What is the best way to keep translation keys and locale files synced? Verify and update entries in demo/locales files whenever new translation keys are added to maintain strict locale parity across all supported languages.

How does deterministic loading for internationalization work in tests?

How does deterministic loading for internationalization work in tests? Set up IntlMsg in demos and tests to verify runtime configuration, ensuring translation keys load consistently and predictably during automated test execution.

Can I use this internationalization approach for Cells components?

Can I use this internationalization approach for Cells components? Yes, it is specifically designed to enable consistent internationalization for Cells components by managing translation keys, updating locale files, and configuring IntlMsg for runtime verification.

Why do I need to verify locale parity after adding new translation keys?

Why do I need to verify locale parity after adding new translation keys? Verifying locale parity ensures all translation keys exist across demo/locales files, preventing missing translations and runtime errors when switching languages in the component.

What steps are needed to automate i18n setup for user-visible text?

What steps are needed to automate i18n setup for user-visible text? Scan the component to locate literals, update them to this.t calls, ensure entries exist in demo/locales files, and configure IntlMsg for deterministic loading and runtime verification.