vtex-io-storefront-theme-versioning — Claude Code skill: setup guide
Guides coding agents through publishing, updating, or rolling back VTEX IO storefront themes without losing merchant Site Editor data across major versions.
npx skills add vtex/skills --skill vtex-io-storefront-theme-versioning -a claude-codeWhat vtex-io-storefront-theme-versioning does
The skill governs version transitions for storefront apps holding files under store/. In VTEX IO, vtex.pages-graphql indexes merchant page layouts by the major release tag. Bumping to a new major changes that index key. The storefront immediately loses existing block layouts and displays fallback platform defaults.
The agent enforces a verified staging flow instead of direct upgrades in master. You create a production dev workspace, install the theme release, and trigger the updateThemeIds GraphQL mutation. This call rekeys custom routes, redirect maps, and editor configs to the new major version. Omitting updateThemeIds guarantees an empty storefront after cutover.
Promoting via vtex workspace promote triggers a three-way merge against VBase storage. The platform writes automatic snapshots to userData_backup whenever merge collisions arise. That mechanism protects previous edits if unexpected conflicts happen during promotion.
What it helps with
- prevent merchant layout loss during theme major version upgrades
- rekey pages and redirect entries across major releases using
updateThemeIds - validate storefront layouts inside a production dev workspace before promote
- plan rollback procedures between major versions without rebuilding content
Example prompts for the agent
- Help me upgrade
vendor.store-themefrom major 2 to 3 without dropping Site Editor data. - Prepare the
updateThemeIdsmutation payload to migrate pages from major 0 to 1. - Audit my deploy workflow before I promote the theme workspace to master.
How to install vtex-io-storefront-theme-versioning
1Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-storefront-theme-versioning -a claude-code2Manually: put the files in place
~/.claude/skills/vtex-io-storefront-theme-versioning/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vtex-io-storefront-theme-versioning/
1Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-storefront-theme-versioning -a codex2Manually: put the files in place
.agents/skills/vtex-io-storefront-theme-versioning/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-storefront-theme-versioning -a cursor2Manually: put the files in place
.cursor/skills/vtex-io-storefront-theme-versioning/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vtex/skills vtex-io-storefront-theme-versioning2Manually: put the files in place
.github/skills/vtex-io-storefront-theme-versioning/SKILL.md1Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-storefront-theme-versioning -a gemini-cli2Platform CLI
gemini skills install https://github.com/vtex/skills --path skills/vtex-io-storefront-theme-versioningManually: put the files in place
.devin/skills/vtex-io-storefront-theme-versioning/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-storefront-theme-versioning -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vtex-io-storefront-theme-versioning
How to install vtex-io-storefront-theme-versioning in Claude Code?
Run npx skills add vtex/skills --skill vtex-io-storefront-theme-versioning -a claude-code. The skill file installs to ~/.claude/skills/vtex-io-storefront-theme-versioning/SKILL.md.
Why does bumping a theme major version erase storefront content?
VTEX IO stores editor entries under keys tagged with the major version number. A newly installed major queries a fresh key space and renders default placeholder blocks instead.
What role does updateThemeIds play during migration?
The mutation transfers Site Editor configurations, custom routes, and URL redirects from the previous major key space to the new one.