From zero to a working store, end to end.

You click “Create my store”

You land on GitHub’s normal “create a new repo from a template” page. Pick a name (any name — you can change it later), click create, and GitHub copies our starter into your account in a few seconds.

We never see your account. The button is just a deep-link to GitHub — you sign in with your own GitHub account, and your repo is yours. You can make it public, you can make it private, its entirely up to you.

GitHub builds a real, running store in your browser

On your new repo, click Code → Codespaces → Create codespace. GitHub spins up a Linux machine, installs Magento, sets up the database, and opens VS Code right in your browser.

First launch takes ~5 minutes while everything builds. After that, starting your store again is seconds.

You open Claude inside your store

In the Codespace terminal, type claude. Claude reads your store’s files, knows the project conventions (we ship a AGENTS.md for it), and is ready to help.

Pick the storefront that fits you: the starter wires up either Hyva (Magento’s modern theme, no JS framework needed) or Daffodil (Angular-based headless). Claude knows both.

You tell Claude what you want, in plain English

“Add a sale banner to the homepage.” “Make shipping free over $50.” “Create a new product category for holiday gifts.” Claude explains what it’s doing, makes the change, and asks before anything risky.

Try the change in your browser

Codespaces shows your store live in another browser tab. Refresh it and your change is right there — actually click around the site and test it before you keep it. Don’t like it? Tell Claude to undo. Nothing is locked in yet.

When you’re happy, Claude saves it back to GitHub

Tell Claude “save this” (or any natural phrase) and it copies the change from your Codespace back to your repo on GitHub. Think of it like Google Docs’ autosave — except instead of one document, the whole store gets saved as a labeled snapshot you can return to.

For developers: this is the standard git commit + git push. Non-technical users don’t need to know what those words mean — Claude handles them.

GitHub double-checks every saved change

The instant your change lands on GitHub, an automated checkup kicks off on GitHub’s servers — a fresh, clean copy of your store is built from your code and put through the same tests we use on the starter itself. It usually finishes in a couple of minutes.

You’ll see a small green ✓ next to the change if your store still works, or a red ✗ if something broke. Click into the red X and you see a plain-text report of what failed — and Claude can read that same report and walk you through fixing it.

For developers: this is a GitHub Actions workflow (check-store from graycoreio/github-actions-magento2) running on every push to the default branch.