i18n

Manage i18n translation keys across SEBT locales and namespaces.

10|1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/codeforamerica/sebt-self-service-portal --skill i18n-codeforamerica
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/codeforamerica/sebt-self-service-portal/tree/main/.claude/skills/i18n
Command: npx skills add https://github.com/codeforamerica/sebt-self-service-portal --skill i18n-codeforamerica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The i18n Skill guides teams in adding, locating, and debugging translation keys within the SEBT portal, ensuring user-facing text is present and accurate across locales.

Core Features & Use Cases

  • Create, locate, and audit i18n keys in the codebase
  • Validate translations across locales (e.g., en, co, dc) and identify blanks or mismatches
  • Diagnose missing keys and explain how to resolve them in the code and Google Sheet
  • Use with code to retrieve translations via useTranslation and namespace-based organization

Quick Start

Identify an i18n key, verify its translations across locales, and fix missing or empty values.

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I find and fix missing i18n translation keys in a React project?

Find missing i18n translation keys by auditing the codebase to locate blanks or mismatches across locales and namespaces, then aligning code with translation files to resolve the gaps.

How do I validate translations across multiple locales in SEBT?

Validate translations across locales by auditing i18n keys to identify blank or mismatched values in translation files, ensuring user-facing text is accurate across all specified locales.

What is the best way to organize i18n keys using namespaces and useTranslation?

Organize i18n keys using namespace-based structures and retrieve translations via the useTranslation hook, centralizing management of user-facing text across locales and namespaces.

Can I use this i18n workflow to debug translation mismatches in Google Sheets?

Yes, you can diagnose missing keys and resolve them in both the code and the Google Sheet, ensuring translation files and external documentation remain synchronized.

Why are my frontend translations showing blank values for certain locales?

Blank frontend translations occur when i18n keys are missing or empty in specific locale files, diagnosed by validating translations across locales and identifying blanks or mismatches.