shopbuilder-translate
Skill9 starsChanged 5 months agoMITView on GitHub
Translates Shop Builder page copy: hero, buttons, FAQ, section titles and page SEO. Use for "translate the FAQ", "add a language to Shop Builder", "my store is only in English". Catalog and LiveOps text are out of scope. Confirms before any write. Not for building the shop or setting prices.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/xsolla-ai-kit.mdcCursor rule
- catalog-designSkill
- description-to-shopSkill
- game-web-portalSkill
- headless-checkout-integrationSkill
- login-setupSkill
- login-stylingSkill
- merchant-setupSkill
- nocode-shop-setupSkill
- productionSkill
- quest-setupSkill
- shop-builder-assemblySkill
- shop-setupSkill
- webhooks-implSkill
- xla-pagesSkill
- catalog-designSkill
- description-to-shopSkill
- game-web-portalSkill
- headless-checkout-integrationSkill
- login-setupSkill
- login-stylingSkill
- merchant-setupSkill
- nocode-shop-setupSkill
- productionSkill
- quest-setupSkill
- shop-builder-assemblySkill
- shopbuilder-translateSkill
- shop-setupSkill
- webhooks-implSkill
- xla-pagesSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Ask whether they already have translations.
- Very specific: line 26
Run apply.sh as a dry run and show the plan: locale, what will change, and the dry run's list of existing translations it would replace.
- Distinctive: line 31
After the storefront exists.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Translate Shop Builder page copy
This skill writes Shop Builder page copy only. Catalog and LiveOps text (items, groups, bundles, currency, promotions, reward chains) are out of scope. Do not translate them here.
The model does the translation. There is no machine-translation service.
Nothing here publishes the site. --commit writes the live project named by XSOLLA_PROJECT_ID. There is no Shop Builder sandbox. --commit does not change the language the shop opens in.
Before any write
- Name the target locale in the user's words (
Japanese→ja-JP). Codes are in references/i18n-support.md. - Ask whether they already have translations. If yes,
scripts/ingest-user-translations.sh. If no, the model fills the gaps after they confirm the plan. - Run
apply.shas a dry run and show the plan: locale, what will change, and the dry run's list of existing translations it would replace. Wait for an explicit yes. Then write. - Catalog and LiveOps strings are out of scope. Stop. Do not translate them with this skill.
Page copy
After the storefront exists. Silent failures and the script list: references/storefront.md. Field failures: references/translation-notes.md.
scripts/preflight.sh
scripts/export-backup.sh <domain> l10n/backup/<timestamp>
scripts/extract.sh en-US ja-JP
scripts/apply.sh <domain> ja-JP # dry run
# explicit yes, then: enable the language and write
scripts/apply.sh <domain> ja-JP --commit --confirm-overwrites
scripts/verify.sh <domain> ja-JPexport-backup.sh reads the live site with get-structure and get-localization and writes those two files. It does not change the site. Before any write, the CLI's configured project must match XSOLLA_MERCHANT_ID and XSOLLA_PROJECT_ID. The scripts read the IDs only from the environment; on the Shop Builder path, set them from xsolla config list --json for each run. The slug must also appear in that project's list-websites result. get-structure is not that check.
--commit enables the language with add-language, then writes the copy. It runs add-language only after the project check, the list-websites check and the pre-write export. If the pre-write export already lists the locale, add-language is skipped. A 400 with the message "language is taken" is also success. Any other failure stops the run before any copy is written. If the copy write fails after this run enabled the language, the run prints the delete-language command for it. Show it to the user. This skill does not run it.
--commit blocks when it would replace an existing translation until --confirm-overwrites. That list comes from the dry run and is part of the plan, so the yes covers it: pass the flag then, without asking again. --commit exports the site again into l10n/pre-write/ and blocks if the text about to be written changed since extract. A write that returns non-zero fails the run.
The shop opens in the first language of the site language list. This skill does not reorder that list and does not call delete-language. If the partner wants the shop to open in the new language, they reorder the list in Publisher Account.
Out of scope
Catalog and LiveOps text. Prices and regional availability. Legal copy. Text baked into images. Publishing the site. Changing the language the shop opens in.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

