skills.rest
jellyrock
jellyrockOFFICIAL
Explore all skills by this author →
WebsiteGitHub

translation-add

Add compliant translation keys to JellyRock's JSON i18n system.

37|2|Updated Jun 28, 2025
Search Tags:#localization#translation#json#i18n#jellyrock#roku#brightscript
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill translation-add
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: translation-add
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/translation-add
Command: npx skills add https://github.com/jellyrock/jellyrock --skill translation-add

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adding new user-visible strings to JellyRock's custom JSON i18n system requires adhering to strict naming, sorting, and formatting conventions that are easy to violate, leading to lint failures, broken UI text, or build errors.

Core Features & Use Cases

  • Convention-compliant key naming: Guides selection of the correct PascalCase key prefix (Button, Label, Message, etc.) per project rules to avoid invalid key naming.
  • Edge case support: Provides explicit instructions for plural forms using Zero/One/Many suffixes, indexed {0}/{1} placeholders, and mandatory ISO 639-2 alias mapping for track language keys.
  • Built-in validation: Directs you to run required lint checks to catch sorting errors, placeholder mismatches, and missing language aliases before pushing code, preventing avoidable build failures.
  • Use Case: When adding a new "Add to watchlist" button label, the skill ensures you add the key to the correct location in en_US.json, follow all naming conventions, and pass all validation steps to avoid CI failures.

Quick Start

Use the translation-add skill to add a new translation key for the "Share media" button label to JellyRock's en_US.json file following all project i18n conventions.

Frequently Asked Questions about translation-add

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

FAQPage Schema
How do I add new i18n translation keys to a Roku BrightScript JSON file without lint failures?▼

Adding i18n translation keys to JSON files requires following strict PascalCase prefix naming conventions, alphabetical sorting, and placeholder parity enforcement to pass lint validation. The translation-add skill guides this process for the Roku BrightScript client to avoid build errors.

How do I handle plural forms and indexed placeholders when adding JSON localization strings?▼

JSON localization string plural forms require Zero/One/Many suffixes, while indexed placeholders use {0}/{1} syntax. The translation-add skill ensures correct placeholder parity enforcement across all translated strings to maintain formatting consistency.

How do I map track language aliases using ISO 639-2 codes in a Roku media client?▼

Mapping track language aliases requires ISO 639-2 code mapping for track language keys in the JSON i18n system. The translation-add skill enforces mandatory alias mapping compliance for the Roku media client to ensure correct language display.

Why does my Roku internationalization build fail when adding new user-visible strings?▼

Roku internationalization builds fail due to invalid key naming, alphabetical sorting errors, or placeholder mismatches in the JSON translation files. The translation-add skill validates these project requirements before code integration to prevent avoidable CI failures.

What is the best way to maintain alphabetical key sorting in an internationalization JSON file?▼

Maintaining alphabetical key sorting in i18n JSON files requires inserting new translation keys in the correct sequence and running validation checks. The translation-add skill directs you to run required lint checks to catch sorting errors before pushing code.

Can I use translation-add to ensure placeholder parity across all translated strings in en_US.json?▼

Translation-add ensures placeholder parity enforcement by validating that indexed {0}/{1} placeholders match exactly across all translated strings in en_US.json. It directs you to run required lint validation checks prior to code integration to catch mismatches.

Related Skills

Explore More Software Engineering Skills→
hiyeshuhiyeshu
4

localize

Extract static text and synchronize translation files across languages.

Community
Intermediate
Fr-e-dFr-e-d
157

i18n-validate

Validate i18n JSON files for missing translations, placeholder mismatches, and syntax errors.

Community
Advanced
aaronjoeldevaaronjoeldev
55

sync-translations

Synchronize next-intl locale JSON files against de.json keys.

Community
Intermediate
vechainvechain
9

translate

Manage react-i18next translation JSON files across multiple languages.

Official
Intermediate