shopify-developer▌
tech-leads-club/agent-skills · updated May 23, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Complete Shopify development reference covering Liquid templating, OS 2.0 themes, GraphQL APIs, Hydrogen, Functions, and performance optimization (API v2026-01). Use when working with .liquid files, building Shopify themes or apps, writing GraphQL queries for Shopify, debugging Liquid errors, creating app extensions, migrating from Scripts to Functions, or building headless storefronts. Triggers on "Shopify", "Liquid template", "Hydrogen", "Storefront API", "theme development", "Shopify Functions", "Polaris". Do NOT use for non-Shopify e-commerce platforms.
| name | shopify-developer |
| description | Complete Shopify development reference covering Liquid templating, OS 2.0 themes, GraphQL APIs, Hydrogen, Functions, and performance optimization (API v2026-01). Use when working with .liquid files, building Shopify themes or apps, writing GraphQL queries for Shopify, debugging Liquid errors, creating app extensions, migrating from Scripts to Functions, or building headless storefronts. Triggers on "Shopify", "Liquid template", "Hydrogen", "Storefront API", "theme development", "Shopify Functions", "Polaris". Do NOT use for non-Shopify e-commerce platforms. |
Shopify Developer Reference
Comprehensive reference for professional Shopify development - API version 2026-01.
Quick Reference
| Item | Value |
|---|---|
| API version | 2026-01 (stable) |
| GraphQL Admin | POST https://{store}.myshopify.com/admin/api/2026-01/graphql.json |
| Storefront API | POST https://{store}.myshopify.com/api/2026-01/graphql.json |
| Ajax API (theme) | /cart.js, /cart/add.js, /cart/change.js |
| CLI install | npm install -g @shopify/cli |
| Theme dev | shopify theme dev --store {store}.myshopify.com |
| App dev | shopify app dev |
| Deploy | shopify app deploy |
| Docs | shopify.dev |
Choose Your Path
Read the reference file(s) that match your task:
Liquid templating - writing or debugging .liquid files:
- references/liquid-syntax.md - Tags, control flow, iteration, whitespace, LiquidDoc
- references/liquid-filters.md - All filter categories with examples
- references/liquid-objects.md - Product, collection, cart, customer, and global objects
Theme development - building or customising themes:
- references/theme-development.md - OS 2.0 architecture, sections, blocks, JSON templates, settings schema
API integration - fetching or modifying data programmatically:
- references/api-admin.md - GraphQL Admin API (primary), REST (legacy), OAuth, webhooks, rate limiting
- references/api-storefront.md - Storefront API, Ajax API, cart operations
App development - building Shopify apps:
- references/app-development.md - Shopify CLI, extensions, Polaris Web Components, App Bridge
Serverless logic - custom business rules:
- references/functions.md - Shopify Functions (replacing Scripts), Rust/JS targets, deployment
Headless commerce - custom storefronts:
- references/hydrogen.md - Hydrogen framework, React Router 7, Storefront API integration
Optimisation and troubleshooting:
- references/performance.md - Images, JS, CSS, fonts, Liquid, Core Web Vitals
- references/debugging.md - Liquid errors, API errors, cart issues, webhook failures
Deprecation Notices
| Deprecated | Replacement | Deadline |
|---|---|---|
| Shopify Scripts | Shopify Functions | August 2025 (migration), sundown TBD |
| checkout.liquid | Checkout Extensibility | August 2024 (Plus), done |
| REST Admin API | GraphQL Admin API | Active deprecation (no removal date yet) |
| Legacy custom apps | New auth model | January 2025 (done) |
| Polaris React | Polaris Web Components | Active migration |
| Remix (app framework) | React Router 7 | Hydrogen 2025.5.0+ |
Liquid Essentials
Three syntax types:
{{ product.title | upcase }} {# Output with filter #}
{% if product.available %}In stock{% endif %} {# Logic tag #}
{% assign sale = product.price | times: 0.8 %} {# Assignment #}
{%- if condition -%}Stripped whitespace{%- endif -%}
Key patterns:
{% for product in collection.products limit: 5 %}
{% render 'product-card', product: product %}
{% endfor %}
{% paginate collection.products by 12 %}
{% for product in paginate.collection.products %}...{% endfor %}
{{ paginate | default_pagination }}
{% endpaginate %}
API Essentials
// GraphQL Admin - always use GraphQL over REST
const response = await fetch(`https://${store}.myshopify.com/admin/api/2026-01/graphql.json`, {
method: 'POST',
headers: {
'X-Shopify-Access-Token': accessToken,
'Content-Type': 'application/json',
},
body: JSON.stringify({ query, variables }),
})
const { data, errors } = await response.json()
if (errors) throw new Error(errors[0].message)
// Ajax API (theme-only cart operations)
fetch('/cart/add.js', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ id: variantId, quantity: 1 }),
})
Reference Files
| File | Lines | Coverage |
|---|---|---|
| liquid-syntax.md | ~600 | Tags, control flow, iteration, variables, whitespace, LiquidDoc |
| liquid-filters.md | ~870 | String, numeric, array, Shopify-specific, date, URL, colour filters |
| liquid-objects.md | ~695 | All Shopify objects: product, variant, collection, cart, customer, order, etc. |
| theme-development.md | ~1200 | File structure, JSON templates, sections, blocks, settings schema, layout |
| api-admin.md | ~595 | GraphQL queries/mutations, REST (legacy), OAuth, webhooks, rate limiting |
| api-storefront.md | ~235 | Storefront API, Ajax API, cart operations, Customer Account API |
| app-development.md | ~760 | CLI, app architecture, extensions, Polaris Web Components, deployment |
| functions.md | ~300 | Function types, Rust/JS targets, CLI workflow, Scripts migration |
| hydrogen.md | ~375 | Setup, routing, data loading, Storefront API, deployment |
| performance.md | ~605 | Images, JS, CSS, fonts, Liquid, third-party scripts, Core Web Vitals |
| debugging.md | ~650 | Liquid, JavaScript, API, cart, webhook, theme editor troubleshooting |
How to use shopify-developer on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add shopify-developer
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches shopify-developer from GitHub repository tech-leads-club/agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate shopify-developer. Access the skill through slash commands (e.g., /shopify-developer) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Accelerate Code Development
Use skill to generate boilerplate code, refactor legacy code, and write tests faster
Example
Generate React component with TypeScript types, styled-components, and comprehensive test suite in minutes
Reduce development time by 40-60% for repetitive coding tasks
Code Review Automation
Systematically review code for bugs, security issues, and style violations
Example
Analyze pull requests for common anti-patterns, suggest performance improvements, flag security vulnerabilities
Catch 70%+ of code issues before human review, improve code quality
Debug Complex Issues
Trace errors through stack traces and identify root causes faster
Example
Analyze error logs, suggest probable causes, recommend fixes with code examples
Cut debugging time by 30-50%, especially for unfamiliar codebases
Learn New Technologies
Get explanations, examples, and best practices for unfamiliar frameworks
Example
Understand Next.js app router, learn Rust ownership, grasp Kubernetes concepts with practical examples
Accelerate learning curve by 2-3x, reduce onboarding time for new tech stacks
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill installation support
- ›Basic understanding of programming concepts and version control (Git)
- ›Code editor or IDE for testing generated code (VS Code, JetBrains, etc.)
- ›Test environment separate from production for validating skill outputs
Time Estimate
15-30 minutes to install and see first useful output
Installation Steps
- 1.Install the skill using provided installation command
- 2.Verify skill is loaded in Claude Desktop (check ~/.claude/skills directory)
- 3.Test skill with simple prompt: 'Help me review this code snippet'
- 4.Gradually increase complexity: code generation → refactoring → architecture advice
- 5.Review all generated code before committing to repository
- 6.Iterate on prompts to improve output quality and relevance
- 7.Share effective prompts with team for consistency
Common Pitfalls
- ⚠Blindly trusting generated code without testing—always run tests and manual review
- ⚠Not providing enough context about your project structure and coding standards
- ⚠Expecting perfection on first generation—iteration and refinement are normal
- ⚠Sharing proprietary code or API keys in prompts—maintain confidentiality
- ⚠Over-relying on skill for critical security or business logic code
- ⚠Skipping documentation of why AI-generated code was chosen over alternatives
Best Practices▌
✓ Do
- +Always review and test AI-generated code before merging
- +Provide clear context: language, framework, coding standards, constraints
- +Use for boilerplate, tests, docs—areas where mistakes are easily caught
- +Iterate on prompts: start broad, refine with specific requirements
- +Combine AI suggestions with human judgment and domain expertise
- +Document successful prompt patterns for team reuse
- +Keep version control so you can rollback if needed
- +Use skill for learning and exploration, not production-critical features initially
✗ Don't
- −Don't commit AI code without thorough testing and review
- −Don't expose sensitive code, credentials, or proprietary algorithms
- −Don't use for security-critical code (auth, crypto, payments) without expert review
- −Don't skip peer review process just because AI generated it
- −Don't assume code follows your team's conventions—verify
- −Don't let junior developers skip learning fundamentals by relying solely on AI
- −Don't ignore compiler warnings or test failures in generated code
💡 Pro Tips
- ★Describe desired patterns explicitly: 'Use async/await, avoid callbacks'
- ★Ask for alternatives: 'Show 3 approaches to solve this, with tradeoffs'
- ★Request explanations: 'Explain why this approach is better than X'
- ★Use skill for 70% generation + 30% manual refinement for best results
- ★Build a prompt library for common patterns (API endpoints, components, tests)
- ★Pair program with AI: describe problem → review solution → iterate → refine
When to Use This▌
✓ Use When
Use coding skills for boilerplate generation, code reviews, refactoring legacy code, writing tests, learning new frameworks, and debugging non-critical issues. Best for repetitive tasks where errors are easy to catch.
✗ Avoid When
Avoid for production security features (auth, encryption, payment processing), complex business logic requiring deep domain knowledge, performance-critical algorithms, or when learning fundamentals is more valuable than speed.
Learning Path▌
- 1Start with simple tasks: generate functions, write tests, explain code
- 2Progress to code review: analyze PRs, suggest improvements
- 3Advanced: architectural decisions, refactoring strategies, performance optimization
- 4Expert: use for exploring new paradigms, researching best practices, mentoring juniors
Integration▌
- →VS Code
- →JetBrains IDEs
- →Cursor
- →GitHub Copilot
- →Git workflows
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★63 reviews- ★★★★★Carlos Menon· Dec 16, 2024
Registry listing for shopify-developer matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Jin Dixit· Dec 8, 2024
Useful defaults in shopify-developer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Amelia Rahman· Dec 4, 2024
I recommend shopify-developer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Zaid Lopez· Nov 27, 2024
shopify-developer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Daniel Zhang· Nov 23, 2024
Solid pick for teams standardizing on skills: shopify-developer is focused, and the summary matches what you get after install.
- ★★★★★Sakshi Patil· Nov 15, 2024
We added shopify-developer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Carlos Bansal· Nov 7, 2024
Keeps context tight: shopify-developer is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Anika Huang· Oct 26, 2024
shopify-developer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Anaya Farah· Oct 18, 2024
Solid pick for teams standardizing on skills: shopify-developer is focused, and the summary matches what you get after install.
- ★★★★★Mateo Ramirez· Oct 14, 2024
shopify-developer has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 63