Loading...
Loading...
Manage app translations with goman.live. Use when: adding translations, adding i18n keys, localizing components, checking translation keys exist, searching translations, updating language content, managing i18n strings, extract hardcoded strings, localize folder, audit missing translations.
npx skill4agent add bel-frontend/goman-live-skills goman-translations.envGOMAN_API_KEY=your_api_key_here
GOMAN_APP_ID=your_application_id_herecreated. Please fill in.envandGOMAN_API_KEYwith values from the goman.live dashboard → Settings → API Keys, then ask me to continue.GOMAN_APP_ID
| Script | What it does | Example |
|---|---|---|
| List active language codes | |
| List translation namespaces | |
| Get translations for a key | |
| Search/filter translations | |
| Add or update translations | |
| ⚠️ Delete a key permanently | |
JSON.parse()namespace.key"screens.login.submitButton""screens.login""submitButton"fullKeySTEP 1: node goman-languages.js → get valid language codes
STEP 2: node goman-get.js <fullKey> → check if key already exists
STEP 3: node goman-create.js <fullKey> <json> <context> → create/updateSTEP 1: Receive component code from user
STEP 2: Find ALL hardcoded user-visible strings
(labels, placeholders, titles, errors, tooltips — skip console.log, URLs, CSS)
STEP 3: node goman-languages.js
STEP 4: Plan keys: namespace = component name, key = descriptive name
Show plan to user and ask: "Should I proceed?"
STEP 5: After confirmation → node goman-create.js for each key (all languages at once)
STEP 6: Show replacement code snippets:
Before: <button>Submit</button>
After: <button>{t("LoginForm.submitButton")}</button>STEP 1: node goman-namespaces.js → understand project structure
STEP 2: node goman-search.js → filter by namespace or search query
STEP 3: node goman-languages.js → compare found keys vs active languages
STEP 4: Report missing translations per keySTEP 1: List files in the folder (ask user if not provided)
STEP 2: For each file: find hardcoded strings
STEP 3: node goman-languages.js
STEP 4: Show full plan across all files, ask confirmation
STEP 5: Batch node goman-create.js calls
STEP 6: Show replacement code for each filegoman-delete.jsgoman-languages.jscontextgoman-create.js