shopify-expert
Builds and debugs Shopify themes (.liquid files, theme.json, sections), develops custom Shopify apps (shopify.app.toml, OAuth, webhooks), and implements Storefront API integrations for headless storefronts. Use when building or customizing Shopify themes, creating Hydrogen or custom React storefronts, developing Shopify apps, implementing checkout UI extensions or Shopify Functions, optimizing performance, or integrating third-party services. Invoke for Liquid templating, Storefront API, app development, checkout customization, Shopify Plus features, App Bridge, Polaris, or Shopify CLI workflo
npx skills add Jeffallan/claude-skills --skill shopify-expert --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Shopify Expert Senior Shopify developer with expertise in theme development, headless commerce, app architecture, and custom checkout solutions. ## Core Workflow 1. **Requirements analysis** — Identify if theme, app, or headless approach fits needs 2. **Architecture setup** — Scaffold with `shopify theme init` or `shopify app create`; configure `shopify.app.toml` and theme schema 3. **Implementation** — Build Liquid templates, write GraphQL queries, or develop app features (see examples below) 4. **Validation** — Run `shopify theme check` for Liquid linting; if errors are found, fix them and re-run before proceeding. Run `shopify app dev` to verify app locally; test checkout extensions in sandbox. If validation fails at any step, resolve all reported issues before moving to deployment 5. **Deploy and monitor** — `shopify theme push` for themes; `shopify app deploy` for apps; watch Shopify error logs and performance metrics post-deploy ## Reference Guide Load detailed guidance based on context: | Topic | Reference | Load When | |-------|-----------|-----------| | Liquid Templating | `references/liquid-templating.md` | Theme development, template customization | | Storefront API |
- Core Workflow
- Reference Guide
- Code Examples
- Liquid — Product template with metafield access
- Liquid — Collection filtering (Online Store 2.0)
- Storefront API — GraphQL product query
- Shopify CLI — Common commands
- App — Authenticated Admin API fetch (TypeScript)
- Constraints
- MUST DO
- MUST NOT DO
- Output Templates
- Knowledge Reference
Theme development shopify theme dev --store=your-store.myshopify.com # Live preview with hot reload shopify theme check # Lint Liquid for errors/warnings shopify theme push --only templates/ sections/ # Partial push shopify theme pull # Sync remote changes locally App development shopify app create node # Scaffold Node.js app shopify app dev # Local dev with ngrok tunnel shopify app deploy # Submit app version shopify app generate extension # Add checkout UI extension
What does the shopify-expert skill do?
Builds and debugs Shopify themes (.liquid files, theme.json, sections), develops custom Shopify apps (shopify.app.toml, OAuth, webhooks), and implements Storefront API integrations for headless storefronts. Use when building or customizing Shopify themes, creating Hydrogen or custom React storefronts, developing Shopify apps, implementing checkout UI extensions or Shopify Functions, optimizing performance, or integrating third-party services. Invoke for Liquid templating, Storefront API, app development, checkout customization, Shopify Plus features, App Bridge, Polaris, or Shopify CLI workflo
How do I install it?
Run `npx skills add Jeffallan/claude-skills --skill shopify-expert --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Jeffallan/claude-skills, a repository with 10,871 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.