add-translation

Add Hebrew and English translation keys to LanguageContext.jsx in React i18n systems.

Updated Dec 5, 2025
One-click install
npx skills add https://github.com/doleval013/Barak-web --skill add-translation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-translation
Source: https://github.com/doleval013/Barak-web/tree/main/.agent/skills/add-translation
Command: npx skills add https://github.com/doleval013/Barak-web --skill add-translation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill simplifies updating i18n translations by adding new Hebrew and English keys to the LanguageContext, reducing manual editing and sync errors.

Core Features & Use Cases

  • Identify missing translation keys in both Hebrew and English objects in src/context/LanguageContext.jsx
  • Update translations consistently across both locales
  • Use case: when new UI text is introduced, add a new key and provide translations for both locales

Quick Start

To add a new translation key, extend both he and en blocks in the translations object inside src/context/LanguageContext.jsx and reference the key with t('new_key') in components.

Frequently Asked Questions about add-translation

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

FAQPage Schema
How do I add new translation keys to a React LanguageContext for Hebrew and English?

To add new translation keys to a React LanguageContext, extend both the Hebrew and English blocks inside the translations object in src/context/LanguageContext.jsx, then reference the new key using the t('new_key') function in your components.

What is the best way to prevent sync errors when updating i18n translations in React?

The best way to prevent sync errors when updating i18n translations in React is to enforce updating both the Hebrew and English language objects together inside your centralized LanguageContext, avoiding hardcoded strings and preserving naming conventions.

Can I use a centralized i18n system to avoid hardcoded strings in my React application?

Yes, you can use a centralized i18n system in React by managing your localized texts within a LanguageContext and accessing them via the t(key) function, which ensures all UI text is handled dynamically without hardcoded strings.

Why are my Hebrew and English translation objects out of sync in my React app?

Hebrew and English translation objects in React fall out of sync when new UI text is introduced manually without updating both language objects together, causing missing translation keys that a centralized LanguageContext update can fix.

Does updating React localization keys require modifying both language objects in LanguageContext.jsx?

Yes, updating React localization keys requires modifying both the Hebrew and English language objects in src/context/LanguageContext.jsx to ensure consistent translations across both locales and prevent missing text.