translation-add

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.