Menu
Translates Simple History Premium plugin strings for one or multiple locales. Use when translating or updating premium plugin PO files.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | premium-translate |
| description | Translates Simple History Premium plugin strings for one or multiple locales. Use when translating or updating premium plugin PO files. |
| argument-hint | [locales] |
| allowed-tools | Read, Edit, Write, Bash(cat:*), Bash(ls:*), Bash(npm run:*), Bash(npm:*), Bash(wp:*), Bash(msgfmt:*), Glob, Agent |
Translate the Simple History Premium plugin's PO files from English to specified locales.
See CLAUDE.local.md for the premium add-on path. Read it first to determine the correct path. All commands below should be run from that directory.
CLAUDE.local.md to find the premium add-on pathtranslation-config.json in the premium add-on to get configured localeslanguages/ directorynpm runBreak up $ARGUMENTS into parts — each part is a locale.
If no locales are provided, use all locales defined in the translation config.
Confirm that each locale is valid and defined in the translation config. If not, show an error and exit.
Show the locales to be translated for confirmation.
Run from the premium add-on path:
npm run i18n:make-pot — Update the POT file with latest strings from source codenpm run i18n:update-po — Update PO files for all localesIf translating 1-2 locales: Translate sequentially in the main conversation.
If translating 3+ locales: Use batched parallel agents:
Translation rules for each locale:
msgid (English string), provide an accurate translation in the corresponding msgstr%s, %d, %1$s) unchangedRun from the premium add-on path:
npm run i18n:make-mo — Compile MO filesnpm run i18n:make-php — Compile PHP files/premium-translate de_DE — Translate to German/premium-translate sv_SE da_DK — Translate to Swedish and Danish/premium-translate — Translate all configured localesAdds changelog entries to readme.txt following keepachangelog format. Use when updating the Unreleased section or documenting changes for a release.
Reproducibly capture in-product UI screenshots (admin popovers, settings teasers, dashboard widgets) used as embedded images in premium upsell teasers. Use whenever a teaser image needs refreshing after the underlying UI changes.
Guides implementation of structured action links on log events. Use when adding get_action_links() to a logger or migrating from get_log_row_details_output().
Enforces active voice for logger messages and the Event Details API. Use when writing a new logger class or modifying message arrays in getInfo().
How to design and regenerate marketing screenshots for the wordpress.org plugin page (banner-1544x500.png, screenshot-1.png, etc). Covers the event mix that converts, the reproducible WordPress Playground pipeline that bakes it, and every non-obvious gotcha from previous shoots. Use when refreshing screenshot-1.png, banners, or any image showing the Simple History event log.
Guidance for writing and running tests in Simple History. Covers which framework to use, how to run existing tests, and how to create new ones (including the codegen recording workflow).