Edit a theme safely, in plain language
Describe the change. Claude plans it, validates it, and shows you a preview before anything lands.
The point of this flow is that the risky step is last, small, and explicitly yours.
The path
gem.plan_experience_changeturns your sentence into a target, an intent and a set of patch operations. Nothing is created.gemtheme.propose_theme_editturns the plan into a scoped patch workflow. Still nothing in Shopify.gemtheme.validate_theme_patchchecks it and attaches a quality report.gemtheme.preview_theme_patchrenders the patched result so you can look at it.- Approve, then
gemtheme.apply_theme_patch_to_draftwrites it to the draft.
Say what you want
Using gemboss: plan this change for shop your-store.myshopify.com. On the product page, move the reviews section above the description, and make the add to cart button full width on mobile. Show me the plan and the risk assessment before proposing anything.
You get back the target it resolved, the operations it intends, and its own read of the risk. Argue with it here, while nothing exists yet.
Target the right page
A change aimed at the wrong page fails quietly: a page type that does not match falls back to the homepage. So when the change is for a specific page, pin it down first.
List the plan pages first, and tell me which address you will use for this change.
gem.list_plan_pages returns each page with the address to use, by type for templates and
by handle for content pages such as landing pages and policies.
Look at the preview, not the description
Validate the patch, then render a preview and give me the link.
The quality report catches structural problems. The preview catches the ones only eyes catch. Both come before the approval gate, on purpose.
Land it
Request approval, and after I approve, apply the patch to the draft theme.
It lands on a draft. Publishing remains a separate, deliberate act in Shopify.
Knowing what is available
If you are not sure a change is even expressible:
What section capabilities are available for a product page?
gem.list_section_capabilities lists what the section library can do, with stable
sections ranked ahead of candidates. It is a better starting point than guessing and
finding out at validation.
Next
Stuck on the connection?
You connect at https://mcp.gemboss.com/mcp and sign in through your browser — there is no key to ask for. If the browser step does not finish, the troubleshooting page walks through what to check.
Thanks. That goes straight to the people who write these.