AIShopifyTip

Claude Code for Shopify work: the 15 controls that matter

3 min read Published: 27 October 2026 Matt Grochala

4 min read · Pleroma Commerce · 4 sources

In short

Claude Code cheat sheets are everywhere, and most of them list 40 commands with equal weight. For Shopify theme and store work, about 15 controls matter: one key that sets how much Claude may do without asking, a handful of shortcuts to stop, rewind and inspect, and the commands that keep a long session clean. Learn those, work on an unpublished theme, and check your own command list with / because the tool changes every few weeks.

Why this matters for Shopify work

In April 2026 Shopify open-sourced its AI Toolkit as an MCP server, which gives coding agents such as Claude Code access to Shopify's developer documentation, GraphQL schemas and CLI[4]. That makes Claude Code a realistic tool for theme sections, Liquid fixes, metafield definitions and Admin API scripts. It also means an agent can now touch a live store, so the controls below are less about speed and more about where the brakes are.

Set the brakes first: permission modes

Press Shift+Tab to cycle permission modes. The indicator shows which one is active[1][2]:

  • Manual (default): Claude asks before editing files or running commands. Use it on anything connected to a live store.
  • acceptEdits: file edits go through without asking, shell commands still ask. Good for a theme you pulled to your machine.
  • plan: Claude reads and proposes, but changes nothing. Start every larger theme change here, or type /plan followed by the task.
  • auto and bypassPermissions: only appear when enabled. Keep them away from any session that holds store credentials.

To make the rules stick between sessions, run /permissions and add allow, ask and deny rules, for example deny any command that publishes a theme[3].

Eight shortcuts worth memorising

  • Esc: stop Claude mid-turn without losing the work done so far.
  • Esc, Esc on an empty prompt: open the rewind menu and restore code and conversation from an earlier point. With text in the prompt, it clears the draft instead.
  • Ctrl+C: interrupt a running operation. With nothing running, the first press clears the prompt and the second exits.
  • Ctrl+R: search your previous prompts.
  • Ctrl+O: open the transcript viewer to see exactly which tools ran and what they did.
  • @: reference a file, for example @sections/main-product.liquid.
  • ! at the start: run a shell command yourself, such as ! shopify theme check, and Claude reads the output.
  • ? on an empty prompt: show the shortcuts available in your terminal.

Shortcuts vary by terminal and platform, so the ? panel is the source of truth on your machine[2].

The commands that keep a theme session clean

  • /init once per repository to generate CLAUDE.md, then /memory to add your rules: which theme is live, which files never to touch, how you name sections.
  • /mcp to connect and authorise MCP servers, including Shopify's.
  • /context to see what is filling the context window, /compact to summarise it when it gets long.
  • /btw for a quick side question that stays out of the conversation history.
  • /diff to review every change before you push it anywhere.
  • /rewind when a change went wrong, /clear to start a new task, /resume to return to an earlier one.
  • /usage for cost and plan limits, /doctor when the installation misbehaves.

A safe workflow on a Shopify theme

  1. Pull the theme to your machine and work on a copy, never the published theme.
  2. Start in plan mode and let Claude read the relevant sections before it proposes anything.
  3. Switch to acceptEdits only once you agree with the plan.
  4. Run ! shopify theme check and review /diff.
  5. Push to an unpublished theme, preview it, and publish by hand.

That last step is the important one. An agent that can push code should never be the one that decides when customers see it.

Why most cheat sheets are already out of date

Claude Code ships changes every few weeks. /vim was removed in v2.1.92 and moved to /config, /agents now prints a reminder rather than opening an editor, and /cost is an alias for /usage[3]. Type / in your own session to see the commands available to you; the list depends on your plan, platform and version.

Want this set up for your team?

We set up Claude Code for Shopify teams with project rules in CLAUDE.md, permission rules that block publishing, and a theme workflow your developers can follow from day one.

Start with the store and channel audit

Sources

  1. Claude Code Docs, “Permission modes”, accessed 26 October 2026. https://code.claude.com/docs/en/permission-modes
  2. Claude Code Docs, “Interactive mode”, accessed 26 October 2026. https://code.claude.com/docs/en/interactive-mode
  3. Claude Code Docs, “Commands”, accessed 26 October 2026. https://code.claude.com/docs/en/commands
  4. Peliqan, “Shopify MCP: Connect your store to AI agents”, October 2026. https://peliqan.io/blog/shopify-mcp/

About the author

Matt Grochala is the founder and lead operator of Pleroma Commerce. His work spans Shopify, marketplaces, product data and commerce operations in the UK and Poland.

Published by Pleroma Commerce.

Go deeper 100 Growth Hacks for Shopify Stores An operator's playbook for Shopify brands selling across store, marketplaces and European markets. Get it free → Free All ebooks →