playbooks

home / skills / omer-metin / skills-for-antigravity / shopify-apps

shopify-apps skill

/skills/shopify-apps

This skill helps you implement Shopify app patterns using Remix/React Router, App Bridge, Polaris, and GraphQL Admin API with best practices.

npx playbooks add skill omer-metin/skills-for-antigravity --skill shopify-apps

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.2 KB
---
name: shopify-apps
description: Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions. Use when "shopify app, shopify, embedded app, polaris, app bridge, shopify webhook, shopify, ecommerce, apps, embedded-apps, polaris, app-bridge" mentioned. 
---

# Shopify Apps

## Identity



## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill packages expert patterns for building production-grade Shopify apps, covering Remix/React Router, embedded apps with App Bridge, Polaris UI, webhook handling, GraphQL Admin API usage, billing, and app extensions. It provides concrete, opinionated guidance so developers follow consistent, secure, and maintainable architectures.

How this skill works

The skill encodes recommended patterns and validates designs against a reference system: pattern guidance for creation, a sharp-edges checklist for diagnosis of critical failures, and strict validations for reviews. Use it to generate code snippets, diagnose integration failures, and verify that app flows meet established constraints.

When to use it

  • Starting a new Shopify app with Remix or React Router and needing an opinionated architecture
  • Converting a public app to an embedded app using App Bridge and Polaris
  • Implementing reliable webhook handling and retry-safe background processing
  • Designing GraphQL Admin API queries and mutation flows with pagination and rate limits
  • Adding billing, recurring charges, or app extensions with correct OAuth and permissions

Best practices

  • Follow the provided patterns for auth, session storage, and embedded-app lifecycle instead of ad-hoc solutions
  • Validate every webhook handler against the sharp-edges checklist to avoid lost events and duplicated processing
  • Keep GraphQL Admin API calls batched, paginated, and rate-limit aware; prefer server-side execution where possible
  • Use Polaris components for consistent UX and App Bridge for secure embedded behavior
  • Run the validation rules before deploy: security, required scopes, and billing flow correctness

Example use cases

  • Scaffold a Remix app with pre-wired OAuth, session storage, and Polaris layout for an embedded admin experience
  • Diagnose a webhook delivery issue by applying the sharp-edges checklist and recommended retry semantics
  • Review a billing implementation to ensure correct charge creation, user prompts, and fallback handling
  • Design an app extension that surfaces admin actions using Polaris components and the Admin GraphQL API
  • Migrate a storefront integration to use server-side Admin API calls with rate-limit handling

FAQ

Which files should I consult to follow the recommendations?

Consult the provided pattern guidance for creation, the sharp-edges checklist for diagnosis of critical failures, and the validations for strict review rules.

Can I mix these patterns with other frameworks?

Yes, but preserve the core patterns for auth, webhooks, billing, and API usage; deviations must be validated against the sharp-edges and validation rules.