Sign inStart your setup
We asked Claude

We asked Claude how a store owner should start with Claude Code. Here is its answer, and what Oomira does with it.

On October 28, 2026 we sent Claude one message through its API, with no instructions of our own:

“Help me use Claude Code on my Shopify store. I run a small store and I am not a developer.”

What came back is a good answer, about 900 words long, and it is printed in full further down. It hands you a to-do list. This page sets each item on that list beside what Oomira does for it.

It is a good answer.Careful and correct. It tells you to duplicate the live theme, push unpublished, set up Git and read every permission prompt. We would not change its advice.
It hands you the work.Terminal commands to paste, a spreadsheet detour, the Shopify CLI, a theme to duplicate in the admin, Git to set up, and three questions back before anything happens.
Nothing checks anything.Its safety rules are “never edit the live theme” and “read what Claude asks”. Both depend on you knowing what you are looking at. No step confirms the copy was saved or the right theme is open.
The same list, this afternoon

A store owner on Windows, not a developer. Twenty minutes, no terminal.

These are the times Oomira recorded on 28 October 2026 as her laptop and her store reported each step. She did not open a terminal once.

“Easy, instructions were clear, the interface was great, and I didn’t have any issues. The only thing is that it requires a level of trust to add different things to my computer without really understanding why they’re needed.”By email, the same afternoon

She is right about the trust, and it is the next thing we are working on: one line of why, beside every install, before Claude runs it.

  1. Claude Code installed and signed in
  2. Claude connected to Oomira
  3. Laptop reported: Windows 11, the Opus model picked
  4. Laptop signed in to the store with her own staff login; Oomira saw the store and its themes
  5. Private GitHub repository made, named after the store, connected to Oomira
What changes with Oomira

Four things the answer cannot give you.

  • No terminal.You use the Claude Code desktop app. Every command the answer tells you to paste, Claude runs itself.
  • Nothing you do not need.No CSV export, no extra installs, no “optional” detours. The list is your theme and the change you asked for.
  • The right page opens for you.When a sign-in needs you, Claude opens that page in its own browser pane and tells you what to press. You never hunt for a tab.
  • What Claude can do, Claude does.The folder, the Shopify CLI, the copy of your theme, the repository, the staging theme. The answer tells you to do these; Oomira has Claude do them, and checks each one.
Step by step

Claude’s list, and who does each line.

Claude saysOn your ownWith Oomira
1Get a paid Claude plan. Open Terminal and paste the install command.You, in the terminal.Claude Code's desktop app. No terminal, for this step or any other: Claude runs every command itself. Your laptop reports it and Oomira marks the step done.
2Make a folder, cd into it, type claude, log in.You, learning what cd means.Claude makes the folder and opens in it. You never type cd. Oomira records the folder from the laptop report.
3Export your products as a CSV. Keep a backup copy. Bulk-edit descriptions first.A spreadsheet detour, before any design work.Not on the list. Nothing you do not need gets installed or exported. Your setup is your theme, then the change you asked for.
4Ask Claude to install the Shopify CLI and pull your theme.You, hoping the install goes well.Claude installs it and signs your laptop in with your own staff login. Oomira sees the store and its themes from that sign-in and marks the step done.
5Duplicate your live theme in the Shopify admin first. Never edit the live one.You, in the admin, finding the right menu.Claude saves a copy of the live theme before anything changes. Oomira checks that the copy exists.
6Push the theme as unpublished, preview it, publish it yourself.You, each time.Claude works on a staging theme and hands you the preview. Oomira shows Staging and Live side by side. You say go.
7Ask Claude to set up Git so you can undo mistakes.You, if you remember to ask.Claude makes a private GitHub repository named after your store. When GitHub needs your sign-in, Claude opens that page for you, in its own browser pane, with the code to type. Oomira then reads the branches and who can change it.
8Read every permission it asks for. Ask "what will this do?"You, on every prompt.The Oomira connector tells Claude the next step in plain words, in order. Stuck? One press tells Oomira, and a person is on the session with you.

The connector is a piece of Oomira that sits inside Claude. It hands Claude the next step in plain words, in order, and Oomira reads your store, your repository and your laptop from outside and marks each step as it lands. You do the saying go.

What the answer never mentions

Four things a store owner hits in the first hour.

  • Which theme is live, and which one Claude is editingOomira reads the store's themes and names the live one and the staging one on the dashboard.
  • A teammate who also needs to work on the storeThe setup checks each person's own staff login and their place on the repository, and tells the owner who still needs adding.
  • What happens when Claude Code reaches its usage limit mid-sessionA backup is part of getting ready, so the session carries on.
  • Where to turn when a step failsEvery step on the dashboard has an "I'm stuck" press that tells Oomira, and the live session has a person in it.
The gotchas

Twelve things people hit. We hit them first, so you do not.

Every one of these came from a real session. Each is now a rule in Claude’s brief, a check Oomira runs, a slide, or a written snag with what to press.

  • Homebrew or the full Xcode install, forty minutes goneNever. Git on a Mac needs the command line tools alone, Node comes from nodejs.org, the rest from their own installers. The rule is in Claude's brief.
  • The GitHub sign-in needs a terminal, a code, and a Y you did not know to pressClaude runs the sign-in itself, opens the GitHub page in its own browser pane, and tells you the code to type and the one button to press.
  • Claude on the Sonnet model, quietly building a worse siteThe laptop report says which model is on. If it is not Opus, Claude is told to switch before the first change.
  • A video call and twenty tabs open while the build runs, and the laptop crawlsGetting ready includes closing what you are not using. The laptop report carries the load, and the dashboard shows red when it is too high.
  • Claude opens three terminals; you do not know which one to look atClaude never asks you to open a terminal. When something must be shown, it names the one pane.
  • A "What's next" box or a permission dialog that Claude waits on foreverBefore anything raises a box, Claude says which box and what to press. The snags for each box are written down, with what to press.
  • Claude Code hits its usage limit halfway throughThe backup is part of getting ready, so the work carries on.
  • Editing the wrong theme, or not knowing which one is liveOomira reads the store's themes and names the live one and the staging one on the dashboard. The copy is checked before anything changes.
  • Connecting GitHub to Shopify, and missing the second connection after the loginA slide with both presses, and Oomira detects whether the connection landed.
  • A teammate who cannot reach the store or the repositoryThe setup checks each person's staff login and their place on the repository, and tells the owner who still needs adding.
  • A rebuild that turns into an hour of questionsA hard rule: Claude asks nothing, builds from the live site, and reports when done.
  • Images and fonts missing from the rebuilt siteEvery image, font and file from every page is downloaded and counted, before and after.
The whole answer

Claude’s reply, unedited.

Model claude-opus-5-5, no system prompt, one message. We changed nothing, not a word.

Using Claude Code on Your Shopify Store (For Non-Developers)

Claude Code is an AI assistant that can read, create, and edit files on your computer and run commands for you. You describe what you want in plain English, and it does the technical work, asking permission before it changes anything.

First: Do You Actually Need Claude Code?

TaskBest tool
Write a few product descriptions, emails, or policiesRegular Claude chat (claude.ai) is simpler
Bulk-edit hundreds of products (titles, tags, SEO, prices)Claude Code
Change how your theme looks or works beyond the theme editorClaude Code
Analyze sales or order exportsClaude Code or Claude chat with file upload
Build custom automationsClaude Code (more advanced)

Claude Code earns its keep when you're working with files: product spreadsheets and theme code.

Step 1: Install Claude Code

You need a paid Claude plan (Pro or Max) or an Anthropic API account.

On a Mac:

  1. Open the Terminal app (press Cmd + Space, type "Terminal").
  2. Paste this and press Enter: 
    curl -fsSL https://claude.ai/install.sh | bash

On Windows:

  1. Open PowerShell from the Start menu.
  2. Paste this and press Enter: 
    irm https://claude.ai/install.ps1 | iex

Prefer not to use the terminal? Claude Code also has a desktop app and a VS Code extension with a more familiar interface. Check Anthropic's Claude Code docs for the current options.

Then:

  1. Create a folder on your Desktop called my-store.
  2. In Terminal, type cd (with a space), drag the folder into the window, and press Enter.
  3. Type claude and press Enter. Log in when prompted.

You're now chatting with Claude Code inside that folder.

Step 2: Start with the Easiest Win, Bulk Product Edits

This needs no coding setup and is very useful.

  1. In Shopify Admin, go to Products → Export and export all products as CSV.
  2. Save a backup copy of the file somewhere else.
  3. Move the CSV into your my-store folder.
  4. In Claude Code, try prompts like:

"Look at products_export.csv. Explain what columns are in it and summarize my catalog."

"Find any products with missing descriptions, missing images, or no SEO title. Give me a list."

"Write SEO titles (under 60 characters) and meta descriptions (under 155 characters) for every product missing them. Save the result as a new file called products_updated.csv. Don't change anything else."

"Add the tag 'summer-sale' to every product in the 'Swimwear' product type."

  1. Open the new file and spot-check it.
  2. Import it via Products → Import and check "Overwrite products with matching handles."

Tip: Test with 5–10 products first before importing hundreds.

Step 3 (Optional): Customizing Your Theme

This lets Claude change your store's design and features, such as adding a size chart, changing the layout, or creating custom sections.

Setup (Claude can walk you through it): In Claude Code, say:

"I want to edit my Shopify theme locally. Help me install Shopify CLI and download my theme. Explain each step simply."

It will guide you through commands like:

  • shopify theme pull to download your theme
  • shopify theme dev to preview changes privately in your browser
  • shopify theme push --unpublished to upload as a new, unpublished theme

Example prompts once your theme is downloaded:

"Add a 'Free shipping over $50' banner at the top of every page that I can turn on/off in the theme editor."

"On product pages, add a size chart popup that appears when someone clicks 'Size Guide'."

"Make the 'Add to Cart' button bigger and dark green on mobile."

"Explain how my product page is built, in plain English."

Safety Rules

  1. Never edit your live theme directly. In Shopify go to Online Store → Themes → ⋯ → Duplicate first, and work on the copy.
  2. Always push as unpublished, preview it, then publish yourself when happy.
  3. Back up CSVs before importing changes.
  4. Read what Claude asks permission for. If you don't understand, ask "What will this do?" before approving.
  5. Ask Claude to set up Git (version history) so you can undo mistakes. Just say: "Set up Git in this folder so I can undo changes, and explain how to use it simply."
  6. Don't share passwords or API keys in chat unless you understand why they're needed. Never post them publicly.

Prompting Tips for Non-Developers

  • Tell it you're not a developer: "I'm not technical, so explain things simply and tell me before you do anything risky."
  • Ask for a plan first: "Before changing anything, tell me your plan."
  • Be specific: "Make the header nicer" works less well than "Make the header logo smaller and center the menu."
  • Ask questions anytime: "What does this file do?" or "Why did that error happen?"

Where Do You Want to Start?

Tell me a bit more and I can give you exact step-by-step instructions:

  • Are you on Mac or Windows?
  • What do you most want to do? (fix product listings, change the design, add a feature, analyze sales, etc.)
  • Which theme do you use? (e.g., Dawn, or a paid theme)
We asked about a Wix site too: “Help me start using Claude Code to replace my Wix site. I am not a developer.”

The same shape, about 1000 words: copy every page by hand, build a static site, pick a host from four, then move the domain with a warning that the wrong DNS change breaks your email. Our builder sessions exist for that last step.

Replacing Your Wix Site with Claude Code: A Beginner's Guide

You don't need to know how to code. Claude Code writes the code, and your job is to describe what you want and check the results. Here's the path from start to finish.

Step 0: Check Whether Your Site Is a Good Fit

Easy to replace:

  • Informational sites (home, about, services, contact)
  • Portfolios and galleries
  • Restaurant, salon, or small business sites
  • Simple blogs
  • Contact forms (using a free service like Formspree or Netlify Forms)

Harder, and needs extra services:

  • Online stores (you'd connect something like Shopify, Stripe, or Gumroad)
  • Appointment booking (you'd embed Calendly, Acuity, etc.)
  • Member logins or paid memberships
  • Wix-specific apps you rely on

If your site is mostly the first list, you're in great shape.

Step 1: Gather Your Content from Wix

Wix doesn't offer a clean "export everything" button, so before you cancel anything:

  1. Make a folder on your computer called something like my-website.
  2. Copy all your text from each page into a document, one section per page.
  3. Download your images (logo, photos) into a subfolder called images.
  4. Take screenshots of each page so you can show Claude what you like about the current design.
  5. Write down your settings: domain name, where your domain is registered (Wix or elsewhere), email setup, and any forms or integrations.

Don't cancel Wix yet. Keep it running until the new site is live.

Step 2: Get Claude Code

  1. Get a subscription. Claude Code requires a paid Claude plan (Pro or higher) or an Anthropic API account. Pro is the simplest starting point.

  2. Choose how to use it:

    • Desktop app or web version (easiest): Look for Claude Code in the Claude desktop app or at claude.ai/code. These avoid the command line.
    • Terminal (the classic way): Open the Terminal app (Mac) or PowerShell (Windows) and paste:
      • Mac/Linux: curl -fsSL https://claude.ai/install.sh | bash
      • Windows: irm https://claude.ai/install.ps1 | iex

    Check Anthropic's docs (docs.claude.com) for the latest instructions, since these change occasionally.

  3. Start it in your website folder. In the terminal, type:

    cd ~/Desktop/my-website
claude

    (Adjust the path to wherever your folder is.) It will ask you to log in the first time.

Step 3: Tell Claude What to Build

Talk to it like you'd talk to a web designer you hired. A good first message:

I'm not a developer. I want to replace my Wix website with a simple, fast website I own. Please build it as a plain static site (HTML/CSS, no complicated frameworks) so it's easy to host for free.

My business is [describe it]. I need these pages: Home, About, Services, Contact.

My content is in content.docx and images are in the images folder. Screenshots of my current site are in screenshots. Keep a similar feel but make it cleaner and mobile-friendly.

Please explain what you're doing in plain English and tell me how to preview the site.

Tips:

  • Claude will ask permission before creating files or running commands. Read what it's asking, and approve if it makes sense.
  • Ask it to explain anything you don't understand. "What does that mean?" is always fair.
  • Make changes one at a time: "Make the header dark blue," "Add my phone number to the footer," "The photos look too big on my phone."

Step 4: Preview and Refine

Ask Claude: "How do I preview this site in my browser?" Often you can just double-click index.html, or Claude will start a local preview for you.

Check it on your computer, then ask Claude how to view it on your phone too. Keep iterating until you're happy.

Step 5: Put It Online (Usually Free)

Good beginner-friendly hosts for simple sites:

  • Netlify: you can drag and drop your folder onto their website
  • Cloudflare Pages
  • GitHub Pages
  • Vercel

Ask Claude:

Walk me step by step through putting this site on Netlify. Assume I've never done this before.

Claude can also help you set up GitHub, which saves every version of your site so you can undo mistakes. This is worth doing.

Step 6: Move Your Domain

This step needs the most care.

  • If your domain was bought through Wix: you'll either transfer it to a registrar (like Cloudflare, Namecheap, or Porkbun) or update its settings to point to your new host.
  • If it's registered elsewhere: you just change the DNS settings to point to your new host.
  • If you use email on your domain (like [email protected]), tell Claude before you change anything. Wrong DNS changes can break email.

Ask Claude:

My domain is [name], registered at [Wix/other]. I use [email provider] for email. How do I point it to my new site without breaking my email?

Step 7: Cancel Wix (Last!)

Only after the new site is live on your domain, you've checked it works, and your email still works.

Rough Costs

ItemCost
Claude Pro~$20/month (you can cancel after the build)
HostingUsually free for simple sites
Domain~$10–20/year

Compare that to your current Wix plan.

If You Get Stuck

  • Copy any error message and paste it to Claude: "I got this error, what do I do?"
  • Ask "What's the simplest way to do this?" whenever something seems complicated.
  • If Claude suggests something you don't understand, ask it to slow down.

To help me give you more specific advice: What kind of site do you have now, and does it use features like a store, bookings, a blog, or member logins? And is your domain registered through Wix?

The same list, done with you.

A live session with us, or the remote guide at your own pace for Shopify. Claude does each step, Oomira checks it, you say go.

Start your setup →Back to the homepage